_______ 
(  ____ \
| (    \/
| (_____ 
(_____  )
      ) |
/\____) |
\_______)
         

 _____ 
/  __ \
| /  \/
| |    
| \__/\
 \____/
       
       

         
         
  ####   
     ##  
  #####  
 ##  ##  
  #####  
         

 __        __
 \ \      / /
  \ \ /\ / / 
   \ V  V /  
    \_/\_/   
             

_________
\__   __/
   ) (   
   | |   
   | |   
   | |   
___) (___
\_______/
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
After you have compiled your firmware (you read GenBoard/Firmware/BuildFirmwareFAQ ) Uploading the firmware is really easy. You can construct a device for 1 Euro in about 5 minutes from a DB25 male connector if you have a PC with parallel port. Don't forget to save old configuration and tables with mcd and mct commands before upgrading the firmware! The human-readable ascii output of these commands can be grabbed from the serial interface. Name them etc/config.txt and etc/tables.txt. After the new code is in place, restore the config: make mtt and dump the etc/tables.mtt, etc/config.mtt files to the board with a TerminalProgram. See GenBoard/InitialConfig for initial configuration. ----- [http://megasquirtavr.sourceforge.net/manual/Basics.Install.Upgrade.html [Manual: Basics.Install.Upgrade]] --------- This is great news. For motorola you need a $65 ($49 programmer + $16 adapter for processor) equipment (theoretically you can build a whole GenBoard for that!), or send your board to some of the kind people who can program it for you (and you need to mess with a socket). http://www.futurlec.com/MotorolaProg.shtml ----- [http://megasquirtavr.sourceforge.net/manual/Basics.Install.Upgrade.html [Manual: Basics.Install.Upgrade]] ---- '''asking for help regarding boot/main.c upload''' I usually upload bootloader via avrdude (see bin/mintest.sh). However I'm not satisfied: * avrdude sends 128kbyte instead of just the upper 2 kbyte (ideas?) Tried UISP? * we'd like to store '''some information''' in flash, maybe 6 bytes '''right below the flagword''': (byte address 0x1FFF8..0x1FFFD ?) ** board version ** board assembly variant (flags: knockchip, etc...). ** maybe calibration data would also be useful (hard to fit if bootloader is kept in 2 kbytes .. maybe on a page below ). ** board serial number We'd need a small script that puts these into the boot/main.hex. Either perl or gcc could be used to achieve this. ''Script added to cvs and the bootloader is patched slightly. 12 bytes are now available that can be read through the menu interface.'' ---- If you choose to diverge from what most of us use, or over-curious here are some links: * google: atmel isp programmer parallel * http://www.cs.berkeley.edu/~awoo/smartdust/cable.html * http://bray.velenje.cx/avr/ * http://medo.fov.uni-mb.si/mapp/uTools/uisp-parport-connect.txt * http://wiredworld.tripod.com/tronics/atmel_isp.html * http://www.xs4all.nl/~sbolt/e-spider_prog.html * http://www.burnill.freeserve.co.uk/atmel.htm * http://x-dsl.hu/programmer.txt my notes on the programmer cable I built for uisp '''(no longer available?)''' * http://www.freeweb.hu/vfx/avr/index.html another description about a simple programmer Hungarian, with graphics
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.