265 Hemi to efi

Converting To Delco ECU From Carby Or Other Injection Systems
heff0018
Posts: 888
Joined: Tue Apr 21, 2015 1:42 pm
cars: CL valiant charger, VH valiant charger

Re: 265 Hemi to efi

Post by heff0018 »

Also grabbed 2 x 808 ECM's while I was there.
heff0018
Posts: 888
Joined: Tue Apr 21, 2015 1:42 pm
cars: CL valiant charger, VH valiant charger

Re: 265 Hemi to efi

Post by heff0018 »

vlad01 wrote:Yeah I use the flash tool, get bin and then burn the bin to a 512k eeprom at 8000 offset and call it done.

Just don't solder the EEPROMs, I found this is what was causing most of mine to fail. They don't like the heat of soldering, at least the ones I have don't. Solder a socket into the memcal and you can then just burn the chip and push them in, that way you don't need an adapter either.
Hi all, I must be have the offset wrong. I have a 512k eprom and entered what I thought was an 8000 offset but got a verify failed message. Any ideas? Thanks

Also is it correct that an Eprom can be erased in GQ USB program and that it doesn’t need a UV eraser. If not that may be my problem as the first bin I burnt worked but I didn’t have the offset entered. Cheers
Attachments
E22F4039-51D1-4A69-809A-4EBBAFD31645.jpeg
Dylan
Posts: 3355
Joined: Mon Aug 02, 2010 6:35 pm
cars: VR Commodore V8

Re: 265 Hemi to efi

Post by Dylan »

Can't you just stack the bin?
User avatar
vlad01
Posts: 7780
Joined: Mon Oct 08, 2012 6:41 pm
cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive
Location: Kyneton, Vic

Re: 265 Hemi to efi

Post by vlad01 »

I think its becasue you have set both a file and device offset of 8000 which basically will run the code off the end of the eeprom address range.

When you select the device leave everything default, upon opening the BIN file from your PC it is there on that window that you set an offset of 8000. It should work fine from there.
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
heff0018
Posts: 888
Joined: Tue Apr 21, 2015 1:42 pm
cars: CL valiant charger, VH valiant charger

Re: 265 Hemi to efi

Post by heff0018 »

Thanks for the reply I only entered the file offset this time. Strange I still get an error but now the address is 0x008001. If I can’t get this working I will try stacking.
heff0018
Posts: 888
Joined: Tue Apr 21, 2015 1:42 pm
cars: CL valiant charger, VH valiant charger

Re: 265 Hemi to efi

Post by heff0018 »

I stacked the bin in TunerPro and the file size shows as 512k but get this error when writing the file.
Attachments
B786EC32-D088-49C7-B2DB-6354237EE682.jpeg
Dylan
Posts: 3355
Joined: Mon Aug 02, 2010 6:35 pm
cars: VR Commodore V8

Re: 265 Hemi to efi

Post by Dylan »

Windows need a to show 64k to fit a 512k memcal
heff0018
Posts: 888
Joined: Tue Apr 21, 2015 1:42 pm
cars: CL valiant charger, VH valiant charger

Re: 265 Hemi to efi

Post by heff0018 »

Thanks but now I am really confused. So I should only stack the bin twice in TunerPro?
Dylan
Posts: 3355
Joined: Mon Aug 02, 2010 6:35 pm
cars: VR Commodore V8

Re: 265 Hemi to efi

Post by Dylan »

Looks like a VR auto memcals being a 512kb?
12P stack once so windows says it's a 64k file.
11P write straight up.

Google difference between bits and bytes and see what you can make of it
Dylan
Posts: 3355
Joined: Mon Aug 02, 2010 6:35 pm
cars: VR Commodore V8

Re: 265 Hemi to efi

Post by Dylan »

The software will be able to erase an EEprom only
An Eprom will need the UV eraser still
Post Reply