KTAG
KTAG
Hi Team,
Has anyone been able to use a KTAG from alien Tech to read the flash chip and EEPROM from a PCM APS-234 Spanish Oak 1024kb PCM for the Ford Falcon?
I can't seem to find any support for the MPC565 PCM within KTAG.
If anyone has, would be interesting to see what was used? I'm well aware of other tools, just want to see if it's feasible with such unit.
I'm more interested in the bootloader (EEPROM), I have not yet physically opened the ECU to identify the components, before i do this, want to ensure KTAG is feasible, if not I'll have to use EEPROM programmer.
thanks, in advance.
ABS
Has anyone been able to use a KTAG from alien Tech to read the flash chip and EEPROM from a PCM APS-234 Spanish Oak 1024kb PCM for the Ford Falcon?
I can't seem to find any support for the MPC565 PCM within KTAG.
If anyone has, would be interesting to see what was used? I'm well aware of other tools, just want to see if it's feasible with such unit.
I'm more interested in the bootloader (EEPROM), I have not yet physically opened the ECU to identify the components, before i do this, want to ensure KTAG is feasible, if not I'll have to use EEPROM programmer.
thanks, in advance.
ABS
Re: KTAG
Looking at their website it seems the Ford Territory is supported? Ill try the Kess module
Type Brand Model Type From Version Engine Code Fuel PS/HP Ecu Type Ecu Brand Ecu Version Micro Method
Car Ford Territory 2011 4.0 6AT Petrol 265 ECM Ford EEC-VI
Type Brand Model Type From Version Engine Code Fuel PS/HP Ecu Type Ecu Brand Ecu Version Micro Method
Car Ford Territory 2011 4.0 6AT Petrol 265 ECM Ford EEC-VI
Re: KTAG
I was successfully, able to extract the binary file, but it seems to be the OS hex file. I may just open the ECU to view the MLB to see what i can access.
-
- Posts: 88
- Joined: Fri Jan 11, 2019 4:15 pm
- cars: Ba Futura Wagon - Been turboed since 2009
3 x Celica GT4s 1 is a Group A
ST141 Corona - 3sgte swap is planned
EP71 Toyota Starlet Turbo S
A few e36 BMW's - Location: Victoria
Re: KTAG
So you used the Kess tool or ktag to access the OS Binary?
-
- Posts: 2950
- Joined: Sun Aug 02, 2009 9:16 pm
- Location: Bayside, Melbourne, Victoria
- Contact:
Re: KTAG
The kess should have grabbed the raw binary & be around 1MB from memory, what are you trying to do with it?
Re: KTAG
pardon late reply,
yes, that's correct binary file was retrieved. I'm actually after the bootloader.
i have put this project on ice for the moment.
yes, that's correct binary file was retrieved. I'm actually after the bootloader.
i have put this project on ice for the moment.
Re: KTAG
If you ever get around to opening one up, this doc will be useful. Especially the first page.
https://www.nxp.com/docs/en/application-note/AN2000.pdf
https://www.nxp.com/docs/en/application-note/AN2000.pdf
Re: KTAG
Thanks HJ Turbo, ill check it out.
So, I jumped back onto this project, opened up a AP232 PCM and boy they glued the fucker down! as I want to see the bottom side of the MLB to also.
There is a test point pad i see but need to know each test point pinout, don't look like standard BDM pinouts like on other ECUS.
Anyone opened one and removed PCB? Too hard to remove without damaging the board. There has to be solvents to dissolve the silicone.
Looked at the Semiconductors from what i can see, MCP, Fan driver, Canbus transceiver.
***update, I have been browsing around to see if there is any close pinouts for the BDM, it seems the ECU's are Visteon's.
I have located the like of diag port pads from other forums
https://carmasters.org/topic/32142-visteon-esu-131/
https://ecu.design/ecu-pinout/pinout-vi ... -132-ford/
Looking at KTAG, the closest i can find is the Transit TT9 which are Visteon's with the same diag pad, but different ECU or BDM MPC for FoMoCo Aston Martin
Anyone read more than the flash chips from such ECU?
So, I jumped back onto this project, opened up a AP232 PCM and boy they glued the fucker down! as I want to see the bottom side of the MLB to also.
There is a test point pad i see but need to know each test point pinout, don't look like standard BDM pinouts like on other ECUS.
Anyone opened one and removed PCB? Too hard to remove without damaging the board. There has to be solvents to dissolve the silicone.
Looked at the Semiconductors from what i can see, MCP, Fan driver, Canbus transceiver.
***update, I have been browsing around to see if there is any close pinouts for the BDM, it seems the ECU's are Visteon's.
I have located the like of diag port pads from other forums
https://carmasters.org/topic/32142-visteon-esu-131/
https://ecu.design/ecu-pinout/pinout-vi ... -132-ford/
Looking at KTAG, the closest i can find is the Transit TT9 which are Visteon's with the same diag pad, but different ECU or BDM MPC for FoMoCo Aston Martin
Anyone read more than the flash chips from such ECU?
- Attachments
-
- PInout1.png (676.14 KiB) Viewed 1030 times
-
- PCM-232-1.PNG (1.86 MiB) Viewed 1115 times
-
- PCM-232.PNG (2.02 MiB) Viewed 1115 times
Re: KTAG
Quick Update,
Since removing the MLB deemed challenging. I decided to use the BDM contacts to see what can be retrieved from the PCM via KTAG.
based on the pin outs seen from another car. I was able to communicate but, it seemed the ECU cannot be identified (makes sense) but managed to extract the binary.
based on this PCM model, it doesn't seem the PCM has an external flash or EEPROM embedded like other variant ecu's. Pretty much its behaving just like Kess or other flash tools to extract the binary.
Ideally, I would like to locate the PCM S/N and model which is forked into the binary.
A factory default ford binary file doesn't have such data. thus, saying it's populated into the binary once it's flashed to the PCM and rebooted.
I hope I'm making sense.
Since removing the MLB deemed challenging. I decided to use the BDM contacts to see what can be retrieved from the PCM via KTAG.
based on the pin outs seen from another car. I was able to communicate but, it seemed the ECU cannot be identified (makes sense) but managed to extract the binary.
based on this PCM model, it doesn't seem the PCM has an external flash or EEPROM embedded like other variant ecu's. Pretty much its behaving just like Kess or other flash tools to extract the binary.
Ideally, I would like to locate the PCM S/N and model which is forked into the binary.
A factory default ford binary file doesn't have such data. thus, saying it's populated into the binary once it's flashed to the PCM and rebooted.
I hope I'm making sense.
- Attachments
-
- Ktag-1.png (82.25 KiB) Viewed 1002 times
-
- KTAG.png (112.03 KiB) Viewed 1002 times