Inexpensive Opensource Flashing(Read is 100% working)
#701
That would be great!
Especially if you've got the AMD flash chip, but if you've got the Intel I'd still like to take a shot at it.
Do you have any idea why the Intel works and AMD doesn't? If it's just a matter of getting the magic numbers written to the right places then I'm sure it's solvable in software, but if there's an extra write-enable line that needs voltage then it's going to require an extra connection to the board somewhere.
Especially if you've got the AMD flash chip, but if you've got the Intel I'd still like to take a shot at it.
Do you have any idea why the Intel works and AMD doesn't? If it's just a matter of getting the magic numbers written to the right places then I'm sure it's solvable in software, but if there's an extra write-enable line that needs voltage then it's going to require an extra connection to the board somewhere.
The following users liked this post:
kpeters59 (10-31-2019)
#702
TECH Veteran
iTrader: (1)
I believe that there are some pins on the AMD flash chip that must also have voltage applied in order for writing to work. In my car, immediately prior to accessing the erase and write command functions, there is assembly code affecting external chip select pins, if i recall correctly. although this is highly dependent on ecu wiring, i could dig out that assembly code if it would help you.
The following users liked this post:
kpeters59 (10-31-2019)
#703
9 Second Club
Being the fool I am...I bought the OBDLink MX+ ( arrived quickly too )
I have bluetooth etc, and I appear to be connected to the device ok....even though it was a bit of a pain with drivers. But now when I open PCM Hammer, it just seems to sit there frozen ? no menu options available.
I dont believe I have any conflicts to prevent it working, albeit with 3 COM's assigned.
I have bluetooth etc, and I appear to be connected to the device ok....even though it was a bit of a pain with drivers. But now when I open PCM Hammer, it just seems to sit there frozen ? no menu options available.
I dont believe I have any conflicts to prevent it working, albeit with 3 COM's assigned.
#704
I think you need to update drivers or software, I think the yellow ! is saying there is an issue. I also had a hard time with the drivers, if you buy a new device and download the software, you should get the drivers for it, just saying.
Stampede.
Stampede.
#705
9 Second Club
The yellows are not relating to the new MX+ device.
One has been on the PC for years, the other my NAS drive even though it works perfectly.
Maybe the ecu I have sitting here is dead in some respects ? as it was bought with some other stuff, so is an unknown. And I find it very odd that even though the OBD software appears to connect to the ecu ok, there are no fault codes.....which there should be loads for an unplugged ecu.
One has been on the PC for years, the other my NAS drive even though it works perfectly.
Maybe the ecu I have sitting here is dead in some respects ? as it was bought with some other stuff, so is an unknown. And I find it very odd that even though the OBD software appears to connect to the ecu ok, there are no fault codes.....which there should be loads for an unplugged ecu.
#707
Teching In
Hi all.
App is definitely hanging up trying to initialize the Bluetooth Com Port.
Try removing the Bluetooth dongle from the PC (or otherwise disabling it), Restart PCM Hammer and try selecting a DIFFERENT Com Port.
Then Re-enable Bluetooth device and try App again.
You basically want to get PCMHammer to re-initialize the Com Port settings!
Mike
PS PCMHammer SHOULD at least get to the point of selecting a device EVEN without ANY Bluetooth or USB devices present.
App is definitely hanging up trying to initialize the Bluetooth Com Port.
Try removing the Bluetooth dongle from the PC (or otherwise disabling it), Restart PCM Hammer and try selecting a DIFFERENT Com Port.
Then Re-enable Bluetooth device and try App again.
You basically want to get PCMHammer to re-initialize the Com Port settings!
Mike
PS PCMHammer SHOULD at least get to the point of selecting a device EVEN without ANY Bluetooth or USB devices present.
The following users liked this post:
Dave V (11-01-2019)
#709
#710
Dave V, on your OBDII, what pin out do have? I think I found my issue, the obd plug I got from a Silverado is different then what I found to use, and then the instructions is different then the diagram, so, pin 4 and 5 are grounds, what pin number is for data, and what pin is power?
And what pin are you using to ground the pcm, I have pin 1.
Thanks.
And what pin are you using to ground the pcm, I have pin 1.
Thanks.
The following users liked this post:
Dave V (11-15-2019)
#716
In regards to tuning for boost (reply 10-09-2019) and modifying all the tables for a MAP hack(using 2 bar sensor on 1 bar tables), for a boat only used at sea level would it be possible to use the baro multiplier (table B0404) as it starts at 65kpa?
Anyone have any thoughts or experience with this ?
Anyone have any thoughts or experience with this ?
#718
9 Second Club
iTrader: (11)
Would you happen to know the service number or even what year your P59 was? I spent a great deal of time on this and the only one I've ever gotten it to work on was the 2003 P59 that used the Intel flash chip. I thought I had it close on the AMD version of the P59 a couple of times I've gone back and revisited this but was never able to get it to write correctly.
I have also used usbbdm jtag dozens of times on p59.
First batch was intel 28f800. 12v to RP. No pull up. 100% sucess
Only had a problem with one, it was same 1mb p59 type, but discovered am29f800 (AMD flash)
Made new flash type. Do not have data sheet. Ultimately I had Success with NO BOOT BLOCK LOCK. I did not use 12v or 12v pull up anywhere to unlock. 100% write and read success
Edit= if I applied 12v to the rp pin on the amd, then it seem successful but the erase wouldn't erase 100% and the write would not write 100% it all seemed to work just fine but would not verify erased and would not verify the write. By trial and error or accident (I don't recall) I successfully erased and wrote and verified with out 12volts to the RP pin. (boot block pin).
From memory this pin rp needs 12v on Intel f800 and the wpp? Needs 12v on the intel f400 512 pcms (411) maybe boot block isn't what it's called.... Write protect maybe?
I haven't done any of this jtag stuff since LSDroid release has allowed me to do all that I need without opening pcms.
Last edited by i420tom; 11-14-2019 at 04:32 PM.
#719
I have also used usbbdm jtag dozens of times on p59.
First batch was intel 28f800. 12v to RP. No pull up. 100% sucess
Only had a problem with one, it was same 1mb p59 type, but discovered am29f800 (AMD flash)
Made new flash type. Do not have data sheet. Ultimately I had Success with NO BOOT BLOCK LOCK. I did not use 12v or 12v pull up anywhere to unlock. 100% write and read success
Edit= if I applied 12v to the rp pin on the amd, then it seem successful but the erase wouldn't erase 100% and the write would not write 100% it all seemed to work just fine but would not verify erased and would not verify the write. By trial and error or accident (I don't recall) I successfully erased and wrote and verified with out 12volts to the RP pin. (boot block pin).
From memory this pin rp needs 12v on Intel f800 and the wpp? Needs 12v on the intel f400 512 pcms (411) maybe boot block isn't what it's called.... Write protect maybe?
I haven't done any of this jtag stuff since LSDroid release has allowed me to do all that I need without opening pcms.
First batch was intel 28f800. 12v to RP. No pull up. 100% sucess
Only had a problem with one, it was same 1mb p59 type, but discovered am29f800 (AMD flash)
Made new flash type. Do not have data sheet. Ultimately I had Success with NO BOOT BLOCK LOCK. I did not use 12v or 12v pull up anywhere to unlock. 100% write and read success
Edit= if I applied 12v to the rp pin on the amd, then it seem successful but the erase wouldn't erase 100% and the write would not write 100% it all seemed to work just fine but would not verify erased and would not verify the write. By trial and error or accident (I don't recall) I successfully erased and wrote and verified with out 12volts to the RP pin. (boot block pin).
From memory this pin rp needs 12v on Intel f800 and the wpp? Needs 12v on the intel f400 512 pcms (411) maybe boot block isn't what it's called.... Write protect maybe?
I haven't done any of this jtag stuff since LSDroid release has allowed me to do all that I need without opening pcms.
Can you share the configuration file that worked for USB-BDM flashing with the AMD chip? That's what I need to bring my test P59s back to life, and with a little more trial-and-error I should be able to release a version of PCM Hammer that supports P59s.
#720
9 Second Club
iTrader: (11)
The first P59 that I bricked had that 12v line active and I'm sure that's where I want wrong. Not sure about the second one though...
Can you share the configuration file that worked for USB-BDM flashing with the AMD chip? That's what I need to bring my test P59s back to life, and with a little more trial-and-error I should be able to release a version of PCM Hammer that supports P59s.
Can you share the configuration file that worked for USB-BDM flashing with the AMD chip? That's what I need to bring my test P59s back to life, and with a little more trial-and-error I should be able to release a version of PCM Hammer that supports P59s.