PowerPCM_Flasher: my tool for E38 and E67

[daniel2345]

For antus problem:

With the output window and tests done i can say that a message is received, but it does not have correct content.

I add message payload printing for not ok results in debug mode for next release tonight.

[ironduke]

How hard would it be to be able to enter your own key, like if it's tuner locked.. Or if you just did what I did and tried a different OS(older) and bricked it.. Seed is given as 0x3F80 but the key doesn't work.. Running my unlocker on it now, but it could be a few days.. When I do get it it might be nice to be able to simply tell it what key I want it to use.. lol..

[daniel2345]

Sure, that's easy.

Ill add a third option with FFFF to the dropdown box.

This is used as is for answer and you can enter what you want.

[Tazzi]

How hard would it be to be able to enter your own key, like if it's tuner locked.. Or if you just did what I did and tried a different OS(older) and bricked it.. Seed is given as 0x3F80 but the key doesn't work.. Running my unlocker on it now, but it could be a few days.. When I do get it it might be nice to be able to simply tell it what key I want it to use.. lol..

Try FFFF, 0000 or C07F as your keys.

[ironduke]

How hard would it be to be able to enter your own key, like if it's tuner locked.. Or if you just did what I did and tried a different OS(older) and bricked it.. Seed is given as 0x3F80 but the key doesn't work.. Running my unlocker on it now, but it could be a few days.. When I do get it it might be nice to be able to simply tell it what key I want it to use.. lol..

Try FFFF, 0000 or C07F as your keys.

Thanks, already tried 0000, and FFFF, just tried c07f with no luck though..

[antus]

Today I was attempting to gather some debug info by logging the bus traffing while testing v0004. And, on my first attempt while logging bus traffic, it read the bin successfully!

Code: Select all

initialising Tool J2534 PassThru
Bosch - MDI...
ok.
connecting...
start diagnostic session (0x10 0x03)...ok.
disable normal communication (0x28)...ok.
security access (0x27)...
	 request seed...NOT ok, no valid seed received.
	 Wait 30s after power on or failed attempt.
connecting...
start diagnostic session (0x10 0x03)...ok.
disable normal communication (0x28)...ok.
security access (0x27)...
	 request seed...ok.
	 seed: 	 0x0000335F
	 key: 	 0x000075A3
	 sending key...ok.
request programming mode...ok.
sending enable programming mode...done.
downloading prog...
busy.
ok.
run prog...ok.
ready to upload flash or download calibration.
upload flash...
upload progress: 4% (0x010000)
upload progress: 7% (0x020000)
upload progress: 10% (0x030000)
upload progress: 13% (0x040000)
upload progress: 16% (0x050000)
upload progress: 19% (0x060000)
upload progress: 22% (0x070000)
upload progress: 25% (0x080000)
upload progress: 29% (0x090000)
upload progress: 32% (0x0A0000)
upload progress: 35% (0x0B0000)
upload progress: 38% (0x0C0000)
upload progress: 41% (0x0D0000)
upload progress: 44% (0x0E0000)
upload progress: 47% (0x0F0000)
upload progress: 50% (0x100000)
upload progress: 54% (0x110000)
upload progress: 57% (0x120000)
upload progress: 60% (0x130000)
upload progress: 63% (0x140000)
upload progress: 66% (0x150000)
upload progress: 69% (0x160000)
upload progress: 72% (0x170000)
upload progress: 75% (0x180000)
upload progress: 79% (0x190000)
upload progress: 82% (0x1A0000)
upload progress: 85% (0x1B0000)
upload progress: 88% (0x1C0000)
upload progress: 91% (0x1D0000)
upload progress: 94% (0x1E0000)
upload progress: 97% (0x1F0000)
upload progress: 100% (0x200000)
done.
validating upload...ok, valid.

pcmflasher0004-2.log

(1.01 MiB) Downloaded 245 times

pcmflasher0004-2.bin

(2 MiB) Downloaded 242 times

The log is AVT Format, so the first byte, or two bytes depending on the length of the packet are the length. If you understand the can packets you will be able to see where they start. It was logged on the bus.

[antus]

I was fairly sure this was a unicorn run, and next log would fail. But Ive now read it 4 times in a row successfully. Im not doing anything different (other than running a logger, but the same hardware was connected before). The only thing ive done is install 2 visual basic OCXs for the avt log tool, and I dont expect they would have made a difference. I have zero idea why it would have been consistently failing before, and consistently working now.

[antus]

Since I cant fault it again, I decided to re-write the cal. Which worked. But disconnect still does not work.

Code: Select all

erase calib...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
ok.
done.
download calib...
download progress: 13% (0x008000)
download progress: 25% (0x010000)
download progress: 38% (0x018000)
download progress: 50% (0x020000)
download progress: 63% (0x028000)
download progress: 75% (0x030000)
download progress: 88% (0x038000)
download progress: 100% (0x040000)
done.
validating download...ok, valid.
hit disconnect or read.
disconnecting...NOT ok.

[daniel2345]

Good morning

That are good news. Maybe the logger added some voltage or capacity to the can line?

When you disconnect the logger, will it fail again?


Ill have a look why disconnect fails...


But very nice that two independent persons can use it with MDI

[daniel2345]

Update to Version 0.0.0.5

I reworked the "design" as you may call it...
Hope that is ok, seems more can/need/should be configurable as inital thought.
So i added menu bar for file and settings.
DLL path has moved there.

With the more space on the gui i decided to put more ID, CVN and Checksum Info in the File-Info Box.


I added info (Returncodes) in case something is not ok and for debug printing the received message buffer.
I added the third option to the seed&key box, the content of the box after 0xFFFF is chosen will be send.


ELM:
I worked a little bit on the ELM, too. It is now setup to have autimatic current(initial) baudrate detection.
For my ELM i can now always init it with each try. No need to cycle power or remove from usb.

In case anything fails, you can choose the baudrate it should have in the Settings Menu.
Target baudrate is not implemented yet, it will always try 500k.


Unfortunately im still not able to send/receive fast frames with it.
Sometimes it decides to not get frames. No "NO DATA", nothing. Just an empty read buffer.
Dont know why. Maybe flow control of ELM will help, will try that the next days.



Most interesting thing is still why reset/disconnect is not working for antus...