DRA821U-Q1: Boot Linux with SBL from emmc failed

Hi,

Assigned engineer is currently out of office, expect delay in response.

Regards,

Manojna

Hi Shicheng,

Sorry for the la

• Can you help us with the hardware schematics of eMMC as there is a CQE recovery and power on failed issue coming up.

• Also,I think you have missed copying the other main domain related firmwares as below:

Regards

Gokul

Hi Gokul

Thanks for your reply

Gokul Praveen said:

Can you help us with the hardware schematics of eMMC as there is a CQE recovery and power on failed issue coming up.

Bellow is our hardware schematics of eMMC.

Gokul Praveen said:

Also,I think you have missed copying the other main domain related firmwares as below:

I am use DRA821U-Q1I am use DRA821U-Q1, j7200, do not have DSP cores

HI Shancheng,

Thanks for the reply.

After discussing it internally,I found out that only bootapp using SD card and OSPI is supported.

However,we have raised a jira to enable support for bootapp using emmc which will mostly come in future releases of the SDK.We will inform you as soon as this feature is enabled shancheng.

Regards

Gokul

Hi Gokul

Gokul Praveen said:

After discussing it internally,I found out that only bootapp using SD card and OSPI is supported.

You mean, it is not support that I want to use bootapp from eMMC?

Is there any method with SBL from eMMC? I have try SBL from SD card is OK.

Hi Shicheng,

shicheng wang said:

You mean, it is not support that I want to use bootapp from eMMC?

Yes,Shicheng,you are right.

We have raised a request to enable this feature and we will get back to you as soon as this is enabled.

Regards

Gokul

Hi Gokul

I try some changes, and the error is different

I add bellow codes in MCU1_0 app:

/* Ensure all the key memory interfaces are handed off properly, for HLOS control */
AppUtils_Printf(MSG_NORMAL, "Sciclient_pmSetModuleState Off, DevId: %d \n", TISCI_DEV_MMCSD0);
    if(Sciclient_pmSetModuleState(TISCI_DEV_MMCSD0, TISCI_MSG_VALUE_DEVICE_SW_STATE_AUTO_OFF, TISCI_MSG_FLAG_AOP, SCICLIENT_SERVICE_WAIT_FOREVER) != E_PASS)
    {
        AppUtils_Printf(MSG_NORMAL, "Sciclient_pmSetModuleState failed to power OFF eMMC, DevId: %d \n", TISCI_DEV_MMCSD0);
    }

And the linux boot follow is hang on Waiting for root device /dev/mmcblk0p2...

Here are error logs:

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
I/TC: 
I/TC: OP-TEE version: 4.2.0-dev (gcc version 13.3.0 (GCC)) #1 Fri Apr 12 09:51:21 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
I/TC: SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
[    0.000000] Linux version 6.6.58 (root@0ee7ce3b84a1) (aarch64-oe-linux-gcc (GCC) 13.3.0, GNU ld (GNU Binutils) 2.42.0.20240716) #5 SMP PREEMPT Tue Mar 18 11:27:53 CST 205
[    0.000000] KASLR disabled due to lack of seed
[    0.000000] Machine model: Texas Instruments J7200 EVM
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
[    0.000000] efi: UEFI not found.
[    0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!
[    0.000000] OF: reserved mem: OVERLAP DETECTED!
[    0.000000] optee@9e800000 (0x000000009e800000--0x00000000a0000000) overlaps with sharememory_for_dv@9ffff000 (0x000000009ffff000--0x00000000a0000000)
[    0.000000] OF: reserved mem: 0x000000009e800000..0x000000009fffffff (24576 KiB) nomap non-reusable optee@9e800000
[    0.000000] OF: reserved mem: 0x000000009ffff000..0x000000009fffffff (4 KiB) nomap non-reusable sharememory_for_dv@9ffff000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a0000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a0000000..0x00000000a00fffff (1024 KiB) nomap non-reusable r5f-dma-memory@a0000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a0100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a0100000..0x00000000a0ffffff (15360 KiB) nomap non-reusable r5f-memory@a0100000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a1000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a1000000..0x00000000a10fffff (1024 KiB) nomap non-reusable r5f-dma-memory@a1000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a1100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a1100000..0x00000000a1ffffff (15360 KiB) nomap non-reusable r5f-memory@a1100000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a2000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a2000000..0x00000000a20fffff (1024 KiB) nomap non-reusable r5f-dma-memory@a2000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a2100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a2100000..0x00000000a2ffffff (15360 KiB) nomap non-reusable r5f-memory@a2100000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a3000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a3000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a3000000..0x00000000a30fffff (1024 KiB) nomap non-reusable r5f-dma-memory@a3000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a3100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a3100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a3100000..0x00000000a3ffffff (15360 KiB) nomap non-reusable r5f-memory@a3100000
[    0.000000] OF: reserved mem: 0x00000000a4000000..0x00000000a47fffff (8192 KiB) nomap non-reusable ipc-memories@a4000000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x00000008ffffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x000000009e7fffff]
[    0.000000]   node   0: [mem 0x000000009e800000-0x00000000a47fffff]
[    0.000000]   node   0: [mem 0x00000000a4800000-0x00000000ffffffff]
[    0.000000]   node   0: [mem 0x0000000880000000-0x00000008ffffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000008ffffffff]
[    0.000000] cma: Reserved 32 MiB at 0x00000000fe000000 on node -1
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.4
[    0.000000] percpu: Embedded 20 pages/cpu s43176 r8192 d30552 u81920
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] CPU features: detected: Spectre-v3a
[    0.000000] CPU features: detected: Spectre-BHB
[    0.000000] CPU features: detected: ARM erratum 1742098
[    0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1032192
[    0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[    0.000000] software IO TLB: area num 2.
[    0.000000] software IO TLB: mapped [mem 0x00000000fa000000-0x00000000fe000000] (64MB)
[    0.000000] Memory: 3896068K/4194304K available (12096K kernel code, 1276K rwdata, 4044K rodata, 2496K init, 457K bss, 265468K reserved, 32768K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000]  Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 960 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GICv3: GICv3 features: 16 PPIs
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001900000
[    0.000000] ITS [mem 0x01820000-0x0182ffff]
[    0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
[    0.000000] ITS@0x0000000001820000: Devices Table too large, reduce ids 20->19
[    0.000000] ITS@0x0000000001820000: allocated 524288 Devices @880800000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x0000000880040000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000880050000
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0x3ffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns
[    0.000000] sched_clock: 58 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
[    0.008359] Console: colour dummy device 80x25
[    0.012925] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.023596] pid_max: default: 32768 minimum: 301
[    0.028350] LSM: initializing lsm=capability,selinux,integrity
[    0.034324] SELinux:  Initializing.
[    0.037955] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.045531] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.054435] RCU Tasks: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[    0.061700] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[    0.069566] rcu: Hierarchical SRCU implementation.
[    0.074465] rcu:     Max phase no-delay instances is 1000.
[    0.079984] Platform MSI: msi-controller@1820000 domain created
[    0.086156] PCI/MSI: /bus@100000/interrupt-controller@1800000/msi-controller@1820000 domain created
[    0.095537] EFI services will not be available.
[    0.100285] smp: Bringing up secondary CPUs ...
ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Request to start core failed: -60
[    1.129293] psci: failed to boot CPU1 (-22)
[    1.133633] CPU1: failed to boot: -22
[    1.137410] smp: Brought up 1 node, 1 CPU
[    1.141508] SMP: Total of 1 processors activated.
[    1.146318] CPU features: detected: 32-bit EL0 Support
[    1.151571] CPU features: detected: CRC32 instructions
[    1.156853] CPU: All CPU(s) started at EL2
[    1.161035] alternatives: applying system-wide alternatives
[    1.167508] devtmpfs: initialized
[    1.176172] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    1.186157] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    1.193719] pinctrl core: initialized pinctrl subsystem
[    1.199314] DMI not present or invalid.
[    1.203755] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    1.210243] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[    1.217556] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    1.225596] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    1.233715] audit: initializing netlink subsys (disabled)
[    1.239330] audit: type=2000 audit(0.136:1): state=initialized audit_enabled=0 res=1
[    1.247475] thermal_sys: Registered thermal governor 'step_wise'
[    1.247479] thermal_sys: Registered thermal governor 'power_allocator'
[    1.253639] cpuidle: using governor menu
[    1.264397] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    1.271348] ASID allocator initialised with 65536 entries
[    1.279886] /bus@100000/interrupt-controller@1800000: Fixed dependency cycle(s) with /bus@100000/interrupt-controller@1800000
[    1.296756] /bus@100000/pinctrl@a40000: Fixed dependency cycle(s) with /bus@100000/pinctrl@a40000/mcu-cpsw-cpts
[    1.308416] Modules: 27632 pages in range for non-PLT usage
[    1.308421] Modules: 519152 pages in range for PLT usage
[    1.314550] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    1.326919] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    1.333321] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[    1.340254] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    1.346657] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    1.353590] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    1.359992] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[    1.366926] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    1.374101] k3-chipinfo 43000014.chipid: Family:J7200 rev:SR2.0 JTAGID[0x1bb6d02f] Detected
[    1.383568] iommu: Default domain type: Translated
[    1.388489] iommu: DMA domain TLB invalidation policy: strict mode
[    1.394933] SCSI subsystem initialized
[    1.398931] usbcore: registered new interface driver usbfs
[    1.404548] usbcore: registered new interface driver hub
[    1.409986] usbcore: registered new device driver usb
[    1.415353] pps_core: LinuxPPS API ver. 1 registered
[    1.420424] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.429762] PTP clock support registered
[    1.433883] EDAC MC: Ver: 3.0.0
[    1.437339] scmi_core: SCMI protocol bus registered
[    1.442486] FPGA manager framework
[    1.445997] Advanced Linux Sound Architecture Driver Initialized.
[    1.452737] clocksource: Switched to clocksource arch_sys_counter
[    1.459119] VFS: Disk quotas dquot_6.6.0
[    1.463144] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.473415] NET: Registered PF_INET protocol family
[    1.478658] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    1.487826] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    1.496577] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    1.504502] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    1.512709] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
[    1.521407] TCP: Hash tables configured (established 32768 bind 32768)
[    1.528233] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    1.535148] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    1.542579] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.548660] RPC: Registered named UNIX socket transport module.
[    1.554719] RPC: Registered udp transport module.
[    1.559522] RPC: Registered tcp transport module.
[    1.564325] RPC: Registered tcp-with-tls transport module.
[    1.569938] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.576523] NET: Registered PF_XDP protocol family
[    1.581427] PCI: CLS 0 bytes, default 64
[    1.586147] Initialise system trusted keyrings
[    1.590821] workingset: timestamp_bits=46 max_order=20 bucket_order=0
[    1.597571] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.603671] NFS: Registering the id_resolver key type
[    1.608850] Key type id_resolver registered
[    1.613121] Key type id_legacy registered
[    1.617223] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.624071] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.645848] Key type asymmetric registered
[    1.650035] Asymmetric key parser 'x509' registered
[    1.655044] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    1.662692] io scheduler mq-deadline registered
[    1.667323] io scheduler kyber registered
[    1.671433] io scheduler bfq registered
[    1.677187] pinctrl-single 4301c000.pinctrl: 13 pins, size 52
[    1.683190] pinctrl-single 4301c038.pinctrl: 2 pins, size 8
[    1.689009] pinctrl-single 4301c068.pinctrl: 59 pins, size 236
[    1.695097] pinctrl-single 4301c174.pinctrl: 8 pins, size 32
[    1.700997] pinctrl-single 104200.pinctrl: 20 pins, size 80
[    1.706769] pinctrl-single 104280.pinctrl: 8 pins, size 32
[    1.712477] pinctrl-single 11c000.pinctrl: 67 pins, size 268
[    1.718619] pinctrl-single 11c110.pinctrl: 1 pins, size 4
[    1.724211] pinctrl-single 11c11c.pinctrl: 3 pins, size 12
[    1.729930] pinctrl-single 11c164.pinctrl: 2 pins, size 8
[    1.735809] pinctrl-single a40000.pinctrl: 512 pins, size 2048
[    1.745420] Serial: 8250/16550 driver, 12 ports, IRQ sharing enabled
[    1.757436] loop: module loaded
[    1.761292] megasas: 07.725.01.00-rc1
[    1.766788] tun: Universal TUN/TAP device driver, 1.6
[    1.772536] VFIO - User Level meta-driver version: 0.3
[    1.778405] usbcore: registered new interface driver usb-storage
[    1.784714] gadgetfs: USB Gadget filesystem, version 24 Aug 2004
[    1.790862] file system registered
[    1.794637] i2c_dev: i2c /dev entries driver
[    1.799649] sdhci: Secure Digital Host Controller Interface driver
[    1.805988] sdhci: Copyright(c) Pierre Ossman
[    1.810591] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.816699] ledtrig-cpu: registered to indicate activity on CPUs
[    1.822996] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.830005] usbcore: registered new interface driver usbhid
[    1.835701] usbhid: USB HID core driver
[    1.840326] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
[    1.848974] optee: probing for conduit method.
I/TC: Reserved shared memory is enabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are disabled
[    1.853537] optee: revision 4.2 (12d7c4ee)
[    1.869993] optee: dynamic shared memory is enabled
[    1.879629] random: crng init done
[    1.883272] optee: initialized driver
[    1.888210] Initializing XFRM netlink socket
[    1.892626] NET: Registered PF_PACKET protocol family
[    1.897846] Key type dns_resolver registered
[    1.906095] registered taskstats version 1
[    1.910363] Loading compiled-in X.509 certificates
[    2.920748] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: platform_probe+0x68/0xc4)
[    2.930282] ti-sci 44083000.system-controller: Mbox send fail -110
[    2.936597] ti-sci 44083000.system-controller: Unable to communicate with TISCI(-110)
[    2.944627] ti-sci: probe of 44083000.system-controller failed with error -110
[    2.956608] clk: Disabling unused clocks
[    2.960661] ALSA device list:
[    2.963704]   No soundcards found.
[    2.967216] Warning: unable to open an initial console.
[    2.972603] Waiting for root device /dev/mmcblk0p2...
[   13.194657] omap8250 2800000.serial: deferred probe timeout, ignoring dependency
[   13.202332] omap8250: probe of 2800000.serial failed with error -110
[   13.209194] platform 2430000.timer: deferred probe pending
[   13.214820] platform 2440000.timer: deferred probe pending
[   13.220442] platform 2450000.timer: deferred probe pending
[   13.226049] platform 2460000.timer: deferred probe pending
[   13.231653] platform 2470000.timer: deferred probe pending
[   13.237266] platform 2480000.timer: deferred probe pending
[   13.242870] platform 2490000.timer: deferred probe pending
[   13.248473] platform 24a0000.timer: deferred probe pending
[   13.254085] platform 24b0000.timer: deferred probe pending
[   13.259689] platform 24c0000.timer: deferred probe pending
[   13.265292] platform 24d0000.timer: deferred probe pending
[   13.270903] platform 24e0000.timer: deferred probe pending
[   13.276507] platform 24f0000.timer: deferred probe pending
[   13.282110] platform 2500000.timer: deferred probe pending
[   13.287722] platform 2510000.timer: deferred probe pending
[   13.293326] platform 2520000.timer: deferred probe pending
[   13.298931] platform 2530000.timer: deferred probe pending
[   13.304543] platform 42110000.gpio: deferred probe pending
[   13.310146] platform 600000.gpio: deferred probe pending
[   13.315572] platform 42200000.interrupt-controller: deferred probe pending
[   13.322610] platform bus@100000:interrupt-controller@a00000: deferred probe pending
[   13.330436] platform 310e0000.interrupt-controller: deferred probe pending
[   13.337470] platform 33d00000.msi-controller: deferred probe pending
[   13.343962] platform bus@100000:wiz@5060000: deferred probe pending
[   13.350364] platform 285c0000.dma-controller: deferred probe pending
[   13.356864] platform 31150000.dma-controller: deferred probe pending
[   13.363356] platform 2b800000.ringacc: deferred probe pending
[   13.369225] platform 3c000000.ringacc: deferred probe pending
[   13.375103] platform 4f80000.mmc: deferred probe pending
[   13.380530] platform 2800000.serial: deferred probe pending
[   13.386222] platform 2810000.serial: deferred probe pending
[   13.391922] platform 47040000.spi: deferred probe pending
[   13.397437] platform 46000000.ethernet: deferred probe pending
[   13.403397] platform 310d0000.cpts: deferred probe pending
[   13.409009] platform 4fb0000.mmc: deferred probe pending

Is there any resaon about MCU1_0? Thanks

Hi Shincheng,

shicheng wang said:

Waiting for root device /dev/mmcblk0p2...

You have powered off the emmc ,hence it is not able to fetch the rootfs from emmc.

shicheng wang said:

Is there any method with SBL from eMMC

I just found out that the feature for using bootapp wirh eMMC UDA has been enabled in  10.01.00.04 RTOS SDK of J7200.

Can you try the following steps to boot using BOOTAPP with eMMC UDA:

**Booting Linux via EMMC UDA**

• Download the  10.01.00.04 RTOS SDK of J7200.
• Generate lateapps by using the following commands
           * goto <PDK>/packages/ti/boot/sbl/example/boot_app/scripts
           * Run ./make_multicore_appimages.sh <board_name>
           * Multicore images(lateapps) will be generated in <PDK>/packages/ti/boot/sbl/example/boot_app/multicore_images/$BOARD/.
           * Stage1 image corresponds to lateapp1, stage2 image corresponds to lateapp2 and stage3 image corresponds to lateapp3.
        
• Copy sbl_emmc_uda_img_mcu1_0_release.tiimage as tiboot3.bin to /media/$USER/rootfs/home/root in the SD card
• Copy tifs.bin to /media/$USER/rootfs/home/root in the SD card
       
• Build boot_app_emmc_uda_linux by using the following command
           * make BOARD=<board_name> CORE=mcu1_0 boot_app_emmc_uda_linux -sj
• Copy sbl_boot_app_emmc_uda_linux_<board_name>_mcu1_0_freertos_TestApp_release.appimage image as app to /media/$USER/rootfs/home/root in the SD card.
• Copy stage1 image as lateapp1, stage2 image as lateapp2 to /media/$USER/rootfs/home/root in the SD card.
• Copy atf_optee.appimage, tidtb_linux.appimage, tikernelimage_linux.appimage to the boot partition of SD card.
• Boot in SD boot mode: SW8: 1000 0010 SW9: 0000 0000
• Login as root
• Copy the following images to eMMC FAT32 partition(/dev/mmcblk0p1) from the SD card
           * mkdir eMMC
           * mount /dev/mmcblk0p1 eMMC
           * cp tiboot3.bin eMMC
           * cp tifs.bin eMMC
           * cp app eMMC
           * cp lateapp1 eMMC
           * cp lateapp2 eMMC
           * cp tidtb_linux.appimage eMMC
           * cp tikernelimage_linux.appimage eMMC
           * cp atf_optee.appimage eMMC
• Change boot mode to eMMC UDA partition and boot the board: SW8: 1000 0000 SW9: 0000 0000

Regards

Gokul

Hi Gokul

Gokul Praveen said:

I just found out that the feature for using bootapp wirh eMMC UDA has been enabled in  10.01.00.04 RTOS SDK of J7200.

Can you try the following steps to boot using BOOTAPP with eMMC UDA:

Now we  are using 10_00_00_03 and it is not convenient and easy to change to 10.01.00.04.

Could you pelases show me the patch about the differents with SBL from eMMC between 10.01.00.04 and 10_00_00_03?

I try to add patch to 10_00_00_03.

Thanks very much

Hi Shicheng,

Please follow the below link for the patches:

• https://git.ti.com/cgit/processor-sdk/pdk/commit/?id=b1608b4dc5c7bc75be7253cea700acffe47e05d9

Regards

Gokul

Hi Gokul

Thanks for your reply. 

I have add the patches to our SDK 10_00_00_03, but there are two questions:

Q1. I follow below steps and use sbl_boot_app_emmc_uda_j7200_evm_mcu1_0_freertos_TestApp_release.appimage as bootApp to boot from eMMC UDA, there are error:

Gokul Praveen said:

Can you try the following steps to boot using BOOTAPP with eMMC UDA:

**Booting Linux via EMMC UDA**

• Download the  10.01.00.04 RTOS SDK of J7200.
• Generate lateapps by using the following commands
           * goto <PDK>/packages/ti/boot/sbl/example/boot_app/scripts
           * Run ./make_multicore_appimages.sh <board_name>
           * Multicore images(lateapps) will be generated in <PDK>/packages/ti/boot/sbl/example/boot_app/multicore_images/$BOARD/.
           * Stage1 image corresponds to lateapp1, stage2 image corresponds to lateapp2 and stage3 image corresponds to lateapp3.
        
• Copy sbl_emmc_uda_img_mcu1_0_release.tiimage as tiboot3.bin to /media/$USER/rootfs/home/root in the SD card
• Copy tifs.bin to /media/$USER/rootfs/home/root in the SD card
       
• Build boot_app_emmc_uda_linux by using the following command
           * make BOARD=<board_name> CORE=mcu1_0 boot_app_emmc_uda_linux -sj
• Copy sbl_boot_app_emmc_uda_linux_<board_name>_mcu1_0_freertos_TestApp_release.appimage image as app to /media/$USER/rootfs/home/root in the SD card.
• Copy stage1 image as lateapp1, stage2 image as lateapp2 to /media/$USER/rootfs/home/root in the SD card.
• Copy atf_optee.appimage, tidtb_linux.appimage, tikernelimage_linux.appimage to the boot partition of SD card.
• Boot in SD boot mode: SW8: 1000 0010 SW9: 0000 0000
• Login as root
• Copy the following images to eMMC FAT32 partition(/dev/mmcblk0p1) from the SD card
           * mkdir eMMC
           * mount /dev/mmcblk0p1 eMMC
           * cp tiboot3.bin eMMC
           * cp tifs.bin eMMC
           * cp app eMMC
           * cp lateapp1 eMMC
           * cp lateapp2 eMMC
           * cp tidtb_linux.appimage eMMC
           * cp tikernelimage_linux.appimage eMMC
           * cp atf_optee.appimage eMMC
• Change boot mode to eMMC UDA partition and boot the board: SW8: 1000 0000 SW9: 0000 0000

Q2. I carefully checked the content of the patches，most of the modifications revolve around the bootapp under the path:$(pdk_path)/packages/ti/boot/sbl/example/boot_app; 

But in fact, what bootapp we are using is called can_boot_app_mcu_rtos_mcu1_0_release.appimage under the path:$mcusw_path/mcuss_demos/boot_app_mcu_rtos. It also has function to boot linux. The error message is the same as when I first report the question.

So that, how to fix problem 1, I would prefer to solve problem 2 because it is the program we are actually using in our project.

Thanks

Hi Gokul

Add some supplements。

In the previous reply post， The error in question 1 has been confirmed because I copied the wrong image:sbl_boot_app_emmc_uda_j7200_evm_mcu1_0_freertos_TestApp_release.appimage, I sould copy sbl_boot_app_emmc_uda_linux_j7200_evm_mcu1_0_freertos_TestApp_release.appimage.

And when use sbl_boot_app_emmc_uda_linux_j7200_evm_mcu1_0_freertos_TestApp_release.appimage, the errors is same as Q2.

So now Q1 and Q2 have same error that can not boot from emmc UDA

Hi Shicheng,

Can you try the following steps:

• Follow all the steps mentioned above.
• Download the 10.0 linux SDK of J7200.
• Go to <LINUX_SDK>/board-support/<Linux folder>/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts and make the following edits:
  • ie:the bootargs parameter needs to be added as per the below image.
  • 
• After that go back to the <Linux SDK> directory and run the following command :
  • make linux-dtbs
• Copy the dtb present in <LINUX_SDK>/board-support/<Linux folder>/arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dtb to the the following folder:
  
  
  • <PDK FOLDER>/packages/ti/boot/sbl/tools/combined_appimage/bin/j7200_evm
• Copy the  k3-j7200-common-proc-board.dtb  to <PDK FOLDER>/packages/ti/boot/sbl/tools/combined_appimage/bin/j7200_evm and rename it as  as base-board.dtb
• Now,Run the constructappimageshlos.sh present in <PDK>/packages/ti/boot/sbl/example/boot_app/scripts/hlos
• Copy the tidtb_linux.appimage to the eMMC FAT32 partition

Regards

Gokul

Hi Gokul

Gokul Praveen said:

Now,Run the constructappimageshlos.sh present in <PDK>/packages/ti/boot/sbl/example/boot_app/scripts/hlos

Q1. There is no such path and file in SDK 10.0.0.3, see bellow pitcure:

Q2. I only find a file called constructappimageshlos.sh  in path:<RTOS_SDK FOLDER>/mcusw/mcuss_demos/boot_app_mcu_rtos/main_domain_apps/scripts/hlos

And the Q2 method is what we are actually using, which is what I mentioned to you in my previous reply,  use can_boot_app_mcu_rtos_mcu1_0_release.appimage.

By the way, I use constructappimageshlos.sh  in path:<RTOS_SDK FOLDER>/mcusw/mcuss_demos/boot_app_mcu_rtos/main_domain_apps/scripts/hlos generate tidtb_linux.appimage, tikernelimage_linux.appimage, atf_optee.appimage and copy those to the eMMC FAT32 partition, it report same errors.

So I think it's no problem with linux kernel and dtb, Based on this, I made the following attempts，Please carefully review：

Firstly, do the same steps to generate and copy files :tiboot3.bin , tifs.bin, app, lateapp1, tidtb_linux.appimage, tikernelimage_linux.appimage, atf_optee.appimage to  SD card boot partition 

Tes1: SBL from SD card, and rootfs in SD card too eg:root=/dev/mmcblk1p2 rw rootfstype=ext4 rootwait

copy sbl_mmcsd_img_mcu1_0_release.tiimage to SD card boot partition and rename it as tiboo3.bin

copy sbl_boot_app_mmcsd_linux_j7200_evm_mcu1_0_freertos_TestApp_release.appimage and rename it as app

RESULT: It can boot linux and login successfully!

Tes2: SBL from SD card, and rootfs in eMMC UDA eg:root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait

Just rebuild the dtb as the bootargs changed and replace it in SD card boot partition. All other files are same with TEST1

RESULT: It can boot linux and login successfully!

TEST3: SBL from SD card, but rootfs in eMMC UDA  eg:root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait

still copy sbl_mmcsd_img_mcu1_0_release.tiimage to SD card boot partition and rename it as tiboo3.bin

copy sbl_boot_app_emmc_uda_linux_j7200_evm_mcu1_0_freertos_TestApp_release.appimage  to SD card boot partition and rename it as app

Keep only three files in boot partition of SD card and delete other files.

Because other files are in boot parition in eMMC UDA, rootfs is also in rootfs partition in eMMC UDA.

RESULT: SBL from SD card can load app, and app can load kernel, but when kernel load roots, it report the same errors as I mentioned before

So I think there are some problems in app: sbl_boot_app_emmc_uda_linux_j7200_evm_mcu1_0_freertos_TestApp_release.appimage

Am I right? Please check

Thanks

Hi Shicheng,

Just to confirm in Test 3 ,you have taken SBL from emmc uda and not SD card right?Also you are using the tidtb_linux.appimage respective to emmc [ie:dtb with bootargs changed to emmc(/dev/mmcblk0p2)] right,while booting sbl from emmc UDA?

Regards

Gokul

Hi Gokul

Gokul Praveen said:

you have taken SBL from emmc uda and not SD card right?

No I use sbl_mmcsd_img_mcu1_0_release.tiimage to taken SBL from SD card

Gokul Praveen said:

Also you are using the tidtb_linux.appimage respective to emmc [ie:dtb with bootargs changed to emmc(/dev/mmcblk0p2)] right,while booting sbl from emmc UDA?

There are only three files in SD card: tiboo3.bin, app, tifs.bin. And lateapp1, tidtb_linux.appimage, tikernelimage_linux.appimage, atf_optee.appimage are all in eMMC FAT32 partition.

In this case, load tiboot3.bin from SD card, and then load tifs.bin, next load app. (app is sbl_boot_app_emmc_uda_linux_j7200_evm_mcu1_0_freertos_TestApp_release.appimage compile with command: make BOARD=j7200_evm CORE=mcu1_0 boot_app_emmc_uda_linux -sj)

But app load lateapp1, tidtb_linux.appimage, tikernelimage_linux.appimage, atf_optee.appimage from eMMC UDA and it's successful.

But kernel load rootfs  which is in /dev/mmcblk0p2 failed.

The purpose of my doing this is to compare with TEST2, only change app. And kernel is load successful, but rootfs in eMMC is failed

Hi Shicheng,

Have you tried booting everything including SBL and bootapp from emmc UDA?

The reason I am asking this is because,we do not currently support taking SBL and bootapp from SD mixed with taking the other files like lateapp,atf/optee,kernel and dtb app image from eMMC.

Regards

Gokul

Hi Gokul

Thanks for your replyYes,

Gokul Praveen said:

Have you tried booting everything including SBL and bootapp from emmc UDA?

Yes, I have indeed done so, And this was the context when I first raised this question. I have add new patches in current SDK 10.0, but it not worked, still report error when loading rootfs eg: mmc0: running CQE recovery

Gokul Praveen said:

The reason I am asking this is because,we do not currently support taking SBL and bootapp from SD mixed with taking the other files like lateapp,atf/optee,kernel and dtb app image from eMMC.

The mixed method was solely employed for comparative tesing to indentify the reason of the issues. In practice, such a mixed methodology would not be implemented in actual projects.

So now, SBL booting every thing from emmc UDA, still report error: mmc0: running CQE recovery, but SBL from SD card is OK.

How to fix it? 

And have your help check the hardware schematics of eMMC. Is there any problem?

Thanks

Hi Shicheng,

Regarding this , I will try it on our end and get back to you.

I will also loop in the hardware expert to see if there any issues in the hardware schematics.

Regards

Gokul

Hi Gokul

Add some information.

We add some debug print in mmc driver, and found that error:

mmc0: cqhci:IRQ status: 0x00000002   cmd_err0r=0 data_error=-5

Maybe you can see some useful information from this.

Thanks

Hi Shicheng,

I have reproduced this issue on my end and have reported this issue to the internal team.

An alternative that I would suggest would be to use the SBL development workflow which goes through u-boot:

I am attaching the steps for the same below:

• Copy the below file as tiboot3.bin to the boot partition (fat32) partition of emmc uda/

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/sbl_5F00_emmc_5F00_uda_5F00_img_5F00_hlos_5F00_mcu1_5F00_0_5F00_release.tiimage

• Copy the below file as app to the boot partition (fat32) partition of emmc uda.
  • https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/combined_5F00_dev.appimage
• Copy the below file as tifs.bin to the boot partition (fat32) partition of emmc uda.
  
  • https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/2746.tifs.bin
• Copy the below file as u-boot.img to the boot partition (fat32) partition of emmc uda.
  • https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/5460.u_2D00_boot.img
• Once that is done,boot using emmc uda and get into the uboot command prompt and enter the following commands:

  • >setenv args_mmc "run finduuid;setenv bootargs console=ttyS2,115200n8  root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait"
    >setenv bootdev 0
    >setenv mmcdev 0
    >setenv bootpart 0:2

NOTE:ENSURE that rootfs is present in (/dev/mmcblk0p2)[EXT4] partition of emmc.

Regards

Gokul

Hi Gokul

Thanks for your reply.

Gokul Praveen said:

An alternative that I would suggest would be to use the SBL development workflow which goes through u-boot:

We have already verified that boot with u-boot from emmc is OK.

The finally method we want to use is still boot with SBL from emmc.

It is a good news that you can reproduce the problem. Is there any process?