A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
AM62A7: Bootfs.img generation and eMMC flashing over USB
# Write boot filesystem to eMMC # The image can be build with make_bootfs.sh # Note: dfu-util may need to be run as root. # # U-Boot should be waiting for conneciton before running: # > setenv dfu_alt_info ${dfu_alt_info_emmc} # > dfu 0 mmc 0 sudo dfu-util -a boot -D bootfs.img
SoC: AM62AX SR1.0 HS-FS Model: Texas Instruments AM62A7 SK DRAM: 2 GiB Core: 56 devices, 25 uclasses, devicetree: separate MMC: mmc@fa10000: 0 Loading Environment from nowhere... OK In: serial@2800000 Out: serial@2800000 Err: serial@2800000 Failed to probe am65_cpsw_nuss driver Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device SD/MMC found on device 0 Failed to load 'boot.scr' Can't set block device ## Error: "main_cpsw0_qsgmii_phyinit" not defined 19909120 bytes read in 131 ms (144.9 MiB/s) Failed to load '//dtb/ti/k3-am62a7-sk.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image MMC Device 1 not found no mmc device at slot 1 starting USB... No working controllers found USB is stopped. Please issue 'usb start' first. starting USB... No working controllers found No ethernet found. missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/00000000 No ethernet found. Retrieving file: pxelinux.cfg/0000000 No ethernet found. Retrieving file: pxelinux.cfg/000000 No ethernet found. Retrieving file: pxelinux.cfg/00000 No ethernet found. Retrieving file: pxelinux.cfg/0000 No ethernet found. Retrieving file: pxelinux.cfg/000 No ethernet found. Retrieving file: pxelinux.cfg/00 No ethernet found. Retrieving file: pxelinux.cfg/0 No ethernet found. Retrieving file: pxelinux.cfg/default-arm-k3-am62ax No ethernet found. Retrieving file: pxelinux.cfg/default-arm-k3 No ethernet found. Retrieving file: pxelinux.cfg/default-arm No ethernet found. Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found starting USB... No working controllers found No ethernet found. No ethernet found.
U-Boot is looking for the kernel devicetree file under /boot/dtb/ti/ directory. Did you copy the file k3-am62a7-sk.dtb to the correct location before creating bootfs.img?
The command sequence to create the bootfs image seems to be correct, except you should know what file size to use, which is determined by the rootfs you use for your project. For example, the Processor SDK provides the following prebuilt rootfs images:
Sorry, it is my bad, I didn't realize that your "flash_bootfs.sh" script only flashes to the eMMC boot partition, but not the rootfs, all our previous communication is invalid. Sorry for the confusion.
Can you please follow the instruction linked below for flashing the eMMC?
The following instructions can be used to prepare the <your_rootfs.ext4> using tisdk-base-image-am62xx-evm.tar.xz:
$ cd <path-ti-psdk>/filesystem
$ dd if=/dev/null of=tisdk-base.ext4 bs=1M seek=300
$ mkfs.ext4 -F tisdk-base.ext4
$ mkdir mnt_fs
$ sudo mount -t ext4 tisdk-base.ext4 mnt_fs
$ cd mnt_fs
$ sudo tar xvf ../tisdk-base-image-am62xx-evm.tar.xz
$ cd ..
$ sudo umount mnt_fs
then you need the following command to flash the rootfs image to emmc. Please ensure you copied kernel image and dtb to the rootfs created using the instructions above.
Okay, now I understand the problem you are trying to resolve - just updating kernel in eMMC during software development.
I can think of two different solutions.
1. after initially flashed the entire Linux to eMMC and whenever you need to update the kernel image or dtb, boot your board from eMMC to Linux, then use whatever interface on your board to copy/download the individual files in Linux and write them to the corresponding locations in eMMC, then reboot your board. This is basically the same way that how to use a Linux computer.
Whenever the updated kernel image or dtb causes your board unable to boot, you would need to use DFU to flash the entire rootfs to recover.
-2. partition your eMMC to separate kernel image and dtb from the rootfs, so that both files are not in the rootfs. Then you can just use DFU to update the kernel image and dtb whenever you want to. You just need to modify U-Boot to load the kernel image and dtb from the new partition, but not from the rootfs.
This is not supported in the SDK, so I don't have an example to show you. But I already explained it in my previous post, you should be able follow and implement it.
this "rootfs" points to mmcblk0p2, instead of mmcblk0 which is the default.
To dfu flash kernel image and dtb to mmcblk0p1, you need to add two entries to $dfu_alt_info_emmc so that both files can be written to mmcblk0p1 in FAT file format.
dfu_alt_info_nand=NAND.tiboot3 part 0 1; NAND.tispl part 0 2; NAND.tiboot3.backup part 0 3; NAND.u-boot part 0 4; NAND.u-boot-env part 0 5; NAND.u-boot-env.backup part 07
dfu_alt_info_ospi=tiboot3.bin raw 0x0 0x080000; tispl.bin raw 0x080000 0x200000; u-boot.img raw 0x280000 0x400000; u-boot-env raw 0x680000 0x020000; sysfw.itb raw 0x6c000
dfu_alt_info_ospi_nand=ospi_nand.tiboot3 part 1; ospi_nand.tispl part 2; ospi_nand.u-boot part 3; ospi_nand.env part 4; ospi_nand.env.backup part 5; ospi_nand.rootfs par7
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1; boot part 0 1; rootfs part 0 2; tiboot3.bin.raw raw 0x0 0x400 mmcpart 1; tispl.bin.raw raw 0x400 0x1000 mmcpart 1; u-1
dfu_alt_info_mmc=boot part 1 1; rootfs part 1 2; tiboot3.bin fat 1 1; tispl.bin fat 1 1; u-boot.img fat 1 1; uEnv.txt fat 1 1; sysfw.itb fat 1 1
dfu_alt_info_nand=NAND.tiboot3 part 0 1; NAND.tispl part 0 2; NAND.tiboot3.backup part 0 3; NAND.u-boot part 0 4; NAND.u-boot-env part 0 5; NAND.u-boot-env.backup part 07
dfu_alt_info_ospi=tiboot3.bin raw 0x0 0x080000; tispl.bin raw 0x080000 0x200000; u-boot.img raw 0x280000 0x400000; u-boot-env raw 0x680000 0x020000; sysfw.itb raw 0x6c000
dfu_alt_info_ospi_nand=ospi_nand.tiboot3 part 1; ospi_nand.tispl part 2; ospi_nand.u-boot part 3; ospi_nand.env part 4; ospi_nand.env.backup part 5; ospi_nand.rootfs par7
dfu_alt_info_ram=tispl.bin ram 0x80080000 0x200000; u-boot.img ram 0x81000000 0x400000
Q1) could you please share how to update the "dfu_alt_info_emmc"? Q2) do i need to flash bootloader as explained in below command to flash my kernel and dtb?
sudo dfu-util -a tiboot3.bin.raw -D <your_tiboot3.bin>
sudo dfu-util -a tispl.bin.raw -D <your_tispl.bin>
sudo dfu-util -a u-boot.img.raw -D <your_u-boot.img>
