If the bootloader has been erased from the storage media (or written with an invalid image) and the target does not boot, you can:

Boot U-Boot in USB debug mode

Requirements

  • Root/administrator permissions on your development computer.

  • Serial console cable.

  • A micro USB cable.

Instructions

  1. Download the U-Boot bootloader binary image file from https://ftp1.digi.com/support/digiembeddedyocto/3.0/r4/images/ccimx8mn-dvk/xwayland/

    See U-Boot files by variant to verify which U-Boot binary you need.
  2. Download the latest Universal Update Utility (UUU) tool, a software tool from NXP.

  3. Place the uuu executable in a directory in your PATH, such as /usr/bin.

  4. Install udev rules to allow any user to run the uuu for accessing the USB port:

    ~$ sudo sh -c "uuu -udev >> /etc/udev/rules.d/99-uuu.rules"
    ~$ sudo udevadm control --reload-rules
  5. Connect the micro USB cable to the USB recovery connector of the board (top side, next to the USB host connectors) and the other end to the development computer.

  6. Change the boot mode configuration to boot from USB. To do so, set the boot mode micro-switches as follows:

    • S1.1: ON

    • S1.2: ON

    • S1.3: N/A

    • S1:4: N/A

  7. Open a serial terminal at 115200/8/n/1.

  8. Power up the board.

  9. On the host computer run the uuu tool with the U-Boot file to boot as parameter. For example:

    ~$ uuu  </path/to/u-boot-file>
    When TrustFence support is enabled, Digi Embedded Yocto builds a signed U-Boot file imx-boot-signed-ccimx8mn-dvk.bin. Use this file to recover a closed device from USB.

    The serial terminal shows the device starting U-Boot.

  10. Once you have booted U-Boot, you can proceed to re-program U-Boot into the eMMC. See Update U-Boot in the eMMC.

Boot U-Boot from the microSD card

Requirements

  • Root/administrator permissions in your development computer

  • A microSD card with a minimum capacity of 2 GB

The following procedure will destroy existing data in the microSD card.

Instructions

  1. Create a bootable microSD card.

    1. Download the U-Boot bootloader binary image file from https://ftp1.digi.com/support/digiembeddedyocto/3.0/r4/images/ccimx8mn-dvk/xwayland/

      See U-Boot files by variant to verify which U-Boot binary you need.
    2. Copy the U-Boot file into a folder of your choice.

    3. Insert the microSD card into your computer and check the node Linux assigns to it (/dev/<sdcard>) using dmesg:

      $ dmesg
      [1413652.901270] sd 41:0:0:0: [sdc] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB)
      [1413652.903140] sd 41:0:0:0: [sdc] No Caching mode page present
      [1413652.903144] sd 41:0:0:0: [sdc] Assuming drive cache: write through
      [1413652.905638] sd 41:0:0:0: [sdc] No Caching mode page present
      [1413652.905642] sd 41:0:0:0: [sdc] Assuming drive cache: write through
      [1413652.915154] sdc: sdc1

      Do not mount any partitions the card might contain (or unmount any partition if automatically mounted), as you will be writing to the entire block device.

      Using an incorrect device node in the next step might destroy all data on your computer hard drive.
    4. Raw write the image file to the microSD card with this command:

      ~$ sudo dd if=<path/filename.bin> of=/dev/<sdcard> bs=1k seek=32 oflag=sync
      • <path/filename.bin> must be substituted with the path and filename to the U-Boot image.

      • <sdcard> must be substituted with the device node that Linux assigns to your microSD card.

        The microSD card is now ready.

  2. Power off the device.

  3. Insert the microSD card into the microSD card holder.

  4. Change the boot source configuration to boot from the microSD card. To do so, set the boot mode micro-switches as follows:

    • S1.1: OFF

    • S1.2: ON

    • S1.3: ON

    • S1:4: n/a

  5. Power on the device.

  6. Once you have booted U-Boot, you can proceed to re-program U-Boot into the eMMC. See Update U-Boot in the eMMC.

Update U-Boot in the eMMC

Once U-Boot is running, you can use it to update the bootloader in the eMMC using one of these methods:

Update bootloader from USB using Fastboot

To update U-Boot via USB OTG using uuu and the Fastboot protocol:

  1. Connect a micro USB cable between target and host.

  2. Then, on the target, run the fastboot command from the U-Boot console, selecting the USB interface you want it to listen to:

    => fastboot 0
  3. On the host, run the following fastboot command through the uuu tool (as root):

    ~$ uuu FB: flash bootloader <file>
  4. Change the boot source configuration to boot from the internal eMMC.

    To do so, set the boot mode micro-switches as follows:

    • S1.1: OFF

    • S1.2: OFF

    • S1.3: OFF

    • S1:4: n/a

  5. Power-cycle the board. The target now boots from the eMMC.

For additional commands and information, see the NXP UUU manual.

Update bootloader from Ethernet (TFTP)

  1. Place the U-Boot binary inside your host computer TFTP exported folder.

  2. On the target, configure your network settings (IP of the device, IP of the host/server):

    => setenv ipaddr <your-ip>
    => setenv serverip <server-ip>
  3. Connect an Ethernet cable to the Ethernet port.

  4. Run the following command to update U-Boot into the eMMC:

    => update uboot tftp <u-boot-filename>.bin
  5. Change the boot source configuration to boot from the internal eMMC.

    To do so, set the boot mode micro-switches as follows:

    • S1.1: OFF

    • S1.2: OFF

    • S1.3: OFF

    • S1:4: n/a

  6. Power-cycle the board. The target now boots from the eMMC.

Update bootloader from microSD card

  1. Place the U-Boot binary inside a FAT-formatted microSD card.

  2. Insert the microSD card in the board.

  3. Run the following command to update U-Boot into the eMMC:

    => update uboot mmc 1 fat <u-boot-filename>.bin
  4. Change the boot source configuration to boot from the internal eMMC.

    To do so, set the boot mode micro-switches as follows:

    • S1.1: OFF

    • S1.2: OFF

    • S1.3: OFF

    • S1:4: n/a

  5. Power-cycle the board. The target now boots from the eMMC.