MicroHacker Forum

Agree, I also guess so.

As I was sayig above it seem to be the case because pulling down corresponding to EXT_BOOT pin has expected effect - no logo is shown and device sends something out via pin correspondong to OUT pin if we use signal names from this page https://mk4-wiki.denkdose.de/artikel/na ... chse_x3806

I didn't try MAIN_RESET signal yet but I'm pretty sure with the result.

Found the image again. It may not of any use because the Bosch partnumber is a bit different (7 612 830 092 instead of "095") but maybe the HW-plattform is the same. Also this dump is taken from a locked device. But to analyze the content and just to program to see if it makes a difference to your reboot-loop one, it will be good enough.
You could also try to read the current content of your broken device, erase the flash and program it back again. In some rare cases this is sufficient.

You could also put an image of your Update-CD here, if you like.

The content from the CD is able to recreate mostly everything on the device, but some things are special, like the bootsector. Also the Flash contains some sort of filesystem, so it is not simply a 1:1 copy of the CDs files.

The FX update-content will not be of any use, because the board is different in many ways, even if they are out of the same "family". You should better not try to mess around with it in your device...

What's interesting is, that the navigation-unit seems to know fixed speed-cams, as you find many text messages of it in the dump

Shuher wrote: ↑20 Apr 2020, 20:15 I didn't try MAIN_RESET signal yet but I'm pretty sure with the result.

It's not MAIN_RESET it is MAN_RESET, short for "manual reset" and simply resets the OMAP while put GND on this pin.

Maybe, some day i get my hands on such a device for a good price (mainly a defective one), because all i can help you is in pure theory. But it seems they do not have the same problems with RAM, so the prices, even here in Germany are very high.

Thanks for the image - I really hope that mine is alive at least partially and in worst case I will be capable to transfer sector 507 contents.

I've uploaded the update ISO in this topic viewtopic.php?f=3&t=78&p=2111#p2111

Found another image. I also assume that they will use the same PIN-algos as the other Bosch-Devices use. Some said New-Algo-5 is working but i can't check this.
What's really neat of those device is, that they show the serial in the display, when you enter the wrong PIN. No need to rip it out the center trim...

Yesterday I managed to do one more check with another FT232HQ based JTAG adapter (J-link is still travelling while I cannot wait and want to do something around it). Unsuccessful so far - connection is still unstable, sometimes I even get different TAP IDs for same TAPs...

But I have found out that EXT_BOOT pin being pulled low indeed puts my unit into stable standby mode allowing uninterrupted JTAG connectivity so for it this may be an equivalent of Touareg-mode pin. And the unit doesn't react at all on MAN_RESET and V850_HMI_WDT pins equivalents. Just to share the findings.

Also, the idea that this 30 pin connector is just a join of 16+14 pin MicroMatch connectors from Ford satnavs got proven - GND connections and Vcc +14V seem to be on a proper places and both UART_OUT pins are transmitting something out once device is powered on. So until we found repair manual for this device with definitive pinout I guess we may state that the below one is true:

Great findings! I would be glad to put this onto my Wiki, as other information we find.

Meanwhile I got my spare S29GL512 delivered, hope that it's genuine or at least workable, huh Though, it looks ok so if the one in my unit is faulty I'm ready to replace.
And still waiting for Jlink - it is already travelling for over a month since I've ordered it

Soldering BGA needs some special knowledge and tools. Also i did not find a defective flash chip on all satnavs i ever repaired...