Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:xboot:readme [2012/03/02 23:26] alex [2.4 Notes for Main Application] |
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 123: | Line 123: | ||
| 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 === | + | === - 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: | 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: | ||
| Line 129: | Line 129: | ||
| <code> | <code> | ||
| srec_cat xboot.hex -intel main.hex -intel -o mergedfile.hex -intel | srec_cat xboot.hex -intel main.hex -intel -o mergedfile.hex -intel | ||
| - | <code> | + | </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. | 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. | ||
| Line 135: | Line 135: | ||
| ===== - 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 246: | 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 === | ||