Skip to content

03.05 eMMc

chunyu1021 edited this page Oct 21, 2025 · 2 revisions

3.5SpacereMMC Storage

This procedure applies to devices that boot and store the OS on internal eMMC storage.

3.5.1SpacerStep 1: Prepare the Master Device

Set up the master device (e.g., MIC-733, MIC-730AI) with all desired OS configurations, applications, and libraries.

3.5.2SpacerStep 2: Create the System Image (Clone)

  1. Enter Recovery Mode: Shut down the master device, connect it to the host PC via the Micro-USB recovery port, and put it into Recovery Mode.

  2. Verify Connection: Run lsusb on the host PC to confirm the device is detected.

  3. Navigate to BSP Directory: In the terminal, change your directory to the location where you extracted the Advantech BSP for your device. For example:

    cd /home/user/MIC-733AO_Orin_5.1.2_V1.0.3_SDK/
  4. (One-Time Setup for New BSP): If this is the first time you are using this extracted BSP to flash or clone, you must first run the following command to prepare the environment. This step only needs to be done once per BSP extraction.

    sudo ./flash.sh --no-flash [Device Target] [Storage Partition]
    # e.g., sudo ./flash.sh --no-flash jetson-agx-orin-devkit mmcblk0p1

    After the command completes, you may need to put the device back into recovery mode.

  5. Execute Clone Command: Run the following command to create a backup image of the device's eMMC. This will generate a file named backup.img.

    sudo ./flash.sh -r -k APP-G backup.img [Device Target] [Storage Partition]
    # e.g., sudo ./flash.sh -r -k APP-G backup.img jetson-agx-xavier-devkit mmcblk0p1

    This process will take several minutes to complete. Once finished, you will have a backup.img file in your BSP directory.

3.5.3SpacerStep 3: Prepare the Image for Flashing

  1. Rename the Image: Rename the newly created backup.img to system.img.

    mv backup.img system.img
  2. Move the Image: Move the new system.img file into the bootloader/ subdirectory within your BSP folder.

    mv system.img bootloader/

    ℹ️ Note: If a system.img or system.img.raw file already exists in the bootloader/ directory, you should remove it before moving the new one.

  3. Set Permissions: Grant the correct permissions to the new system image.

    sudo chmod 755 bootloader/system.img

3.5.4SpacerStep 4: Flash the Cloned Image (Restore)

  1. Prepare New Device: Take a new target device, put it into Recovery Mode, and connect it to the host PC.

  2. Execute Flash Command: From the BSP root directory, execute the following command to flash the new device using the custom system.img:

    sudo ./flash.sh -r [Device Target] [Storage Partition]
    # e.g., sudo ./flash.sh -r jetson-agx-orin-devkit internal

    Once the flashing process is complete, the new device will boot up with an exact copy of your master system. You can repeat this step for all other devices you need to deploy.

⬆️ Top

Wiki contents

Previous page Previous chapter Home Next page
   Home

       Welcome to Wiki for MIC AI Series
       What info can be found in the Wiki?

1    BSP Support

   1.1      What's Jetpack BSP?
   1.2      What can be found in BSP folder?
   1.3      Jetpack BSP installation concept
   1.4      Support Jetpack Version
   1.5      MIC-711 Series BSP
   1.6      MIC-713 Series BSP
   1.7      MIC-732 Series BSP
   1.8      MIC-733 Series BSP
   1.9      MIC-742 Series BSP
   1.10      MIC-743 Series BSP
   1.11      MIC-710 Series BSP
   1.12      MIC-712 Series BSP
   1.13      MIC-715 Series BSP
   1.14      MIC-717 Series BSP
   1.15      MIC-720 Series BSP
   1.16      MIC-730 Series BSP

2    I/O Function Support

   2.1      Locating the Correct Package
   2.2      The Test Utility
   2.3      The Guide is Key
   2.4      Support Models
   2.5      MIC-713(S)
   2.6      MIC-733

3    System Clone

   3.1      Introduction
   3.2      General Procedure
   3.3      Prerequisties
   3.4      Support Storage Formats
   3.5      eMMC
   3.6      NVMe

   FAQ
⬇️ End of page

Clone this wiki locally