So what you posted is the preparation/setup for the ECU, which includes unlocking, disabling chatter ect. Once that is done, the kernel (Also called bootloader) is sent to the ECU which then executes and allows reading/writing/whatever you want.kostia111 wrote:hello !
why not use a lot of frame message
the same way as when programming a block
then it will be possible to transfer about 4k
in one message
or use a standard service
ReadMemoryByAddress ($23) Service.
maybe I'm writing stupidity
and misunderstood you
When looking at the GM logs, you will see in most car computers, a bit of code is uploaded to it first. Is that code which I am referring to in this thread where I am trying to code it up to read/write the ECU.
The more I write with PPC, the easier its becoming and the better ways of coding I am finding.
The mode 23 doesnt allow reading all memory address, and also allows only reading 8bytes at a time which is extremely slow. Whereas with a custom kernel, we could download up to 0xFFF (4,095) bytes at a time if we wanted.
This is the basic setup Im going for:
1) Unlock ECU
2) perform ecu setups (disable chatter, faults ect)
3) Upload bootloader code and execute
4) Request data to read using 7E0 06 35 XX XX YY YY YY where XX is length of data, and YY is the address offset from 0.
5) ECU will respond as 7E8 1Z ZZ 75 XX XX YY YY YY.... then data frames from here. Where ZZ is the canbus frame length (XX+6), XX is the requested length and YY the address offset.
6) kernel will comply with SAE standards so it can be happily read using a J2534 tool, which is the canbus formatting I was working out above.
