cj2 wrote:
1) Opoenport 2.0 works with these 32bit Risc chips?
The Openport 2 is a J2534 device supporting various ECU protocols via the OBD connection. It's used with other software such as EcuFlash to read ECUs ROMs and of course RomRaider to log data. Modern Subaru ECUs use k-line and/or CAN for communications via the OBD connection.
cj2 wrote:
2) you base your hex files using OpenECU, how does that work and it is working with AUD?
Not AUD. EcuFlash opens a OBD diagnostics connection with the ECU via the Openport 2 over the OBD connection. Once the diag session is established EcuFlash uploads code to RAM and causes the ECU to run this code. The code is EcuFlash's ROM read/write kernel. So reading a ROM commands the kernel to read the ROM segments and send them to EcuFlash where it writes them to hex files. Basically a direct copy of the flash ROM. Both EcuFlash and RomRaider can be use to edit the ROM. Once the ROM is ready is can be written back to the ECU. EcuFlash sends the ROM data to the kernel and it flashes the blocks which are different. Of course Volvo versions of ECUs probably support some OBD diagnostic modes. Mode 23 (if supported) can be used to read arbitrary addresses.
cj2 wrote:
3) any insight you can give will be much appreciated and we look forward to working with the Subaru Guys whom look like that have kick this problem in the but already.
Any Help, Any Idea would be greatly appreciated...
If you can get a complete copy of the ROM via AUD then you have something to work with. Disassemble it with IDA Pro, try a find the OBD modes if not known. From the service manual figure out what kind of OBD diagnostic modes are supported and which protocol is used (k-line, CAN, etc). All this can be helpful to further your understanding of the supported communications and how it can be utilized. Get the CPU hardware and software manual as you'll need them to understand the disassembly.
