Lack of clarity when flashing image to emmc

  • Hi,


    in "F&S i.MX8ULP Linux First Steps" you reference a so called <image-name>.wic.zst (section 3.1.5 Deploy Images), which is not available in my case when building the fus-image-std with Yocto. Where can I find the *.wic file? In /tmp/deploy/images I get the following image files. Furthermore it seems like that commands like update.install via UBoot using the *.sysimg are not available anymore.

    Since the *.wic file is not available, I am trying the flash via UUU (section 3.2.1). I set the board to fastboot and placed the *.sysimg and imx-boot-tagged in the same folder with uuu. A connection to the board is possible.

    Code
    1. uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.182-0-gda3cd53
    2. Connected Known USB Devices
    3. Path Chip Pro Vid Pid BcdVersion Serial_no
    4. ====================================================================
    5. 2:7 FB: 0x0525 0xA4A5 0x0221

    I'm using the same uuu.auto script as shown in the appendix in your first steps document. What's the meaning of the flash.bin file (see SDPS: boot -f flash.bin)? Such a file was not generated and therefore the error "can't find ext name in path: >flash.bin" is generated when executing the script with uuu. I assume that flash.bin might be the imx-boot-tagged file, just want to verify it here.


    What am I missing? Please let me know further details.


    Best regards,

    Björn

  • Hi BSenkel ,


    In the second pre-release the file is called <image-name>.sysimg.


    flash.bin can be downloaded from our download area at fs-net.de


    If the system does not start with USB boot, you can also comment out the SDPS flash.bin with '#' in the uuu.auto script.

    In U-Boot, you can start fastboot with '=> fastboot 0'

    Furthermore it seems like that commands like update.install via UBoot using the *.sysimg are not available anymore.

    The update cmd is not implemented yet.

    I would prefer to use the uuu tool to write the sysimg.


    I hope that I could help you :)

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • @fs-support_CS thank you


    However, when I enter fastboot, and connect the F&S development board Rev.1.30 USB-C port to my notebook (cable was shipped with the dev board), and run uuu with the uuu.auto script, I get the following error.

    Code
    1. ./uuu uuu.auto
    2. uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.182-0-gda3cd53
    3. Success 0 Failure 1
    4. 2:7- 1/ 0 [Failure open usb device ]

    I'm using Windows 11 23H2. The device manager shows an unknown device called "USB download gadget" (VID: 0x0525 (Netchip Technology Inc.), PID: 0xA4A5), which might be the root cause here. When I comment out the SDPS part, I get the same error. It seems like that other people facing similar issues with uuu and Windows 10 already.


    How are you performing the sysimg write (=> uuu in Linux?)? Do you have the Windows driver for the stated device available?

  • For anyone having the same issue: UUU works with Linux. However, this should be fixed to run on Windows 11 as well. The NXP docs refer to Windows 10 support, which does not even work and gets EOL next year.

  • Why doesn't it work with the compiled loader (imx-boot-tagged). There is a kernel panic during the boot.

    The flash.bin contains a custom m33 image that allows the Cortex-A to access the RGPIO controller for GPIOB and GPIOA.

    If the RDC is not configured, access to the regs will fail.


    It is possible to disable the GPIOA and GPIOB nodes in the device tree. This means that the controllers are not used, but WLAN and touch will not work in Linux.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.