MIDIbox

User Tools

Site Tools

Trace:
mios_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
Next revisionBoth sides next revision
mios_pic18f4620 [2008/03/14 08:16] – tobamaimios_pic18f4620 [2008/12/01 07:16] – Durisian
Line 10: Line 10:
 The PIC18F4620 is almost software compatible to existing MIOS applications. There is a special MIOS version which needs to be uploaded, the major differences are different memory limit checks (e.g. code upload to addresses >= 0x8000 are possible). The PIC18F4620 is almost software compatible to existing MIOS applications. There is a special MIOS version which needs to be uploaded, the major differences are different memory limit checks (e.g. code upload to addresses >= 0x8000 are possible).
  
-For information on developing or converting applications to use the PIC18F4620, please see [[application_development#using_the_pic18f4620_or_pic18f4520|the page on Application Development]] 
  
 ====== FAQ ====== ====== FAQ ======
Line 21: Line 20:
  
 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. 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 have seen small changes 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+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
  
  
mios_pic18f4620.txt · Last modified: 2011/09/17 17:09 by dougster