3P's TCCS Disassembly/Analysis

Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
I have not pulled the code out of the 42 pin MCU, but all indications from others who have are that is shares the same architecture and instruction set as the 64 pin version. There is an incomplete pinout of the 42 pin chip on Toyota Wiki http://toyota.kgbconsulting.ca/wiki/Pinout_42_pin

Obviously, with fewer pins some IO capability is lost, and this would affect some of the IO registers that are available in the 64 pin version. Obtaining further information will require some experimentation.
 
Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
Yes, I know where in the code they check for fuel cut, RPM cut, and so on. My problem right now is getting my extender board to work reliably. Damn thing is being a pain in the butt.
 

Nick M

Black Rifles Matter
Sep 9, 2005
8,894
38
48
U.S.
www.ebay.com
How about now? I want to run the larger 1UZFE meter with the screw in, and raised overboost cut with slightly leaner mixture than Toyota delivered 9.7:1 under load. You have no consideration for my feelings. ;)

I keep delaying a piggyback because I want to avoid that route.
 
Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
Yeah, me too!

This project is being worked pretty hard, but has been slow going. If its any consolation, it works some of the time, but that's not good enough to make it usable in the field, and tracking down the problem has been very tough.

Nick M;1603538 said:
I keep delaying a piggyback because I want to avoid that route.


---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------

I don't know much about the 1J ECU. Is it a two processor design like the 2J? And what kind of map do you need? There is work underway to map out the I/O for the dual processor MR2 ECU, but I'm not sure how relevant that is for the 1J.



lom51;1603566 said:
Hello!
I need address map for 1JZ-GTE ecu firmware.
Can help me?
 
Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
I loaded this code into IDA and it looks like typical ECU code form Toyota. Without knowing how the sensors and such are mapped to the MCU ports on a 1J ECU, it is hard to proceed further.

The data file you sent is a little weird in that it has 32770 bytes of data, but the first 20482 bytes are junk and can be discarded. It is designed for a 16kB processor, which is one of the later versions. It probably runs at 16MHz too. The code entry point address is 0xC005.

lom51;1603566 said:
Hello!
I need address map for 1JZ-GTE ecu firmware.
Can help me?
 

figgie

Supramania Contributor
Mar 30, 2005
5,224
16
38
50
Twin Cities, Minnesot-ah
Folks

QUIT with the I needs.

Jon is working hard along with the rest of the group on this. They don't need any more presure than what they have. Let them do thier work!

Any other posts asking to look at any other ECU and I will start whacking posts and handing out infractions!
 
Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
This is the 7MGTE ECU running in external mode on the FLASH board. The code is being run in SRAM, so it can be changed on the fly. All the tables, etc. can be changed in real time. A nice GUI to do that is being worked on, but is not ready yet.

[video=youtube;4SSAQbanRZw]http://www.youtube.com/watch?v=4SSAQbanRZw[/video]

In the video, the ECU data in RAM is being interrogated from a PC connected to the board via USB. Data rate is 4.8-6kb/s. The first 16 bit number is the ECU timer, then some data registers, and the last 16 bit number is the code serial number 1332.

[video=youtube;LHjOJvRx8WE]http://www.youtube.com/watch?v=LHjOJvRx8WE[/video]
 
Last edited:

auto351

New Member
Oct 22, 2008
19
0
1
Sydney
Hi,

On the data acquisition side of this at what speed will the data be able to be read and written to the board & how many registers can be dumped at a time?

Manuel
 
Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
The ECU permits one 16 bit read from RAM every 2.1ms (7.5kB/s). That is the best that you can do without rewriting the ECU diagnostics code. The serial port is running at 1 Mb/s, so more could theoretically be extracted, but would need to be careful since it is shared with the ADC.
 

JonS

New Member
Apr 9, 2009
25
0
1
Cambridge
darrylp;1621396 said:
has anyone looked into reading the RAM, in an alternate cylces of the cpu accessing the memory ?

That's a very good point actually, I don't think anyone has yet looked in to using the 'spare' data bus cycles for reading the RAM.

It should theoretically be possible for a 2nd processor to read from/write to the RAM when the Denso MCU isn't using the data bus. A memory access cycle only uses the data bus for half of the cycle, which would allow time to sneak in another access before the Denso MCU needs to use the data bus again.

It would certainly need a larger CPLD though as the current design is pushing the limits of the CPLD being used.
 
Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
The RAM is internal to the CPU, making reads on alternate cycles not an option. Would have to shadow the RAM to an external chip to do this. Given that portions of the internal RAM are retained during engine shutdown, this would be some work to implement. If throughput becomes an issue it may make more sense to add some code in the ECU to improve diagnostic bandwidth.
 
Oct 11, 2005
3,816
16
38
Thousand Oaks, CA
The daughter board should work on the GE. The only reason it might not is that early GE ECUs are single board and thinner, and the daughter board might not fit.

The ECU hardware between the GE and GTE is completely different, so a firmware change will not swap between the two.

It does seem possible to swap between M/T and A/T with only a firmware change for the GTE. The GE is even easier, you just need to add a resistor.
 

Manianac

New Member
Oct 9, 2010
11
0
0
Indy
So I saw the CPU pinouts for the GE, any chance you can post the differences with the GTE? I figure there are some with the ASR0 using the KM airflow sensor if I'm not mistaken, but I was hoping you could post the entire pinout