> > Do you have an LED on your ATMega8? Was it flashing appropriately?
> No LED. The Robostix schematic says that the red LED is connected to
> /RESET, which is PC6 on the Atmega-8.
Huh. On the Robostix, the Red LED is connected to PG4.
The i2c-Bootloader uses Config-LED.h to control which pin the LED maps
to for various cpus. I set it up to map to PB4 which is MISO.
> > Finally, when you connected the scope, was the ATMega8 connected to the=
OK - so it would be useful to try it with just the pullups on the
gumstix side and no atmega.
> What are you programming your Atmega with?
My gumstix, using uisp.
> Atmel has that bizzare
> convention wherein 0 means 'programmed' and 1 means 'unprogrammed'.;
> does your programmer reverse that convention, or preserve it?
I'm using 0's and 1's exactly as they're mentioned in the datasheet.
Much less confusion than trying to translate to checked/no-checked.
And yes, 0 means programmed, 1 means unprogrammed (which is how flash works=
> using PonyProg, which reverses the convention so 'checked' =3D=3D
> programmed =3D=3D 0). I'll assume that your '1' means 'unprogrammed',
> which means 'unchecked'. PonyProg2000 doesn't allow SPIEN to be
> programmed, for reasons I dont understand, but regardless we'll see
> what happens...
PonyProg doesn't allow SPIEN to be unprogrammed (regardless of what
the UI shows). It's actually programmed, and unprogramming it would
cause ISP (In System Programming) to fail, since ISP requires the SPI
> Same thing, only this time it appears the Gumstix is pulling SCL low
> and leaving it that way. However, I can't detect any flashing on any
> pin on the Atmega-8, which would either explain the unresponsiveness,
> or imply there are two problems.
I think that the ATMega8 may be the problem in this case. If you can't
get the LED flashing, then something is wrong.
And just to clarify, you are using i2c-Boot-m8-16MHz.hex and not
Vancouver, BC, Canada