Differences

This shows you the differences between two versions of the page.

--- mcan [2018/08/03 12:46] – [Enhanced Mode] antichambre
+++ mcan [2018/08/03 12:53] (current) – [A basic example] antichambre
@@ Line 256: / Line 256: @@
 **But before any MIDI features we need the MIOS32 driver for that CAN controller...**
 ----
-===== MIOS32_CAN implementation =====
+===== MIOS32_CAN =====
 ==== CAN controller as a generic peripheral in MIOS32. ====
 MIOS32_CAN feature is only compilable under STM32F4.\\
@@ Line 395: / Line 395: @@
 ----
-===== MIOS32_CAN_MIDI implementation =====
+===== MIOS32_CAN_MIDI =====
 ==== Package and Packet ====
 Like the others MIDI peripherals, we need a bridge between our new CAN features(mios32_can.c/h) and the MIDI process[[http://www.midibox.org/mios32/manual/group___m_i_o_s32___m_i_d_i.html|(mios32_midi.c/h)]]\\
@@ Line 458: / Line 458: @@
 ----
-===== Basic Mode =====
+===== MCAN Basic Mode =====
 This is the default mode, the funny one, just interconnect some Cores in parallel with J18 and they are able to communicate in MIDI. Easy.\\
 In this mode:
@@ Line 565: / Line 565: @@
 ==== A basic example ====
-For this example we will use 2 Core to get an 8 MIDI ports link between 2 different computers.\\
+For this example we will use 2 Cores to get an 8 MIDI ports link between 2 different computers.\\
 \\
 <WRAP group>
@@ Line 616: / Line 616: @@
   }
 }
-</code>
+</code>\\
+\\
+**Done! Your App with the MCAN(Basic) is ready to upload and is the same for both Cores. 8-) **
+\\
+\\
+\\
+----
 ===== MCAN Enhanced Mode =====
 <WRAP center round todo 60%>