I know this topic is almost hush hush but I hope someone can tone in and give me some pointers. I have an 09 MCS ECU the Tricore TC1766. To read the internal flash, I am using Galletto v54 which proved to be working fine with TC1797 and TC1767 tricore chips. after i connect the wires and the boot mode wire per the document, I get an error. the question is, how can i get the internal flash from this ECU?

 

What pads/vias are you probing to?

 

Per the diagram, it is a singe wire with a 1k ohm resistor to be connected to a solder point leading to the chip.

 

 

Are you using the supplied wiring harness? If so, are you using the "gray" wire to connect to the boot pad? The reason I'm asking is that the included harness may have a 1k resistor built into the gray wire - If you've added your own resistor you may have too much resistance to trip the boot mode.

As far as I can see, you're on the right pad...

 

Yes, I am using the supplied harness. you are also correct about the gray wire with a built in resistor. no additional resistors are used. I am not sure why this particular ECU is not responding.

 

Is the error specific or just a generic communications problem?

 

The error is specific to booting the ECU.

 

 

Look up the datasheet for the TC1767 and TC1766 online, and check that the pinout did not change. The datasheet will also give you the details for the boot mode.

 

 

I scanned through the pin out of the two chips, they are not the same. they both talk about booting signal, but they done tell you how to achieve it for example where to put a resistor or how many ohms etc

 

I tapped each on to be sure your arrow didnt move, but no lock! The ECU is know to work and the reader is also known to work :(

 

Boot pin configuration depends on the board/processor revision as well as the hardware used to read the ECU. Some are the same and others are not. Is this the pin you used?

 

This is exactly what I used. Other ECUs like TC1797 and TC1767 were read fine. This one is giving me hard time.

 

 

Don't really have any other info then unfortunately. Might be a corrupted protocol file or an issue inside the cracked software on the clone your using but that's the problem with knock-offs. No updates, no support, etc. I'm not gonna get on a soapbox about other aspects of using a clone. I don't need to.

Just be aware that once in a blue moon even real tools can brick an ecu. However, with support I've never seen one I couldn't recover, read and successfully write.

Are you trying to clone the ecu or just read it out for educational purposes?

 

OP has a 1766 not 1796.

 

MiniToBe you 100% sure the ecu is good?

 

Yes I'm trying to clone it since I cannot guarantee it fixing the issue. You could be right about the corrupted protocol for this Chip. The ECU is in good working order with some codes.

 

Yeah...I'm having trouble with TC1766...but what are you using; Ktag or Kess or something elase?

 

 

can you attached the boot mode manual here? or can you see if/how the MED17 with TC1766 is covered/wired?

 

My go to for TriCores without an OBD solution or for cloning ecu's. K-TAG Master w/K-Suite 3.19. The following image is Copyright Alientech s.r.l. For the N14 Mini TC1766 use protocol 152. Original Kess V2 will read and write the N14 via OBD using protocol 206. However, to clone you need K-Tag and boot mode.


As noted previously, same ecu but different tools using a different boot pin.
Maybe re-installing your software will work. If not any local tuner who's serious about his work should have the tools to do this for you.

 

I installed the software a handful of times. This boot pin eventually traces to the same pin F.G. Technology uses...I think at this point, I need to get me a K_tag. It is an investment that needs to happen. I will get one and report back.

Now off I go to my 95 Legend Cpe for an engine rebuild.

I want to thank all of you for the feedback. I really appreciate it.