Project

General

Profile

Enhancement #323

Wireless bootloading

Added by Kevin Woo about 14 years ago. Updated over 13 years ago.

Status:
Fixed
Priority:
Tabled
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

90%


History

#1 Updated by Kevin Woo about 14 years ago

  • Status changed from New to Feedback
  • Assignee deleted (Unassigned Ticket -)

#2 Updated by Rich Hong about 14 years ago

  • Category set to 29

#3 Updated by Kevin Woo almost 14 years ago

The sparkfun method uses a custommized windows program to do it. They could not get it to work with avrdude. Also, they use the RTS/DIO pin to reset the avr in order to put it into bootloader mode. According to initial research done by Chris, our SBees have a firmware bg that disables RTS/CTS.

#4 Updated by Ryan Cahoon over 13 years ago

  • Status changed from Feedback to Fixed
  • Assignee set to Ryan Cahoon
  • % Done changed from 0 to 90

Prototype code added in SVN revision 1428. New bootloader code supports both wired and wireless programming. Requires use of new loader client instead of avrdude, but code can be compiled cross-platform. No hardware changes are required, but AVRs requires an avrisp or similar to flash new bootloaders.

Code download works on all programs tested thus far, but "guinea-pig" testers should probably use the new loader for a while before it could become the default loader.

Further ideas:
--Create a hook on a special command in libwireless which sets the robot into program mode, so no physical contact with the robots is required to program them
--Allow robots to program each other, so code updates could be pushed to a single robot, which could then recursively push it to others

Also available in: Atom PDF