Incompatible Firmware revision

Nash Weber

The Javelin Stamp that I'm using has stopped communicating with the Javelin Stamp IDE. The Javelin itself still works, and is able to run the last program that I sent to it, but will no longer communicate with the IDE.

I've tried to contact tech support and after two days they have not been able to help me at all, I'm hoping that someone has seen this error before. I've attached a screen shot of the error

Here's the error I get (same error from all three available versions of the Javelin IDE: 2.00, 2.0.1, and 2.0.3)
Error IDE-0052: Incompatible firmware revision ($%x).
Description: The firmware in the Javelin is not compatible with this version of the IDE.
Solution: Get the correct version of the IDE to work with the firmware in the Javelin you have.


Here's my setup:
-Javelin Stamp
-Parallax Development Kit for the Javelin
-Standard power supply (7.5V 1000mA) that ships with the development kit
-NO external circuitry, for troubleshooting purposes its just the Javelin sitting on the dev board
-Javelin Stamp IDE version 2.0.3, although i've tried both of the older versions
Windows XP SP2 (automatic Windows updates is disabled, OS hasn't changed in weeks)

What I've already tried:
- Resetting the Javelin
- Rebooting the computer
- Uninstalling and reinstalling the Javelin Stamp IDE (all versions, currently on 2.0.3)
- Re-seating the Javelin chip on the Dev Board, verified every pin is making contact and that chip is not installed upside-down.
- Tested with DMM that the power supply is indeed outputting about 7.5 V (exactly 7.65V)


Has anyone experienced or heard of it problems with the firmware? Is it possible to replace the firmware in the Javelin?

Thanks,

-Nash

Peter Verkaik

Do you get a stable 5V at pin 21 (VDD)?
If not, the regulator circuitry on the javelin module may be faulty.
In that case try inserting the javelin without pin24 into the socket,
so you can power the module directly with 5V via pin 21.
You can use the demoboard 5V.

regards peter

Nash Weber

Yes, I'm getting a stable 4.94 volts on pin 21 (VDD).

Nash Weber

I've added a new attachment, it's the output of the Project-->Identify option...it gives a little more info on the problem.

-Nash

Peter Verkaik

Check your serial cable and pc serial port.
The reason is because it looks the IDE receives
something (wrong version number) but no echo.
If your pc serial port is unable to transmit,
then the received version would be invalid, because
the javelin needs its pin SIN idle state (which is connected
to the pc serial port TX line) to·transmit.

regards peter

Nash Weber

Specifically what aspects of the cable and port should I check? I'm using Parallax's USB to serial adapter (which has worked without problems for months).

Peter Verkaik

The serial cable uses pins 2 (RX), 3 (TX), 4 (DTR),·5 (GND), 6 (DSR)·and 7 (RTS).
6 and 7 are ok as you get the loopback.
Pin 3 is the pc tx pin, and this line could be damaged.
Just check the cable with your multimeter.
If you measure a large resistance between identical pins on both ends
of the cable,·the wire between those pins is damaged.
If you measure a small resistance between a pin on one side and any other
pin than the identical pin, you have a short between pins in the cable.

To test the serial port just temporarily connect a 1k resistor
between pins 2 and 3 and open hyperterminal for that com port.
With local echo disabled, anything you type then must appear
in the hyperterminal window.
If you do not get the typed characters into hyperterminal
then your usb2ser device is defect.

If it all checks out ok we know the serial port and the
connection to the javelin board are ok.

regards peter
·

Nash Weber

Thanks for taking the time to help with this, Peter! While testing each of the pins of Javelin, I found the problem. The Javelin was sitting on an extra IC socket so that it could easily be moved back and forth to a breadboard, and the IC socket was flakey. The plastic was bowed and it caused one or two of the pins not to make contact correctly. I replaced the IC socket with a new one and all is well now, thanks again!

-Nash