Differences

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

--- mios_pic18f4620 [2008/03/06 19:32]
admin change info about EUSART bug
+++ mios_pic18f4620 [2011/09/17 17:09] (current)
dougster
@@ Line 20: / Line 20: @@
 ===== Can I run an old PIC18F452 Application on a PIC18F4620?=====
-Yes, all applications are binary compatible, which means, that you even don't need to build a new .hex file, just upload the precompiled code.
+Yes, all applications are binary compatible, which means, that you don't even need to build a new .hex file, just upload the precompiled code.
-Only the Bootloader and MIOS itself got some small adaptions in order to allow to program the upper flash area, and the extented EEPROM range. Therefore you will find special versions in the MIOS update package within the pic18f4620/ directory
+The Bootloader and MIOS have been changed slightly to allow programs to use the upper flash area and extended EEPROM range. Special versions of the MIOS update package are found in the pic18f4620/ directory
-=====Do I really need to build a MBHP_IIC_MIDI module as workaround for the EUSART bug?=====
-It depends on the application. The EUSART based MIDI Out port of the core module will mostly work, you are even able to upload code without failures. The error (inserted 0x00 bytes which violate the MIDI protocol) only happens very rarely under special circumstances. It can only happen, when MIDI data is also received at the MIDI In port at the same time at the wrong moment (in simple words, details are documented in the errata sheet). As a result, you could notice a hanging note, or a wrong controller once or two times a hour when you are using the MIDIbox.
-Accordingly, so long the MIDIbox application only receives MIDI data, or so long it only sends MIDI data while nothing is received, the bug will never appear, and therefore a MBHP_IIC_MIDI module is not required in this case.
-//(removed part about MIDIbox SID examples, as it has been decided to use a [[mios_pic18f4685|PIC18F4685]])//
-Remaining Example:
-MIDIbox SEQ: when used as standalone sequencer, no external MIDI keyboard or MIDI clock source connected to the MIDI In, a MBHP_IIC_MIDI module is not required.
-In all other configurations one or up to 4 MBHP_IIC_MIDI modules are recommented. Note that MIDIbox SEQ allows to output MIDI events on different MBHP_IIC_MIDI ports, this is nice for reducing the MIDI latency
-=====Do I need to built a complete MBHP_IIC_MIDI module with MIDI In and Out port?=====
-No, you only need the reduced version with MIDI Out port only.
-The MIDI In port is *not* natively supported by most applications, currently it is only used by the MIDI router project. Adding support for multiple MIDI Ins is not so trivial, since it affects the performance of the application - therefore it cannot be expected that it will be supported by many applications in future, only by special ones.
-Info for Newbies: if you are unsure, how a "MIDI Out only" version looks like when you are using the MBHP_IIC_MIDI PCB, just stuff all components, and left out the optocoupler and the MIDI In LED.
-=====How do I upload MIOS and application code via the MBHP_IIC_MIDI interface?=====
-Proposal for Beginners/Electronic Newbies:
-  * buy a preprogrammed PIC18F4620 from SmashTV or Mike with PIC ID 0000000000000000
-  * build the core module and test the MIDI In/Out of the board
-  * upload the PIC18F4620 version of MIOS via the MIDI Out port of the Core module
-  * build a MBHP_IIC_MIDI module and test it like explained at the MBHP_IIC_MIDI page
-  * select the ID 10 (both jumpers stuffed)
-  * upload the iic_midi_10.hex binary of the change_id package, this will change the PIC ID to 0000000000100000
-  * now the MIDI out stream is redirected to the MIDI Out port of the MBHP_IIC_MIDI module, you don't need to use the MIDI Out port of the core module anymore (even for code uploads it's not required anymore)
-Proposal for Experts:
-  * buy a preprogrammed PIC18F4620 from SmashTV or Mike with PIC ID 0000000000100000, or burn the bootloader by yourself into the chip with this ID
-  * build the Core + MBHP_IIC_MIDI module
-  * the MBHP_IIC_MIDI module should send the upload request each 2 seconds so long MIOS is not installed
-  * upload the PIC18F4620 version of MIOS via the MIDI Out of the MBHP_IIC_MIDI module
-Note that it is possible to change the PIC ID, or to upload MIOS without the MIDI Out Port, when the "no feedback from core" option is selected in MIOS Studio. This method is not recommented, as erroneous uploads won't be notified, but it helps in "emergency cases", e.g. when you wrongly uploaded the main.hex file of the change_id application and you are not able to open the case of your MIDIbox quickly in order to get access to the core based MIDI Out port.
-=====Can I use one or more BankSticks together with the MBHP_IIC_MIDI module(s)?=====
-Yes, on an IIC bus all SCL/SDA (clock/data) lines are connected together, each device must have an unique address, so that the IIC Master (the core module) can perform read/write transactions on a specific IIC Slave. On the MBHP_IIC_MIDI module the address 10/12/14/16 (hexadecimal) is selected via jumpers, on IIC EEPROMs (BankSticks) the address 50/52/54/56/58/5A/5C/5E (hexadecimal) is selected with the Chip Select inputs Pin 1, 2 and 3.
-As you can see, there is no address conflict between MBHP_IIC_MIDI modules and BankSticks
 =====Can I use my old JDM burner to burn the bootloader onto a PIC18F4620?=====

MIDIbox

User Tools

Site Tools

Differences

Page Tools