crashmeplease
New Member
While I am not entirely new to AVRs, something that is new to me is the Boot Loader and Self Programming features...
In a nutshell I was thinking about designing a board that has several AVRs on, and to aid this I was given a tray of surface mount AVRs.. Obviously I don't really want to put several ISP headers c/w additional circuitry on the board, plus with surface mount I can't just swap out the chips when I want to update the s/w, which is when I came across the Self Programming idea..
So basically do the Self Programming features allow you to reprogram the AVRs say by the UART or SPI bus? How does this work, would I upload the new s/w via PC to a Master AVR and then send a command to initiate an update to Slave AVRs via SPI?
Looking at the App Notes it seems much more complicated than this, and I don't want to spend forever trying to understand them to find out it doesn't suit my requirements! I am given the impression that I would have to write a custom Boot Loader etc, and surprised that nothing generic exists?
TIA
In a nutshell I was thinking about designing a board that has several AVRs on, and to aid this I was given a tray of surface mount AVRs.. Obviously I don't really want to put several ISP headers c/w additional circuitry on the board, plus with surface mount I can't just swap out the chips when I want to update the s/w, which is when I came across the Self Programming idea..
So basically do the Self Programming features allow you to reprogram the AVRs say by the UART or SPI bus? How does this work, would I upload the new s/w via PC to a Master AVR and then send a command to initiate an update to Slave AVRs via SPI?
Looking at the App Notes it seems much more complicated than this, and I don't want to spend forever trying to understand them to find out it doesn't suit my requirements! I am given the impression that I would have to write a custom Boot Loader etc, and surprised that nothing generic exists?
TIA