Author Topic: IFR1200 CPU Card Corrupted -Dead --Need Help (Read 4113 times)

try2fix · « **Reply #25 on:** June 25, 2019, 05:16:18 am »

boy I must be on another setting or something as I looked and I cannot see any repeats. I am useing Hex Editor but just learning as I go, sorry for my errors

TheSteve · « **Reply #26 on:** June 25, 2019, 05:30:12 am »

The last file has valid data in it. Although it isn't even half full - hopefully that is just because they overspec'd the eprom size required.

try2fix · « **Reply #27 on:** June 25, 2019, 05:39:11 am »

Does this last file look like there is something that would be repeating in its code so it would not work as there is no life out of the cpu card when I put it in. I have no other cpu cards like this one so I have no way of switching out the rom with anouther at this time- I did sw out the procesor (N80C188) and proved that it is working.

fzabkar · « **Reply #28 on:** June 25, 2019, 06:00:01 am »

The latest dump looks OK, although I haven't worked out the checksum algorithm. The easiest way to see the differences is to ZIP each file. Your bad dumps will produce very small ZIPs due to their mostly redundant content.

Your good dump has a lot of text strings before 0x30000. The first two bytes (EB 02) decode to an x86 JMP 0104 instruction, so it could be that the CPU is an Intel chip of some sort. I suspect that bytes 2 and 3 may be the checksum (since the JMP instruction jumps around them).

That said, I can't see anything in the dumps that would enable me to suggest where to start fault finding your Willem programmer. Perhaps someone else can see something.

Edit: I posted my reply before I saw your last post.

try2fix · « **Reply #29 on:** June 25, 2019, 04:59:53 pm »

Thanks, the cpu is N80C188 and on the rom chip [M27C4001] is a labeled "F080-2200-100 v1.12 U3" I am thinking maybe the correct check sum should be F080 and it is version 1.12 but the other who knows.
Please if someone has some of these files can you send the hex so it can be compared to know what is corrupt in mine, I have about 4 or 5 different versions of the files but I have to now figure out what is wrong with my reader as it reads out wrong values.

try2fix · « **Reply #30 on:** June 25, 2019, 10:54:04 pm »

Good news I got my eprom reader fixed now I just have to figure out what pins it took out of the 2 27c512 chips I read --so I managed to copy and write to a blank 27c512 of a working version 3.0 - and it works on the ifr now...so here is the file of a working unit, if any one can determine what got corrupted on the version 7.1 chips it would greatly help me to get this working again.
The 7.1 version is what I am trying to get working as it has all my tracking options-this is on 2 chips.
The 6.1 version & 7.1 Version some how got corrupted and will not work after I removed them from a working ifr1200s and read them.
The 1.12 version is from a ifr super s with all the options but it to is corrupted.

So I took the version 6.1 chip erased it and programed it with all zeros as I thought if there is a problem with the chip some should not program..well all programed perfect, so I am really confused how the eprom could have got corrupted in me reading it as it sure seems to work fine now -I'm sure you guys will let me know where I error
Thanks for all the help.

CJay · « **Reply #31 on:** June 26, 2019, 06:24:15 am »

Quote from: try2fix on June 25, 2019, 10:54:04 pm

Good news I got my eprom reader fixed now I just have to figure out what pins it took out of the 2 27c512 chips I read --so I managed to copy and write to a blank 27c512 of a working version 3.0 - and it works on the ifr now...so here is the file of a working unit, if any one can determine what got corrupted on the version 7.1 chips it would greatly help me to get this working again.
The 7.1 version is what I am trying to get working as it has all my tracking options-this is on 2 chips.
The 6.1 version & 7.1 Version some how got corrupted and will not work after I removed them from a working ifr1200s and read them.
The 1.12 version is from a ifr super s with all the options but it to is corrupted.

So I took the version 6.1 chip erased it and programed it with all zeros as I thought if there is a problem with the chip some should not program..well all programed perfect, so I am really confused how the eprom could have got corrupted in me reading it as it sure seems to work fine now -I'm sure you guys will let me know where I error
Thanks for all the help.

What was the problem with the EPROM programmer that caused it to read incorrectly?

try2fix · « **Reply #32 on:** June 26, 2019, 07:02:36 pm »

Quote from: CJay on June 26, 2019, 06:24:15 am

Quote from: try2fix on June 25, 2019, 10:54:04 pm
Good news I got my eprom reader fixed now I just have to figure out what pins it took out of the 2 27c512 chips I read --so I managed to copy and write to a blank 27c512 of a working version 3.0 - and it works on the ifr now...so here is the file of a working unit, if any one can determine what got corrupted on the version 7.1 chips it would greatly help me to get this working again.
The 7.1 version is what I am trying to get working as it has all my tracking options-this is on 2 chips.
The 6.1 version & 7.1 Version some how got corrupted and will not work after I removed them from a working ifr1200s and read them.
The 1.12 version is from a ifr super s with all the options but it to is corrupted.

So I took the version 6.1 chip erased it and programed it with all zeros as I thought if there is a problem with the chip some should not program..well all programed perfect, so I am really confused how the eprom could have got corrupted in me reading it as it sure seems to work fine now -I'm sure you guys will let me know where I error
Thanks for all the help.

What was the problem with the EPROM programmer that caused it to read incorrectly?

there was a jumper in the wrong position, I can't figure out how it corrupted the rom, but that being said I am now looking for some rom files if anyone has ver6.1 and 7.1 that would be a great help

fzabkar · « **Reply #33 on:** June 27, 2019, 07:02:02 am »

The file which looks OK, but isn't OK, probably has bit or byte errors. Did you set the Vcc to 3.6V or 5V?

try2fix · « **Reply #34 on:** June 27, 2019, 04:17:23 pm »

"Did you set the Vcc to 3.6V or 5V? "
5v
So I copied and programed a few chips to test and all is working on the programmer now

try2fix · « **Reply #35 on:** June 29, 2019, 05:08:48 pm »

Okay so maybe some of you that understand ziping files to gether to find common trends might be able to tell me what the common diff is on these files that work vs the corrupted ones that do not work.There are 2 eprom chips on the board U3 & U4. Still trying to figure all this stuff out, Thanks

fzabkar · « **Reply #36 on:** June 29, 2019, 10:46:01 pm »

Are these checksums printed on the EPROM's original label?

try2fix · « **Reply #37 on:** June 30, 2019, 07:51:23 pm »

Are these checksums printed on the EPROM's original label?

Yes, That is correct

TheSteve · « **Reply #38 on:** June 30, 2019, 08:11:42 pm »

If you perform a checksum 16 on the "working" files the digest value will match what is on the label. I verified both files with Hex Workshop.

try2fix · « **Reply #39 on:** July 01, 2019, 12:01:31 am »

okay, thanks. So the corrupted files have no pattern in regards to the wking ones -just trying to figure out how to fix a bad file without knowing what it is/was originally

fzabkar · « **Reply #40 on:** July 01, 2019, 02:36:44 am »

Launch HxD and open a non-working hex dump.

Got to offset 0 and drag your cursor over the 0x100 bytes of data between
offsets 0 - FF. Those 0x100 bytes should be highlighted.

At the bottom of the screen you should see ...

Now go to Search -> Find, select Datatype -> Hex-Values, place your cursor
in the "Search for" box and then type Ctrl-V. Then click OK.

Hit the F3 key to search for this block of data and keep hitting the F3 key
to repeat the search. Now do you see the problem?

To compute the checksum for your hex dump, select Analysis -> Checksums ->
Checksum-16 -> Entire File.

try2fix · « **Reply #41 on:** July 01, 2019, 04:18:27 pm »

okay, well that sure helps when you walk me trough the steps, thanks

try2fix · « **Reply #42 on:** July 04, 2019, 04:38:12 pm »

I have IFR1200 Super S with corrupted eprom in the cpu card, looking for someone with the hex file to help me get this back up and running

try2fix · « **Reply #43 on:** July 09, 2019, 04:15:39 pm »

I been asked for pics of what the dif is on the new IFR1200s to super s vs the older---well this is some what I have found -see word doc for the pics
THe Hi loop module is dif - I do not have picture
The CPU board has what I have seen 2 types for the 1200s and a 3rd for the super s -see word doc for pics on the later 2
The Rx Audio PC Board & the Interface board are dif-see word doc for pics

-I am sure there are a lot more of you out there that know a whole lot more than me, but this is what I have found for those of you that wanted pics, have a great day.
I am still looking for anyone that knows what is wrong with my super s file ---look at it and let me know , thanks


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: IFR1200 CPU Card Corrupted -Dead --Need Help (Read 4113 times)

Share me