• State Resolved
  • Locked Locked
  • Replies 27 replies
  • Subscribers 100 subscribers
  • Views 1068 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TDA4VH-Q1: TDA4VH - DFU blocking the TDA4 Booting

CH Mallesh
Prodigy 120 points
Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Hi TI,

I have flashed the TI-Linux image in TDA4VH 140 SIP in USB boot mode(0 1 0 1)
Then I have changes the boot mode from USB(0101) to OSPI(1000)
After That if hard reset the TDA4 (power off - on) it is not booting automatically ..
Then I disconnected the DFU cable and did the power reset It was Booted automatically.

Why DFU is blocking here we need to set any Switches in TDA4.??

Can you elaborate bit more about the boot process 
How can we achieve automatic boot mode even DFU connected also ..?



Regards,
Mallesh CH

  • 0
    TI__Guru 55835 points

    Hi Mallesh CH

    Are you testing this on EVM or custom board?

    Can you share the complete boot switch settings including primary and backup boot mode as well?

    Please confirm that you are doing the correct boot switch setting as per the doc 

    https://www.ti.com/lit/an/spracy5/spracy5.pdf?ts=1716376561323&ref_url=https%253A%252F%252Fwww.google.com%252F

    Regards
    Diwakar

  • 0 in reply to Diwakar Dhyani
    Prodigy 120 points

    Hi Diwakar,

    We are using the custom boards OSPAS TDA140VH. and below is the switch configuration we are using.
    While flashing the board is  in USB mode (0101) this time we are connect the DFU and UART connections.
    once flashing is Done do power reset and change DIP switch from USB mode to OSPI mode (1000) Board is not booted if remove DFU cable then only Board gets booting up.

    DIP Switch configurations

    SW5000/SW6000
    SW5001/SW6001
    Mode
    1 1 1 1 1 0 0 0 No-boot/Dev boot
    0 1 0 1 0 0 0 0 USB
    1 0 0 1 0 0 0 0

    eMMC (not confirmed)
    1 0 0 0

    0 0 0 0

    OSPI


    Disconnect the DFU cable and do power reset Board is booting automatically.

    So conclusion is 
    DFU cable connected board is not booted when power reset is done in OSPI (1000) mode 

    Thanks,
    Mallesh c h

  • 0 in reply to CH Mallesh
    TI__Guru 55835 points

    Hi Mallesh 

    My assumption is primary boot is configured as DFU and secondary boot is configured as ospi that is why the issue is coming.

    Can you dump the CTRLMMR_WKUP_DEVSTAT and MAIN_DEVSTAT registers.

    Regards
    Diwakar

  • 0 in reply to Diwakar Dhyani
    Prodigy 120 points


    Can you find TI-LINUX booting stages while flashing 
    Each and every time DFU was detecting then only Boot was started.




    Diwakar Dhyani said:

    Can you dump the CTRLMMR_WKUP_DEVSTAT and MAIN_DEVSTAT registers.

    What your expecting to do ..I did not get your point? can you elaborate bit more



    Another thing after flash we can not identify the SRAM memory utilization in ON-chip and MAIN ,MCU domains as well. 
    Can you suggest how can we read SRAM details after entered into Linux prompt.

  • 0 in reply to CH Mallesh
    TI__Guru 55835 points

    Hi Mallesh 

    CH Mallesh said:
    Can you find TI-LINUX booting stages while flashing 
    Each and every time DFU was detecting then only Boot was started.

    This is some custom script  you are having , Do you mean to say that once you do the power on you are always getting a dfu boot mode even though you kept it in OSPI boot mode ?

    CH Mallesh said:
    What your expecting to do ..I did not get your point? can you elaborate bit more

    DEV_STAT registers are used by the Rom to determine the boot mode.Please check the TRM and dump the register value 

    Regards
    Diwakar

  • 0 in reply to Diwakar Dhyani
    Prodigy 120 points
    Diwakar Dhyani said:
    This is some custom script  you are having , Do you mean to say that once you do the power on you are always getting a dfu boot mode even though you kept it in OSPI boot mode ?

    I think No..
    Once power Up until unless remove the DFU cable TDA4 is not booting in OSPI boot mode .

    If you confuse on the issue please see the starting conversation


    See below is the registers value




    root@j784s4-ospas140:~# devmem2 0x43000000
    /dev/mem opened.
    Memory mapped at address 0xffffb161b000.
    Read at address 0x43000000 (0xffffb161b000): 0x61800214
    root@j784s4-ospas140:~# devmem2 0x43000030
    /dev/mem opened.
    Memory mapped at address 0xffffa693e000.
    Read at address 0x43000030 (0xffffa693e030): 0x00070310
    root@j784s4-ospas140:~# devmem2 0x00100000
    /dev/mem opened.
    Memory mapped at address 0xffff92677000.
    Read at address 0x00100000 (0xffff92677000): 0x61800214
    root@j784s4-ospas140:~# devmem2 0x00100030
    /dev/mem opened.
    Memory mapped at address 0xffff912ed000.
    Read at address 0x00100030 (0xffff912ed030): 0x00000007
    root@j784s4-ospas140:~#

  • +1 in reply to CH Mallesh
    TI__Guru 55835 points

    Hi Mallesh 

    CH Mallesh said:
    root@j784s4-ospas140:~# devmem2 0x43000030
    /dev/mem opened.
    Memory mapped at address 0xffffa693e000.
    Read at address 0x43000030 (0xffffa693e030): 0x00070310

    As per the dev stat value is 0x00070310

    Lets map this to the boot mode as per the TRM

    CTRLMMR_WKUP_DEVSTAT[23:16] -> BOOTMODE pin 

    CTRLMMR_WKUP_DEVSTAT[9:0] -> MCU_BOOTMODE pin

    In you case MCU_BOOTMODE pin value is 1100010000 and BOOT pin value is 00000111.

    Primary boot mode pin is 1 and mcu3,4,5 is (010) 

    Regards
    Diwakar

  • 0 in reply to Diwakar Dhyani
    Prodigy 120 points
    Diwakar Dhyani said:
    In you case MCU_BOOTMODE pin value is 1100010000 and BOOT pin value is 00000111.


    Yes as per my dev stat value we can identify if we convert 


    Diwakar Dhyani said:
    Primary boot mode pin is 1 and mcu3,4,5 is (010)

    As MCU_BOOTMODE pin and  BOOT pin 
    what is the expected values or pin change ..??
    Can you please explain bit clear what we have to set the values.
    What is the my dev stat values ..?
    What is expected/correct values..?
    Based on that I will change my code and test it here..

    Please find the DEV STAT values from USB(0101) and OSPI(1000) boot modes 

    (USB mode: 0101)
    root@j784s4-ospas140:~# devmem2 0x43000030
    /dev/mem opened.
    Memory mapped at address 0xffffad57a000.
    Read at address 0x43000030 (0xffffad57a030): 0x00070010
    root@j784s4-ospas140:~# devmem2 0x00100030
    /dev/mem opened.
    Memory mapped at address 0xffffaf192000.
    Read at address 0x00100030 (0xffffaf192030): 0x00000007
    root@j784s4-ospas140:~#

    (OSPI mode: 1000)
    root@j784s4-ospas140:~# devmem2 0x43000030
    /dev/mem opened.
    Memory mapped at address 0xffff9567d000.
    Read at address 0x43000030 (0xffff9567d030): 0x00060008
    root@j784s4-ospas140:~# devmem2 0x00100030
    /dev/mem opened.
    Memory mapped at address 0xffff8b344000.
    Read at address 0x00100030 (0xffff8b344030): 0x00000006
    root@j784s4-ospas140:~#

    We are having issue in OSPI boot mode

    As per below

    CTRLMMR_WKUP_DEVSTAT[23:16] -> BOOTMODE pin 

    CTRLMMR_WKUP_DEVSTAT[9:0] -> MCU_BOOTMODE pin

    0x00060008 --> 00000000000001100000000000001000

    MCU_BOOTMODE --> 0000001000

    Boot pin  --> 00001100

    In above diagram for OSPI
    primary boot mode is 0 MCU 5,4 is 0 MCU 3 is 1  ==> 1000

    So I hope it match our boot mode

    When Board in OSPI boot mode, DFU cable connected TDA4 is not booting


  • 0 in reply to CH Mallesh
    TI__Guru 55835 points

    Hi Mallesh 

    Can you do a small experiment keep the device in OSPI boot mode keep usb cable connected 
    then run lsusb on the host and share the result.
    Regards
    Diwakar
  • 0 in reply to Diwakar Dhyani
    Prodigy 120 points

    I have Done that already lsusb is not found 
    I will try to include in our build.

    and I have updated some thing can you please take a look..

  • 0 in reply to CH Mallesh
    TI__Guru 55835 points

    Hi Mallesh 

    CH Mallesh said:
    I have Done that already lsusb is not found 

    Which build you are talking about are you using windows or ubuntu ?

    We need to check whether the HOST is detecting the board or there is some hardware issue which we need to find out.

    Regards
    Diwakar

  • 0 in reply to CH Mallesh
    Prodigy 120 points
    Diwakar Dhyani said:
    Which build you are talking about are you using windows or ubuntu ?

    We are using Ubuntu in may host machine 
    After flash TI-Linux images, in board consol if enter lsusb it is not found

    Host detected otherwise How we will flash the images..?

    You want me to check lsusb in host(ubuntu) machine.. ??

  • 0 in reply to CH Mallesh
    TI__Guru 55835 points

    Hi Mallesh 

    As you said earlier when you keep the device in OSPI boot mode while the USB cable is still connected , your ovbservation is that you are not able to boot.
    In the above circumstances on the host (ubuntu) what you are seeing when you are giving  lsusb command or may be you can check dmesg on the host.
    Regards
    Diwakar 
  • 0 in reply to Diwakar Dhyani
    Prodigy 120 points
    Diwakar Dhyani said:
    As you said earlier when you keep the device in OSPI boot mode while the USB cable is still connected , your ovbservation is that you are not able to boot.

    Yes .Correct 



    lsusb and dmesg from host (Vm ware ubuntu) attached: host_logs5460.host_logs.txt

    lsusb and dmesg from board console attached: tda4_dmesg_logs

    Fullscreen tda4_dmesg_logs.txt Download 
    root@j784s4-ospas140:~# 
root@j784s4-ospas140:~# dmes
root@j784s4-ospas140:~# dmesg 
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
[    0.000000] Linux version 6.1.46-g5892b80d6b (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Mon Nov 27 16:11:04 UTC 2023
[    0.000000] Machine model: Aptiv OSPAS-140 TDA4VH
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002840000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000d8fe00000, size 1792 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    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] 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] 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] 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] 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] 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] 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] 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] Reserved memory: created DMA memory pool at 0x00000000a4000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a4000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a4100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a4100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a5000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a5000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a5100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a5100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a6000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a6000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a6100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a6100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a7000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a7000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a7100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a7100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a8000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node c71-dma-memory@a8000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a8100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node c71-memory@a8100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a9000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node c71-dma-memory@a9000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a9100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node c71-memory@a9100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000aa000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node c71-dma-memory@aa000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000aa100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node c71-memory@aa100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000ab000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node c71-dma-memory@ab000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000ab100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node c71-memory@ab100000, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x0000000dffffefff]
[    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-0x00000000abffffff]
[    0.000000]   node   0: [mem 0x00000000ac000000-0x00000000ffffefff]
[    0.000000]   node   0: [mem 0x0000000880000000-0x0000000dffffefff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x0000000dffffefff]
[    0.000000] On node 0, zone Normal: 1 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 1 pages in unavailable ranges
[    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 19 pages/cpu s38376 r8192 d31256 u77824
[    0.000000] pcpu-alloc: s38376 r8192 d31256 u77824 alloc=19*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[    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] Built 1 zonelists, mobility grouping on.  Total pages: 6193150
[    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02840000 mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),256k(ospi.env.backup),57088k@8m(ospi.rootfs),256k(ospi.phypattern);spi-nand0:512k(ospi_nand.tiboot3),2m(ospi_nand.tispl),4m(ospi_nand.u-boot),256k(ospi_nand.env),256k(ospi_nand.env.backup),98048k@32m(ospi_nand.rootfs),256k@130816k(ospi_nand.phypattern) root=PARTUUID=4e9346af-040c-ee40-8493-2f2ccbe9b015 rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
[    0.000000] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: area num 8.
[    0.000000] software IO TLB: mapped [mem 0x00000000fbfff000-0x00000000fffff000] (64MB)
[    0.000000] Memory: 22530588K/25165816K available (12352K kernel code, 1268K rwdata, 4036K rodata, 2112K init, 435K bss, 800220K reserved, 1835008K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, 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=8.
[    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=8
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: [Firmware Bug]: GICR region 0x0000000001900000 has overlapping address
[    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 @0x0000000880050000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000880060000
[    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.008405] Console: colour dummy device 80x25
[    0.012977] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.023649] pid_max: default: 32768 minimum: 301
[    0.028386] LSM: Security Framework initializing
[    0.033208] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.041013] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.050151] cblist_init_generic: Setting adjustable number of callback queues.
[    0.057547] cblist_init_generic: Setting shift to 3 and lim to 1.
[    0.063811] cblist_init_generic: Setting adjustable number of callback queues.
[    0.071197] cblist_init_generic: Setting shift to 3 and lim to 1.
[    0.077502] rcu: Hierarchical SRCU implementation.
[    0.082400] rcu: 	Max phase no-delay instances is 1000.
[    0.087883] Platform MSI: msi-controller@1820000 domain created
[    0.094063] PCI/MSI: /bus@100000/interrupt-controller@1800000/msi-controller@1820000 domain created
[    0.103464] EFI services will not be available.
[    0.108297] smp: Bringing up secondary CPUs ...
[    0.121396] Detected PIPT I-cache on CPU1
[    0.121453] GICv3: CPU1: found redistributor 1 region 0:0x0000000001920000
[    0.121467] GICv3: CPU1: using allocated LPI pending table @0x0000000880070000
[    0.121496] CPU1: Booted secondary processor 0x0000000001 [0x411fd080]
[    0.129960] Detected PIPT I-cache on CPU2
[    0.129997] GICv3: CPU2: found redistributor 2 region 0:0x0000000001940000
[    0.130010] GICv3: CPU2: using allocated LPI pending table @0x0000000880080000
[    0.130033] CPU2: Booted secondary processor 0x0000000002 [0x411fd080]
[    0.138445] Detected PIPT I-cache on CPU3
[    0.138488] GICv3: CPU3: found redistributor 3 region 0:0x0000000001960000
[    0.138500] GICv3: CPU3: using allocated LPI pending table @0x0000000880090000
[    0.138523] CPU3: Booted secondary processor 0x0000000003 [0x411fd080]
[    0.146986] Detected PIPT I-cache on CPU4
[    0.147061] GICv3: CPU4: found redistributor 100 region 0:0x0000000001980000
[    0.147075] GICv3: CPU4: using allocated LPI pending table @0x00000008800a0000
[    0.147107] CPU4: Booted secondary processor 0x0000000100 [0x411fd080]
[    0.155581] Detected PIPT I-cache on CPU5
[    0.155631] GICv3: CPU5: found redistributor 101 region 0:0x00000000019a0000
[    0.155644] GICv3: CPU5: using allocated LPI pending table @0x00000008800b0000
[    0.155668] CPU5: Booted secondary processor 0x0000000101 [0x411fd080]
[    0.164105] Detected PIPT I-cache on CPU6
[    0.164155] GICv3: CPU6: found redistributor 102 region 0:0x00000000019c0000
[    0.164167] GICv3: CPU6: using allocated LPI pending table @0x00000008800c0000
[    0.164191] CPU6: Booted secondary processor 0x0000000102 [0x411fd080]
[    0.172626] Detected PIPT I-cache on CPU7
[    0.172679] GICv3: CPU7: found redistributor 103 region 0:0x00000000019e0000
[    0.172692] GICv3: CPU7: using allocated LPI pending table @0x00000008800d0000
[    0.172716] CPU7: Booted secondary processor 0x0000000103 [0x411fd080]
[    0.172761] smp: Brought up 1 node, 8 CPUs
[    0.353755] SMP: Total of 8 processors activated.
[    0.358561] CPU features: detected: 32-bit EL0 Support
[    0.363817] CPU features: detected: CRC32 instructions
[    0.369112] CPU: All CPU(s) started at EL2
[    0.373302] alternatives: applying system-wide alternatives
[    0.379997] devtmpfs: initialized
[    0.392440] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.402422] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[    0.440608] pinctrl core: initialized pinctrl subsystem
[    0.446268] DMI not present or invalid.
[    0.450507] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.457918] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations
[    0.465964] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.474711] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.482947] audit: initializing netlink subsys (disabled)
[    0.488566] audit: type=2000 audit(0.348:1): state=initialized audit_enabled=0 res=1
[    0.488770] thermal_sys: Registered thermal governor 'step_wise'
[    0.496486] thermal_sys: Registered thermal governor 'power_allocator'
[    0.502703] cpuidle: using governor menu
[    0.513445] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.520470] ASID allocator initialised with 65536 entries
[    0.533285] platform a000000.dp-bridge: Fixed dependency cycle(s) with /bus@100000/dss@4a00000
[    0.543816] platform a000000.dp-bridge: Fixed dependency cycle(s) with /dp0-connector
[    0.552273] KASLR disabled due to lack of seed
[    0.559736] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    0.566686] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.573092] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[    0.580028] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.586430] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    0.593365] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.599767] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[    0.606702] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    0.613819] k3-chipinfo 43000014.chipid: Family:J784S4 rev:SR1.0 JTAGID[0x0bb8002f] Detected
[    0.623279] iommu: Default domain type: Translated 
[    0.628266] iommu: DMA domain TLB invalidation policy: strict mode 
[    0.634792] SCSI subsystem initialized
[    0.638691] libata version 3.00 loaded.
[    0.638773] usbcore: registered new interface driver usbfs
[    0.644392] usbcore: registered new interface driver hub
[    0.649833] usbcore: registered new device driver usb
[    0.655166] pps_core: LinuxPPS API ver. 1 registered
[    0.660237] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.669575] PTP clock support registered
[    0.673653] EDAC MC: Ver: 3.0.0
[    0.677308] FPGA manager framework
[    0.680816] Advanced Linux Sound Architecture Driver Initialized.
[    0.687465] clocksource: Switched to clocksource arch_sys_counter
[    0.693807] VFS: Disk quotas dquot_6.6.0
[    0.697834] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.707820] NET: Registered PF_INET protocol family
[    0.713211] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.726104] tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.735161] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.743091] TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.752182] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
[    0.760841] TCP: Hash tables configured (established 262144 bind 65536)
[    0.767739] UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.775087] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.782975] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.789051] RPC: Registered named UNIX socket transport module.
[    0.795111] RPC: Registered udp transport module.
[    0.799913] RPC: Registered tcp transport module.
[    0.804717] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.811298] NET: Registered PF_XDP protocol family
[    0.816205] PCI: CLS 0 bytes, default 64
[    0.820875] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
[    0.830135] Initialise system trusted keyrings
[    0.834795] workingset: timestamp_bits=46 max_order=23 bucket_order=0
[    0.843495] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.849701] NFS: Registering the id_resolver key type
[    0.854881] Key type id_resolver registered
[    0.859153] Key type id_legacy registered
[    0.863274] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.870124] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.896632] Key type asymmetric registered
[    0.900816] Asymmetric key parser 'x509' registered
[    0.905822] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.913471] io scheduler mq-deadline registered
[    0.918103] io scheduler kyber registered
[    0.924326] pinctrl-single 4301c000.pinctrl: 13 pins, size 52
[    0.930284] pinctrl-single 4301c038.pinctrl: 11 pins, size 44
[    0.936375] pinctrl-single 4301c068.pinctrl: 72 pins, size 288
[    0.942416] pinctrl-single 4301c190.pinctrl: 1 pins, size 4
[    0.948252] pinctrl-single 11c000.pinctrl: 72 pins, size 288
[    0.954516] pinctrl-single a40000.pinctrl: 512 pins, size 2048
[    0.964201] Serial: 8250/16550 driver, 6 ports, IRQ sharing enabled
[    0.975634] loop: module loaded
[    0.979415] megasas: 07.719.03.00-rc1
[    0.984671] tun: Universal TUN/TAP device driver, 1.6
[    0.990151] thunder_xcv, ver 1.0
[    0.993471] thunder_bgx, ver 1.0
[    0.996778] nicpf, ver 1.0
[    0.999629] e1000: Intel(R) PRO/1000 Network Driver
[    1.004611] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.010495] e1000e: Intel(R) PRO/1000 Network Driver
[    1.015566] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.021626] igb: Intel(R) Gigabit Ethernet Network Driver
[    1.027140] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.032841] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    1.039243] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.045381] sky2: driver version 1.30
[    1.049521] VFIO - User Level meta-driver version: 0.3
[    1.055100] usbcore: registered new interface driver usb-storage
[    1.061539] i2c_dev: i2c /dev entries driver
[    1.066432] sdhci: Secure Digital Host Controller Interface driver
[    1.072751] sdhci: Copyright(c) Pierre Ossman
[    1.077308] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.083480] ledtrig-cpu: registered to indicate activity on CPUs
[    1.089708] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.096433] usbcore: registered new interface driver usbhid
[    1.102127] usbhid: USB HID core driver
[    1.106518] optee: probing for conduit method.
[    1.111076] optee: revision 4.0 (2a5b1d12)
[    1.127485] optee: dynamic shared memory is enabled
[    1.136878] optee: initialized driver
[    1.141621] Initializing XFRM netlink socket
[    1.146007] NET: Registered PF_PACKET protocol family
[    1.151210] Key type dns_resolver registered
[    1.155770] registered taskstats version 1
[    1.159970] Loading compiled-in X.509 certificates
[    1.170778] ti-sci 44083000.system-controller: ABI: 3.1 (firmware rev 0x0009 '9.1.2--v09.01.02 (Kool Koala)')
[    1.210374] omap_i2c 2020000.i2c: bus 0 rev0.12 at 400 kHz
[    1.216175] ti-sci-intr 42200000.interrupt-controller: Interrupt Router 177 domain created
[    1.224712] ti-sci-intr bus@100000:interrupt-controller@a00000: Interrupt Router 10 domain created
[    1.233953] ti-sci-intr 310e0000.interrupt-controller: Interrupt Router 283 domain created
[    1.242600] ti-sci-inta 33d00000.msi-controller: Interrupt Aggregator domain 321 created
[    1.256467] ti-udma 311a0000.dma-controller: Number of rings: 48
[    1.263264] ti-udma 311a0000.dma-controller: Channels: 24 (bchan: 0, tchan: 8, rchan: 16)
[    1.272468] k3-ringacc 2b800000.ringacc: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:328
[    1.282344] k3-ringacc 2b800000.ringacc: dma-ring-reset-quirk: disabled
[    1.289103] k3-ringacc 2b800000.ringacc: RA Proxy rev. 66349100, num_proxies:64
[    1.298035] k3-ringacc 3c000000.ringacc: Ring Accelerator probed rings:1024, gp-rings[878,128] sci-dev-id:315
[    1.308179] k3-ringacc 3c000000.ringacc: dma-ring-reset-quirk: disabled
[    1.314938] k3-ringacc 3c000000.ringacc: RA Proxy rev. 66349100, num_proxies:64
[    1.322849] 40a00000.serial: ttyS0 at MMIO 0x40a00000 (irq = 213, base_baud = 6000000) is a 8250
[    1.332275] 2810000.serial: ttyS1 at MMIO 0x2810000 (irq = 214, base_baud = 3000000) is a 8250
[    1.341450] 2840000.serial: ttyS2 at MMIO 0x2840000 (irq = 215, base_baud = 3000000) is a 8250
[    1.350304] printk: console [ttyS2] enabled
[    1.358745] printk: bootconsole [ns16550a0] disabled
[    1.369122] 2850000.serial: ttyS5 at MMIO 0x2850000 (irq = 216, base_baud = 3000000) is a 8250
[    1.379138] am65-cpts 310d0000.cpts: CPTS ver 0x4e8a010c, freq:250000000, add_val:3 pps:0
[    1.387982] mmc0: CQHCI version 5.10
[    1.390754] omap-mailbox 31f80000.mailbox: omap mailbox rev 0x66fca100
[    1.398343] omap-mailbox 31f81000.mailbox: omap mailbox rev 0x66fca100
[    1.405121] omap-mailbox 31f82000.mailbox: omap mailbox rev 0x66fca100
[    1.411890] omap-mailbox 31f83000.mailbox: omap mailbox rev 0x66fca100
[    1.418665] omap-mailbox 31f84000.mailbox: omap mailbox rev 0x66fca100
[    1.425437] omap-mailbox 31f85000.mailbox: omap mailbox rev 0x66fca100
[    1.432513] mmc0: SDHCI controller on 4f80000.mmc [4f80000.mmc] using ADMA 64-bit
[    1.436897] ti-udma 285c0000.dma-controller: Channels: 22 (tchan: 11, rchan: 11, gp-rflow: 8)
[    1.449977] ti-udma 31150000.dma-controller: Channels: 66 (tchan: 33, rchan: 33, gp-rflow: 16)
[    1.461993] spi-nor spi0.0: mt35xu512aba (65536 Kbytes)
[    1.467242] 7 cmdlinepart partitions found on MTD device 47040000.spi.0
[    1.473841] Creating 7 MTD partitions on "47040000.spi.0":
[    1.479311] 0x000000000000-0x000000080000 : "ospi.tiboot3"
[    1.485545] 0x000000080000-0x000000280000 : "ospi.tispl"
[    1.491429] 0x000000280000-0x000000680000 : "ospi.u-boot"
[    1.497383] 0x000000680000-0x0000006c0000 : "ospi.env"
[    1.503064] 0x0000006c0000-0x000000700000 : "ospi.env.backup"
[    1.509406] 0x000000800000-0x000003fc0000 : "ospi.rootfs"
[    1.515375] 0x000003fc0000-0x000004000000 : "ospi.phypattern"
[    1.522501] debugfs: Directory 'pd:74' with parent 'pm_genpd' already present!
[    1.529772] debugfs: Directory 'pd:73' with parent 'pm_genpd' already present!
[    1.529888] mmc0: Command Queue Engine enabled
[    1.536996] debugfs: Directory 'pd:72' with parent 'pm_genpd' already present!
[    1.541418] mmc0: new HS200 MMC card at address 0001
[    1.549133] debugfs: Directory 'pd:335' with parent 'pm_genpd' already present!
[    1.553963] mmcblk0: mmc0:0001 G1M15M 59.3 GiB 
[    1.560882] debugfs: Directory 'pd:333' with parent 'pm_genpd' already present!
[    1.567706]  mmcblk0: p1
[    1.572703] debugfs: Directory 'pd:332' with parent 'pm_genpd' already present!
[    1.575501] mmcblk0boot0: mmc0:0001 G1M15M 31.5 MiB 
[    1.588151] mmcblk0boot1: mmc0:0001 G1M15M 31.5 MiB 
[    1.592567] ALSA device list:
[    1.593679] mmcblk0rpmb: mmc0:0001 G1M15M 4.00 MiB, chardev (240:0)
[    1.596070]   No soundcards found.
[    1.613318] EXT4-fs (mmcblk0p1): recovery complete
[    1.618589] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Quota mode: none.
[    1.627125] VFS: Mounted root (ext4 filesystem) on device 179:1.
[    1.633407] devtmpfs: mounted
[    1.637266] Freeing unused kernel memory: 2112K
[    1.641897] Run /sbin/init as init process
[    1.645987]   with arguments:
[    1.645990]     /sbin/init
[    1.645992]   with environment:
[    1.645993]     HOME=/
[    1.645995]     TERM=linux
[    1.710780] systemd[1]: System time before build time, advancing clock.
[    1.733884] NET: Registered PF_INET6 protocol family
[    1.739405] Segment Routing with IPv6
[    1.743088] In-situ OAM (IOAM) with IPv6
[    1.757841] systemd[1]: systemd 250.5+ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=hybrid)
[    1.789387] systemd[1]: Detected architecture arm64.
[    1.863780] systemd[1]: Hostname set to <j784s4-ospas140>.
[    1.999868] systemd[1]: /etc/systemd/system/sync-clocks.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
[    2.038107] systemd[1]: Queued start job for default target Multi-User System.
[    2.081167] systemd[1]: Created slice Slice /system/getty.
[    2.104313] systemd[1]: Created slice Slice /system/modprobe.
[    2.128133] systemd[1]: Created slice Slice /system/serial-getty.
[    2.152074] systemd[1]: Created slice User and Session Slice.
[    2.171615] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    2.195571] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.219617] systemd[1]: Reached target Path Units.
[    2.235526] systemd[1]: Reached target Remote File Systems.
[    2.255503] systemd[1]: Reached target Slice Units.
[    2.271523] systemd[1]: Reached target Swaps.
[    2.289890] systemd[1]: Listening on Process Core Dump Socket.
[    2.311612] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    2.335775] systemd[1]: Listening on Journal Audit Socket.
[    2.355671] systemd[1]: Listening on Journal Socket (/dev/log).
[    2.375685] systemd[1]: Listening on Journal Socket.
[    2.391716] systemd[1]: Listening on Network Service Netlink Socket.
[    2.415730] systemd[1]: Listening on udev Control Socket.
[    2.435623] systemd[1]: Listening on udev Kernel Socket.
[    2.455655] systemd[1]: Listening on User Database Manager Socket.
[    2.491708] systemd[1]: Mounting Huge Pages File System...
[    2.509458] systemd[1]: Mounting POSIX Message Queue File System...
[    2.533507] systemd[1]: Mounting Kernel Debug File System...
[    2.547701] systemd[1]: Kernel Trace File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/tracing).
[    2.562549] systemd[1]: Mounting Temporary Directory /tmp...
[    2.581800] systemd[1]: Starting Create List of Static Device Nodes...
[    2.605624] systemd[1]: Starting Load Kernel Module configfs...
[    2.625597] systemd[1]: Starting Load Kernel Module drm...
[    2.642172] systemd[1]: Starting Load Kernel Module fuse...
[    2.648333] fuse: init (API version 7.37)
[    2.659636] systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
[    2.675073] systemd[1]: Starting Journal Service...
[    2.694861] systemd[1]: Starting Load Kernel Modules...
[    2.703610] cryptodev: loading out-of-tree module taints kernel.
[    2.711999] cryptodev: driver 1.12 loaded.
[    2.714090] systemd[1]: Starting Generate network units from Kernel command line...
[    2.741833] systemd[1]: Starting Remount Root and Kernel File Systems...
[    2.751669] EXT4-fs (mmcblk0p1): re-mounted. Quota mode: none.
[    2.774028] systemd[1]: Starting Coldplug All udev Devices...
[    2.795635] systemd[1]: Started Journal Service.
[    3.086685] systemd-journald[184]: Received client request to flush runtime journal.
[    3.333358] audit: type=1334 audit(1651167746.620:2): prog-id=5 op=LOAD
[    3.339984] audit: type=1334 audit(1651167746.628:3): prog-id=6 op=LOAD
[    3.446630] random: crng init done
[    3.470211] mc: Linux media interface: v0.10
[    3.487922] videodev: Linux video capture interface: v2.00
[    3.504328] k3-dsp-rproc 64800000.dsp: assigned reserved memory node c71-dma-memory@a8000000
[    3.514548] k3-dsp-rproc 64800000.dsp: configured DSP for remoteproc mode
[    3.522063] PVR_K:  213: Device: 4e20000000.gpu
[    3.529142] PVR_K:  213: Read BVNC 36.53.104.796 from HW device registers
[    3.529949] remoteproc remoteproc0: 64800000.dsp is available
[    3.542865] remoteproc remoteproc0: Direct firmware load for j784s4-c71_0-fw failed with error -2
[    3.544250] PVR_K:  213: RGX Device registered BVNC 36.53.104.796 with 1 core in the system
[    3.550504] k3-dsp-rproc 65800000.dsp: assigned reserved memory node c71-dma-memory@a9000000
[    3.552415] k3-dsp-rproc 65800000.dsp: configured DSP for remoteproc mode
[    3.556415] remoteproc remoteproc0: powering up 64800000.dsp
[    3.575216] remoteproc remoteproc1: 65800000.dsp is available
[    3.580102] remoteproc remoteproc0: Direct firmware load for j784s4-c71_0-fw failed with error -2
[    3.580977] [drm] Initialized pvr 23.2.6460340 20170530 for 4e20000000.gpu on minor 0
[    3.586187] remoteproc remoteproc1: Direct firmware load for j784s4-c71_1-fw failed with error -2
[    3.591876] remoteproc remoteproc0: request_firmware failed: -2
[    3.601028] k3-dsp-rproc 66800000.dsp: assigned reserved memory node c71-dma-memory@aa000000
[    3.601488] remoteproc remoteproc1: powering up 65800000.dsp
[    3.601522] remoteproc remoteproc1: Direct firmware load for j784s4-c71_1-fw failed with error -2
[    3.601528] remoteproc remoteproc1: request_firmware failed: -2
[    3.602536] cdns-mhdp8546 a000000.dp-bridge: invalid resource
[    3.602543] cdns-mhdp8546 a000000.dp-bridge: Failed to get SAPB memory resource, HDCP not supported
[    3.662059] platform 41000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[    3.667834] k3-dsp-rproc 66800000.dsp: configured DSP for remoteproc mode
[    3.679133] platform 41000000.r5f: configured R5F for IPC-only mode
[    3.686063] [drm] Initialized tidss 1.0.0 20180215 for 4a00000.dss on minor 1
[    3.692005] platform 41000000.r5f: assigned reserved memory node r5f-dma-memory@a0000000
[    3.699172] tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
[    3.702265] remoteproc remoteproc2: 66800000.dsp is available
[    3.702374] remoteproc remoteproc2: Direct firmware load for j784s4-c71_2-fw failed with error -2
[    3.702383] remoteproc remoteproc2: powering up 66800000.dsp
[    3.702394] remoteproc remoteproc2: Direct firmware load for j784s4-c71_2-fw failed with error -2
[    3.702399] remoteproc remoteproc2: request_firmware failed: -2
[    3.702780] k3-dsp-rproc 67800000.dsp: assigned reserved memory node c71-dma-memory@ab000000
[    3.703393] k3-dsp-rproc 67800000.dsp: configured DSP for remoteproc mode
[    3.703450] remoteproc remoteproc4: 67800000.dsp is available
[    3.703531] remoteproc remoteproc4: Direct firmware load for j784s4-c71_3-fw failed with error -2
[    3.703538] remoteproc remoteproc4: powering up 67800000.dsp
[    3.703549] remoteproc remoteproc4: Direct firmware load for j784s4-c71_3-fw failed with error -2
[    3.703553] remoteproc remoteproc4: request_firmware failed: -2
[    3.712222] remoteproc remoteproc3: 41000000.r5f is available
[    3.713418] tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
[    3.719052] remoteproc remoteproc3: attaching to 41000000.r5f
[    3.785591] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.793541] platform 41000000.r5f: R5F core initialized in IPC-only mode
[    3.803705] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    3.804958] rproc-virtio rproc-virtio.2.auto: assigned reserved memory node r5f-dma-memory@a0000000
[    3.810611] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.817620] virtio_rpmsg_bus virtio0: rpmsg host is online
[    3.824511] cfg80211: failed to load regulatory.db
[    3.830803] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xd
[    3.830860] rproc-virtio rproc-virtio.2.auto: registered virtio0 (type 7)
[    3.830867] remoteproc remoteproc3: remote processor 41000000.r5f is now attached
[    3.860616] platform 41400000.r5f: configured R5F for remoteproc mode
[    3.866660] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0xe
[    3.873546] omap_rng 4e10000.rng: Random Number Generator ver. 241b34c
[    3.881357] platform 41400000.r5f: assigned reserved memory node r5f-dma-memory@a1000000
[    3.916904] remoteproc remoteproc5: 41400000.r5f is available
[    3.927147] remoteproc remoteproc5: Direct firmware load for j784s4-mcu-r5f0_1-fw failed with error -2
[    3.929684] platform 5c00000.r5f: configured R5F for IPC-only mode
[    3.937742] remoteproc remoteproc5: powering up 41400000.r5f
[    3.944119] platform 5c00000.r5f: assigned reserved memory node r5f-dma-memory@a2000000
[    3.949570] remoteproc remoteproc5: Direct firmware load for j784s4-mcu-r5f0_1-fw failed with error -2
[    3.957195] cdns-csi2rx: probe of 4504000.csi-bridge failed with error -22
[    3.958070] remoteproc remoteproc6: 5c00000.r5f is available
[    3.965180] cdns-csi2rx: probe of 4514000.csi-bridge failed with error -22
[    3.966861] remoteproc remoteproc5: request_firmware failed: -2
[    3.970911] cdns-csi2rx: probe of 4524000.csi-bridge failed with error -22
[    3.973776] remoteproc remoteproc6: attaching to 5c00000.r5f
[    4.004971] platform 5c00000.r5f: R5F core initialized in IPC-only mode
[    4.016979] rproc-virtio rproc-virtio.3.auto: assigned reserved memory node r5f-dma-memory@a2000000
[    4.026387] virtio_rpmsg_bus virtio1: rpmsg host is online
[    4.031888] rproc-virtio rproc-virtio.3.auto: registered virtio1 (type 7)
[    4.033451] virtio_rpmsg_bus virtio1: creating channel ti.ethfw.ethdevice addr 0x65
[    4.038670] remoteproc remoteproc6: remote processor 5c00000.r5f is now attached
[    4.053878] platform 5d00000.r5f: configured R5F for remoteproc mode
[    4.065556] platform 5d00000.r5f: assigned reserved memory node r5f-dma-memory@a3000000
[    4.073972] remoteproc remoteproc7: 5d00000.r5f is available
[    4.079711] remoteproc remoteproc7: Direct firmware load for j784s4-main-r5f0_1-fw failed with error -2
[    4.081463] platform 5e00000.r5f: configured R5F for remoteproc mode
[    4.089107] remoteproc remoteproc7: powering up 5d00000.r5f
[    4.089125] remoteproc remoteproc7: Direct firmware load for j784s4-main-r5f0_1-fw failed with error -2
[    4.089130] remoteproc remoteproc7: request_firmware failed: -2
[    4.106327] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0x15
[    4.123699] platform 5e00000.r5f: assigned reserved memory node r5f-dma-memory@a4000000
[    4.132052] remoteproc remoteproc8: 5e00000.r5f is available
[    4.137792] remoteproc remoteproc8: Direct firmware load for j784s4-main-r5f1_0-fw failed with error -2
[    4.138459] platform 5f00000.r5f: configured R5F for remoteproc mode
[    4.147179] remoteproc remoteproc8: powering up 5e00000.r5f
[    4.153801] platform 5f00000.r5f: assigned reserved memory node r5f-dma-memory@a5000000
[    4.159084] remoteproc remoteproc8: Direct firmware load for j784s4-main-r5f1_0-fw failed with error -2
[    4.167473] remoteproc remoteproc9: 5f00000.r5f is available
[    4.176435] remoteproc remoteproc8: request_firmware failed: -2
[    4.182165] remoteproc remoteproc9: Direct firmware load for j784s4-main-r5f1_1-fw failed with error -2
[    4.184157] platform 5900000.r5f: configured R5F for remoteproc mode
[    4.184455] platform 5900000.r5f: assigned reserved memory node r5f-dma-memory@a6000000
[    4.184804] remoteproc remoteproc10: 5900000.r5f is available
[    4.184912] remoteproc remoteproc10: Direct firmware load for j784s4-main-r5f2_0-fw failed with error -2
[    4.184919] remoteproc remoteproc10: powering up 5900000.r5f
[    4.184929] remoteproc remoteproc10: Direct firmware load for j784s4-main-r5f2_0-fw failed with error -2
[    4.184933] remoteproc remoteproc10: request_firmware failed: -2
[    4.185021] platform 5a00000.r5f: configured R5F for remoteproc mode
[    4.185290] platform 5a00000.r5f: assigned reserved memory node r5f-dma-memory@a7000000
[    4.185697] remoteproc remoteproc11: 5a00000.r5f is available
[    4.187043] remoteproc remoteproc11: Direct firmware load for j784s4-main-r5f2_1-fw failed with error -2
[    4.187052] remoteproc remoteproc11: powering up 5a00000.r5f
[    4.187063] remoteproc remoteproc11: Direct firmware load for j784s4-main-r5f2_1-fw failed with error -2
[    4.187067] remoteproc remoteproc11: request_firmware failed: -2
[    4.298592] remoteproc remoteproc9: powering up 5f00000.r5f
[    4.304184] remoteproc remoteproc9: Direct firmware load for j784s4-main-r5f1_1-fw failed with error -2
[    4.313570] remoteproc remoteproc9: request_firmware failed: -2
[    4.522180] ti_cpsw_proxy_client virtio1.ti.ethfw.ethdevice.-1.101: 0 Virtual Switch Port(s), 1 Virtual MAC Only Port(s)
[    4.533053] ti_cpsw_proxy_client virtio1.ti.ethfw.ethdevice.-1.101: Virt Port: 4, Type: MAC Port, Iface: eth0, Token: 400
[    4.699276] ti_cpsw_proxy_client virtio1.ti.ethfw.ethdevice.-1.101: started virt port: 4 on interface eth0
[    4.866565] audit: type=1334 audit(1651186218.200:4): prog-id=7 op=LOAD
[    4.873203] audit: type=1334 audit(1651186218.208:5): prog-id=8 op=LOAD
[   14.767824] platform dp0-connector: deferred probe pending
[   14.773316] platform regulator-dp0-prw: deferred probe pending
[   14.779139] platform regulator-dp1-prw: deferred probe pending
[   73.113181] audit: type=1334 audit(1651186286.448:6): prog-id=9 op=LOAD
[   73.119811] audit: type=1334 audit(1651186286.456:7): prog-id=10 op=LOAD
[   73.279585] audit: type=1006 audit(1651186286.616:8): pid=329 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1
[   73.291869] audit: type=1300 audit(1651186286.616:8): arch=c00000b7 syscall=64 success=yes exit=1 a0=8 a1=ffffe432f9f8 a2=1 a3=ffffbcc86020 items=0 ppid=1 pid=329 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="(systemd)" exe="/lib/systemd/systemd" key=(null)
[   73.318073] audit: type=1327 audit(1651186286.616:8): proctitle="(systemd)"
[   73.325047] audit: type=1334 audit(1651186286.624:9): prog-id=11 op=LOAD
[   73.331753] audit: type=1300 audit(1651186286.624:9): arch=c00000b7 syscall=280 success=yes exit=8 a0=5 a1=ffffef671750 a2=78 a3=0 items=0 ppid=1 pid=329 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="systemd" exe="/lib/systemd/systemd" key=(null)
[   73.357008] audit: type=1327 audit(1651186286.624:9): proctitle="(systemd)"
[   73.363964] audit: type=1334 audit(1651186286.628:10): prog-id=11 op=UNLOAD
[   73.370913] audit: type=1334 audit(1651186286.628:11): prog-id=12 op=LOAD
root@j784s4-ospas140:~# 
root@j784s4-ospas140:~# 
root@j784s4-ospas140:~# 
root@j784s4-ospas140:~# 
root@j784s4-ospas140:~# 
root@j784s4-ospas140:~# lsusb
-sh: lsusb: not found
root@j784s4-ospas140:~#
     

    if you want me to try anything please let me know quickly ..
    Please take the priority and confirm what is causing for this issue.

    Diwakar Dhyani said:
    In the above circumstances on the host (ubuntu) what you are seeing when you are giving  lsusb command or may be you can check dmesg on the host

    above logs are keep the device in OSPI boot mode while the USB cable is connected.

  • 0 in reply to CH Mallesh
    TI__Guru 51465 points

    Board is booting correctly from OSPI when USB cable is removed, yes?  Is it possible the power from USB cable is affecting other circuit items (either processor not correctly resetting or causing incorrect boot modes to be latched)?

  • 0 in reply to Robert Eschler
    Prodigy 120 points
    Robert Eschler said:
    Board is booting correctly from OSPI when USB cable is removed

    Yes..

    Robert Eschler said:
    Is it possible the power from USB cable is affecting other circuit items

    No..! That is not correct assumption ..We observed same scenario When any USB device connected also.

  • 0 in reply to CH Mallesh
    TI__Guru 51465 points

    From the bootmode settings provided, when configured for OSPI, the backup mode is SPI - thus USB is not in the boot sequence at all.

    Are the mcu and bootmode pins used for other functions?

    Anything additional information you can provide in failing case?  is the processor running/functional - just not booting from OSPI (or is it in reset or other)?

  • 0 in reply to Robert Eschler
    Prodigy 120 points
    Robert Eschler said:
    Are the mcu and bootmode pins used for other functions?

    No..

    Robert Eschler said:
    Anything additional information you can provide in failing case?  is the processor running/functional - just not booting from OSPI (or is it in reset or other)?

    If I Remove the USB device, We are observing the logs are started from tiboot3.bin only.

    Here 2 Conditions are possible..

    Once Power On 

    1. Boot Rom Executed and then Waiting for tiboot3.bin
    or
    2. Boot Rom it self Not Executed..

    We can Not Identify whether the Boot Rom is Executed or Not. Thus it is difficult to Identify whether the processor is running or Not..

    Can you advice me How can we check whether the Boot Rom Executed or not.?

  • 0 in reply to CH Mallesh
    TI__Guru 51465 points

    The RESETOUTn signal is a reset output from the device, and should go high when the is ready too boot (execute ROM).  You could probe it and verify it goes high.  With JTAG access, you should be able to connect to processor and see program counter location.  (Not sure if you have JTAG access).  You could probe the OSPI interface to see if any activity - again would indicate the ROM is running and attempting OSPI access.

  • 0 in reply to Robert Eschler
    Prodigy 120 points

    RESETOUT signal is not going to high (Not ready for Boot) until we remove the USB device from OSPAS.

    Based on that we can say 

    Robert Eschler said:
    is the processor running/functiona

    Processor is not in functional.

  • 0 in reply to CH Mallesh
    TI__Guru 51465 points

    I had previously asked "Is it possible the power from USB cable is affecting other circuit items (either processor not correctly resetting or causing incorrect boot modes to be latched)?"  If processor is not booting when USB cable plugged in, then clearly the USB circuit is affecting something (power, reset) causing the processor not to boot.  Can you re-check?  For RESETSTATz to go high, processor needs proper power, proper clock input, and proper reset input.

  • 0 in reply to Robert Eschler
    Prodigy 120 points
    Robert Eschler said:
    I had previously asked "Is it possible the power from USB cable is affecting other circuit items

    As I Mentioned earlier, It is not only for USB cables.
    We have observed any USB devices(pendrive, USB camera) connected to OSPAS Same scenario.

  • 0 in reply to CH Mallesh
    TI__Guru 51465 points

     For RESETSTATz to go high, processor needs proper power (and sequence), proper clock input, and proper reset input.  Recommendation is to check each one with USB connected (failed state)

  • 0 in reply to Robert Eschler
    Prodigy 120 points

    When ever I removed USB device from TDA4, started Booting immediately.

    We just removed USB device remaining is as usual.
    With Same Power. clock

  • 0 in reply to CH Mallesh
    TI__Guru 51465 points

    What is OSPAS?

    When the USB device is connected, VBUS is either applied to the device for VBUS is supplied from the device.  In both conditions - power is supplied and could be affecting other peripherals/power supplies/processor.   It was observed that RESETSTATz is NOT going high until USB device is removed - thus something (USB related) is causing the processor to be reset.

  • 0 in reply to Robert Eschler
    Prodigy 120 points

    As we are discussing from Starting TDA4 is not booting while USB device connected.

    But Expected result would be TDA4 should boot under any condition either USB connected or not.

    Robert Eschler said:
    It was observed that RESETSTATz is NOT going high until USB device is removed

    Yes.. As it was observed earlier this.
    If RESETSTAT not high means ROM code it self Not executed.
    Please let us know How to overcome this issue. 

  • 0 in reply to CH Mallesh
    TI__Guru 51465 points

    If you would like to share your design, I could review and to try and locate the issue.  Yes - RESETSTATz not going high means ROM code is NOT executed.  The issue is NOT with the processor detecting USB - as its not even running (its held in reset).