Tuned and runs on NVRAM Burned chip verifies. Memcal fault

Holden/Delco Tuning. ALDL, OBD 1.5. Circa 1989 to 2004.
4wheelinls1
Posts: 30
Joined: Tue Oct 15, 2013 1:04 pm
cars: X6t

Tuned and runs on NVRAM Burned chip verifies. Memcal fault

Post by 4wheelinls1 »

Its been a few years and I am scratching my head as if I'v forgotten something. Tuning a 12P with NVRAM in a VR man. The car is all tuned and fine on the NVRAM.. I download the file from the emulator to a file and save it. Size is right 32k. Burn the file into the Memcal 27c256 from the car and the ecu is in limp, fan running engine light on. The chip verifies, tried 3 chips and they all verify. Did I forget a step, checksum or something?

Cheers
Dylan
Posts: 3356
Joined: Mon Aug 02, 2010 6:35 pm
cars: VR Commodore V8

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by Dylan »

Post up a read from the memcal
4wheelinls1
Posts: 30
Joined: Tue Oct 15, 2013 1:04 pm
cars: X6t

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by 4wheelinls1 »

I burnt a stock file to the chip and the car starts and runs no fault so I know the programmer and Memcal is good.
Attachments
304_crane_286_man.bin
(32 KiB) Downloaded 232 times
4wheelinls1
Posts: 30
Joined: Tue Oct 15, 2013 1:04 pm
cars: X6t

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by 4wheelinls1 »

This is the read back
Attachments
304_crane_286_man_test.Bin
(32 KiB) Downloaded 251 times
4wheelinls1
Posts: 30
Joined: Tue Oct 15, 2013 1:04 pm
cars: X6t

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by 4wheelinls1 »

Just noticed hadn't selected download all tables. Going to try again.
pman92
Posts: 465
Joined: Thu May 03, 2012 10:50 pm
cars: HZ One Tonner
VE Ute
Location: Castlemaine, Vic

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by pman92 »

Possibly not a complete bin and only the cal section you arw burning to the eprom?
VR-VY Holden BCM Simulator: View Post
MrModule.com.au
4wheelinls1
Posts: 30
Joined: Tue Oct 15, 2013 1:04 pm
cars: X6t

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by 4wheelinls1 »

nope
4wheelinls1
Posts: 30
Joined: Tue Oct 15, 2013 1:04 pm
cars: X6t

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by 4wheelinls1 »

pman92 wrote:Possibly not a complete bin and only the cal section you arw burning to the eprom?

I started by putting the stacked stock 12P on the nvram, tund the car, downloaded the nvram to a file 32k and wrote it.. File size was right so I figured all there. I know its something silly Ive missed.
User avatar
antus
Site Admin
Posts: 8250
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by antus »

Downloading in tunerpro with oseplugin? Have you de-selected "read cal area only"?
Or use the OSE Flashtool and do a get bin.

12P is 32k which 32*8(bit)=256 so your chip is right, just put it straight on.

Is the chip the original known good chip? Did it erase ok?
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
antus
Site Admin
Posts: 8250
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: Tuned and runs on NVRAM Burned chip verifies. Memcal fau

Post by antus »

I just checked your bin, yep no operating system on it. Update the oseplugin config to pull the whole thing then hit download or use the ose flash tool and get bin......

Look at the bin in a hex editor and see the data ends:

Code: Select all

0x00001A90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8A 98  | ................
0x00001AA0: 00 84 00 81 00 8A 01 A9 01 AC 01 5F 01 5B 01 AB  | ..........._.[..
0x00001AB0: 01 AB 01 AA 00 81 01 5F 01 AB 01 6E 00 43 00 6B  | ......._...n.C.k
0x00001AC0: 01 A9 00 6C 01 AA 01 AC 01 AA 01 A9 00 84 00 8A  | ...l............
0x00001AD0: 01 A9 01 AB 00 43 00 6B 10 00 E5 01 26 01 34 05  | .....C.k....&.4.
0x00001AE0: F6 01 7D FF FE FF 00 00 40 FF 10 80 FF 00 00 00  | ..}.....@.......
0x00001AF0: 4F 53 45 31 32 50 72 6F 20 43 61 6C 20 01 01 02  | OSE12Pro Cal ...
0x00001B00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  | ................
0x00001B10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  | ................
0x00001B20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  | ................
0x00001B30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  | ................
0x00001B40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  | ................
0x00001B50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  | ................
That text is at the end of the cal area, and below it you should have an aldl segment and an operating system segment (cant remember the actual text off the top of my head)... that its blank to the end of the file shows the problem.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Post Reply