Look at the 3AC7 mode7 offset address.
This is a scheduler table for 16 messages sent at idle mode. You put the address or pointer to the message in the code. When set to 0000 the pcm stays quite....
Type: Posts; User: kur4o
Look at the 3AC7 mode7 offset address.
This is a scheduler table for 16 messages sent at idle mode. You put the address or pointer to the message in the code. When set to 0000 the pcm stays quite....
That is the vpw class 2 communication chip present on obd2 pcms. The smaller ones that are missing are the rear 02 drivers.
Looks like the kernel program are missing or cant be loaded. They should be in the 68k folder.
Upon startup of flashhack press debug and post what is in the log.
It did compile fine with...
I am absolutely sure that non of the earlier patches interfere with the minirom patch. If the pcm have been flashed with flashhack and later read with eehack you have pre patched bin with minirom....
I checked the bin and it does have some patches. Couldn`t figure which one. It does have some meta data of engine specs.
It looks like the bin have the mini rom patch too. I guess it was flashed...
The problem can be in vin change. Since the pcm gets unlocked and than if any mode 5 is send the pcm will take it and likely crash and will need reset to wake up.
It doesn`t get response on the reboot request. Than the pcm reboots and response on second upload request that is locked. Flashhack assumes it lost comm and tries to unlock pcm. It manages to unlock...
It is on E4.
They look identical. Some standard mode 0c commands.
Mode 1 msg4 also follows the same format as ee.
The same thing happen to me, it is the FFs that are filled at the end of the eside. No need to worry I make sure that the minirom patch is compatible with all the other patches that are floating...
It is affecting all users that use the latest download link.
There are some leftover bugs in 2 files that didn`t get updated in the official release.
You can use the provided files and...
It looks like that it is a mode 0 msg with device id 00. The ccm interprets it is as a mode 00 msg and returns to normal comm.
The norm is that the bus master spams its id every 2 seconds. When you take control of the bus, the tool becomes bus master and it should follow the norm if it doesn`t send any other data. I guess...
I think the best way to keep the bus silent is to send broadcast message every 2 seconds stating that now the bus master is the tool[per ALDL spesc].
You can set the tool with F0 or F1 ID and just...
It is usual 1 bit to enable control of the solenoid and a second bit to turn on/off.
You can try 00000101 00000202 00000404 00000808 00001010 00002020 00004040 00008080
and so on
On PWM...
I looked at the 2 files and they seem to have 32kb rom, eprom or external flash. 95 having some extra code at the end. Pretty similar though.
There is 100 bytes ram on the processor and some ram...
The log doesn`t look that bad as you thought. I can clearly see that ccm is waking in the middle of nowhere and starts spamming the bus.
Initial connection is also slow but the end it make it...
Once I tried the gm factory tool and it didn`t want to connect with y-body bin. I did some sniff scan and the tool was trying to send mode 8 to ccm, but never get a response. I remember it sends once...
I suspect there might be some protection on the bus conflict on a hardware level, and the bombardment might just be ignored and never reach the pcm. Than the aldl chip sends to cpu that bus is...
I checked the logs and it looks like the bus freeze at mode 08 bombardment and than resumes normal communication.
Can you try to give a 4-5 attempts burst than wait for silence, than again 5...