by Miamicanes » Sat Jan 27, 2007 2:51 am
by Miamicanes
Sat Jan 27, 2007 2:51 am
Hmmm. Is it possible to program via SPI without destroying the bootloader? Or at the very least, can the bootloader be ripped via SPI for later restoration (say, for motion-data editing)?
I've been using AVRs for about a year and a half, but I've never actually dealt with a Mega128(*), or tried to coexist with a bootloader. I've always just configured AVR studio to connect to my AVRISP (or more recently, my Dragon), wipe the chip, and auto-upload the .hex and .eep files.
Does Robotis provide any command-line flash utils compatible with their bootloader? I know it's somehow possible to configure AVR studio to use thirdparty commandline utils (like Ponyprog) to upload, so if Robotis had something comparable, the same stunt would probably work with the CM5. Then again, if I can use SPI without killing the bootloader, I'd be pretty happy, too... it'd be a pain to have to figure out how to get the wires inside... but I have to admit, the bootloader upload feels like it takes an eternity to connect and upload. I miss having the whole ISP process run so fast, it's done before I even let go of the mouse button. On the other hand, with a serial bootloader, I could theoretically make the whole programming link wireless and dispense with the cable. Decisions, decisions...
(*)Tiny13, Tiny25, Tiny2313, Mega162, Mega32 (my first robot, w/barello.net AVR Controller 1.1), Mega168, and (sort of) Mega2561
Hmmm. Is it possible to program via SPI without destroying the bootloader? Or at the very least, can the bootloader be ripped via SPI for later restoration (say, for motion-data editing)?
I've been using AVRs for about a year and a half, but I've never actually dealt with a Mega128(*), or tried to coexist with a bootloader. I've always just configured AVR studio to connect to my AVRISP (or more recently, my Dragon), wipe the chip, and auto-upload the .hex and .eep files.
Does Robotis provide any command-line flash utils compatible with their bootloader? I know it's somehow possible to configure AVR studio to use thirdparty commandline utils (like Ponyprog) to upload, so if Robotis had something comparable, the same stunt would probably work with the CM5. Then again, if I can use SPI without killing the bootloader, I'd be pretty happy, too... it'd be a pain to have to figure out how to get the wires inside... but I have to admit, the bootloader upload feels like it takes an eternity to connect and upload. I miss having the whole ISP process run so fast, it's done before I even let go of the mouse button. On the other hand, with a serial bootloader, I could theoretically make the whole programming link wireless and dispense with the cable. Decisions, decisions...
(*)Tiny13, Tiny25, Tiny2313, Mega162, Mega32 (my first robot, w/barello.net AVR Controller 1.1), Mega168, and (sort of) Mega2561