USART bootloader, documentation?

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I need an USART bootloader for my project. There is one in the newest software framework, but I only found release_note.txt. That file referst to "AVR UC3 UART Bootloader user guide", but where is that?

I think that project would a very good start, but the user guide would be very nice - especially since it looks I need to adapt it a little.

Please?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The uart bootloader doc is not published yet. The protocol is similar to the one in the USB DFU user guide.
You'll have to use FLIP/Batchisp to connect to the uart bootloader.

-sma

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

sma wrote:
The uart bootloader doc is not published yet.

Any idea if that's coming in days or weeks? In other words, am I better of spending time in reading the code and figuring it out or waiting a bit and getting the info from the sources? Also, if there are any unofficial notes that would be helpful in pushing me to right directions, I would greatly appreciate it.
sma wrote:

The protocol is similar to the one in the USB DFU user guide. You'll have to use FLIP/Batchisp to connect to the uart bootloader.

-sma


As I suspected:-). this application can 8and needs to be) be much simpler. I'm thinking of something like "activate bootloader, send a page, program a page, repeat when done." I already have Kermit implemented (don't ask...) so something similar would do here.

Cheers,

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I need to customise a bootloader that allows a new image to be used on the micro that is stored on an external dataflash module (AT45DB series)...

Can anyone be of assistance with this? I have read the DFU documentation and it is a bit over my head as to what needs to be done, how, and where to start.

Thank you in advance.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

A bit late, but I did return to the subject. Hope this helps.

(Edit: a correction to the instructions!)

Attachment(s):