Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:xboot:readme [2012/01/09 07:00]
alex [1.1 Compatibility List]
en:xboot:readme [2012/03/07 04:22] (current)
alex [1.1 Compatibility List]
Line 36: Line 36:
     * atxmega256d3     * atxmega256d3
     * atxmega16a4u     * atxmega16a4u
-    * atxmega32a4u+    * atxmega32a4u ​*
     * atxmega64a3u     * atxmega64a3u
     * atxmega64a4u     * atxmega64a4u
Line 54: Line 54:
     * atmega3250     * atmega3250
     * atmega328p *     * atmega328p *
 +    * atmega329
 +    * atmega3290
 +    * atmega64
     * atmega640     * atmega640
     * atmega644     * atmega644
Line 59: Line 62:
     * atmega645     * atmega645
     * atmega6450     * atmega6450
 +    * atmega649
 +    * atmega649p
 +    * atmega6490
 +    * atmega128
     * atmega1280     * atmega1280
     * atmega1281     * atmega1281
Line 115: Line 122:
  
 In many cases, this allows you to use the AVRDude program command without having to manually reset the AVR.  Alternatively,​ the API call ''​xboot_reset()''​ will have the same effect.  ​ In many cases, this allows you to use the AVRDude program command without having to manually reset the AVR.  Alternatively,​ the API call ''​xboot_reset()''​ will have the same effect.  ​
 +
 +=== - Combine hex files ===
 +
 +To streamline programming multiple chips for a production run, the tool ''​srec_cat''​ can be used to combine the hex files. ​ Use the command as follows:
 +
 +<​code>​
 +srec_cat xboot.hex -intel main.hex -intel -o mergedfile.hex -intel
 +</​code>​
 +
 +This will concatenate the two hex files together with the proper offsets. ​ Please make sure to use xboot.hex and not xboot-boot.hex to ensure tha the correct offset is used (xboot.hex is relative to address 0 while xboot-boot.hex is relative to the start of the boot section). ​ Note that the combined hex file cannot be programmed with xboot; it is intended to be written with an ISP programmer so both xboot and the application are written in one step.  ​
  
 ===== - Configuring XBoot ===== ===== - Configuring XBoot =====
  
-XBoot is designed to be reconfigured to suit specific needs. ​ Out of the box, all of the standard features are turned on.  Turning off features and reassigning pins is easy, just pick a .conf.mk file in the .conf folder, make a copy of it, and edit the appropriate parameters. ​ Then build xboot with your parameters by running ​"make [file].conf.mk".  ​+XBoot is designed to be reconfigured to suit specific needs. ​ Out of the box, all of the standard features are turned on.  Turning off features and reassigning pins is easy, just pick a .conf.mk file in the .conf folder, make a copy of it, and edit the appropriate parameters. ​ Then build xboot with your parameters by running ​''​make [file].conf.mk''​.  ​
  
 Recommended configuration:​ Recommended configuration:​
Line 229: Line 246:
   * ''​UART_U2X''​ turns on the double-rate BRG in ATMEGA parts   * ''​UART_U2X''​ turns on the double-rate BRG in ATMEGA parts
     * Note: this only applies to ATMEGA devices     * Note: this only applies to ATMEGA devices
 +  * ''​UART_RX_PUEN''​ enables a pull-up on the UART RX pin
  
 === - USE_UART_EN_PIN === === - USE_UART_EN_PIN ===