This thread has been locked.
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.
I have this reference board SItara AM572x Rev 1.2A
I am using http://software-dl.ti.com/processor-sdk-linux/esd/AM57X/latest/index_FDS.html
I built the kernel, just typing make.
I am flashing the sdcard wit the slightly modified sdcard_create faulty script.
Command (m for help): p Disk /dev/mmcblk0: 14.6 GiB, 15653142528 bytes, 30572544 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xee4090c3 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 * 63 144584 144522 70.6M c W95 FAT32 (LBA) /dev/mmcblk0p2 160650 30572543 30411894 14.5G 83 Linux Command (m for help):
All the files seems to be ok on the sdcard
The boot stops:
Trying to boot Linux from eMMC ... switch to partitions #0, OK mmc1(part 0) is current device SD/MMC found on device 1 ** No partition table - mmc 1 ** Trying to boot Android from eMMC ... switch to partitions #0, OK mmc1(part 0) is current device mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc hwpartition [args...] - does hardware partitioning arguments (sizes in 512-byte blocks): [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition [check|set|complete] - mode, complete set partitioning completed WARNING: Partitioning is a write-once setting once it is set to complete. Power cycling is required to initialize partitions after set to complete. mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DSR register value mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc hwpartition [args...] - does hardware partitioning arguments (sizes in 512-byte blocks): [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition [check|set|complete] - mode, complete set partitioning completed WARNING: Partitioning is a write-once setting once it is set to complete. Power cycling is required to initialize partitions after set to complete. mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DSR register value mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc hwpartition [args...] - does hardware partitioning arguments (sizes in 512-byte blocks): [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition [check|set|complete] - mode, complete set partitioning completed WARNING: Partitioning is a write-once setting once it is set to complete. Power cycling is required to initialize partitions after set to complete. mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DSR register value mmc setdsr <value> - set DSR register value Wrong Image Format for bootm command ERROR: can't get kernel image! //////////////// some extra info => mmc list OMAP SD/MMC: 0 OMAP SD/MMC: 1 (eMMC) => mmc part ## Unknown partition table type 0 => mmc info Device: OMAP SD/MMC Manufacturer ID: 70 OEM: 100 Name: S1001 Bus Speed: 48000000 Mode : MMC DDR52 (52MHz) Rd Block Len: 512 MMC version 5.0 High Capacity: Yes Capacity: 14.6 GiB Bus Width: 8-bit DDR Erase Group Size: 512 KiB HC WP Group Size: 16 MiB User Capacity: 14.6 GiB Boot Capacity: 4 MiB ENH RPMB Capacity: 4 MiB ENH =>
What I am missing.
Hello Marius,
The SD card's first sector address must be 2048, can you change it to that value and retry?
Best regards,
Kemal
Hi,
Thank you
I went all the way standard. My sdcard is a class 10.
A similar SDcard using sdk-am335 scripts and sdk boots fine arago on BBB.
But on sitara AM ref board still .... Cannot boot.
A sdcard made with the sdk cut taken in 2017 works fine. I don't see any obvious a difference
Any help would be appreciated.
sudo ./create-sdcard.sh
marius@pegpc:/BOARDS/BBB_TOW/sdkam57xx$ fdisk /dev/mmcblk0 Welcome to fdisk (util-linux 2.31.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p
Disk /dev/mmcblk0: 14.6 GiB, 15653142528 bytes, 30572544 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7aafe5ca
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 145407 143360 70M e W95 FAT16 (LBA)
/dev/mmcblk0p2 145408 30539775 30394368 14.5G 83 Linux
Command (m for help): ^C
and a glimpse of the sdcard content
. ├── boot │ ├── MLO │ ├── u-boot.img │ └── uEnv.txt └── rootfs ├── boot │ ├── am571x-idk.dtb │ ├── am571x-idk-lcd-osd101t2045.dtb │ ├── am571x-idk-lcd-osd101t2587.dtb │ ├── am571x-idk-pps.dtb │ ├── am571x-idk-pru-excl-uio.dtb │ ├── am572x-idk.dtb │ ├── am572x-idk-jailhouse.dtb │ ├── am572x-idk-lcd-osd101t2045.dtb │ ├── am572x-idk-lcd-osd101t2045-jh.dtb │ ├── am572x-idk-lcd-osd101t2587.dtb │ ├── am572x-idk-lcd-osd101t2587-jh.dtb │ ├── am572x-idk-pps.dtb │ ├── am572x-idk-pru-excl-uio.dtb │ ├── am574x-idk.dtb │ ├── am574x-idk-jailhouse.dtb │ ├── am574x-idk-lcd-osd101t2587.dtb │ ├── am574x-idk-pps.dtb │ ├── am574x-idk-pru-excl-uio.dtb │ ├── am57xx-beagle-x15.dtb │ ├── am57xx-beagle-x15-revb1.dtb │ ├── am57xx-beagle-x15-revc.dtb │ ├── am57xx-evm-cam-mt9t111.dtb │ ├── am57xx-evm-cam-ov10635.dtb │ ├── am57xx-evm.dtb │ ├── am57xx-evm-jailhouse.dtb │ ├── am57xx-evm-reva3-cam-mt9t111.dtb │ ├── am57xx-evm-reva3-cam-ov10635.dtb │ ├── am57xx-evm-reva3.dtb │ ├── am57xx-evm-reva3-jailhouse.dtb │ ├── devicetree-uImage-am571x-idk.dtb -> am571x-idk.dtb │ ├── devicetree-uImage-am571x-idk-lcd-osd101t2045.dtb -> am571x-idk-lcd-osd101t2045.dtb │ ├── devicetree-uImage-am571x-idk-lcd-osd101t2587.dtb -> am571x-idk-lcd-osd101t2587.dtb │ ├── devicetree-uImage-am571x-idk-pps.dtb -> am571x-idk-pps.dtb │ ├── devicetree-uImage-am571x-idk-pru-excl-uio.dtb -> am571x-idk-pru-excl-uio.dtb │ ├── devicetree-uImage-am572x-idk.dtb -> am572x-idk.dtb │ ├── devicetree-uImage-am572x-idk-jailhouse.dtb -> am572x-idk-jailhouse.dtb │ ├── devicetree-uImage-am572x-idk-lcd-osd101t2045.dtb -> am572x-idk-lcd-osd101t2045.dtb │ ├── devicetree-uImage-am572x-idk-lcd-osd101t2045-jh.dtb -> am572x-idk-lcd-osd101t2045-jh.dtb │ ├── devicetree-uImage-am572x-idk-lcd-osd101t2587.dtb -> am572x-idk-lcd-osd101t2587.dtb │ ├── devicetree-uImage-am572x-idk-lcd-osd101t2587-jh.dtb -> am572x-idk-lcd-osd101t2587-jh.dtb │ ├── devicetree-uImage-am572x-idk-pps.dtb -> am572x-idk-pps.dtb │ ├── devicetree-uImage-am572x-idk-pru-excl-uio.dtb -> am572x-idk-pru-excl-uio.dtb │ ├── devicetree-uImage-am574x-idk.dtb -> am574x-idk.dtb │ ├── devicetree-uImage-am574x-idk-jailhouse.dtb -> am574x-idk-jailhouse.dtb │ ├── devicetree-uImage-am574x-idk-lcd-osd101t2587.dtb -> am574x-idk-lcd-osd101t2587.dtb │ ├── devicetree-uImage-am574x-idk-pps.dtb -> am574x-idk-pps.dtb │ ├── devicetree-uImage-am574x-idk-pru-excl-uio.dtb -> am574x-idk-pru-excl-uio.dtb │ ├── devicetree-uImage-am57xx-beagle-x15.dtb -> am57xx-beagle-x15.dtb │ ├── devicetree-uImage-am57xx-beagle-x15-revb1.dtb -> am57xx-beagle-x15-revb1.dtb │ ├── devicetree-uImage-am57xx-beagle-x15-revc.dtb -> am57xx-beagle-x15-revc.dtb │ ├── devicetree-uImage-am57xx-evm-cam-mt9t111.dtb -> am57xx-evm-cam-mt9t111.dtb │ ├── devicetree-uImage-am57xx-evm-cam-ov10635.dtb -> am57xx-evm-cam-ov10635.dtb │ ├── devicetree-uImage-am57xx-evm.dtb -> am57xx-evm.dtb │ ├── devicetree-uImage-am57xx-evm-jailhouse.dtb -> am57xx-evm-jailhouse.dtb │ ├── devicetree-uImage-am57xx-evm-reva3-cam-mt9t111.dtb -> am57xx-evm-reva3-cam-mt9t111.dtb │ ├── devicetree-uImage-am57xx-evm-reva3-cam-ov10635.dtb -> am57xx-evm-reva3-cam-ov10635.dtbCommand (m for help): p
Disk /dev/mmcblk0: 14.6 GiB, 15653142528 bytes, 30572544 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7aafe5ca
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 145407 143360 70M e W95 FAT16 (LBA)
/dev/mmcblk0p2 145408 30539775 30394368 14.5G 83 Linux
│ ├── devicetree-uImage-am57xx-evm-reva3.dtb -> am57xx-evm-reva3.dtb │ ├── devicetree-uImage-am57xx-evm-reva3-jailhouse.dtb -> am57xx-evm-reva3-jailhouse.dtb │ ├── devicetree-zImage-am571x-idk.dtb -> am571x-idk.dtb │ ├── devicetree-zImage-am571x-idk-lcd-osd101t2045.dtb -> am571x-idk-lcd-osd101t2045.dtb │ ├── devicetree-zImage-am571x-idk-lcd-osd101t2587.dtb -> am571x-idk-lcd-osd101t2587.dtb │ ├── devicetree-zImage-am571x-idk-pps.dtb -> am571x-idk-pps.dtb │ ├── devicetree-zImage-am571x-idk-pru-excl-uio.dtb -> am571x-idk-pru-excl-uio.dtb │ ├── devicetree-zImage-am572x-idk.dtb -> am572x-idk.dtb │ ├── devicetree-zImage-am572x-idk-jailhouse.dtb -> am572x-idk-jailhouse.dtb │ ├── devicetree-zImage-am572x-idk-lcd-osd101t2045.dtb -> am572x-idk-lcd-osd101t2045.dtb │ ├── devicetree-zImage-am572x-idk-lcd-osd101t2045-jh.dtb -> am572x-idk-lcd-osd101t2045-jh.dtb │ ├── devicetree-zImage-am572x-idk-lcd-osd101t2587.dtb -> am572x-idk-lcd-osd101t2587.dtb │ ├── devicetree-zImage-am572x-idk-lcd-osd101t2587-jh.dtb -> am572x-idk-lcd-osd101t2587-jh.dtb │ ├── devicetree-zImage-am572x-idk-pps.dtb -> am572x-idk-pps.dtb │ ├── devicetree-zImage-am572x-idk-pru-excl-uio.dtb -> am572x-idk-pru-excl-uio.dtb │ ├── devicetree-zImage-am574x-idk.dtb -> am574x-idk.dtb │ ├── devicetree-zImage-am574x-idk-jailhouse.dtb -> am574x-idk-jailhouse.dtb │ ├── devicetree-zImage-am574x-idk-lcd-osd101t2587.dtb -> am574x-idk-lcd-osd101t2587.dtb │ ├── devicetree-zImage-am574x-idk-pps.dtb -> am574x-idk-pps.dtb │ ├── devicetree-zImage-am574x-idk-pru-excl-uio.dtb -> am574x-idk-pru-excl-uio.dtb │ ├── devicetree-zImage-am57xx-beagle-x15.dtb -> am57xx-beagle-x15.dtb │ ├── devicetree-zImage-am57xx-beagle-x15-revb1.dtb -> am57xx-beagle-x15-revb1.dtb │ ├── devicetree-zImage-am57xx-beagle-x15-revc.dtb -> am57xx-beagle-x15-revc.dtb │ ├── devicetree-zImage-am57xx-evm-cam-mt9t111.dtb -> am57xx-evm-cam-mt9t111.dtb │ ├── devicetree-zImage-am57xx-evm-cam-ov10635.dtb -> am57xx-evm-cam-ov10635.dtb │ ├── devicetree-zImage-am57xx-evm.dtb -> am57xx-evm.dtb │ ├── devicetree-zImage-am57xx-evm-jailhouse.dtb -> am57xx-evm-jailhouse.dtb │ ├── devicetree-zImage-am57xx-evm-reva3-cam-mt9t111.dtb -> am57xx-evm-reva3-cam-mt9t111.dtb │ ├── devicetree-zImage-am57xx-evm-reva3-cam-ov10635.dtb -> am57xx-evm-reva3-cam-ov10635.dtb │ ├── devicetree-zImage-am57xx-evm-reva3.dtb -> am57xx-evm-reva3.dtb │ ├── devicetree-zImage-am57xx-evm-reva3-jailhouse.dtb -> am57xx-evm-reva3-jailhouse.dtb │ ├── uImage -> uImage-4.14.79-ge669d52447 │ ├── uImage-4.14.79-ge669d52447 │ ├── vmlinux-4.14.79-ge669d52447 │ ├── zImage -> zImage-4.14.79-ge669d52447 │ └── zImage-4.14.79-ge669d52447
Boot messages starts now with
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 part_get_info_efi: *** ERROR: Invalid GPT *** GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 part_get_info_efi: *** ERROR: Invalid Backup GPT ***
OMAP SD/MMC: 0, OMAP SD/MMC: 1 GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 part_get_info_efi: *** ERROR: Invalid GPT *** GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 part_get_info_efi: *** ERROR: Invalid Backup GPT *** SCSI: SATA link 0 timeout. AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst scanning bus for devices... Found 0 device(s). Net: Warning: ethernet@48484000 using MAC address from ROM eth0: ethernet@48484000 Hit any key to stop autoboot: 0 Trying to boot Linux from eMMC ... switch to partitions #0, OK mmc1(part 0) is current device SD/MMC found on device 1 ** No partition table - mmc 1 ** Trying to boot Android from eMMC ... switch to partitions #0, OK mmc1(part 0) is current device mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc hwpartition [args...] - does hardware partitioning arguments (sizes in 512-byte blocks): [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition [check|set|complete] - mode, complete set partitioning completed WARNING: Partitioning is a write-once setting once it is set to complete. Power cycling is required to initialize partitions after set to complete. mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DSR register value mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc hwpartition [args...] - does hardware partitioning arguments (sizes in 512-byte blocks): [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition [check|set|complete] - mode, complete set partitioning completed WARNING: Partitioning is a write-once setting once it is set to complete. Power cycling is required to initialize partitions after set to complete. mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DSR register value Wrong Image Format for bootm command ERROR: can't get kernel image! =>
Adding more info
=> mmc info Device: OMAP SD/MMC Manufacturer ID: 70 OEM: 100 Name: S1001 Bus Speed: 48000000 Mode : MMC DDR52 (52MHz) Rd Block Len: 512 MMC version 5.0 High Capacity: Yes Capacity: 14.6 GiB Bus Width: 8-bit DDR Erase Group Size: 512 KiB HC WP Group Size: 16 MiB User Capacity: 14.6 GiB Boot Capacity: 4 MiB ENH RPMB Capacity: 4 MiB ENH => => printenv mmcboot mmcboot=mmc dev ${mmcdev}; setenv devnum ${mmcdev}; setenv devtype mmc; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadimage; then if test ${boot_fit} -eq 1; then run loadfit; else run mmcloados;fi;fi;fi; => => mmc part ## Unknown partition table type 0 => => run mmcboot switch to partitions #0, OK mmc1(part 0) is current device SD/MMC found on device 1 ** No partition table - mmc 1 ** =>
I am using latest processor SDK. My encounters is explained above here.
Meanwhile I partitioned the sdcard manually, I reduced the scind partition jusy above the OS size
Nothing worked,
I tried aside a SDcard build with the SDK from 2017-May and that
boots, The latest SDK problems are explained above here in the post.
Can you enter these commands in U-Boot console and retry?
env default -a -f
saveenv
reset
Hi,
Thank you.
=>
=>
=>
=>
=> env default -a -f
## Resetting to default environment
=> saveenv
Saving Environment to MMC...
Writing to MMC(1)... done
=> reset
resetting ...
U-Boot SPL 2018.01-00569-gfd38f5afef-dirty (Jul 29 2019 - 12:37:15) DRA752-GP ES1.1 Trying to boot from MMC1 no pinctrl state for default mode no pinctrl state for default mode U-Boot 2018.01-00569-gfd38f5afef-dirty (Jul 29 2019 - 12:37:15 -0400) CPU : DRA752-GP ES1.1 Model: TI AM5728 IDK Board: AM572x IDK REV 1.2A DRAM: 2 GiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 part_get_info_efi: *** ERROR: Invalid GPT *** GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645 part_get_info_efi: *** ERROR: Invalid Backup GPT *** SCSI: SATA link 0 timeout. AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst scanning bus for devices... Found 0 device(s). Net: Warning: ethernet@48484000 using MAC address from ROM eth0: ethernet@48484000 Hit any key to stop autoboot: 0 Trying to boot Linux from eMMC ... switch to partitions #0, OK mmc1(part 0) is current device mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc hwpartition [args...] - does hardware partitioning arguments (sizes in 512-byte blocks): [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition [check|set|complete] - mode, complete set partitioning completed WARNING: Partitioning is a write-once setting once it is set to complete. Power cycling is required to initialize partitions after set to complete. mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DSR register value mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current arguments (sizes in 512-byte blocks): [user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes [gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition [check|set|complete] - mode, complete set partitioning completed WARNING: Partitioning is a write-once setting once it is set to complete. Power cycling is required to initialize partitions after set to complete. mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specified device mmc partconf dev [boot_ack boot_partition partition_access] - Show or change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DSR register value Wrong Image Format for bootm command ERROR: can't get kernel image! => mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc hwpartition [args...] - does hardware partitioning
Hello,
It seems like you are booting from the SD card but the your system is trying to boot Linux from the eMMC. I am wondering if that is correct because based on your earlier post, your kernel/FS is on the SD card. Have you changed anything in Uboot config files?
Regards,
Krunal
Hi Krunal,
ROOTFILEPARTH=./targetNFS/ KERNEL_IMAGE = board-support/linux-4.14.79+gitAUTOINC+e669d52447-ge669d52447/arch/arm/boot/zImage UBOOT_BIN = board-support/u-boot-2018.01+gitAUTOINC+313dcd69c2-g825ac6e1ac/u-boot.bin UBOOT_MLO = board-support/u-boot-2018.01+gitAUTOINC+313dcd69c2-g825ac6e1ac/MLO MOUNTS ------------------------------------------------------------------------------------ SDCARD:BOOT MOUNT /dev/mmcblk0p1 -> /tmp/SDC/boot/ SDCARD:ROOTFS MOUNT /dev/mmcblk0p2 -> /tmp/SDC/rootfs/
Then:
sudo rsync -rav $ROOTFILEPARTH /tmp/SDC/rootfs sudo cp -af $UBOOT_IMG /tmp/SDC/boot sudo cp -af $UBOOT_MLO /tmp/SDC/boot
Hello,
As an experiment, I am wondering if you could please run the create-sdcard.sh script. The script will format and load the default images necessary to boot the TI EVM. I understand you have a modified version of the script but please try running the TI script that came with the SDK.
Regards,
Krunal