Part Number: TDA4VM
Other Parts Discussed in Thread: UNIFLASH
Hi,
I created two Images one for the boot Partition and one for the rootfs using the dd on my host machine. I can not use the sdcard and Network.
I have the uboot working from OSPI interface and can load files from a USB storage.
For creating the partition on the EMMC I am using this:
setenv uuid_gpt_disk 37c84ec5-8cc8-42e6-85d0-dfd0ebde3257
setenv uuid_gpt_rootfs b0e8add0-befc-41d2-baed-900d580f605b
setenv uuid_gpt_boot 53e2091a-5ba3-42e5-b79e-dda6c9b371e2
gpt write mmc 0 "uuid_disk=${uuid_gpt_disk};name=boot,start=0,size=20M,bootable,type=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7,uuid=${uuid_gpt_boot};name=rootfs,start=20M,size=-,uuid=${uuid_gpt_rootfs},type=linux;"
when I run the mmc part command, I see the following:
Part Start LBA End LBA Name
Attributes
Type GUID
Partition GUID
1 0x00000022 0x0000a021 "boot"
attrs: 0x0000000000000004
type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
guid: 53e2091a-5ba3-42e5-b79e-dda6c9b371e2
2 0x0000a000 0x01da3fde "rootfs"
attrs: 0x0000000000000000
type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
guid: b0e8add0-befc-41d2-baed-900d580f605b
I copy the Image using the following commands:
mmc write $loadaddr 0x00000022 0XA000
mmc write $loadaddr 0xa000 0x100000
load usb 0 $loadaddr rootfs.img 0x20000000 0x20000000
mmc write $loadaddr 0x10a000 0x100000
load usb 0 $loadaddr rootfs.img 0x20000000 0x40000000
mmc write $loadaddr 0x20a000 0x100000
load usb 0 $loadaddr rootfs.img 0x20000000 0x60000000
mmc write $loadaddr 0x30a000 0x100000
load usb 0 $loadaddr rootfs.img 0x20000000 0x80000000
mmc write $loadaddr 0x40a000 0x100000
Loading rproc fw image from device 3 not supported!
Starting ATF on ARM64 core...
NOTICE: BL31: Built : 09:32:00, Feb 17 2020
I/TC:
I/TC: OP-TEE version: ti2019.05-rc1-dev (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 Mon Feb 17 09:40:16 UTC 2020 aarch64
I/TC: Initialized
Detected: J7X-BASE-CPB rev E3
Detected: J7X-GESI-EXP rev E3
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from SPI
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E7
DRAM: 4 GiB
Flash: 0 Bytes
MMC: sdhci@4fb0000 - probe failed: -123
sdhci@4f80000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
Out: serial@2800000
Err: serial@2800000
Detected: J7X-BASE-CPB rev E3
Detected: J7X-GESI-EXP rev E3
Detected: J7X-VSC8514-ETH rev E2
Net:
Warning: ethernet@046000000 using MAC address from ROM
eth0: ethernet@046000000
Hit any key to stop autoboot: 0
no mmc device at slot 1
SD/MMC found on device 1
Trying to boot Android from eMMC ...
switch to partitions #0, OK
mmc0(part 0) is current device
Wrong Image Format for bootm command
ERROR: can't get kernel image!
So I have the following question:
1) The type for the rootfs is not set correctly (It should be Linux but it is not). How can I have a Linux Partition using uboot?
2) How can I make the uboot load Linux from EMMC when the OSPI loads uboot and rootfs Comes from EMMC?
3) How can I make the emmc only boot mode work (Uboot and rootfs both Comes from emmc)?
Thanks,
Pouyan