This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
using_pic18f4620 [2007/03/30 11:21] stryd_one Warning about extended banks |
using_pic18f4620 [2011/11/18 12:14] (current) lpdunwell removed spam |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Using the PIC18F4620 or PIC18F4520 ====== | ====== Using the PIC18F4620 or PIC18F4520 ====== | ||
+ | |||
+ | FIXME This is really outdated!!! | ||
Historically, MIOS was developed to run on a core module stuffed with a PIC18F452. Recently, the PIC18F4620 has become available. It is near code-compatible with the 452, but features a significant increase in RAM/EEPROM/Codespace. See [[mios_pic18f4620|the PIC18F4620 page]] for details. | Historically, MIOS was developed to run on a core module stuffed with a PIC18F452. Recently, the PIC18F4620 has become available. It is near code-compatible with the 452, but features a significant increase in RAM/EEPROM/Codespace. See [[mios_pic18f4620|the PIC18F4620 page]] for details. | ||
Line 335: | Line 337: | ||
You may create as many or as few sections as you require for your application. | You may create as many or as few sections as you require for your application. | ||
+ | |||
Line 349: | Line 352: | ||
unsigned char MIDI_Table[512]; // Declare the array named 'MIDI_Table', and now it will be stored in 'b512' | unsigned char MIDI_Table[512]; // Declare the array named 'MIDI_Table', and now it will be stored in 'b512' | ||
</code> | </code> | ||
+ | |||
+ | **It is recommended to avoid this wherever possible.** Allow the compiler to allocate the memory wherever possible! | ||
+ | |||
+ | Check [[http://www.midibox.org/forum/index.php?topic=8934.0|An answer to the extended databanks problem]] for more info!!!!!!!!!! | ||
\\ | \\ |