Atmel Bootloader Pc Tool
Atmel AVR2054: Serial Bootloader User Guide[APPLICATION NOTE] 8390C−WIRELESS−06/2013 2 Table of Contents. If the host is not Atmel PC Bootloader tool. 'PC' Tool for bootloaders. Datacolor support. How to write the 'PC Tool' portion of the software. Then you can choose the 'big micro' or a PC to talk to the AVR bootloader.
For a new project, I need to use a bootloader in my AVR. While I have not done that before, there appears to be a ton of information available online (including what appears to be a good FAQ by Brad Schick over in the Tutorials forum). I am fairly sure that through those resources, as well as asking potentially dumb questions here, I will either be able to write my own, or find one already written that will work for me. What concerns me more is the other end - the software that communicates with the AVR. My AVR is going to be a smaller MCU in a larger system, with larger processors. My objective is to have the AVR be field reprogrammable via one of the other processors.
I have not found a ton of information available regarding this process (i.e., how to write the 'PC Tool' portion of the software. How difficult is this? Is the source code of the 'PC Tool' available as a reference? Are there any good resources out there that I have missed? Finally, some AVR App notes out there are really old (and no longer really all that applicable). AVR2054 appears to still be maintained. Is it still relevant, or should I find a more modern reference?
The advantage you have here over a 'PC Tool' is that the link between your big and small micro is fixed and they only need to agree to pass the Sata using a single protocol. The majority of most PC Tools such as avrdude is that they are catering for 10 different communication interfaces and 50 different programming protocols.
So if you look at the source of a typical PC Tool you will be completely overwhelmed. When you think about it, at the end of the day all that has to pass from the big micro to the AVR is a base address for where the data should be placed in flash then the data itself. Now a number of 'protocols' have been developed for passing these kind of things. You'll read about AVR109 for example but even that may be more than you need. I suppose the advantage of using AVR109 or STK500V2 or whatever is that you can easily find ready made bootloader code for the AVR end but that's going to be built on the assumption you are using UART. Perhaps you plan to connect the micros using SPI or I2C or something else?
If so the ready made bootloader might need small modifications. All that then remains is to implement AVR109 or STK500V2 or whatever on the 'big micro'. If you only use a subset of their functionality then it's probably easiest just to implement from scratch using the relevant Atmel application note. AVR109 for example basically starts each 'command' with a single ASCII letter to say what's coming next. It's easy to understand and implement. If you do choose AVR109 then consider Optiboot from the Arduino world for the AVR end as it's undoubtedly the most used and most widely supported AVR109 bootloader in the world.
I would definitely stick with avrdude. It works on Windoze, Linux, Mac. I would also stick with an established protocol. Stk500v1, stk500v2, AVR109. Yes, you can devise something 'better' or more 'efficient'. At the risk of having to write the appropriate custom software. And your clients will not be happy when their new PC can't run your custom software when your company has ceased trading.
Let's face it. If your custom bootloader takes 9 seconds when the 'traditional' protocols take 10 seconds, will your clients really care? Optiboot uses 'stk500v1' protocol.
AVR ATmega Xmega Bootloader Source Code with PC GUI Tool. AVR ATmega Xmega Bootloader Source Code with PC GUI Tool Description: chip45boot2 is a professional bootloader for Atmel AVR ATmega and Xmega micro controllers with Intel hex file support and automatic baudrate adjustment. See infosheet for details. It is available as and commercial source code. Features chip45boot2 provides the following features:. direct input of Intel Hex files.
automatic baud rate adjustment. XON/XOFF protocol. Flash and EEPROM programming. byte-wise writing and reading of SRAM memory. byte-wise writing and reading of EEPROM memory.
2k bootblock size. graphical windows user interface chip45boot2 GUI for convenient programming from PC! The bootloader automatically adjusts at start to the hosts baudrate, so that it is not necessary to recompile the bootloader to a particular MCU clock. There exist for different controller types and probably different UARTs, which work independently from MCU clock. Further Information. License The precompiled hexfiles may be used for either commercial or non-commercial projects and products without limitations.
In case you want to extend the bootloader by own functions or make changes to it, you can buy the source code (as AVR studio project for WinAVR) here. PC Software The chip45boot2 GUI is a comfortable PC/Windows application with a graphical user interface for the bootloader, which simplifies flash and eeprom programming over a COM port. Similar to the precompiled bootloader hexfiles, the chip45boot2 GUI can be downloaded for free. If you want to use the PC software for a customer project, we can build a customized version for you (your company logo and name instead of chip45). Please contact us in case this is of interest for you. Scope of Delivery The most recent version available of the chip45boot2 source code will be send as ZIP file by email. No shipping charges are incurred.
Custom Boot Loader Pc
Downloads.