Our client is trying RAMFS boot with BSP of AM4372 referring to "Processor SDK Linux Software Developer's Guide".
They seem to follow the document like the following log, but it seems to be running from SD / MMC.
$ mkdir target_fs $ cd target_fs $ tar xf ../filesystem/arago-tiny-image-am437x-evm.tar.xz $ find . | cpio -H newc -o > ../target_fs.cpio 26631 blocks $ cd .. $ gzip target_fs.cpio U-Boot# setenv boot ramfs U-Boot# setenv server_ip 192.168.200.3 U-Boot# setenv ipaddr 192.168.200.14 U-Boot# setenv tftp_root target_fs.cpio.gz U-Boot# setenv name_fs target_fs.cpio.gz U-Boot# saveenv Saving Environment to FAT... writing uboot.env done U-Boot# boot switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 reading uEnv.txt 717 bytes read in 5 ms (139.6 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... 4355472 bytes read in 243 ms (17.1 MiB/s) 42675 bytes read in 51 ms (816.4 KiB/s) Booting from mmc0 ... Kernel image @ 0x82000000 [ 0x000000 - 0x427590 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Device Tree to 8fff2000, end 8ffff6b2 ... OK Starting kernel ... ： ： root@am437x-evm:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 2306316 748556 1437276 34% / devtmpfs 501936 4 501932 0% /dev tmpfs 514356 220 514136 0% /run tmpfs 51200 284 50916 1% /var/volatile /dev/mmcblk0p1 71133 569 70565 1% /run/media/mmcblk0p1 /dev/mmcblk0p3 4810396 1781388 2777996 39% /run/media/mmcblk0p3
Is there anything wrong? Or is there a place we should check?
