pcmhacking.net

Sure here bin for 255937

Without looking too closely, none of the checksums are even close.
If that's what you're reading from the chip then your read isn't working properly.

festy wrote:So yours isn't one of those wireless programmers then huh?

Are you sure it's reading ok?
post a bin if you're not sure.

@The1: If the ICMP header is wrong, I guess the chip won't respond to pings?

Do a tracert on it? or ARP/DHCP lookup.

yeh that bin doesn't look right to me either, there's no consistency.

Thinking about it, you must be pretty close.
The byte patterns look ok and the structure is what you'd expect, just the bytes themselves are wrong
It looks almost like a timing issue - it's not that you're missing the first or last bit from each word, because then your nibbles would checksum ok.
Are you using a USB->serial adapter? Is there any options in ponyprog to slow it down a bit?

You're bin ends with these bytes:
3b 88 8d e4 46 a4
but should be more like:
5b a4 65 9a 13 ec

Think your on the right track re timing.

We just tried a different laptop and got different numbers.

I checked the code and yes we should be getting 5BA4 659A 13EC

Not sure how to go about slowing down or checking the timing on this program, we are using com1 serial.

Do you have a suggestion on what program we can use to check the com1 timing

Google tells me you can slow down the timing from ponyprog.ini:

SPIBusSpeed=VERYSLOW
MicroWireBusSpeed=VERYSLOW
I'm not sure which of the two settings would affect these chips, they're kind-of microwire, kind-of spi so just change both

See http://www.lancos.com/e2p/ponyprog2000.html#s2.6.2 for more detail.

have you got it set correctly to si prog api?

Really appreciate all your help.. but still no luck.

I am going to have a beer and then re wire a new socket on the icsp socket.

Will let you know.

The1 wrote:have you got it set correctly to si prog api?

I have tried all 3 si prog api and siprog i/o and JDM api

Just rewired it re checked all the connections and still no joy.

We are now getting the same wrong set of numbers on both laptops.

Have tied loading a good .bin file (from this list) onto a blank chip however that just gives us write failure .

Its got me...