> Now I've already successfully set-up a few robostix/gumstix combinations for
> i2c use already, so I know I have followed all the documented steps.
> However, I'm inclined to believe my robostix is defective because the red
> LED doesn't work (when I load the flashing sequence LED program, they all
> light up except the red!)
The very first batch of robostix had red LEDs that were installed
backwards, but I haven't seen this since then. It could be a defective
> Does reflashing the robostix with "i2c-Boot-m128-16MHz.hex" ensure that its
> i2c address is set to 0x0b? Or do I have to do something else to correct a
> potentially corrupted thing that no amount of reflashing is going to fix?
It depends on the value of the EESAVE fuse. If the EESAVE fuse is
programmed (i.e. set to zero) then the contents of EEPROM are
preserved when reflashing, otherwise they arent't.
You should find an eeprom-init.hex file in the robostix/i2c-Bootloader
directory. You can program that by using (I didn't actually test the
following, but it should work):
uisp --segment=eeprom --upload if=eeprom-init.hex
This should cause the i2c address to be reset to 0x0b
Vancouver, BC, Canada