MIDIbox

User Tools

Site Tools

Trace: • openpad-codeblock • using_pic18f4620 • tm5-codeblock • daw-encoder-display
using_pic18f4620

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
using_pic18f4620 [2007/03/30 11:29] – Added warning re: #pragma udata stryd_oneusing_pic18f4620 [2011/11/18 12:14] (current) – removed spam lpdunwell
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 352: Line 354:
  
 **It is recommended to avoid this wherever possible.** Allow the compiler to allocate the memory wherever possible! **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!!!!!!!!!!
  
 \\ \\
using_pic18f4620.1175254181.txt.gz · Last modified: 2007/04/09 05:01 (external edit)