Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
en:xboot:readme [2012/01/09 04:06] alex [1.1 Compatibility List] |
en:xboot:readme [2012/03/02 23:26] alex [2.4 Notes for Main Application] |
||
---|---|---|---|
Line 13: | Line 13: | ||
Currently, XBoot should work on any XMEGA processor and any ATMEGA with sufficient memory (4K boot NRWW block). The following list of processors are currently supported. An asterisk denotes the MCU has been tested and confirmed XBoot compatible. | Currently, XBoot should work on any XMEGA processor and any ATMEGA with sufficient memory (4K boot NRWW block). The following list of processors are currently supported. An asterisk denotes the MCU has been tested and confirmed XBoot compatible. | ||
- | * XMEGA | + | * XMEGA |
* atxmega16a4 * | * atxmega16a4 * | ||
* atxmega32a4 * | * atxmega32a4 * | ||
Line 20: | Line 20: | ||
* atxmega64a4 | * atxmega64a4 | ||
* atxmega128a1 * | * atxmega128a1 * | ||
- | * atxmega128a3 | + | * atxmega128a3 * |
* atxmega128a4 | * atxmega128a4 | ||
* atxmega192a1 | * atxmega192a1 | ||
Line 49: | Line 49: | ||
* atxmega128b3 | * atxmega128b3 | ||
* ATMEGA | * ATMEGA | ||
- | * atmega328p * | ||
* atmega324 | * atmega324 | ||
* atmega324pa | * atmega324pa | ||
+ | * atmega325 | ||
+ | * atmega3250 | ||
+ | * atmega328p * | ||
+ | * atmega329 | ||
+ | * atmega3290 | ||
+ | * atmega64 | ||
+ | * atmega640 | ||
* atmega644 | * atmega644 | ||
* atmega644pa | * atmega644pa | ||
+ | * atmega645 | ||
+ | * atmega6450 | ||
+ | * atmega649 | ||
+ | * atmega649p | ||
+ | * atmega6490 | ||
+ | * atmega128 | ||
+ | * atmega1280 | ||
+ | * atmega1281 | ||
* atmega1284p * | * atmega1284p * | ||
+ | * atmega2560 | ||
+ | * atmega2561 | ||
===== - Using XBoot ===== | ===== - Using XBoot ===== | ||
Line 106: | 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 ===== |