Search found 22 matches
- 18 Mar 2023, 13:39
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
Your key should be 61 (0x3d) bytes long. out[0] = ( data[0] xor key[0] ) xor 0 out[1] = ( data[1] xor key[1] ) xor 0 out[2] = ( data[2] xor key[2] ) xor 0 out[3] = ( data[3] xor key[3] ) xor 0 out[4] = ( data[4] xor key[4] ) xor 0 out[5] = ( data[5] xor key[5] ) xor 0 out[6] = ( data[6] xor key[6] )...
- 13 Jul 2023, 03:58
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
Look at 0x4000 or 0x6000.
There should be 6 bytes pretty visible.
There should be 6 bytes pretty visible.
- 15 Jul 2023, 13:45
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
AA 00 - Clear the list of all identifiers Add an entry to the list by address or identifier. AA 50 00 EE 10 16 - Append Record Address with length byte. (Address 00EE10, 16 bytes) or AA 20 11 22 - Append Record Identifier (Identifier 1122) A6 F0 00 01 - Read first record 1 time. Result 16 bytes from...
- 21 Jul 2023, 13:05
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
@jeffbolem You can read the type of CEM with 40 B9 F0 This is needed to find the correct meaning of the different configuration bytes. 40 B9 FB Vehicle information 40 B9 FC Vehicle type (configuration) cembrick.csv Second byte in response is possibly length + 16*high byte of checksum. Not tested or ...
- 23 Jul 2023, 16:02
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
@dikidera
I haven't tried datalogging yet, so I don't know if it is normal to repeat the request.
The ETM I have on my desk does not need and SBL to read data with checksum command in programming mode.
I can also read with BB-command.
12 BB 00 40 00 10 reads 0x10 bytes from address 0x004000
I haven't tried datalogging yet, so I don't know if it is normal to repeat the request.
The ETM I have on my desk does not need and SBL to read data with checksum command in programming mode.
I can also read with BB-command.
12 BB 00 40 00 10 reads 0x10 bytes from address 0x004000
- 16 Oct 2023, 13:07
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
M32C comes in different Flash sizes.
320kB starts at 0xFB0000 with size 0x50000
384kB starts at 0xFA0000 with size 0x60000
512kB starts at 0xF80000 with size 0x80000
From the CPUs point of view, the pin is typically 0x2000 from the end at 0xFFE000.
320kB starts at 0xFB0000 with size 0x50000
384kB starts at 0xFA0000 with size 0x60000
512kB starts at 0xF80000 with size 0x80000
From the CPUs point of view, the pin is typically 0x2000 from the end at 0xFFE000.
- 13 Feb 2024, 12:43
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
Here are files needed to compile with tcc.
byteswap.h and getopt.h must be moved to the tcc\include folder.
the rest in the tcc folder
The .bat file will run the command:
tcc.exe seed-gen.c getopt.c -o seed-gen.exe
And create seed-gen.exe
byteswap.h and getopt.h must be moved to the tcc\include folder.
the rest in the tcc folder
The .bat file will run the command:
tcc.exe seed-gen.c getopt.c -o seed-gen.exe
And create seed-gen.exe
- 04 Dec 2024, 11:36
- Jump to forum
- Jump to topic
Re: Vida CEM swapping
So far I have only one idiotic idea in my head - to add the j2534 protocol to your cracker. :wink: J2534 is pass-through, nothing fancy. I use it in a similar hw: https://github.com/vtl/volvo-ddd And there's a "teensy" branch. And the PCB https://oshwlab.com/v.mayatskih/volvo-ddd2_copy wh...
- 16 Jul 2025, 13:22
- Jump to forum
- Jump to topic






