востановление поврежденных голов +/ damage head unit repair - Страница 40
Добро пожаловать на Turbo Quattro.
Страница 40 из 46 ПерваяПервая ... 303839404142 ... ПоследняяПоследняя
Показано с 781 по 800 из 918
  1. #781
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    IPL: Audi 3G 9308 (SH7785) / QNX 6.3.0 [PL_qnx_ipl-3g_9308-sh7785_18282A, built 2003/06/18_15-16-25_UTC]
    CPU: SH7785 (>= 5th cut, clk mode 20. 4xDDR), 792MHz
    RAM: 512 MB (probed, DBCONF=e30002)
    FLASH: Spansion S29GL512N (32bit): 512 sectors x 256K
    FPGA: PL_MMI3G_PLUS_FPGA_9411_D1_11384A (0ms)


    Entering CLI, type '?' or 'help' for help


    => boot 1c0000
    starting image @801c0000 ...


    Startup: PL_qnx_startup-sh7785_11292A, built 2011/07/19_08-03-38_UTC
    RAM : 128 MB @0x08000000
    RAM : 128 MB @0x40000000
    RAM : 256 MB @0x50000000
    FLASH: 128 MB @0x00000000
    FPGA IRQ: Interrupt Controller ID:33 Ver:2.1.0 ILVL:7 Lines:255


    System page at phys:0800a000 user:0800a000 kern:8800a000
    Starting next program at v88046ae0
    ------------------------------------------------------
    Welcome to QNX 6.3.2 (RL_qnx_os_632_PSP3_09423A) MMI3G Audi EMERGENCY SETUP 15325A
    starting pci driver
    *** init FPGA registers ***
    [pcidma] PL_qnx_pcidma_FMod08363A_09274A, built 2009/07/02_11-10-37_UTC
    starting dev-ipc for IOC
    initialize IPC Driver
    starting network driver
    starting atapi driver - setup device /dev/cam0
    [pcidma] finished.
    [pcidma] finished.
    xpt_configure: No eide interfaces found
    Unable to access "/dev/cam0" (2)
    starting devc-pty
    starting flash driver
    starting SDCard driver
    Unable to access "/dev/io-net/en5" (2)
    starting with no network driver
    ================================================== =========
    Emergency IFS is started. Emergency app tries to restore
    the application.
    ================================================== =========
    53265 running /usr/bin/devg-NVTIRM
    DMA is Disabled
    dma disabled, interrupt thread priority = 100
    53267 running /sbin/io-media-nvidia
    53268 running /usr/sbin/io-display
    53269 running /usr/apps/MMI3GEmergencyApp
    ================================================== =========
    Emergency shell started, fix your system and restart again
    ================================================== =========
    discplayer_init: IN
    nvidia_render_manager_init: IN
    INvmRenderManager::GetNvmRenderManager (&pRenderManager);
    er = pRenderManager->Init(oConfig);
    # App FPGA valid 1
    Emergency FPGA valid 1
    Disabling IOC watchdog


    EmergencyApp-MMI3G: version 37.26.2098, date of build 07.08.2015
    pRenderManager->Open()
    nvidia_render_manager_init: OUT
    discplayer_init: OUT
    discplayer_init
    discplayer_init: IN
    nvidia_render_manager_init: IN
    nvidia_render_manager_init: OUT
    discplayer_init: OUT
    dvdtrackplayer_init
    discplayer_init: IN
    nvidia_render_manager_init: IN
    nvidia_render_manager_init: OUT
    discplayer_init: OUT
    dvdnavigator_init
    created navigator control point with 8249288
    mixer_init: IN
    mixer_init: OUT
    NvTRACELEVEL set to 3 (Level Info)
    nVAudio_init: IN
    nvidia_render_manager_init();
    nvidia_render_manager_init: IN
    nvidia_render_manager_init: OUT
    nVAudio_init: OUT
    installing audio decoders
    installing video decoders
    nVAudio_init: IN
    nvidia_render_manager_init();
    nvidia_render_manager_init: IN
    nvidia_render_manager_init: OUT
    nVAudio_init: OUT
    OnIpcGetCaptureUnitSourceCount
    Number of displays: 6
    Number of layers: 9
    Graphics init was successfull: DisplaySize is 800x 480
    The FPGA for the application is valid!
    Emergency application will do nothing!
    result of running command start_efs_driver.sh is 0
    Wait for HBpersistence...
    Wait for HBpersistence...


    #
    #
    #
    #
    #
    #
    #
    #
    #

    Виснет.
    Help. Что ему нужно. Железо...
    result of running command start_efs_driver.sh is 0 ??????

  2. #782

    По умолчанию

    After a while, the emg app will format the persist partotion of the flash and rebuild it from backup file located on efs-extended...

  3. #783
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    Цитата Сообщение от Tschako Посмотреть сообщение
    After a while, the emg app will format the persist partotion of the flash and rebuild it from backup file located on efs-extended...
    the board hangs. then nothing happens. why? maybe I'm wrong. You need to unpack the firmware, look for this script, open it in a notebook, watch what it should execute.

    IFS-root...

  4. #784

    По умолчанию

    My comment points to the missing efs-persist partition... The systems holds a compressed backup of the last working version of persist on the backup folder in efs-extended. Are you able to reflash the missing persist in that situation from sd? You tried?

  5. #785
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    Цитата Сообщение от Tschako Посмотреть сообщение
    My comment points to the missing efs-persist partition... The systems holds a compressed backup of the last working version of persist on the backup folder in efs-extended. Are you able to reflash the missing persist in that situation from sd? You tried?
    I bought a used unit for experiments.


    As it turned out, the unit was under repair. before it fell into my hands.


    two flash flashed from the board. under the eprom chip, the tracks tore. the block was dead. and they decided to sell it.


    I fixed all these problems. Jtag sees. UART sees. Log is. Seemingly.....


    But, the block somehow hangs. Does not work stably or something.


    I managed to record completely slash. but this is not enough...


    What drew attention.


    on the working block. (exactly the same but working) let's say a completely clean flash.


    there is no light in the optics connector.


    1 fill ipl. We see the log.


    2 fill in the FPGA and the optics start blinking. This is all on the work board.


    so here.


    but there is no optics on this block of light.


    okay. as I wrote above. I spill completely slash. and optics shine.


    for today. I erased the entire flash.
    Flooded
    IPL, FPGA, FPGA EM, IFS EM.
    jtag connection.


    flashit, cannot be used.
    The block hangs ....
    #
    #
    #. This is the latest on the terminal.
    The display is black.
    I think. This is a hardware problem.


    OS81050AH removed from the board .. It's not about that. Somewhere before.
    OS81050AH without this chip. the work unit is loading. boot 1c0000 and green display.
    So I can assume that the problem is not in this chip.
    Последний раз редактировалось Clark; 12.07.2020 в 18:42.

  6. #786
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    Цитата Сообщение от Tschako Посмотреть сообщение
    The image file "efs-persist.bin" is not available via the Firmware Update files.
    You have to extract it, from another, fully functional main unit with the following command:

    "cat /dev/fs0p3 > /fs/sd0/backup/flashdump/fs0p3_efs-persist.bin" for the 1st SD Slot of the Unit.

    Now you have the flashdump image of the efs-persist partition (fs0p3), to flash it on the broken unit as descriped above...
    # cat /dev/fs1p3 > /mnt/umass0100t12/backup/flashdump/fs0p3_efs-persist.bin
    Read-only file system

    Help..

  7. #787

    По умолчанию

    you have to re-mount the destination as writable.

    use the "mount -uw" command

  8. #788
    Новичок
    Регистрация
    23.02.2020
    Адрес
    Sinn, DE
    Сообщений
    5

    По умолчанию

    есть у кого содержимое efs-persist от MU9498?

  9. #789
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    Цитата Сообщение от lau-de Посмотреть сообщение
    есть у кого содержимое efs-persist от MU9498?
    Зачем ? Что собрался делать ?

  10. #790
    Новичок
    Регистрация
    23.02.2020
    Адрес
    Sinn, DE
    Сообщений
    5

    По умолчанию

    уже нашёл, всё хорошо

  11. #791
    Новичок
    Регистрация
    01.09.2020
    Адрес
    Kiev
    Сообщений
    4

    По умолчанию

    Привет. Если возможно, помогите поднять 3G+.
    Такая история - была американка Q7 c прошивкой 814, при установке европейской прошивки в ручном режиме отметили чекбоксы в разделах:
    DVD -> Application 0x502000->Application 0x502000
    AH6 -> Application 0x49444->0x49445
    В итоге голова включается, но видимо из-за невозможности инициализации AH6 постоянно ребутится через минуту.

    Может быть кто-то может дать в личку контакт в телеграм или вайбер?
    Плиз, оч. срочно

  12. #792
    Новичок
    Регистрация
    09.05.2019
    Сообщений
    15

    По умолчанию

    Цитата Сообщение от Fisher_piu Посмотреть сообщение
    Привет. Если возможно, помогите поднять 3G+.
    Такая история - была американка Q7 c прошивкой 814, при установке европейской прошивки в ручном режиме отметили чекбоксы в разделах:
    DVD -> Application 0x502000->Application 0x502000
    AH6 -> Application 0x49444->0x49445
    В итоге голова включается, но видимо из-за невозможности инициализации AH6 постоянно ребутится через минуту.

    Может быть кто-то может дать в личку контакт в телеграм или вайбер?
    Плиз, оч. срочно

    так а в чем вопрос - вынима юнит rx - tx - gnd \ ipl - emergency команду \ sd карту с прошивкой в слот - и поднимешь ..

  13. #793
    Новичок
    Регистрация
    01.09.2020
    Адрес
    Kiev
    Сообщений
    4

    По умолчанию

    немного сложнее оказалось, один чип памяти не проходил тест - пришлось заменить (оба для надёжности).
    типа восстановили, в машине она вроде как работает, но исчезла загрузочная картинка (лого).
    насколько я понимаю, нужно заново начисто установить текущую прошивку.
    через user defiened mode не получается, не вижу пунктов Muinic.. muioc и прошивка после нажатия "обновить" просто вырубает ГУ.

    поскольку сейчас прошивка евро 942, то в зеленом меню нет emergency update, наверное нужно скриптом активировать и запустить оттуда сначала emergency update, а потом уже снова user defiened mode ???

    если emergency update из зеленого меню запуститься, то он мне "прибьет" BOSE ? или не тронет? потом user defiened mode ещё раз и выбрать всё-всё кроме BOSE ?

  14. #794
    Новичок
    Регистрация
    09.05.2019
    Сообщений
    15

    По умолчанию

    как вариант да = скриптом можно пробывать активировать emergency update \ bose не прибьет, не тронет \ потом user define mode и не выбираем bose

  15. #795
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    А вы же обновили v850... очень интересно...

  16. #796
    Новичок
    Регистрация
    01.09.2020
    Адрес
    Kiev
    Сообщений
    4

    По умолчанию

    Цитата Сообщение от cultos Посмотреть сообщение
    ... потом user define mode и не выбираем bose
    нужно все-все пункты вручную отметить, кроме bose, или она сама выберет, чего не хватает ? например захожу в DVD, там отмечаю и bootloader и application и так по всем пунктам? или достаточно только application отметить?
    насколько критично если в user defined mode нет в списке устройст для обновления muinic, muioc..
    извините за нубские вопросы..

  17. #797
    Новичок
    Регистрация
    09.05.2019
    Сообщений
    15

    По умолчанию

    все пункты во всем списке - кроме Bose - должны быть сняты галочки

  18. #798
    Новичок
    Регистрация
    01.09.2020
    Адрес
    Kiev
    Сообщений
    4

    По умолчанию

    кто-то может поделиться проверено рабочим скриптом для возврата emergency update на 3G+ в прошивке 0942 ? можно в лс

  19. #799
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    Можно в общий доступ , скрипт.

  20. #800
    Пользователь
    Регистрация
    18.09.2019
    Адрес
    Ростов-на-Дону
    Сообщений
    88

    По умолчанию

    closep
    BIOS: No packet found!
    IPL: Audi 3G 9308 (SH7785) / QNX 6.3.0 [PL_qnx_ipl-3g_9308-sh7785_13382A, built 2013/09/17_15-16-25_UTC]
    CPU: SH7785 (>= 5th cut, clk mode 20. 4xDDR), 792MHz
    RAM: 512 MB (probed, DBCONF=e30002)
    FLASH: Spansion S29GL512N (32bit): 512 sectors x 256K
    FPGA: PL_MMI3G_PLUS_FPGA_9411_D1_09422A
    (0ms)
    *** emergency FPGA loaded!
    *** Old-fashioned mark found on IFS @0x1c0000: .zero=0x3000001a
    starting image @1c0000 ...


    Startup: PL_qnx_startup-sh7785_11292A, built 2011/07/19_08-03-38_UTC
    RAM : 128 MB @0x08000000
    RAM : 128 MB @0x40000000
    RAM : 256 MB @0x50000000
    FLASH: 128 MB @0x00000000
    FPGA IRQ: Interrupt Controller ID:33 Ver:2.1.0 ILVL:7 Lines:255


    System page at phys:0800a000 user:0800a000 kern:8800a000
    Starting next program at v88046ae0
    ------------------------------------------------------
    Welcome to QNX 6.3.2 (RL_qnx_os_632_PSP3_09423A) MMI3G Audi EMERGENCY SETUP 15325A
    starting pci driver
    *** init FPGA registers ***
    [pcidma] PL_qnx_pcidma_FMod08363A_09274A, built 2009/07/02_11-10-37_UTC
    starting dev-ipc for IOC
    initialize IPC Driver
    starting network driver
    starting atapi driver - setup device /dev/cam0
    [pcidma] finished.
    [pcidma] finished.
    xpt_configure: No eide interfaces found
    Unable to access "/dev/cam0" (2)
    starting devc-pty
    starting flash driver
    starting SDCard driver
    Unable to access "/dev/io-net/en5" (2)
    starting with no network driver
    ================================================== =========
    Emergency IFS is started. Emergency app tries to restore
    the application.
    ================================================== =========
    53265 running /usr/bin/devg-NVTIRM
    DMA is Disabled
    dma disabled, interrupt thread priority = 100
    53267 running /sbin/io-media-nvidia
    53268 running /usr/sbin/io-display
    53269 running /usr/apps/MMI3GEmergencyApp
    ================================================== =========
    Emergency shell started, fix your system and restart again
    ================================================== =========
    discplayer_init: IN
    nvidia_render_manager_init: IN
    INvmRenderManager::GetNvmRenderManager (&pRenderManager);
    er = pRenderManager->Init(oConfig);
    # Fpga header is not 0x4744482e (0xffffffff)!
    App FPGA valid 0
    Emergency FPGA valid 1
    Disabling IOC watchdog


    EmergencyApp-MMI3G: version 37.26.2098, date of build 07.08.2015
    Unable to post device
    common/include/NvRefCountImpl.h:134: NV_ASSERT failed: __INvRefCountIMPL_m_ulRefCount == 0


    Process 53267 (io-media-nvidia) terminated SIGSEGV code=1 fltno=11 ip=0805c07c ref=00000000
    gf_dev_attach() failed with 2
    Set DisplayStatus to 2
    OnOff: process IPC event HWsample 225 HWvariant 111 FinalShutdown 0
    pidin ar devf-generics: /usr/sbin/devf-generic -r -b9 -t4 -p400,32 -s0x0,128m,,,,,,5000,100 -D -a . HW 225
    IOC reports wrong HW 225. We use f1 (/usr/sbin/devf-generic -r -b9 -t4 -p400,32 -s0x0,128m,,,,,,5000,100 -D -a )
    SWDL: startUpdate HW index 241, variant 9411
    OnOff: phase Scan metainfo
    We have to erase the FPGA, init the FPGA persistence and delete the orphaned headers (if there are any).
    OnOff: phase Erase
    OnOff: Progress 000
    dev_fd == 7
    devctl returned 0
    arrayinfo.unit_size 262144
    calling devctl with erase struct:
    status: 0
    offset: 0x40000
    limit: 0x40000
    Set DisplayStatus to 4
    devctl(7,-2146694912,xx,12,0) returned 0OnOff: Progress 100
    CEmergencySwdlDevCtrl::continueAfterEraseFpgaIniti al
    SWDL: Stopping EFS driver!
    result of running command stop_efs_driver.sh is 0
    SWDL: Starting EFS driver (automount)!
    ECC mode iresult of running command start_efs_driver.sh is 0
    s disabled
    (devf t1::f3s_table_find:252) fs0p2 corrupt U: 94
    Set DisplayStatus to 6
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!


    CEmergencySwdlDevCtrl.cpp:1647: ASSERTION failed
    SWDL persistence is not available!
    useDefaultValuesForInfo: MU
    FPGA info header @SWDL V1@
    FPGA info version 1
    FPGA info variant 9411
    FPGA info type Main Unit
    FPGA info HW index 61
    FPGA info region <noRegion>
    FPGA info step 0
    FPGA info HW index IT 0
    FPGA info ignore region/variant 1
    FPGA info loop 0
    FPGA info repeat 0
    FPGA info CRC 16c693eb
    SWDL: Stopping EFS driver!
    result of running command stop_efs_driver.sh is 0
    SWDL: Starting EFS driver (automount)!
    ECC mode result of running command start_efs_driver.sh is 0
    is disabled
    (devf t1::f3s_table_find:252) fs0p2 corrupt U: 94
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!
    /HBpersistence/SWDL not found!


    CEmergencySwdlDevCtrl.cpp:1647: ASSERTION failed
    /HBpersistence/SWDL/update.txt doesn't exist
    Copy of /HBpersistence/SWDL/update.txt.backup to /HBpersistence/SWDL/update.txt failed
    Don't use update.txt
    SWDL: Mount from medium 3 (0)
    OnOff: variant 9411
    OnOff: DeviceName MU9411
    Src: Medialauncher is running
    Src: mount OK
    SWDL: mount OK
    SWDL: open metainfo /metainfo2.txt
    SWDL: open finished (120048)
    OnOff: FileAccess for continues!
    OnOff: Current file access type: read
    SWDL: read finished (120048, 0)
    SWDL: parse metainfo
    SWDL: check signature and variant failed
    SWDL: contAfterMetainfoError
    SWDL: Mount from medium 4 (1)
    Src: Medialauncher is running
    Src: mount failed. Retry once in 1 s
    Src: Medialauncher is running
    Src: mount failed (medium unavailable 2)
    SWDL: mount failed
    SWDL: Mount from medium 5 (2)
    Src: Medialauncher is running
    Src: mount failed. Retry once in 1 s
    Src: Medialauncher is running
    Src: mount failed (medium unavailable 2)
    SWDL: mount failed
    SWDL: Mount from medium 2 (3)
    Delay mount internal drive 0 1
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...
    Delay mount internal drive 0 1
    Src: mount from CD ... still waiting...


    Оптика не светит.
    flashit -a 0x00040000 -e 1000, заголовок стирает. но восстановление не запускает.
    Help.



    Что ей надо. ???

 

 

Ваши права

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