Turbo Quattro

**Kastrati** » Чт дек 03, 2020 9:27 am

ivelliosy писал(а):Hey everyone.

Can I flash my rcc_fs0 backup to rcc chip via telnet?

Because right now my rcc doesn't contain persistence folder or fecs I forced to install EU firmware to US unit. (Delphi Audi MHS2)

What should be the correct command via telnet for rcc_fs0 flashing from backup?

on -f rcc flashunlock
flashit -p / net / rcc/ dev/ fs0 -d -f /net/mmx/fs/sda0/rcc_fs0.img
on -f rcc flashlock

**ivelliosy** » Ср дек 02, 2020 10:57 pm

Hey everyone.

Can I flash my rcc_fs0 backup to rcc chip via telnet?

Because right now my rcc doesn't contain persistence folder or fecs I forced to install EU firmware to US unit. (Delphi Audi MHS2)

What should be the correct command via telnet for rcc_fs0 flashing from backup?

**titiura** » Чт авг 20, 2020 1:34 am

@simaservis1108[CENTER] [/CENTER]У меня такая же проблема, поможете?

**simaservis1108** » Сб авг 15, 2020 2:39 am

I can help you restore it,just dont brick it any further

**TT-2016** » Пт авг 14, 2020 12:16 am

KBN писал(а):Not JTAG, you mean serial. On quadlock, find pinout and you can directly get to MMX console and RCC. If RCC dead, only reprogram NAND with programmer, if RCC emergency still alive - you can put it to emrgency download mode (IOC will not power off the device), and then use 'flashit' for RCC and MMX.

I think I have a similar issue.
My MMX is dead, but RCC emergency can still be access, however no /net folder - No USB/SD/CD.
How do I get into the the emergency download mode?

**fouras** » Ср авг 12, 2020 2:05 pm

[quote = KBN; 645352] Not JTAG, you mean serial. On quadlock, find pinout and you can directly get to MMX console and RCC. If RCC dead, only reprogram NAND with programmer, if RCC emergency still alive - you can put it to emrgency download mode (IOC will not power off the device), and then use 'flashit' for RCC and MMX. [/ QUOTE]

I try to access the unit via the quadlock pin J5_TX/RX to access RCC
Is anyone succeed to access IPL by connecting J5_RxD to ground?
Is it mandatory to go with the board edge connector?

I think my RCC has been brick but I don't know if IPL FS has been corrupt or not.
I want to know if I can recover RCC with IPL technic (zmodem, ...) or If I had to unsolder the chip (I'm not equipped to)
Thanks a lot

**fouras** » Вт авг 11, 2020 12:58 am

I succeed to connect to eso pins on quadlock
Here is the content at start :

<.startup><cpu>: [tmon] Probing for device adt7461
<cpu>: nVidia Quickboot 17.14.13 (Build Feb 13 2017)
<cpu>: modified by e.Solutions GmbH
<cpu>: Loading stage 2 primary bootloader...
<cpu>: Stage2 loaded
<cpu>: Primary partion invalid, trying to boot from recovery image
<cpu>: jumping to kernel
Starting serial driver UART-B...
Starting i2c interface for PMU
Starting devg-nvpower
Initializing i2s
Project ID: 61852 board revision: 702
PCIE: port 1: link down, retrying
PCIE: port 1: link down, retrying
PCIE: port 1: link down, retrying
PCIE: port 1: link down, retrying
PCIE: port 1: link down, retrying
pcie_driver_startup axi_regs mapped
afi ok
rp0 ok
rp1 ok
rp2 ok
posix_typed_mem_open success: 4
translations done
checking rootports
PCIe Rootport 1 link up timed out
.PCIe Rootport 1 link up timed out
.PCIe Rootport 1 link up timed out
(...)
.PCIe Rootport 1 link up timed out
.PCIe Rootport 1 link up timed out
Unable to access /dev/socket
Path=0 - Generic SDHCI
Path=0 - Generic SDHCI
.PCIe Rootport 1 link up timed out
Path=0 P-a t
h= target=0 lun=0 Direct-Access(0) - ram Rev: 0
- Generic SDHCI
target=0 lun=0 Direct-Access(0) - MMC:144 HCG8e. Rev: 0.3
.PCIe Rootport 1 link up timed out
(...)
.PCIe Rootport 1 link up timed out
[efu.Main] INFO: Emergency Flash Utility (Production Build)
[efu.Main] INFO: Production Build
[efu.Main] INFO: Copyright (c) 2011 - 2014 e.solutions GmbH. All rights reserved.

[efu.Main] INFO: Starting graphical user interface
[efu.Main] INFO: Establishing IOC communication
[ResMgrI2C.I2cIoc] INFO: First client connected. Start I2C slave
[ResMgrI2C.I2cIoc] INFO: I2C slave thread started
[efu.Main] INFO: Starting monitor
[efu.Main] INFO: Read project identifier: 61852.
[efu.Main] INFO: Detected board revision 702.
[ResMgrI2C.I2cIoc] INFO: Enabled I2C on IOC
[efu.Main] INFO: Waiting for RCC to enter emergency mode
login: .PCIe Rootport 1 link up timed out
[efu.IOC] INFO: Use CRC: true
.PCIe Rootport 1 link up timed out
[efu.Main] ERROR: RCC failed to enter emergency mode.
[efu.Main] INFO: Main partition is invalid.
[efu.Main] INFO: Starting emergency flash utility
[efu.EmergencyFlashUtility] INFO: Starting EFU Version 2.4.0
.PCIe Rootport 1 link up timed out
[efu.EmergencyFlashUtility] INFO: Searching for internal update info.
[efu.EmergencyFlashUtility] INFO: Use external update info.
[efu.EmergencyFlashUtility] INFO: Please insert update media with update info or reboot.
[ResMgrI2C.I2cIoc] ERROR: Timeout in toEsoError (/home/jenkins/workspace/MMX2_rel_SOP1_VW_Build_evo/systools_src/ooc/i2cioc/i2cioc.c:323)
.PCIe Rootport 1 link up timed out
[ResMgrI2C.I2cIoc] ERROR: Timeout in toEsoError (/home/jenkins/workspace/MMX2_rel_SOP1_VW_Build_evo/systools_src/ooc/i2cioc/i2cioc.c:323)
.PCIe Rootport 1 link up timed out
[ResMgrI2C.I2cIoc] ERROR: Timeout in toEsoError (/home/jenkins/workspace/MMX2_rel_SOP1_VW_Build_evo/systools_src/ooc/i2cioc/i2cioc.c:323)
.PCIe Rootport 1 link up timed out

It say that "RCC failed to enter emergency mode"
of course, it seems to have no prompt when press enter

**KBN** » Пн авг 10, 2020 5:52 pm

Not JTAG, you mean serial. On quadlock, find pinout and you can directly get to MMX console and RCC. If RCC dead, only reprogram NAND with programmer, if RCC emergency still alive - you can put it to emrgency download mode (IOC will not power off the device), and then use 'flashit' for RCC and MMX.

**fouras** » Пн авг 10, 2020 3:54 pm

KBN писал(а):flashit -p /net/mmx/dev/fs0 -d -f /net/mmx/fs/sda0/mmx_fs0

Thank you, this was the command I should have typed when I had access to the jtag
I think I made a lot of errors trying to flash either RCC or MMX without knowing there is 2 differents FS
Now, I think I'm stuck with the emergency you see above
[CENTER]

Вложение 20200809_174821.jpg больше недоступно

[/CENTER]
After I tried to restore a dump on /dev/fs0 instead of /net/mmx/dev/fs0
May I have kill the RCC FS?
The last time I check, the jtag connection didn't respond
What is the next step ?
Does-it exist a "last chance" procedure to flashback a FS on RCC?
I've got the two originals dumps of FS rcc_fs0 and mmx_fs0
Thks

**KBN** » Пн авг 10, 2020 1:03 pm

flashit -p /net/mmx/dev/fs0 -d -f /net/mmx/fs/sda0/mmx_fs0

**fouras** » Вс авг 09, 2020 11:53 pm

Hello, thank you for your answer.
I tried with the official firmware on a usb stick and sd card but nothing. It's not emergency flash assistance but emergency flash utility.

I tried downloading the whole file system (fs0 the one that I dumped before) with the flashit command but I think I just bricked my unit.
Now I lost the uart jtag interface and attached 4 new print screens which appear at the start.
I don't know if the IPL is working (not trying) and anyway I don't know how to restore.

I'm desperate

**mibmaster** » Вс авг 09, 2020 5:38 pm

First try to insert a SD card with exactly the same SW, as it is currently in the unit. The unit should recover. If it won't work, I would try other ways...

**fouras** » Вс авг 09, 2020 1:31 pm

Hi Everybody
I'm a french guy stuck in the moud with his Mib2High unit on a passat variant 2015 with discover pro.
After a failed flash of my unit, i'm in mode "Emergency Flash Utility Version 2.4.0
I've got Jtag access and I can mount SDcard and USB and command flashit / flashlock / flashunlock are available
Can anyone help me to recover?
I dumped the RCC and MMX before the flash but I don't know how I can restore those dump.

Thanks a lot for your help guys

You can see the complete start log in the attached file

Turbo Quattro

Recover a vw mib2 unit from Emergency flash assist

Ответить

Развернуть Обзор темы: Recover a vw mib2 unit from Emergency flash assist

Recover a vw mib2 unit from Emergency flash assist