help reading ird and bk atmega au card

[hershey]

hi all,

i use funprogger (a parralel port programmer) and funprom software to programme my card. I have read the external eeprom that is already on the card which saves it as a .hex file. When i try and open the hex file with ATMega_IRD_BoxKey_Reader it is coming up with F3F3F3F3 across each box. After saving the external eeprom i have messed about with the card trying to programme a new external eeprom that i attempted to make but that did not work.

I was wondering if anyone knew how I can read the original ext eeprom hex file i have read with funprom to get my bk and ird details?

 

[hershey]

Just as a further point:

The reason i am doing all this is to update my external eeprom for the date change using toxic7. When the card is in the box i get the "not subscribed to this channel message". in the past when there has been a key change, ive had to download the new hex key, open with willem and set it to 27c128 and save as hex. This is the only way the funprogger has worked in the past and although i dont know the reason for converting with willem the advice was given to me by someone on the forum and it has always worked.

My issue might be to do with the serial programmer that I am using creating dodgy files but im hoping i can somehow decode them! I opened the hex file in notepad and there are loads of F3's at the top but then then at the end of each line and further down there are other characters as well. Any help would be appreciated!!!

 

[Satch]

HiYa,

hershey clear your PM inbox as I think it's full

 

[jamesb4]

If you open your original external eeprom hex file in notepad then go to the following lines:

:1010000007270154010001000000000000AAAAAA32
:10101000AA00000000000000000000000000000092
:1010200000BBBBBBBBBBBBBBBB0738065400002C88

The A's are the IRD - in pairs but in reverse order. The B's are the BK.

James

 

[hershey]

Hey Satch long time mate, cleared my inbox

James, cant find those lines mate. The hex has loads of lines of

101F#####F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3...##

at the top and then

10###0000000000000000000000000000000...##

at the bottom

 

[jamesb4]

I have nothing like F3's, but plenty of 00's, in any of my hex files, so must assume it is corrupt data. A correct file has about 15 lines of data, followed by 10 lines of 00's, followed by 10 lines of data, then a large amount of 00's and then 30 lines of data. So that should let you know if you have a correct file.

James