How to get access to the recovery mode of MMX in MIB2 High unit?
Добро пожаловать на Turbo Quattro.
Показано с 1 по 14 из 14
  1. #1
    Новичок
    Регистрация
    05.01.2018
    Сообщений
    10

    По умолчанию How to get access to the recovery mode of MMX in MIB2 High unit?

    Tried to do brand + region conversion days ago. ( AUDI+XX to VW+YY)

    The MMX got bricked after I did flash the boot loader of MMX without update BCT then reboot.

    I think there is security check in boot rom to ensure the validity of boot loader after invested the document of nVidia Tegra 3.

    The document say CPU would be in RCM (recovery mode) under this situation and user could use USB to load correct boot loader to recovery it.

    Does any one know how to get the USB port to access?
    I tried to connect my PC with MIB2 High USB but it not work.

    btw
    Any one know how to get the newest IOC firmware (V850) of MIB2 (For the 5NA035xxx unit...)?
    I want to solve following issue... or other method could be used to solve it?

    [2018-08-19 05:21:42.892] [ERR]@24147 (151587.0): OOcD: received event from OnOffIPC with unknown IO-Ctrl version!
    [2018-08-19 05:21:43.080] [MSG]@24333 (151587.0): OOcS: getHardwareSample: hwSample = 0x20
    [2018-08-19 05:21:43.091] [MSG]@24344 (151587.0): OOcS: getHardwareVariant: IocVariant = 0x43
    [2018-08-19 05:21:43.100] [MSG]@24351 (151587.0): OOcS: IOCBoloMode: 0, if true SYSTEM-ON will be triggered...
    [2018-08-19 05:21:43.106] [MSG]@24353 (151587.0): OOcS: Upd. newSystemState: 104
    [2018-08-19 05:21:43.109] [ERR]@24358 (151587.0): OOcD: received event from OnOffIPC with unknown IO-Ctrl version!
    [2018-08-19 05:21:43.163] [ERR]@24417 (151587.0): OOcD: received event from OnOffIPC with unknown IO-Ctrl version!
    [2018-08-19 05:21:43.205] [ERR]@24459 (151587.0): OOcD: received event from OnOffIPC with unknown IO-Ctrl version!
    [2018-08-19 05:21:43.252] [ERR]@24507 (151587.0): OOcD: received event from OnOffIPC with unknown IO-Ctrl version!
    [2018-08-19 05:21:43.354] [ERR]@24608 (151587.0): OOcD: received event from OnOffIPC with unknown IO-Ctrl version!
    [2018-08-19 05:21:43.434] [ERR]@24689 (151587.0): OOcD: received event from OnOffIPC with unknown IO-Ctrl version!
    Последний раз редактировалось jvkk; 24.08.2018 в 10:52.

  2. #2
    Пользователь
    Регистрация
    03.02.2015
    Адрес
    Belgium
    Сообщений
    33

    По умолчанию

    Hi,

    What is the hardware/software numbers of the original unit and what software did you try to flash ?

    Regards,

  3. #3
    Новичок
    Регистрация
    05.01.2018
    Сообщений
    10

    По умолчанию

    It's a 8S0035xxx MU from Audi TT.
    HW 040
    SW 0016
    IOC version App: 7384
    IOC Variant:= BOLOTYPE_MIB2_MQB + APPLTYPE_MIB2_MQB_TT3

    I tried to manually flash it using ripped 5NA035050 firmware (Japan) with CP disable and install the UNIT on Golf.
    Every thing works except audio and RVC. I thought the main cause is V850 firmware version. There are error message as original post.
    Finally...
    IOC version App: 7473
    IOC Variant:= BOLOTYPE_MIB2_MQB + APPLTYPE_MIB2_MQB

    Compare to a native 5NA unit, the native one IOC version
    IOC version App: 8863
    IOC Variant:= BOLOTYPE_MIB2_MQB + APPLTYPE_MIB2_MQB

    Please let me know how to get the firmware (could it be ripped? Just prefer non-physical method...), I may pay for it if any one has newer IOC firmware.

  4. #4
    Пользователь
    Регистрация
    03.02.2015
    Адрес
    Belgium
    Сообщений
    33

    По умолчанию

    Hi, looks like MMX is dead.

    1 solution, desolder Flash from MMX board and write backup from dump, these emergency update files for MMX are not available for Q7 units. After that you can use fw update to update unit for the right version.

    Mind the region/version else you might get stuck with "can not read meta info" errors

    While in emergency if you have the good version ifs root you can also write that back and then after repair of MMX you can do a normal firmware update.

    Regards,

    regards,

  5. #5
    Пользователь
    Регистрация
    03.02.2015
    Адрес
    Belgium
    Сообщений
    33

    По умолчанию

    Hi,

    Yes, MMX boards die, for sure. You mention that these MMX problems where there even before you try to flash the IFS root.

    By this command it can't work, just put it back in emergency and flash again, also you need to put the address of the file in your command.

    Like I told you, i think problem is in MMX board, take flash off, repair the flash content and flash IFS-root, you will mostlikely be good to go.


    regards,

  6. #6

    По умолчанию

    no chance a USB stick would work? This is what I see when its trying to boot EmergencyMIB

    We assume production mode is not active
    Display: Info3Text Try medium USB
    Try medium USB
    ERROR: /net/mmx/ramdisk/eassist doesn't exist
    Failed to output Info3Text Try medium USB

  7. #7
    Пользователь
    Регистрация
    03.02.2015
    Адрес
    Belgium
    Сообщений
    33

    По умолчанию

    Hi,

    Yes if this was the exact command you flashed the MMX. So only solution is what i gave you.

    Or send it somewhere to get fixed ....

    This USB is after SD card etc. You don't have the required files to update this in that way, only HB will have them.

    With kind regards,

  8. #8

    По умолчанию

    Hi,
    i'm looking for the JTAG pinouts on the two PCI Express like connectors of MIB2 High units.
    Изображения Изображения

  9. #9

    По умолчанию

    Maybe need a JTAGulator.... brute force pins to find it (1.3v)... Definitely won't be the same as the MMI3G+. You will need to power it up though...

  10. #10
    Местный
    Регистрация
    11.03.2016
    Сообщений
    100

    По умолчанию

    Цитата Сообщение от spyderboyant Посмотреть сообщение
    Have you seen an MMX board die before?
    I cannot believe this happened. Was working 100% until I telnet to the unit and ran "flashit -a 54000 f ifs-root.ifs" - I missed the "-d" argument to reset the bits and hence corrupted the image.
    /net/rcc/usr/bin/flashit -a 540000 -f ifs-root.ifs (which I FTP from update SD card - same FW version as on car"
    *** programming ...
    *** verifying ... flashit: FAILED!!!
    Could it be V850 chip?
    I've seen some MMX bad boards Most was bad nor.
    that flashit , did you run it in eso console or rcc?
    V850 is not the problem here.

  11. #11
    Местный
    Регистрация
    11.03.2016
    Сообщений
    100

    По умолчанию

    I hope you have a backup of that as you cant put just any image.
    There is a check in bootloader and some of the images are hardware dependent and will simply not boot.

  12. #12

    По умолчанию

    Is there a way to backup the NOR without removing ?

  13. #13

    По умолчанию

    Цитата Сообщение от johnson Посмотреть сообщение
    Is there a way to backup the NOR without removing ?
    yes. You need "root" access. Then you can use the QNX commands "dd" or "cat" to copy to the SDCard or USB key. If no root, only other way is JTAG...

  14. #14

    По умолчанию

    I am currently analyzing the BCT and boot loader. But I need other examples.
    If someone would like to help please upload the following on mega.nz or similar:
    - a dump of fs0 from MMX (cat /dev/fs0> /fs/sda0/fs0) packed with 7z
    - Short description: train, version, part number
    - output of: for i in `ls /dev/nvsku/`;do echo -n "$i: "; cat /dev/nvsku/$i; echo ; done

    Otherwise also by PM.
    Последний раз редактировалось johnson; 17.12.2018 в 21:57.

 

 

Ваши права

  • Вы не можете создавать новые темы
  • Вы не можете отвечать в темах
  • Вы не можете прикреплять вложения
  • Вы не можете редактировать свои сообщения
  •  
Back to top