Can't Read Bin in Tunercat coming off EEPROM
#1
Thread Starter
Member
iTrader: (1)
Joined: Dec 2000
Posts: 432
Likes: 0
From: Long Island, N.Y.
Car: 1986 Camaro Z-28
Engine: Chevy ZZ4
Transmission: Select Built 700R4
Axle/Gears: Moser Axles / 3.73 Richmond Gears
Can't Read Bin in Tunercat coming off EEPROM
Using the Pocket ProgrammerII I set the device from 04000-07FFF (using AT29C256 chips) and moved the device to buffer. I then saved the buffer(bin) onto my desktop. When I try to read it in tunercat it says I need definition file $6E yet I created this file using just that before I burned the eeprom to begin with. Am I extracting the information from the eeprom incorrectly?
Someone asked practically the same thing back in April. 2001 as I found doing a search but there was no reply.
(https://www.thirdgen.org/techbb2/sho...+read+bin+file)
Does anybody have an idea of what might be happening or what we're doing wrong?
Someone asked practically the same thing back in April. 2001 as I found doing a search but there was no reply.
(https://www.thirdgen.org/techbb2/sho...+read+bin+file)
Does anybody have an idea of what might be happening or what we're doing wrong?
#2
it proably got to do with the fact that your adress in teh hex file are all offset by $4000. keep a copy of your working bin on disk and then work form it. you dont need to use what on the chip as long as you have a backup copy.
#3
Thread Starter
Member
iTrader: (1)
Joined: Dec 2000
Posts: 432
Likes: 0
From: Long Island, N.Y.
Car: 1986 Camaro Z-28
Engine: Chevy ZZ4
Transmission: Select Built 700R4
Axle/Gears: Moser Axles / 3.73 Richmond Gears
I was trying to read from the chip b/c I wanted to double check that the file I had saved was truly the most recent one I was running. I transferred alot of stuff between two machines so I second guessed myself that I took every file. I guess it's not that important but it does seem strange that it doesn't work. Oh well.
#5
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 3
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
If this is a MAF bin (which I assume it is), just set the Pocket Programmer to a "27C128" eprom and you will be able to read it properly. This is what you are emulating when you burnt your bin with the hex 4000 offset in the first place
Trending Topics
#8
Thread Starter
Member
iTrader: (1)
Joined: Dec 2000
Posts: 432
Likes: 0
From: Long Island, N.Y.
Car: 1986 Camaro Z-28
Engine: Chevy ZZ4
Transmission: Select Built 700R4
Axle/Gears: Moser Axles / 3.73 Richmond Gears
If this is a MAF bin (which I assume it is), just set the Pocket Programmer to a "27C128" eprom and you will be able to read it properly. This is what you are emulating when you burnt your bin with the hex 4000 offset in the first place
#9
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 3
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
Originally posted by funstick
that wont work becuase the programmer will read the lower first 0000 to $4000 adress's as FF
that wont work becuase the programmer will read the lower first 0000 to $4000 adress's as FF
Remember, you are tricking the ECM by offsetting the MAF bin by x4000 when you write it onto a 29C256 (or 27C256) to THINK it has a 27C128. Therefore the EASIEST way to read it is to read it as a 27C128...exactly what you are trying to emulate.
#11
Supreme Member
Joined: Jul 1999
Posts: 1,577
Likes: 0
From: Baton Rouge, LA, USA
Car: 87 T/A
Engine: 441 SBC 12.5:1 0.680" Lift
Transmission: T-56
Axle/Gears: 4.10 TruTrac Moser 9"
Download HexWorks. Then download your full EPROM contents. Load the downloaded 32k BIN into HexWorks and delete half of it. Then resave. Open it in TunerCat that way.
Actually if you just want to do a file compare, HexWorks will do that directly....
Actually if you just want to do a file compare, HexWorks will do that directly....
Thread
Thread Starter
Forum
Replies
Last Post
Ghettobird52
Tech / General Engine
16
07-06-2024 12:18 AM