Updating the TI EVM Debian Image for the MitySOM-AM62x DevKit¶

These instructions are what was done to update a TI supplied Debian micro-SD card image for the AM62x EVM to support / work with the MitySOM-AM62x Development Kit. These instructions were performed on a Ubuntu Linux host and require sudo privileges.

Please use the correct images for this procedure. The SDK version of the TI image and the Critical Link version should match. If you are targeting the AM62P, make sure you use the am62pxx images. If you are targeting the am62x, make sure you are using the am62x images.

NOTE: Detailed testing of all of the peripherals on the Debian image has not been performed. Console, display, and ethernet has been validated.

1. fetch both the TI debian image and the Critical Link image from the same SDk release. In this example SDk 10 was used, and the files downloaded were "tisdk-debian-trixie-am62xx-evm.wic.xz" from TI and "tisdk-default-image-mitysom-am62x.rootfs-SDK10.01.10_28-20250220175550.img.zip" from Critical Link.
2. Uncompress the files (assumed in /tmp)
   

   user:/tmp # xz -d tisdk-debian-trixie-am62xx-evm.wic.xz
   user:/tmp # unzip tisdk-default-image-mitysom-am62x.rootfs-SDK10.01.10_28-20250220175550.img.zip
   

3. create a loopback device for the Debian Image and mount both the partitions. Note: the losetup command will likely report a different loopback device number. Make sure you update your commands to use the correct loopdevice /dev/loopXX reported by the first command!
   

   user:/tmp # sudo losetup --find --show --partscan tisdk-debian-trixie-am62xx-evm.wic
   /dev/loop20
   user:/tmp # mkdir /tmp/debianp1
   user:/tmp # sudo mount /dev/loop20p1 /tmp/debianp1
   user:/tmp # mkdir /tmp/debianp2
   user:/tmp # sudo mount /dev/loop20p2 /tmp/debianp2
   

4. Repeat the same procedure for the CL provided Yocto Image:
   

   user:/tmp # sudo losetup --find --show --partscan tisdk-default-image-mitysom-am62x.rootfs-20250220175550.img
   /dev/loop50
   user:/tmp # mkdir /tmp/clp1
   user:/tmp # sudo mount /dev/loop50p1 /tmp/clp1
   user:/tmp # mkdir /tmp/clp2
   user:/tmp # sudo mount /dev/loop50p2 /tmp/clp2
   

5. Copy the boot images over to the debian boot partition
   

   user:/tmp # cd /tmp/debianp1
   user:/tmp # sudo mkdir old && mv * old
   user:/tmp # sudo cp -Rap /tmp/clp1/* .
   

6. Copy over the kernel, device tree files, and kernel modules to the debian root partition
   

   user:/tmp # cd /tmp/debianp2/boot
   user:/tmp # sudo mv Image Image.old
   user:/tmp # sudo cp -Rap /tmp/clp2/boot/Image* .
   user:/tmp # cd /tmp/debianp2/boot/dtb/ti
   user:/tmp # sudo cp -Rap /tmp/clp2/boot/dtb/ti/* .
   user:/tmp # cd /tmp/debianp2/lib/modules
   user:/tmp # sudo cp -Rap /tmp/clp2/lib/modules/* .
   

7. unmount the filesystems and close down the loop device
   

   user:/tmp # cd /tmp
   user:/tmp # sudo umount /tmp/clp1
   user:/tmp # sudo umount /tmp/clp2
   user:/tmp # sudo umount /tmp/debianp1
   user:/tmp # sudo umount /tmp/debianp2
   user:/tmp # sudo losetup -d /dev/loop20
   user:/tmp # sudo losetup -d /dev/loop50
   

8. at this point the tisdk-debian-trixie-am62xx-evm.wic image should now be ready to flash to an SD card and run on the MitySOM-AM62x DevKit.