quick help tunerpro chip read function???

[Blazer3664]

Long version........

Trying to familiarize myself with the new equipment.
So I got my AutoProm all hooked up inside where its WARM (freezing out by the way), tunerpro rt going.
Pulled the eprom out of a 7747 I have sitting here, thinking I should start by trying to read a stock chip. Put it in the AutoProm as stated on the quick start.
Tools
>hardware utilities
>moates prom I/O
>supported chip set as "2732A (read only)
>read chip
and I get

"reading device into buffer..."
"ERROR: Memory range and/or address outside selected eprom size"


now if I do the same but chose any of the following
29C256
29F040
27SF512

I get a progress bar and then
"PROM I/O succeeded"

?????Pretty sure thats not right?????

Also pretty sure its my oops, not the equipment.
So what am I doing wrong here?

Short version......
HELP!!

Thans in advance,
Jim

[EagleMark]

For some reason when you choose a chip it will change the Chip and Buffer offset... but not always correctly...

Use these settings to read a 2732a chip:
Chip start - end: 000000 -> 000FFF
Buffer start - end: 000000 -> 000FFF

Then Verify Buffer to Chip. Load Buffer to file and save with whatever BCC chip is. When you open it check to see it is 4k in size.

[Blazer3664]

Well buffer end was showing OO7FFF

Fixed that but now

"FAILURE: Verification failed (not matched)

[Blazer3664]

It does say
"PROM I/O succeeded"
if I hit "Read chip" now though.

[Blazer3664]

Load Buffer to file and save with whatever BCC chip is. When you open it check to see it is 4k in size.

Bytes written to file: 4096
File loaded: C/ bla bla bla......
File size in bytes (Interger/hex): 4096/0*1000
Bytes written to file: 4096

That look right?

If so, the only question is why it wont verify?

Thanks for bearing with here,
Jim

[EagleMark]

It does say
"PROM I/O succeeded"
if I hit "Read chip" now though.

Good! Then Verify Chip with Buffer should come up with Success!

4096 Byte is 4 Kilobyte so... Open the file in TunerPro with XDF loaded and check Mask ID, should say 42.

EDIT: Do you have chip at bottom of socket furthest away form handle and notch facing handle?

[Blazer3664]

Yep, Yep, and Yes sir

All good now. So, I guess it was only partly me.

Maybe tommorow I'll take it down and plug into my DD and see if I can data log something.

Thanks for your patience and help, .....again.

Jim

[Six_Shooter]

The 2732 chip reading is broken in the latest builds of Tuner Pro using the AutoProm or Burn2.

I use the stand alone Flash 'n' Burn utility to read 2732 EPROMs.

[Blazer3664]

Just practicing to get familiar with where things are and how they work in TP.

But yea, that buffer end value changing itself sucks.

Tomorrow more practice. I am off till tuesday, and plan to have at least half my head wrapped around this stuff by then. Wont actually be tuning the rig in my sig till spring. By then I should be OK.

Jim

[EagleMark]

The 2732 chip reading is broken in the latest builds of Tuner Pro using the AutoProm or Burn2.

I use the stand alone Flash 'n' Burn utility to read 2732 EPROMs.

any paticulars? Because mine just worked as described above, but they are differant offsets then what I used in the past?

[Six_Shooter]

any paticulars? Because mine just worked as described above, but they are differant offsets then what I used in the past?

Particulars of what?

I tried to get the built in utility to work for reading 2732s and ended up just using the stand alone utility, was much easier and quick to do so, worked perfect the first time.