PROCESSOR-SDK-AM62X: Watchdog Issues on AM62x Custom Board Based on AM62X SK Board

Anil medak

Tool/software:

Hi TI Team,

I am encountering two issues with the watchdog functionality on our AM62x custom board, which is based on the AM62X SK board reference design:

Issue with Watchdog5: The 5th watchdog appears to cause a boot failure, as indicated by the logs.

Delayed Trigger Response: Watchdogs 0, 1, 2, and 3 are taking longer than expected to trigger.

As per our configuration, the A53 core has watchdogs 0, 1, 2, 3, and 5. We are testing the watchdog trigger using the following command:

echo 1 > /dev/watchdog

Could you please help us troubleshoot these issues? Additionally, I can share the Linux configuration for the watchdog if needed.

Looking forward to your guidance.

Currently we disabled 5^th watchdog and proceeding.

Boot fail with 5th watchdog enable:

Crash log:

[ 1.443273] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19

[ 1.452340] @@@@In rti_wdt_probe starting...

[ 1.456684] @@@@In rti_wdt_probe wdt->base =(____ptrval____)

[ 1.462642] @@@@In rti_wdt_probe ending1...

[ 1.467463] @@@@In rti_wdt_probe starting...

[ 1.471790] @@@@In rti_wdt_probe wdt->base =(____ptrval____)

[ 1.477600] @@@@In rti_wdt_probe ending1...

[ 1.482327] @@@@In rti_wdt_probe starting...

[ 1.486638] @@@@In rti_wdt_probe wdt->base =(____ptrval____)

[ 1.492435] @@@@In rti_wdt_probe ending1...

[ 1.497125] @@@@In rti_wdt_probe starting...

[ 1.501421] @@@@In rti_wdt_probe wdt->base =(____ptrval____)

[ 1.507216] @@@@In rti_wdt_probe ending1...

[ 1.511912] @@@@In rti_wdt_probe starting...

[ 1.516209] @@@@In rti_wdt_probe wdt->base =(____ptrval____)

[ 1.521866] Internal error: synchronous external abort: 0000000096000010 [#1] PREEMPT SMP

[ 1.530027] Modules linked in:

[ 1.533077] CPU: 1 PID: 65 Comm: kworker/u8:2 Not tainted 6.1.33-g40c32565ca #1

[ 1.540371] Hardware name: TI AM62x ALC NGZN V4 experimental 2 (DT)

[ 1.546624] Workqueue: events_unbound deferred_probe_work_func

[ 1.552461] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)

[ 1.559408] pc : readl+0x4/0x20

[ 1.562545] lr : rti_wdt_probe+0x20c/0x484

[ 1.566630] sp : ffff80000982bb60

[ 1.569932] x29: ffff80000982bb60 x28: 0000000000000000 x27: 0000000000000000

[ 1.577056] x26: ffff800009399b78 x25: ffff00000000900d x24: 0000000000000027

[ 1.584180] x23: ffff800009362828 x22: ffff000000280800 x21: ffff0000013a7490

[ 1.591304] x20: ffff000000280810 x19: ffff0000013a7480 x18: ffffffffffffffff

[ 1.598429] x17: 0003000800000000 x16: 74656e7265687465 x15: ffff80008982b857

[ 1.605553] x14: 0000000000000000 x13: ffff800009271550 x12: 000000000000033f

[ 1.612677] x11: 0000000000000115 x10: ffff8000092c9550 x9 : ffff800009271550

[ 1.619800] x8 : 00000000ffffefff x7 : ffff8000092c9550 x6 : 0000000000000000

[ 1.626924] x5 : 000000000000bff4 x4 : 0000000000000000 x3 : 0000000000000000

[ 1.634048] x2 : 0000000000000000 x1 : ffff0000001b3900 x0 : ffff8000095d5090

[ 1.641172] Call trace:

[ 1.643610] readl+0x4/0x20

[ 1.646394] platform_probe+0x68/0xe0

[ 1.650051] really_probe+0xbc/0x2dc

[ 1.653619] __driver_probe_device+0x78/0x114

[ 1.657968] driver_probe_device+0xd8/0x15c

[ 1.662143] __device_attach_driver+0xb8/0x134

[ 1.666576] bus_for_each_drv+0x78/0xd0

[ 1.670404] __device_attach+0xa8/0x1c0

[ 1.674232] device_initial_probe+0x14/0x20

[ 1.678404] bus_probe_device+0x9c/0xa4

[ 1.682232] deferred_probe_work_func+0x88/0xc0

[ 1.686753] process_one_work+0x1d0/0x320

[ 1.690755] worker_thread+0x2c8/0x444

[ 1.694494] kthread+0x10c/0x110

[ 1.697717] ret_from_fork+0x10/0x20

[ 1.701289] Code: 910003fd 913f0000 97ffc43a d503233f (b9400000)

[ 1.707369] ---[ end trace 0000000000000000 ]---

Linux config for watchdog:

root@am62xx-alc:~# zcat /proc/config.gz | grep -i watchdog

# CONFIG_IPMI_WATCHDOG is not set

CONFIG_WATCHDOG=y

CONFIG_WATCHDOG_CORE=y

# CONFIG_WATCHDOG_NOWAYOUT is not set

CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y

CONFIG_WATCHDOG_OPEN_TIMEOUT=0

CONFIG_WATCHDOG_SYSFS=y

# CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT is not set

# Watchdog Pretimeout Governors

# CONFIG_WATCHDOG_PRETIMEOUT_GOV is not set

# Watchdog Device Drivers

# CONFIG_SOFT_WATCHDOG is not set

# CONFIG_GPIO_WATCHDOG is not set

# CONFIG_XILINX_WATCHDOG is not set

# CONFIG_ZIIRAVE_WATCHDOG is not set

CONFIG_ARM_SP805_WATCHDOG=y

CONFIG_ARM_SBSA_WATCHDOG=y

# CONFIG_CADENCE_WATCHDOG is not set

CONFIG_DW_WATCHDOG=y

CONFIG_K3_RTI_WATCHDOG=y

# CONFIG_MAX63XX_WATCHDOG is not set

# CONFIG_MAX77620_WATCHDOG is not set

CONFIG_ARM_SMC_WATCHDOG=y

# CONFIG_HP_WATCHDOG is not set

# PCI-based Watchdog Cards

# CONFIG_PCIPCWATCHDOG is not set

# USB-based Watchdog Cards

# CONFIG_USBPCWATCHDOG is not set

# CONFIG_WQ_WATCHDOG is not set

root@am62xx-alc:~#

Thanks,

Anil

7 months ago

0 Nick Saulnier 6 months ago

TI__Guru** 101960 points

Hello Anil,

First off, are you using an AM62x part number that has all 4 A53 cores? If not, then you need to disable the RTI (i.e., watchdog timer) that is associated with every core that does not exist on that specific part number: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1272468/faq-am62ax-am62x-am64x-rti_wdt_probe-error-on-linux-boot

Secondly, I see you are using SDK 9.x. Please make sure that you have applied the patch to prevent Linux from petting the watchdog before the RTI's window opens:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1311045/am623-wdt_rti-control-via-systemd/5166054#5166054

Regards,

Nick

0 Anil medak 6 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,
Thanks for the reply.
Yes, AM62x part number has all the 4 A53 cores and the rti15 is corresponds to GPU, So, after changing the clock ID in the watchdog node from assigned-clock-parents = <&k3_clks 125 2>; to assigned-clock-parents = <&k3_clks 125 4>;, the trigger time has changed from 2.30 seconds to 55 seconds

After that, I tried to enable the watchdog in U-Boot as well. However, I noticed some misbehavior in the kernel log. What am I missing?

Watchdog added in U-Boot and Kernel: The kernel log shows that CPU1, 2, and 3 failed to come online
[ 0.097787] EFI services will not be available.
[ 0.102724] smp: Bringing up secondary CPUs ...
[ 5.134743] CPU1: failed to come online
[ 5.138667] CPU1: failed in unknown state : 0x0
[ 10.262728] CPU2: failed to come online
[ 10.266650] CPU2: failed in unknown state : 0x0
[ 15.390715] CPU3: failed to come online
[ 15.394638] CPU3: failed in unknown state : 0x0
[ 15.399338] smp: Brought up 1 node, 1 CPU
[ 15.403450] SMP: Total of 1 processors activated.
[ 15.408275] CPU features: detected: 32-bit EL0 Support
[ 15.413535] CPU features: detected: CRC32 instructions
[ 15.418860] CPU: All CPU(s) started at EL2
[ 15.423046] alternatives: applying system-wide alternatives
[ 15.430224] devtmpfs: initialized

For the same kernel, after disabling the watchdog addition in U-Boot, the CPU failure log is not appearing
[ 0.097819] EFI services will not be available.
[ 0.102751] smp: Bringing up secondary CPUs ...
[ 0.108068] Detected VIPT I-cache on CPU1
[ 0.108188] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000
[ 0.108208] GICv3: CPU1: using allocated LPI pending table @0x0000000080060000
[ 0.108264] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.108976] Detected VIPT I-cache on CPU2
[ 0.109056] GICv3: CPU2: found redistributor 2 region 0:0x00000000018c0000
[ 0.109071] GICv3: CPU2: using allocated LPI pending table @0x0000000080070000
[ 0.109103] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.109729] Detected VIPT I-cache on CPU3
[ 0.109813] GICv3: CPU3: found redistributor 3 region 0:0x00000000018e0000
[ 0.109826] GICv3: CPU3: using allocated LPI pending table @0x0000000080080000
[ 0.109856] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.109929] smp: Brought up 1 node, 4 CPUs
[ 0.189660] SMP: Total of 4 processors activated.
[ 0.194473] CPU features: detected: 32-bit EL0 Support
[ 0.199745] CPU features: detected: CRC32 instructions
[ 0.205068] CPU: All CPU(s) started at EL2
[ 0.209265] alternatives: applying system-wide alternatives
[ 0.216552] devtmpfs: initialized

defconfig added for watchdog in uboot
CONFIG_CYCLIC=y
CONFIG_CYCLIC_MAX_CPU_TIME_US=1000
CONFIG_CMD_CYCLIC=y
CONFIG_WATCHDOG=y
CONFIG_CMD_WDT=y
CONFIG_WATCHDOG_AUTOSTART=y
# CONFIG_DESIGNWARE_WATCHDOG is not set
CONFIG_WDT=y
# CONFIG_WDT_APPLE is not set
# CONFIG_WDT_ASPEED is not set
# CONFIG_WDT_AST2600 is not set
# CONFIG_WDT_AT91 is not set
# CONFIG_WDT_CDNS is not set
# CONFIG_WDT_CORTINA is not set
# CONFIG_WDT_GPIO is not set
# CONFIG_WDT_MAX6370 is not set
# CONFIG_WDT_MESON_GXBB is not set
# CONFIG_WDT_ORION is not set
CONFIG_WDT_K3_RTI=y
# CONFIG_WDT_K3_RTI_LOAD_FW is not set
# CONFIG_WDT_SBSA is not set
# CONFIG_WDT_SP805 is not set
# CONFIG_WDT_STM32MP is not set
# CONFIG_XILINX_TB_WATCHDOG is not set

Here the log:

Fullscreen bootlog_after_wdt_enable_uboot_kernel.txt Download

▒▒▒▒A▒@A``@@▒ '▒
U-Boot SPL 2023.04-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 13376 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 00:42:57, Jan 13 2023

U-Boot SPL 2023.04ALC-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 1856 bytes
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04ALC-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: TI AM62x ALC NGZN V3
EEPROM not available at 81, trying to read at 82
Reading on-board EEPROM at 0x52 failed -121
DRAM:  1 GiB
Core:  73 devices, 28 uclasses, devicetree: separate
WDT:   Started watchdog@e000000 with servicing every 1000ms (60s timeout)
WDT:   Started watchdog@e010000 with servicing every 1000ms (60s timeout)
WDT:   Started watchdog@e020000 with servicing every 1000ms (60s timeout)
WDT:   Started watchdog@e030000 with servicing every 1000ms (60s timeout)
MMC:   mmc@fa10000: 0
Loading Environment from nowhere... OK
Net:   Could not get PHY for ethernet@8000000port@1: addr 0
am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed
No ethernet found.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
SD/MMC found on device 0
Failed to load 'boot.scr'
Can't set block device
## Error: "main_cpsw0_qsgmii_phyinit" not defined
20933120 bytes read in 132 ms (151.2 MiB/s)
63725 bytes read in 16 ms (3.8 MiB/s)
Working FDT set to 88000000
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 000000008feed000, end 000000008fffffff ... OK
Working FDT set to 8feed000

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.1.33-g40c32565ca (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Thu Jul  6 14:17:24 UTC 2023
[    0.000000] Machine model: TI AM62x ALC NGZN V4
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000b8000000, size 128 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009c800000, size 3 MiB
[    0.000000] OF: reserved mem: initialized node ipc-memories@9c800000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cb00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node m4f-dma-memory@9cb00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cc00000, size 14 MiB
[    0.000000] OF: reserved mem: initialized node m4f-memory@9cc00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009da00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9da00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009db00000, size 12 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@9db00000, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000bfffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x000000009c7fffff]
[    0.000000]   node   0: [mem 0x000000009c800000-0x000000009e6fffff]
[    0.000000]   node   0: [mem 0x000000009e700000-0x000000009e77ffff]
[    0.000000]   node   0: [mem 0x000000009e780000-0x000000009fffffff]
[    0.000000]   node   0: [mem 0x00000000a0000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000bfffffff]
[    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.2
[    0.000000] percpu: Embedded 19 pages/cpu s38376 r8192 d31256 u77824
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 258048
[    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 mtdparts=spi-nand0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),256k(ospi.env.backup),98048k@32m(ospi.rootfs),256k@130816k(ospi.phypattern);omap2-nand.0:2m(NAND.tiboot3),2m(NAND.tispl),2m(NAND.tiboot3.backup),4m(NAND.u-boot),256k(NAND.u-boot-env),256k(NAND.u-boot-env.backup),-(NAND.file-system) root=PARTUUID=6217ed9d-15d5-4966-8ff3-19d7fdbf12d5 rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 818128K/1048576K available (12672K kernel code, 1306K rwdata, 4128K rodata, 2240K init, 519K bss, 99376K reserved, 131072K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, 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=4.
[    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=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 256 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:0x0000000001880000
[    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 @80800000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x0000000080040000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000080050000
[    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.000001] sched_clock: 58 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
[    0.008553] Console: colour dummy device 80x25
[    0.013148] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.023832] pid_max: default: 32768 minimum: 301
[    0.028609] LSM: Security Framework initializing
[    0.033454] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.041032] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.050847] cblist_init_generic: Setting adjustable number of callback queues.
[    0.058311] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.064617] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.071026] rcu: Hierarchical SRCU implementation.
[    0.075931] rcu:     Max phase no-delay instances is 1000.
[    0.081534] Platform MSI: msi-controller@1820000 domain created
[    0.087872] PCI/MSI: /bus@f0000/interrupt-controller@1800000/msi-controller@1820000 domain created
[    0.097787] EFI services will not be available.
[    0.102724] smp: Bringing up secondary CPUs ...
[    5.134743] CPU1: failed to come online
[    5.138667] CPU1: failed in unknown state : 0x0
[   10.262728] CPU2: failed to come online
[   10.266650] CPU2: failed in unknown state : 0x0
[   15.390715] CPU3: failed to come online
[   15.394638] CPU3: failed in unknown state : 0x0
[   15.399338] smp: Brought up 1 node, 1 CPU
[   15.403450] SMP: Total of 1 processors activated.
[   15.408275] CPU features: detected: 32-bit EL0 Support
[   15.413535] CPU features: detected: CRC32 instructions
[   15.418860] CPU: All CPU(s) started at EL2
[   15.423046] alternatives: applying system-wide alternatives
[   15.430224] devtmpfs: initialized
[   15.442388] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[   15.452417] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[   15.463933] pinctrl core: initialized pinctrl subsystem
[   15.469941] DMI not present or invalid.
[   15.474510] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[   15.481437] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[   15.488745] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[   15.496745] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[   15.504911] audit: initializing netlink subsys (disabled)
[   15.511149] thermal_sys: Registered thermal governor 'step_wise'
[   15.511159] thermal_sys: Registered thermal governor 'power_allocator'
[   15.517325] audit: type=2000 audit(15.408:1): state=initialized audit_enabled=0 res=1
[   15.532048] cpuidle: using governor menu
[   15.536247] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[   15.543235] ASID allocator initialised with 65536 entries
[   15.560495] platform 30200000.dss: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/sii9022@3b
[   15.571864] platform connector: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/sii9022@3b
[   15.582966] KASLR disabled due to lack of seed
[   15.594744] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[   15.601775] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[   15.608264] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[   15.615207] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[   15.621616] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[   15.628555] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[   15.634963] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[   15.641901] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[   15.650128] k3-chipinfo 43000014.chipid: Family:AM62X rev:SR1.0 JTAGID[0x0bb7e02f] Detected
[   15.659598] iommu: Default domain type: Translated
[   15.664627] iommu: DMA domain TLB invalidation policy: strict mode
[   15.671321] SCSI subsystem initialized
[   15.675505] usbcore: registered new interface driver usbfs
[   15.681162] usbcore: registered new interface driver hub
[   15.686625] usbcore: registered new device driver usb
[   15.692320] pps_core: LinuxPPS API ver. 1 registered
[   15.697403] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[   15.706755] PTP clock support registered
[   15.710887] EDAC MC: Ver: 3.0.0
[   15.715001] omap-mailbox 29000000.mailbox: omap mailbox rev 0x66fc9100
[   15.722129] FPGA manager framework
[   15.725713] Advanced Linux Sound Architecture Driver Initialized.
[   15.732957] clocksource: Switched to clocksource arch_sys_counter
[   15.739492] VFS: Disk quotas dquot_6.6.0
[   15.743549] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[   15.755979] NET: Registered PF_INET protocol family
[   15.761226] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[   15.770001] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
[   15.778627] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[   15.786567] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
[   15.794543] TCP bind hash table entries: 8192 (order: 6, 262144 bytes, linear)
[   15.802186] TCP: Hash tables configured (established 8192 bind 8192)
[   15.808865] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[   15.815666] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[   15.823062] NET: Registered PF_UNIX/PF_LOCAL protocol family
[   15.829324] RPC: Registered named UNIX socket transport module.
[   15.835422] RPC: Registered udp transport module.
[   15.840233] RPC: Registered tcp transport module.
[   15.845042] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   15.851632] NET: Registered PF_XDP protocol family
[   15.856545] PCI: CLS 0 bytes, default 64
[   15.861370] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[   15.871406] Initialise system trusted keyrings
[   15.876260] workingset: timestamp_bits=46 max_order=18 bucket_order=0
[   15.888536] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   15.895233] NFS: Registering the id_resolver key type
[   15.900467] Key type id_resolver registered
[   15.904746] Key type id_legacy registered
[   15.908908] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[   15.915764] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[   15.923529] 9p: Installing v9fs 9p2000 file system support
[   15.964909] Key type asymmetric registered
[   15.969100] Asymmetric key parser 'x509' registered
[   15.974144] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[   15.981895] io scheduler mq-deadline registered
[   15.986563] io scheduler kyber registered
[   15.993765] pinctrl-single 4084000.pinctrl: 34 pins, size 136
[   16.000474] pinctrl-single f4000.pinctrl: 171 pins, size 684
[   16.007370] pinctrl-single a40000.pinctrl: 512 pins, size 2048
[   16.020909] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[   16.035372] loop: module loaded
[   16.039943] megasas: 07.719.03.00-rc1
[   16.047900] tun: Universal TUN/TAP device driver, 1.6
[   16.053846] thunder_xcv, ver 1.0
[   16.057230] thunder_bgx, ver 1.0
[   16.060550] nicpf, ver 1.0
[   16.063736] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[   16.071132] hns3: Copyright (c) 2017 Huawei Corporation.
[   16.076646] hclge is initializing
[   16.080057] e1000: Intel(R) PRO/1000 Network Driver
[   16.085051] e1000: Copyright (c) 1999-2006 Intel Corporation.
[   16.090959] e1000e: Intel(R) PRO/1000 Network Driver
[   16.096035] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   16.102121] igb: Intel(R) Gigabit Ethernet Network Driver
[   16.107641] igb: Copyright (c) 2007-2014 Intel Corporation.
[   16.113365] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[   16.119773] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[   16.125953] sky2: driver version 1.30
[   16.130424] VFIO - User Level meta-driver version: 0.3
[   16.137338] usbcore: registered new interface driver usb-storage
[   16.144372] i2c_dev: i2c /dev entries driver
[   16.151076] sdhci: Secure Digital Host Controller Interface driver
[   16.157505] sdhci: Copyright(c) Pierre Ossman
[   16.162498] Synopsys Designware Multimedia Card Interface Driver
[   16.169085] sdhci-pltfm: SDHCI platform and OF driver helper
[   16.175819] ledtrig-cpu: registered to indicate activity on CPUs
[   16.182143] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[   16.189115] usbcore: registered new interface driver usbhid
[   16.194818] usbhid: USB HID core driver
[   16.200056] optee: probing for conduit method.
[   16.204663] optee: revision 3.20 (8e74d476)
[   16.204975] optee: dynamic shared memory is enabled
[   16.214495] optee: initialized driver
[   16.220081] Initializing XFRM netlink socket
[   16.224587] NET: Registered PF_PACKET protocol family
[   16.229919] 9pnet: Installing 9P2000 support
[   16.234364] Key type dns_resolver registered
[   16.239161] registered taskstats version 1
[   16.243382] Loading compiled-in X.509 certificates
[   16.259618] ti-sci 44043000.system-controller: ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
[   16.356522] at24 0-0050: supply vcc not found, using dummy regulator
[   16.363569] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[   16.370903] at24 0-0051: supply vcc not found, using dummy regulator
[   16.377770] at24 0-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[   16.385061] pca953x 0-0022: supply vcc not found, using dummy regulator
[   16.391911] pca953x 0-0022: using AI
[   16.398340] rtc-pcf8523 0-0068: registered as rtc0
[   16.403551] rtc-pcf8523 0-0068: setting system clock to 2022-04-28T18:17:03 UTC (1651169823)
[   16.412239] omap_i2c 20000000.i2c: bus 0 rev0.12 at 400 kHz
[   16.420035] omap_i2c 20010000.i2c: bus 1 rev0.12 at 100 kHz
[   16.426459] ti-sci-intr 4210000.interrupt-controller: Interrupt Router 5 domain created
[   16.434834] ti-sci-intr bus@f0000:interrupt-controller@a00000: Interrupt Router 3 domain created
[   16.444079] ti-sci-inta 48000000.interrupt-controller: Interrupt Aggregator domain 28 created
[   16.453994] ti-udma 485c0100.dma-controller: Number of rings: 82
[   16.462236] ti-udma 485c0100.dma-controller: Channels: 48 (bchan: 18, tchan: 12, rchan: 18)
[   16.473394] ti-udma 485c0000.dma-controller: Number of rings: 150
[   16.483500] ti-udma 485c0000.dma-controller: Channels: 35 (tchan: 20, rchan: 15)
[   16.493789] printk: console [ttyS2] disabled
[   16.498286] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 286, base_baud = 3000000) is a 8250
[   16.507205] printk: console [ttyS2] enabled
[   16.507205] printk: console [ttyS2] enabled
[   16.515667] printk: bootconsole [ns16550a0] disabled
[   16.515667] printk: bootconsole [ns16550a0] disabled
[   16.527286] davinci_mdio 8000f00.mdio: Configuring MDIO in manual mode
[   16.572973] davinci_mdio 8000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[   16.581900] am65-cpsw-nuss 8000000.ethernet: initializing am65 cpsw nuss version 0x6BA01103, cpsw version 0x6BA81103 Ports: 3 quirks:00000006
[   16.594991] am65-cpsw-nuss 8000000.ethernet: Use random MAC address
[   16.601292] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.5
[   16.608453] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512
[   16.615112] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010c, freq:500000000, add_val:1 pps:0
[   16.625430] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19
[   16.635615] xhci-hcd xhci-hcd.2.auto: USB3 root hub has no ports
[   16.641681] xhci-hcd xhci-hcd.2.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000000000010010
[   16.651125] xhci-hcd xhci-hcd.2.auto: irq 291, io mem 0x31000000
[   16.657928] hub 1-0:1.0: 1 port detected
[   16.664256] xhci-hcd xhci-hcd.3.auto: USB3 root hub has no ports
[   16.670395] xhci-hcd xhci-hcd.3.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000000000010010
[   16.679842] xhci-hcd xhci-hcd.3.auto: irq 292, io mem 0x31100000
[   16.686681] hub 2-0:1.0: 1 port detected
[   16.692112] rti-wdt e000000.watchdog: watchdog already running, ignoring heartbeat config!
[   16.706616] mmc0: CQHCI version 5.10
[   16.718875] pinctrl-single f4000.pinctrl: pin PIN31 already requested by 600000.gpio; cannot claim for regulator-4
[   16.729410] pinctrl-single f4000.pinctrl: pin-31 (regulator-4) status -22
[   16.736303] pinctrl-single f4000.pinctrl: could not request pin 31 (PIN31) from group vdd-sd-dv-pins-default  on device pinctrl-single
[   16.748507] gpio-regulator regulator-4: Error applying setting, reverse things back
[   16.756344] pinctrl-single f4000.pinctrl: pin PIN117 already requested by 601000.gpio; cannot claim for 1-0022
[   16.766350] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
[   16.773968] pinctrl-single f4000.pinctrl: pin-117 (1-0022) status -22
[   16.780793] pinctrl-single f4000.pinctrl: could not request pin 117 (PIN117) from group main-gpio1-ioexp-intr-pins-default  on device pinctrl-single
[   16.794319] pca953x 1-0022: Error applying setting, reverse things back
[   16.801445] davinci_mdio 8000f00.mdio: Configuring MDIO in manual mode
[   16.844979] davinci_mdio 8000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[   16.859058] mmc0: Command Queue Engine enabled
[   16.863608] mmc0: new HS200 MMC card at address 0001
[   16.869491] mmcblk0: mmc0:0001 IS008G 7.28 GiB
[   16.878676]  mmcblk0: p1
[   16.881882] mmcblk0boot0: mmc0:0001 IS008G 4.00 MiB
[   16.888011] mmcblk0boot1: mmc0:0001 IS008G 4.00 MiB
[   16.894067] mmcblk0rpmb: mmc0:0001 IS008G 4.00 MiB, chardev (239:0)
[   16.989442] davinci_mdio 8000f00.mdio: phy[0]: device 8000f00.mdio:00, driver unknown
[   16.997507] davinci_mdio 8000f00.mdio: phy[1]: device 8000f00.mdio:01, driver unknown
[   17.010567] debugfs: Directory 'pd:182' with parent 'pm_genpd' already present!
[   17.032103] ALSA device list:
[   17.035452]   No soundcards found.
[   17.051010] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Quota mode: none.
[   17.059651] VFS: Mounted root (ext4 filesystem) on device 179:1.
[   17.069322] devtmpfs: mounted
[   17.073755] Freeing unused kernel memory: 2240K
[   17.078423] Run /sbin/init as init process
[   17.189157] NET: Registered PF_INET6 protocol family
[   17.195788] Segment Routing with IPv6
[   17.199557] In-situ OAM (IOAM) with IPv6
[   17.221319] 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)
[   17.252909] systemd[1]: Detected architecture arm64.

Welcome to Linux!

[   17.306906] systemd[1]: Hostname set to <am62xx-alc>.
[   17.480069] systemd-sysv-generator[141]: SysV service '/etc/init.d/watchdogd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.504855] systemd-sysv-generator[141]: SysV service '/etc/init.d/mount_var_debrick' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.537550] systemd-sysv-generator[141]: SysV service '/etc/init.d/hostapd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.561608] systemd-sysv-generator[141]: SysV service '/etc/init.d/runlevel-change-done' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.586858] systemd-sysv-generator[141]: SysV service '/etc/init.d/inetd.busybox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.611473] systemd-sysv-generator[141]: SysV service '/etc/init.d/populate-volatile.sh.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.637516] systemd-sysv-generator[141]: SysV service '/etc/init.d/modutils.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.661908] systemd-sysv-generator[141]: SysV service '/etc/init.d/dnsmasq' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.686028] systemd-sysv-generator[141]: SysV service '/etc/init.d/launch-lam.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.710563] systemd-sysv-generator[141]: SysV service '/etc/init.d/sshd.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.735932] systemd-sysv-generator[141]: SysV service '/etc/init.d/rc' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.761861] systemd-sysv-generator[141]: SysV service '/etc/init.d/fwexd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.788116] systemd-sysv-generator[141]: SysV service '/etc/init.d/usbNetConfig' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.817424] systemd-sysv-generator[141]: SysV service '/etc/init.d/check-recovery' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.850003] systemd-sysv-generator[141]: SysV service '/etc/init.d/populate-volatile.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.875360] systemd-sysv-generator[141]: SysV service '/etc/init.d/functions.initscripts' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.900525] systemd-sysv-generator[141]: SysV service '/etc/init.d/dbus-1' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.924269] systemd-sysv-generator[141]: SysV service '/etc/init.d/ethportconfig' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.948620] systemd-sysv-generator[141]: SysV service '/etc/init.d/maintain_emmc_integrity.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.974103] systemd-sysv-generator[141]: SysV service '/etc/init.d/syslog.busybox.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   17.999483] systemd-sysv-generator[141]: SysV service '/etc/init.d/loginShell' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.023599] systemd-sysv-generator[141]: SysV service '/etc/init.d/launch-fwex_cntrl.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.048553] systemd-sysv-generator[141]: SysV service '/etc/init.d/mount_var' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.072554] systemd-sysv-generator[141]: SysV service '/etc/init.d/launch-io-server_cntrl.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.098474] systemd-sysv-generator[141]: SysV service '/etc/init.d/functions' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.122544] systemd-sysv-generator[141]: SysV service '/etc/init.d/rc.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.146899] systemd-sysv-generator[141]: SysV service '/etc/init.d/loginShell.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.171979] systemd-sysv-generator[141]: SysV service '/etc/init.d/watchdog_updated' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.196565] systemd-sysv-generator[141]: SysV service '/etc/init.d/firewall' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.220465] systemd-sysv-generator[141]: SysV service '/etc/init.d/load_am335x_adc' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.245019] systemd-sysv-generator[141]: SysV service '/etc/init.d/telnetd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.268829] systemd-sysv-generator[141]: SysV service '/etc/init.d/io-serverd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.292900] systemd-sysv-generator[141]: SysV service '/etc/init.d/fpga_load' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.316892] systemd-sysv-generator[141]: SysV service '/etc/init.d/reset-alc-usb' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.341275] systemd-sysv-generator[141]: SysV service '/etc/init.d/firewall.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.366175] systemd-sysv-generator[141]: SysV service '/etc/init.d/usbWifiConfig' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.390523] systemd-sysv-generator[141]: SysV service '/etc/init.d/mount_var.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[   18.466954] systemd-sysv-generator[141]: Overwriting existing symlink /run/systemd/generator.late/reset-alc-usb.service with real service.
[   18.729671] 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.
[   18.793427] systemd[1]: Queued start job for default target Multi-User System.
[   18.845229] systemd[1]: Created slice Slice /system/getty.
[  OK  ] Created slice Slice /system/getty.
[   18.867139] systemd[1]: Created slice Slice /system/modprobe.
[  OK  ] Created slice Slice /system/modprobe.
[   18.891249] systemd[1]: Created slice Slice /system/serial-getty.
[  OK  ] Created slice Slice /system/serial-getty.
[   18.914889] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[   18.937682] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[   18.961581] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[   18.985689] systemd[1]: Reached target Path Units.
[  OK  ] Reached target Path Units.
[   19.005175] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[   19.025165] systemd[1]: Reached target Slice Units.
[  OK  ] Reached target Slice Units.
[   19.045480] systemd[1]: Reached target Swaps.
[  OK  ] Reached target Swaps.
[   19.072467] systemd[1]: Listening on Syslog Socket.
[  OK  ] Listening on Syslog Socket.
[   19.094038] systemd[1]: Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[   19.118967] systemd[1]: Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Audit Socket.
[   19.142239] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[   19.167053] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[   19.190999] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[   19.216371] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[   19.239334] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[   19.263604] systemd[1]: Listening on User Database Manager Socket.
[  OK  ] Listening on User Database Manager Socket.
[   19.313916] systemd[1]: Mounting Huge Pages File System...
         Mounting Huge Pages File System...
[   19.345695] systemd[1]: Mounting POSIX Message Queue File System...
         Mounting POSIX Message Queue File System...
[   19.389658] systemd[1]: Mounting Kernel Debug File System...
         Mounting Kernel Debug File System...
[   19.417448] systemd[1]: Kernel Trace File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/tracing).
[   19.449594] systemd[1]: Mounting Temporary Directory /tmp...
         Mounting Temporary Directory /tmp...
[   19.493762] systemd[1]: Starting Create List of Static Device Nodes...
         Starting Create List of Static Device Nodes...
[   19.537841] systemd[1]: Starting Load Kernel Module configfs...
         Starting Load Kernel Module configfs...
[   19.585794] systemd[1]: Starting Load Kernel Module drm...
         Starting Load Kernel Module drm...
[   19.629761] systemd[1]: Starting Load Kernel Module fuse...
         Starting Load Kernel Module fuse...
[   19.653739] systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
[   19.685914] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[   19.734044] systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...
[   19.780292] systemd[1]: Starting Generate network units from Kernel command line...
[   19.796388] cryptodev: loading out-of-tree module taints kernel.
         Starting Generate network …ts from Kernel command line...
[   19.825469] cryptodev: driver 1.12 loaded.
[   19.838103] systemd[1]: Starting Remount Root and Kernel File Systems...
         Starting Remount Root and Kernel File Systems...
[   19.894011] systemd[1]: Starting Coldplug All udev Devices...
         Starting Coldplug All udev Devices...
[   19.950647] systemd[1]: Mounted Huge Pages File System.
[   19.967013] EXT4-fs (mmcblk0p1): re-mounted. Quota mode: none.
[  OK  ] Mounted Huge Pages File System.
[   19.999935] systemd[1]: Mounted POSIX Message Queue File System.
[  OK  ] Mounted POSIX Message Queue File System.
[   20.040145] systemd[1]: Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Debug File System.
[   20.077959] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
[  OK  ] Mounted Temporary Directory /tmp.
[  OK  ] Finished Create List of Static Device Nodes.
[  OK  ] Finished Load Kernel Module configfs.
[  OK  ] Finished Load Kernel Module drm.
[  OK  ] Finished Load Kernel Module fuse.
[  OK  ] Finished Load Kernel Modules.
[  OK  ] Finished Generate network units from Kernel command line.
[  OK  ] Finished Remount Root and Kernel File Systems.
         Mounting Kernel Configuration File System...
         Starting Flush Journal to Persistent Storage...
         Starting Apply Kernel Variables...
[   20.422130] systemd-journald[150]: Received client request to flush runtime journal.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Finished Flush Journal to Persistent Storage.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Reached target Preparation for Local File Systems.
         Mounting /media/ram...
         Mounting /var/volatile...
[   20.645384] audit: type=1334 audit(1651169827.740:2): prog-id=5 op=LOAD
         Starting Rule-based Manage…for Device Events[   20.669513] audit: type=1334 audit(1651169827.748:3): prog-id=6 op=LOAD
 and Files...
[  OK  ] Mounted /media/ram.
[  OK  ] Mounted /var/volatile.
         Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Create Volatile Files and Directories.
         Starting Network Time Synchronization...
         Starting Record System Boot/Shutdown in UTMP...
[  OK  ] Started Rule-based Manager for Device Events and Files.
[  OK  ] Finished Record System Boot/Shutdown in UTMP.
[  OK  ] Finished Coldplug All udev Devices.
[   21.793025] random: crng init done
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target System Time Set.
[  OK  ] Reached target Timer Units.
[  OK  ] Listening on D-Bus System Message Bus Socket.
         Starting sshd.socket...
[  OK  ] Listening on sshd.socket.
[  OK  ] Reached target Socket Units.
[  OK  ] Reached target Basic System.
[  OK  ] Started Periodic Command Scheduler.
         Starting D-Bus System Message Bus...
[  OK  ] Started A minimalistic net…Pv4, rdisc and DHCPv6 support.
         Starting Print notice about GPLv3 packages...
         Starting IPv6 Packet Filtering Framework...
         Starting IPv4 Packet Filtering Framework...
[  OK  ] Started Start usb mass storage gadget.
[  OK  ] Started System Logging Service.
grep: /var/lib/opkg/info/*.control: No such file or directory
         Starting User Login Management...
         Starting OpenSSH Key Generation...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Finished Print notice about GPLv3 packages.
[  OK  ] Finished IPv6 Packet Filtering Framework.
[  OK  ] Finished IPv4 Packet Filtering Framework.
[  OK  ] Finished OpenSSH Key Generation.
[  OK  ] Reached target Preparation for Network.
         Starting Network Configuration...
[  OK  ] Started User Login Management.
[  OK  ] Started Network Configuration.
         Starting Network Name Resolution...
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Started Respond to IPv6 Node Information Queries.
[  OK  ] Started Network Router Discovery Daemon.
         Starting Permit User Sessions...
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS2.
[  OK  ] Started Serial Getty on ttyS3.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
         Starting Synchronize System and HW clocks...
         Starting Record Runlevel Change in UTMP...
[  OK  ] Finished Synchronize System and HW clocks.
[  OK  ] Finished Record Runlevel Change in UTMP.

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project am62xx-alc ttyS2

Carrier Linux Reference Distrbution nodistro.0 am62xx-alc ttyS2

am62xx-alc login: root
root@am62xx-alc:~#

0 Nick Saulnier 6 months ago in reply to Anil medak

TI__Guru** 101960 points

Hello Anil,

To confirm, at what point in the boot process do you want the watchdog timers to get configured and begin counting down? Note that once the watchdog is enabled it cannot be disabled and reconfigured, so if you are enabling a watchdog counter before Linux boot, I believe you would need to have Linux side code that knew that the hardware was already configured and counting down.

Did you make any other modifications to the uboot code? I see the rti nodes getting defined in ti-u-boot-2023.04+gitAUTOINC+f9b966c674/arch/arm/dts/k3-am62-main.dtsi, but I do not see them actually getting configured anywhere. At this point I have not looked into enabling watchdog timers before Linux boot.

Regards,

Nick

0 Anil medak 6 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,

I modified U-Boot by disabling main_rti15 in git/arch/arm/dts/k3-am625-alc_ngzn.dts (which is defined in /arch/arm/dts/k3-am62-main.dtsi) and enabling the watchdog configurations

If I want to enable the watchdog in U-Boot (before Linux boots), what do I need to do?
is enable the watchdog configurations in U-Boot is sufficient, if so i did it.
Since Linux needs to know that the watchdog is already running, how can I ensure that?
How can I ensure that Linux takes over the watchdog?

What is the reason for the CPU's failure in an unknown state?
Please let me know if I am missing anything

Thanks,

Anil

0 Nick Saulnier 6 months ago in reply to Anil medak

TI__Guru** 101960 points

Hello Anil,

Lots of open questions here that we'll have to work through together.

From the Linux side, I am not sure if it is sufficient to just enable watchdog during boot, or if that could cause issues (e.g., if Linux fails when it sees watchdog already initialized, if Linux starts counting from 0 instead of reading how much time elapsed between watchdog start and Linux driver initializing, etc).

Let's focus on getting a watchdog running in u-boot first.

It does look like there is a uboot driver for the watchdog on AM62x:

ti-u-boot-2023.04+gitAUTOINC+8366064208$ vi arch/arm/dts/k3-am62-main.dtsi
...
        main_rti0: watchdog@e000000 {
                compatible = "ti,j7-rti-wdt";
                reg = <0x00 0x0e000000 0x00 0x100>;
                clocks = <&k3_clks 125 0>;
                power-domains = <&k3_pds 125 TI_SCI_PD_EXCLUSIVE>;
                assigned-clocks = <&k3_clks 125 0>;
                assigned-clock-parents = <&k3_clks 125 2>;
        };


ti-u-boot-2023.04+gitAUTOINC+8366064208$ grep -r 'ti,j7-rti-wdt'
drivers/watchdog/rti_wdt.c:     { .compatible = "ti,j7-rti-wdt" },

there is not any watchdog firmware for the RTI on AM62x, so that part of the driver can be ignored.

That's the progress I had time for today. Maybe that will enable you to make some progress on your side, I will try to spend a bit more time on it tomorrow as well.

Regards,

Nick

0 Nick Saulnier 6 months ago in reply to Anil medak

TI__Guru** 101960 points

Hello Anil,

Lots of open questions here that we'll have to work through together.

Let's focus on getting a watchdog running in u-boot first.

It does look like there is a uboot driver for the watchdog on AM62x:

ti-u-boot-2023.04+gitAUTOINC+8366064208$ vi arch/arm/dts/k3-am62-main.dtsi
...
        main_rti0: watchdog@e000000 {
                compatible = "ti,j7-rti-wdt";
                reg = <0x00 0x0e000000 0x00 0x100>;
                clocks = <&k3_clks 125 0>;
                power-domains = <&k3_pds 125 TI_SCI_PD_EXCLUSIVE>;
                assigned-clocks = <&k3_clks 125 0>;
                assigned-clock-parents = <&k3_clks 125 2>;
        };


ti-u-boot-2023.04+gitAUTOINC+8366064208$ grep -r 'ti,j7-rti-wdt'
drivers/watchdog/rti_wdt.c:     { .compatible = "ti,j7-rti-wdt" },

there is not any watchdog firmware for the RTI on AM62x, so that part of the driver can be ignored.

That's the progress I had time for today. Maybe that will enable you to make some progress on your side, I will try to spend a bit more time on it tomorrow as well.

Regards,

Nick

0 Anil medak 6 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,

main_rti0: watchdog@e000000 {
compatible = "ti,j7-rti-wdt";
reg = <0x00 0x0e000000 0x00 0x100>;
clocks = <&k3_clks 125 0>;
power-domains = <&k3_pds 125 TI_SCI_PD_EXCLUSIVE>;
assigned-clocks = <&k3_clks 125 0>;
assigned-clock-parents = <&k3_clks 125 2>;
};

1) The entries for main_rti1, main_rti2, and main_rti3 are present in U-Boot at arch/arm/dts/k3-am62-main.dtsi. U-Boot is coming up on the board, and the kernel is also booting successfully. Based on this, we believe that the watchdog is running on the board. Is there a way to confirm whether the watchdog is running in U-Boot?

2) After this, the kernel boot started, and we observed the following log with an error:

[ 0.097787] EFI services will not be available.
[ 0.102724] smp: Bringing up secondary CPUs ...
[ 5.134743] CPU1: failed to come online
[ 5.138667] CPU1: failed in unknown state : 0x0
[ 10.262728] CPU2: failed to come online
[ 10.266650] CPU2: failed in unknown state : 0x0
[ 15.390715] CPU3: failed to come online
[ 15.394638] CPU3: failed in unknown state : 0x0
[ 15.399338] smp: Brought up 1 node, 1 CPU
[ 15.403450] SMP: Total of 1 processors activated.
[ 15.408275] CPU features: detected: 32-bit EL0 Support
[ 15.413535] CPU features: detected: CRC32 instructions
[ 15.418860] CPU: All CPU(s) started at EL2
[ 15.423046] alternatives: applying system-wide alternatives
[ 15.430224] devtmpfs: initialized

Please let me know your input.

Thanks,

Anil

0 Karan Saxena 5 months ago in reply to Anil medak

TI__Guru* 77884 points

Unlocking the thread for further discussion on this open issue.

Anil, please post if there are any additional updates from your last response.

Regards

Karan

0 Anil medak 5 months ago in reply to Karan Saxena

Prodigy 50 points

Hi Karan,

Still, we haven't found a solution for the CPU failure state while enabling the watchdog in U-Boot.
I also checked with CONFIG_SPL_WATCHDOG disabled, but we still see the same issue.

Thanks,

Anil

0 Nick Saulnier 5 months ago in reply to Anil medak

TI__Guru** 101960 points

Hello Anil,

Thanks for reaching out to Karan so we could re-start this conversation.

I did not notice earlier that it took a full 15 seconds for the processor to try (and fail) to initialize the additional A53 cores after core0 in your boot logs:

// March 12 response

[    0.102724] smp: Bringing up secondary CPUs ...
[    5.134743] CPU1: failed to come online
[    5.138667] CPU1: failed in unknown state : 0x0
[   10.262728] CPU2: failed to come online
[   10.266650] CPU2: failed in unknown state : 0x0
[   15.390715] CPU3: failed to come online
[   15.394638] CPU3: failed in unknown state : 0x0
[   15.399338] smp: Brought up 1 node, 1 CPU
[   15.403450] SMP: Total of 1 processors activated.

// specifically called out in your March 14 response as well

I am not sure I understand your latest response. When you do NOT try to initialize watchdog timers during uboot, do you see the same failures? Or do the other 3 cores in the A53 cluster successfully come up in fractions of a second, as in the default example?

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.12.17-ti-rt-00771-gc85877d40f8e (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 13.3.0, GNU ld (GNU Binuti
ls) 2.42.0.20240723) #1 SMP PREEMPT_RT Tue Mar 25 12:45:29 UTC 2025
...
[    0.035356] smp: Bringing up secondary CPUs ...
[    0.035929] Detected VIPT I-cache on CPU1
[    0.036000] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000
[    0.036015] GICv3: CPU1: using allocated LPI pending table @0x0000000880060000
[    0.036059] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.107353] Detected VIPT I-cache on CPU2
[    0.107413] GICv3: CPU2: found redistributor 2 region 0:0x00000000018c0000
[    0.107426] GICv3: CPU2: using allocated LPI pending table @0x0000000880070000
[    0.107459] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.193903] Detected VIPT I-cache on CPU3
[    0.193962] GICv3: CPU3: found redistributor 3 region 0:0x00000000018e0000
[    0.193976] GICv3: CPU3: using allocated LPI pending table @0x0000000880080000
[    0.194008] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.222785] smp: Brought up 1 node, 4 CPUs
[    0.222792] SMP: Total of 4 processors activated.
[    0.222795] CPU: All CPU(s) started at EL2

Regards,

Nick

0 Anil medak 5 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,

Thank you, looking forward to continuing the discussion.
When I disable the watchdog in U-Boot, Linux boots properly without any additional delay.
[ 0.097821] EFI services will not be available.
[ 0.102758] smp: Bringing up secondary CPUs ...
[ 0.108074] Detected VIPT I-cache on CPU1
[ 0.108196] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000
[ 0.108214] GICv3: CPU1: using allocated LPI pending table @0x0000000080060000
[ 0.108271] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.108981] Detected VIPT I-cache on CPU2
[ 0.109062] GICv3: CPU2: found redistributor 2 region 0:0x00000000018c0000
[ 0.109076] GICv3: CPU2: using allocated LPI pending table @0x0000000080070000
[ 0.109109] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.109735] Detected VIPT I-cache on CPU3
[ 0.109816] GICv3: CPU3: found redistributor 3 region 0:0x00000000018e0000
[ 0.109829] GICv3: CPU3: using allocated LPI pending table @0x0000000080080000
[ 0.109861] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.109933] smp: Brought up 1 node, 4 CPUs
[ 0.189663] SMP: Total of 4 processors activated.
[ 0.194477] CPU features: detected: 32-bit EL0 Support
[ 0.199749] CPU features: detected: CRC32 instructions
[ 0.205071] CPU: All CPU(s) started at EL2
[ 0.209267] alternatives: applying system-wide alternatives
[ 0.216560] devtmpfs: initialized

But when I enable it in U-Boot, the CPUs bring up fail.
[ 0.087872] PCI/MSI: /bus@f0000/interrupt-controller@1800000/msi-controller@1820000 domain created
[ 0.097787] EFI services will not be available.
[ 0.102724] smp: Bringing up secondary CPUs ...
[ 5.134743] CPU1: failed to come online
[ 5.138667] CPU1: failed in unknown state : 0x0
[ 10.262728] CPU2: failed to come online
[ 10.266650] CPU2: failed in unknown state : 0x0
[ 15.390715] CPU3: failed to come online
[ 15.394638] CPU3: failed in unknown state : 0x0
[ 15.399338] smp: Brought up 1 node, 1 CPU
[ 15.403450] SMP: Total of 1 processors activated.
[ 15.408275] CPU features: detected: 32-bit EL0 Support
[ 15.413535] CPU features: detected: CRC32 instructions
[ 15.418860] CPU: All CPU(s) started at EL2
[ 15.423046] alternatives: applying system-wide alternatives
[ 15.430224] devtmpfs: initialized

Thanks,

Anil

0 MK 5 months ago in reply to Anil medak

TI__Intellectual 1690 points

Hi Nick,
Does this info help you? Let us know if you need any other logs.

Best Regards,
Madhurya

0 Nick Saulnier 5 months ago in reply to MK

TI__Guru** 101960 points

Hello Madhurya & Anil,

I am going to try to replicate your observations on my side. Is there any additional information I should know other than
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1484145/processor-sdk-am62x-watchdog-issues-on-am62x-custom-board-based-on-am62x-sk-board/5712219#5712219 ?

Out of curiosity, what happens when you only enable a single watchdog? Do all A53 cores other than core0 still fail to initialize, or do you see different behavior?

Regards,

Nick

0 Nick Saulnier 5 months ago in reply to Nick Saulnier

TI__Guru** 101960 points

ok, I am starting off with testing on an unmodified AM62x Linux SDK 10.1. It is a later kernel and u-boot version, but all of the kernel and uboot patches for the bugs we found in Linux SDK 9.1 and earlier are applied. So this is my "known good" starting point.

Test 1: can all 5 watchdog instances reboot the processor?

Yes. Each watchdog rebooted the processor 1 minute after I started it:

root@am62xx-evm:~# ls /dev/watchdog
watchdog   watchdog0  watchdog1  watchdog2  watchdog3  watchdog4

root@am62xx-evm:~# echo 1 > /dev/watchdog4
[   42.526582] watchdog: watchdog4: nowayout prevents watchdog being stopped!
[   42.533495] watchdog: watchdog4: watchdog did not stop!
root@am62xx-evm:~#
// a minute passes
U-Boot SPL 2024.04-ti-g29d0c23d67ee (Nov 29 2024 - 11:41:54 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)')
...

Note that /dev/watchdog is just a link to /dev/watchdog0. I tested watchdog0 through watchdog4.

Followup on the initial post

I assumed that the issues in your initial post have been resolved. If not, please let me know which of these is still an issue:

1) watchdog5

a) are you actually seeing a /dev/watchdog5? Or are you referring to watchdog4 here?

b) all 5 watchdogs are enabled by default in Linux on the AM62x SK for SDK 10.1. I am not getting any crashes or boot errors related to watchdog. Are you still seeing issues, or is this working as expected now?

2) Delayed trigger response

I assume after you adjusted your clock settings, all the watchdogs are timing out at the expected time?

0 Nick Saulnier 5 months ago in reply to Nick Saulnier

TI__Guru** 101960 points

Test 2: can watchdog instances reboot the processor from uboot?

Only the A53 core0, and the DM R5F watchdogs. This makes sense, as the watchdogs are tied to each core. So if a core has not yet been powered, I would expect that you could not yet program the watchdog associated with that core.

configure the watchdog to time out after about a second

Hit any key to stop autoboot:  0
// RTI0
=> mw.l 0xE0000A4 0xa 1
=> mw.l 0xE000090 0xA98559DA 1

// RTI1, RTI2, RTI3 throw an error when I try to write
// probably because those A53 cores have not been powered on yet

// MCU_RTI0 throws an error, probably because the MCU_R5 has not been
// powered on yet

// DM R5F RTI (i.e., WKUP_RTI0)
=> mw.l 0x2B0000A4 0xa 1
=> mw.l 0x2B000090 0xA98559DA 1

Question: Which watchdog instance or instances did you try enabling in uboot? Please show me exactly how you enabled the watchdogs in uboot

I would expect that you should be able to start the watchdog for A53 core0, or the watchdog for the DM R5F, in uboot. However, if a core has not been powered on yet, I would not expect that you could start using its watchdog in uboot.

Regards,

Nick

0 Anil medak 5 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,

Followup on the initial post

Yes, the initial issue related to watchdog5 is resolved. Since our AM623x has no GPU, we disabled the 5th watchdog.

Regarding the delayed trigger issue, after changing the clock ID value, watchdog timers 0, 1, 2, and 3 are now triggering at the expected time.

Out of curiosity, what happens when you only enable a single watchdog? Do all A53 cores other than core0 still fail to initialize, or do you see different behavior?

No, I haven’t tried enabling a single watchdog and disabling the others while the watchdog is enabled in U-Boot

Question: Which watchdog instance or instances did you try enabling in uboot? Please show me exactly how you enabled the watchdogs in uboot

The 5th instance of the watchdog is disabled, while the other instances main_rti0, main_rti1, main_rti2, and main_rti3 — are enabled by default.

&main_rti15 {
status = "disabled";
};

The defconfig changes for the watchdog have been added in U-Boot are:

CONFIG_CYCLIC=y
CONFIG_CYCLIC_MAX_CPU_TIME_US=1000
CONFIG_CMD_CYCLIC=y
CONFIG_WATCHDOG=y
CONFIG_CMD_WDT=y
CONFIG_WATCHDOG_AUTOSTART=y
# CONFIG_DESIGNWARE_WATCHDOG is not set
CONFIG_WDT=y
# CONFIG_WDT_APPLE is not set
# CONFIG_WDT_ASPEED is not set
# CONFIG_WDT_AST2600 is not set
# CONFIG_WDT_AT91 is not set
# CONFIG_WDT_CDNS is not set
# CONFIG_WDT_CORTINA is not set
# CONFIG_WDT_GPIO is not set
# CONFIG_WDT_MAX6370 is not set
# CONFIG_WDT_MESON_GXBB is not set
# CONFIG_WDT_ORION is not set
CONFIG_WDT_K3_RTI=y
# CONFIG_WDT_K3_RTI_LOAD_FW is not set
# CONFIG_WDT_SBSA is not set
# CONFIG_WDT_SP805 is not set
# CONFIG_WDT_STM32MP is not set
# CONFIG_XILINX_TB_WATCHDOG is not set

Thanks,

Anil

0 Nick Saulnier 5 months ago in reply to Anil medak

TI__Guru** 101960 points

Hello Anil,

Thanks for that. I have blocked off tomorrow afternoon to run more tests.

If you need to make progress in the meantime, I would be curious to see if you still run into boot issues if you disable main_rti1 through 3 in uboot, only enabling main_rti0.

Regards,

Nick

0 Anil medak 5 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,

If you need to make progress in the meantime, I would be curious to see if you still run into boot issues if you disable main_rti1 through 3 in uboot, only enabling main_rti0.

After disabling main_rti1, main_rti2, and main_rti3 and enabling only main_rti0 in U-Boot, I did not see any "CPU failed to come online" messages.
Here is the log:

Fullscreen bootlog_after_wdt1_enable_wdt2_3_4_dis_uboot_kernel.txt Download

▒88▒▒
U-Boot SPL 2023.04-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 13376 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 00:42:57, Jan 13 2023

U-Boot SPL 2023.04ALC-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 1856 bytes
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04ALC-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: TI AM62x ALC NGZN V4
EEPROM not available at 81, trying to read at 82
Reading on-board EEPROM at 0x52 failed -121
DRAM:  1 GiB
Core:  80 devices, 30 uclasses, devicetree: separate
WDT:   Started watchdog@e000000 with servicing every 1000ms (60s timeout)
MMC:   mmc@fa10000: 0
Loading Environment from nowhere... OK
Net:   eth0: ethernet@8000000port@1, eth1: ethernet@8000000port@2
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
SD/MMC found on device 0
Failed to load 'boot.scr'
Can't set block device
## Error: "main_cpsw0_qsgmii_phyinit" not defined
24969728 bytes read in 152 ms (156.7 MiB/s)
57883 bytes read in 17 ms (3.2 MiB/s)
Working FDT set to 88000000
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 000000008feee000, end 000000008fffffff ... OK
Working FDT set to 8feee000

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.1.129-g42f3118c41 (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Mon Mar 17 11:55:47 UTC 2025
[    0.000000] Machine model: TI AM62x ALC NGZN V4
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000b8000000, size 128 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009c800000, size 3 MiB
[    0.000000] OF: reserved mem: initialized node ipc-memories@9c800000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cb00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node m4f-dma-memory@9cb00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cc00000, size 14 MiB
[    0.000000] OF: reserved mem: initialized node m4f-memory@9cc00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009da00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9da00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009db00000, size 12 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@9db00000, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000bfffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x000000009c7fffff]
[    0.000000]   node   0: [mem 0x000000009c800000-0x000000009e6fffff]
[    0.000000]   node   0: [mem 0x000000009e700000-0x000000009e77ffff]
[    0.000000]   node   0: [mem 0x000000009e780000-0x000000009fffffff]
[    0.000000]   node   0: [mem 0x00000000a0000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000bfffffff]
[    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.2
[    0.000000] percpu: Embedded 29 pages/cpu s77928 r8192 d32664 u118784
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 258048
[    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 mtdparts=spi-nand0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),256k(ospi.env.backup),98048k@32m(ospi.rootfs),256k@130816k(ospi.phypattern);omap2-nand.0:2m(NAND.tiboot3),2m(NAND.tispl),2m(NAND.tiboot3.backup),4m(NAND.u-boot),256k(NAND.u-boot-env),256k(NAND.u-boot-env.backup),-(NAND.file-system) root=PARTUUID=e6b78e84-a3d7-fb47-89c1-55f05363ec46 rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 814096K/1048576K available (13312K kernel code, 2432K rwdata, 5060K rodata, 3456K init, 465K bss, 103408K reserved, 131072K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] trace event string verifier disabled
[    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=4.
[    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=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 256 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:0x0000000001880000
[    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 @80800000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x00000000800d0000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000000800e0000
[    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.000001] sched_clock: 58 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
[    0.008670] Console: colour dummy device 80x25
[    0.013273] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.023956] pid_max: default: 32768 minimum: 301
[    0.028751] LSM: Security Framework initializing
[    0.033581] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.041157] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    0.050963] cblist_init_generic: Setting adjustable number of callback queues.
[    0.058414] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.064711] cblist_init_generic: Setting adjustable number of callback queues.
[    0.072108] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.078527] rcu: Hierarchical SRCU implementation.
[    0.083438] rcu:     Max phase no-delay instances is 1000.
[    0.089627] Platform MSI: msi-controller@1820000 domain created
[    0.095972] PCI/MSI: /bus@f0000/interrupt-controller@1800000/msi-controller@1820000 domain created
[    0.105341] EFI services will not be available.
[    0.110359] smp: Bringing up secondary CPUs ...
[    0.115720] Detected VIPT I-cache on CPU1
[    0.115832] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000
[    0.115850] GICv3: CPU1: using allocated LPI pending table @0x00000000800f0000
[    0.115909] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.116632] Detected VIPT I-cache on CPU2
[    0.116709] GICv3: CPU2: found redistributor 2 region 0:0x00000000018c0000
[    0.116722] GICv3: CPU2: using allocated LPI pending table @0x0000000080100000
[    0.116754] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.117396] Detected VIPT I-cache on CPU3
[    0.117472] GICv3: CPU3: found redistributor 3 region 0:0x00000000018e0000
[    0.117485] GICv3: CPU3: using allocated LPI pending table @0x0000000080110000
[    0.117515] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.117581] smp: Brought up 1 node, 4 CPUs
[    0.197336] SMP: Total of 4 processors activated.
[    0.202150] CPU features: detected: 32-bit EL0 Support
[    0.207424] CPU features: detected: CRC32 instructions
[    0.212742] CPU: All CPU(s) started at EL2
[    0.216940] alternatives: applying system-wide alternatives
[    0.224216] devtmpfs: initialized
[    0.235416] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.245445] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.257464] pinctrl core: initialized pinctrl subsystem
[    0.263498] DMI not present or invalid.
[    0.268072] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.275310] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[    0.282774] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.290795] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.298979] audit: initializing netlink subsys (disabled)
[    0.304673] audit: type=2000 audit(0.192:1): state=initialized audit_enabled=0 res=1
[    0.305159] thermal_sys: Registered thermal governor 'step_wise'
[    0.312603] thermal_sys: Registered thermal governor 'power_allocator'
[    0.318790] cpuidle: using governor menu
[    0.329640] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.336670] ASID allocator initialised with 65536 entries
[    0.346133] /bus@f0000/interrupt-controller@1800000: Fixed dependency cycle(s) with /bus@f0000/interrupt-controller@1800000
[    0.363947] /bus@f0000/pinctrl@a40000: Fixed dependency cycle(s) with /bus@f0000/pinctrl@a40000/cpsw-cpts
[    0.376042] KASLR disabled due to lack of seed
[    0.387338] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    0.394319] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.400731] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[    0.407672] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.414080] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    0.421019] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.427428] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[    0.434367] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    0.442320] k3-chipinfo 43000014.chipid: Family:AM62X rev:SR1.0 JTAGID[0x0bb7e02f] Detected
[    0.451951] iommu: Default domain type: Translated
[    0.457013] iommu: DMA domain TLB invalidation policy: strict mode
[    0.463721] SCSI subsystem initialized
[    0.467896] usbcore: registered new interface driver usbfs
[    0.473550] usbcore: registered new interface driver hub
[    0.479022] usbcore: registered new device driver usb
[    0.484618] pps_core: LinuxPPS API ver. 1 registered
[    0.489704] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.499055] PTP clock support registered
[    0.503190] EDAC MC: Ver: 3.0.0
[    0.507320] omap-mailbox 29000000.mailbox: omap mailbox rev 0x66fc9100
[    0.514336] FPGA manager framework
[    0.517893] Advanced Linux Sound Architecture Driver Initialized.
[    0.525118] clocksource: Switched to clocksource arch_sys_counter
[    0.531753] VFS: Disk quotas dquot_6.6.0
[    0.535820] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.548839] NET: Registered PF_INET protocol family
[    0.554056] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.562693] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.571309] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.579243] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.587222] TCP bind hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    0.594870] TCP: Hash tables configured (established 8192 bind 8192)
[    0.601548] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.608344] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.615739] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.622082] RPC: Registered named UNIX socket transport module.
[    0.628156] RPC: Registered udp transport module.
[    0.632966] RPC: Registered tcp transport module.
[    0.637774] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.644365] NET: Registered PF_XDP protocol family
[    0.649298] PCI: CLS 0 bytes, default 64
[    0.654270] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    1.204687] Initialise system trusted keyrings
[    1.209640] workingset: timestamp_bits=46 max_order=18 bucket_order=0
[    1.220647] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.227302] NFS: Registering the id_resolver key type
[    1.232638] Key type id_resolver registered
[    1.236927] Key type id_legacy registered
[    1.241100] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.247963] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.291930] Key type asymmetric registered
[    1.296125] Asymmetric key parser 'x509' registered
[    1.301167] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    1.308897] io scheduler mq-deadline registered
[    1.313548] io scheduler kyber registered
[    1.321163] pinctrl-single 4084000.pinctrl: 34 pins, size 136
[    1.328697] pinctrl-single f4000.pinctrl: 171 pins, size 684
[    1.339019] pinctrl-single a40000.pinctrl: 512 pins, size 2048
[    1.351261] Serial: 8250/16550 driver, 12 ports, IRQ sharing enabled
[    1.367563] loop: module loaded
[    1.371931] megasas: 07.719.03.00-rc1
[    1.378719] tun: Universal TUN/TAP device driver, 1.6
[    1.384615] VFIO - User Level meta-driver version: 0.3
[    1.391380] usbcore: registered new interface driver usb-storage
[    1.398147] i2c_dev: i2c /dev entries driver
[    1.404156] sdhci: Secure Digital Host Controller Interface driver
[    1.410518] sdhci: Copyright(c) Pierre Ossman
[    1.415154] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.421637] ledtrig-cpu: registered to indicate activity on CPUs
[    1.427961] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.434872] usbcore: registered new interface driver usbhid
[    1.440575] usbhid: USB HID core driver
[    1.445414] optee: probing for conduit method.
[    1.450000] optee: revision 3.20 (8e74d476)
[    1.450305] optee: dynamic shared memory is enabled
[    1.459861] optee: initialized driver
[    1.465301] Initializing XFRM netlink socket
[    1.469708] NET: Registered PF_PACKET protocol family
[    1.474950] Key type dns_resolver registered
[    1.479763] registered taskstats version 1
[    1.483985] Loading compiled-in X.509 certificates
[    1.499947] ti-sci 44043000.system-controller: ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
[    1.575227] /bus@f0000/i2c@20000000/pmic@30: Fixed dependency cycle(s) with /bus@f0000/i2c@20000000/pmic@30/regulators/buck2
[    1.617704] at24 0-0050: supply vcc not found, using dummy regulator
[    1.624750] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    1.632085] at24 0-0051: supply vcc not found, using dummy regulator
[    1.638990] at24 0-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    1.646309] pca953x 0-0022: supply vcc not found, using dummy regulator
[    1.653194] pca953x 0-0022: using AI
[    1.659692] rtc-pcf8523 0-0068: registered as rtc0
[    1.664911] rtc-pcf8523 0-0068: setting system clock to 2025-05-06T07:10:21 UTC (1746515421)
[    1.673603] omap_i2c 20000000.i2c: bus 0 rev0.12 at 400 kHz
[    1.679830] ti-sci-intr 4210000.interrupt-controller: Interrupt Router 5 domain created
[    1.688188] ti-sci-intr bus@f0000:interrupt-controller@a00000: Interrupt Router 3 domain created
[    1.697436] ti-sci-inta 48000000.interrupt-controller: Interrupt Aggregator domain 28 created
[    1.707988] ti-udma 485c0100.dma-controller: Number of rings: 82
[    1.716247] ti-udma 485c0100.dma-controller: Channels: 48 (bchan: 18, tchan: 12, rchan: 18)
[    1.727295] ti-udma 485c0000.dma-controller: Number of rings: 150
[    1.737462] ti-udma 485c0000.dma-controller: Channels: 35 (tchan: 20, rchan: 15)
[    1.747693] printk: console [ttyS2] disabled
[    1.752198] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 285, base_baud = 3000000) is a 8250
[    1.761086] printk: console [ttyS2] enabled
[    1.761086] printk: console [ttyS2] enabled
[    1.769543] printk: bootconsole [ns16550a0] disabled
[    1.769543] printk: bootconsole [ns16550a0] disabled
[    1.781453] davinci_mdio 8000f00.mdio: Configuring MDIO in manual mode
[    1.825137] davinci_mdio 8000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[    1.834094] am65-cpsw-nuss 8000000.ethernet: initializing am65 cpsw nuss version 0x6BA01103, cpsw version 0x6BA81103 Ports: 3 quirks:00000006
[    1.846973] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.5
[    1.854101] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512
[    1.860756] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010c, freq:500000000, add_val:1 pps:0
[    1.871195] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19
[    1.882419] xhci-hcd xhci-hcd.2.auto: USB3 root hub has no ports
[    1.888465] xhci-hcd xhci-hcd.2.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000008000010010
[    1.897905] xhci-hcd xhci-hcd.2.auto: irq 290, io mem 0x31000000
[    1.904718] hub 1-0:1.0: 1 port detected
[    1.911666] xhci-hcd xhci-hcd.3.auto: USB3 root hub has no ports
[    1.917698] xhci-hcd xhci-hcd.3.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000008000010010
[    1.927133] xhci-hcd xhci-hcd.3.auto: irq 291, io mem 0x31100000
[    1.933918] hub 2-0:1.0: 1 port detected
[    1.939116] rti-wdt e000000.watchdog: watchdog already running, ignoring heartbeat config!
[    1.952775] mmc0: CQHCI version 5.10
[    1.963293] davinci_mdio 8000f00.mdio: Configuring MDIO in manual mode
[    1.997874] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
[    2.009140] davinci_mdio 8000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[    2.057636] mmc0: Command Queue Engine enabled
[    2.062118] mmc0: new HS200 MMC card at address 0001
[    2.068064] mmcblk0: mmc0:0001 IS008G 7.28 GiB
[    2.077919]  mmcblk0: p1
[    2.081237] mmcblk0boot0: mmc0:0001 IS008G 4.00 MiB
[    2.087469] mmcblk0boot1: mmc0:0001 IS008G 4.00 MiB
[    2.093496] mmcblk0rpmb: mmc0:0001 IS008G 4.00 MiB, chardev (239:0)
[    2.153522] davinci_mdio 8000f00.mdio: phy[0]: device 8000f00.mdio:00, driver unknown
[    2.161377] davinci_mdio 8000f00.mdio: phy[1]: device 8000f00.mdio:01, driver unknown
[    2.176823] clk: Disabling unused clocks
[    2.191932] ALSA device list:
[    2.194940]   No soundcards found.
[    2.233095] EXT4-fs (mmcblk0p1): recovery complete
[    2.241357] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Quota mode: none.
[    2.249974] VFS: Mounted root (ext4 filesystem) on device 179:1.
[    2.259553] devtmpfs: mounted
[    2.264736] Freeing unused kernel memory: 3456K
[    2.269524] Run /sbin/init as init process
[    2.377811] NET: Registered PF_INET6 protocol family
[    2.384226] Segment Routing with IPv6
[    2.387982] In-situ OAM (IOAM) with IPv6
[    2.410648] 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)
[    2.442685] systemd[1]: Detected architecture arm64.

Welcome to Linux!

[    2.519610] systemd[1]: Hostname set to <am62xx-alc>.
[    2.631334] systemd-sysv-generator[153]: SysV service '/etc/init.d/maintain_emmc_integrity.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.658501] systemd-sysv-generator[153]: SysV service '/etc/init.d/load_am335x_adc' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.683489] systemd-sysv-generator[153]: SysV service '/etc/init.d/rc' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.707067] systemd-sysv-generator[153]: SysV service '/etc/init.d/loginShell.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.732114] systemd-sysv-generator[153]: SysV service '/etc/init.d/populate-volatile.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.757056] systemd-sysv-generator[153]: SysV service '/etc/init.d/sshd.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.781557] systemd-sysv-generator[153]: SysV service '/etc/init.d/mount_var_debrick' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.806247] systemd-sysv-generator[153]: SysV service '/etc/init.d/loginShell' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.830331] systemd-sysv-generator[153]: SysV service '/etc/init.d/check-recovery' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.854767] systemd-sysv-generator[153]: SysV service '/etc/init.d/watchdogd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.878746] systemd-sysv-generator[153]: SysV service '/etc/init.d/rc.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.903061] systemd-sysv-generator[153]: SysV service '/etc/init.d/dnsmasq' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.926863] systemd-sysv-generator[153]: SysV service '/etc/init.d/modutils.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.951074] systemd-sysv-generator[153]: SysV service '/etc/init.d/usbNetConfig' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.975322] systemd-sysv-generator[153]: SysV service '/etc/init.d/reset-alc-usb' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    2.999699] systemd-sysv-generator[153]: SysV service '/etc/init.d/functions' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.023996] systemd-sysv-generator[153]: SysV service '/etc/init.d/launch-lam.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.048342] systemd-sysv-generator[153]: SysV service '/etc/init.d/launch-fwex_cntrl.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.073289] systemd-sysv-generator[153]: SysV service '/etc/init.d/fpga_load' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.097290] systemd-sysv-generator[153]: SysV service '/etc/init.d/populate-volatile.sh.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.123177] systemd-sysv-generator[153]: SysV service '/etc/init.d/runlevel-change-done' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.148093] systemd-sysv-generator[153]: SysV service '/etc/init.d/dbus-1' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.172409] systemd-sysv-generator[153]: SysV service '/etc/init.d/mount_var.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.197367] systemd-sysv-generator[153]: SysV service '/etc/init.d/ethportconfig' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.222425] systemd-sysv-generator[153]: SysV service '/etc/init.d/functions.initscripts' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.247519] systemd-sysv-generator[153]: SysV service '/etc/init.d/launch-io-server_cntrl.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.272893] systemd-sysv-generator[153]: SysV service '/etc/init.d/firewall.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.297722] systemd-sysv-generator[153]: SysV service '/etc/init.d/hostapd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.321522] systemd-sysv-generator[153]: SysV service '/etc/init.d/io-serverd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.345598] systemd-sysv-generator[153]: SysV service '/etc/init.d/watchdog_updated' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.370409] systemd-sysv-generator[153]: SysV service '/etc/init.d/firewall' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.394319] systemd-sysv-generator[153]: SysV service '/etc/init.d/syslog.busybox.bundle-new' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.419711] systemd-sysv-generator[153]: SysV service '/etc/init.d/mount_var' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.443684] systemd-sysv-generator[153]: SysV service '/etc/init.d/usbWifiConfig' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.468000] systemd-sysv-generator[153]: SysV service '/etc/init.d/fwexd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.491636] systemd-sysv-generator[153]: SysV service '/etc/init.d/inetd.busybox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.516002] systemd-sysv-generator[153]: SysV service '/etc/init.d/telnetd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.591756] systemd-sysv-generator[153]: Overwriting existing symlink /run/systemd/generator.late/reset-alc-usb.service with real service.
[    3.860254] 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.
[    3.922028] systemd[1]: Queued start job for default target Multi-User System.
[    3.984058] systemd[1]: Created slice Slice /system/getty.
[  OK  ] Created slice Slice /system/getty.
[    4.007484] systemd[1]: Created slice Slice /system/modprobe.
[  OK  ] Created slice Slice /system/modprobe.
[    4.031726] systemd[1]: Created slice Slice /system/serial-getty.
[  OK  ] Created slice Slice /system/serial-getty.
[    4.055547] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    4.077898] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[    4.101727] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[    4.126019] systemd[1]: Reached target Path Units.
[  OK  ] Reached target Path Units.
[    4.141547] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    4.161437] systemd[1]: Reached target Slice Units.
[  OK  ] Reached target Slice Units.
[    4.177392] systemd[1]: Reached target Swaps.
[  OK  ] Reached target Swaps.
[    4.200570] systemd[1]: Listening on Syslog Socket.
[  OK  ] Listening on Syslog Socket.
[    4.218244] systemd[1]: Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[    4.243268] systemd[1]: Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Audit Socket.
[    4.266509] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    4.291947] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    4.311265] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[    4.336441] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    4.359321] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    4.383667] systemd[1]: Listening on User Database Manager Socket.
[  OK  ] Listening on User Database Manager Socket.
[    4.445846] systemd[1]: Mounting Huge Pages File System...
         Mounting Huge Pages File System...
[    4.467430] systemd[1]: Mounting POSIX Message Queue File System...
         Mounting POSIX Message Queue File System...
[    4.496757] systemd[1]: Mounting Kernel Debug File System...
         Mounting Kernel Debug File System...
[    4.520533] systemd[1]: Mounting Kernel Trace File System...
         Mounting Kernel Trace File System...
[    4.565872] systemd[1]: Mounting Temporary Directory /tmp...
         Mounting Temporary Directory /tmp...
[    4.589426] systemd[1]: Starting Create List of Static Device Nodes...
         Starting Create List of Static Device Nodes...
[    4.623769] systemd[1]: Starting Load Kernel Module configfs...
         Starting Load Kernel Module configfs...
[    4.647610] systemd[1]: Starting Load Kernel Module drm...
         Starting Load Kernel Module drm...
[    4.671497] systemd[1]: Starting Load Kernel Module fuse...
         Starting Load Kernel Module fuse...
[    4.689722] systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
[    4.713569] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[    4.754205] systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...
[    4.773925] cryptodev: loading out-of-tree module taints kernel.
[    4.774796] systemd[1]: Starting Generate network units from Kernel command line...
         Starting Generate network …ts from Kernel co[    4.788742] cryptodev: driver 1.12 loaded.
mmand line...
[    4.814314] systemd[1]: Starting Remount Root and Kernel File Systems...
         Starting Remount Root and Kernel File Systems...
[    4.838229] EXT4-fs (mmcblk0p1): re-mounted. Quota mode: none.
[    4.843098] systemd[1]: Starting Coldplug All udev Devices...
         Starting Coldplug All udev Devices...
[    4.869743] systemd[1]: Mounted Huge Pages File System.
[  OK  ] Mounted Huge Pages File System.
[    4.894127] systemd[1]: Mounted POSIX Message Queue File System.
[  OK  ] Mounted POSIX Message Queue File System.
[    4.918077] systemd[1]: Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Debug File System.
[    4.942155] systemd[1]: Mounted Kernel Trace File System.
[  OK  ] Mounted Kernel Trace File System.
[    4.970268] systemd[1]: Mounted Temporary Directory /tmp.
[  OK  ] Mounted Temporary Directory /tmp.
[    4.995259] systemd[1]: Finished Create List of Static Device Nodes.
[  OK  ] Finished Create List of Static Device Nodes.
[    5.018955] systemd[1]: modprobe@configfs.service: Deactivated successfully.
[    5.027196] systemd[1]: Finished Load Kernel Module configfs.
[  OK  ] Finished Load Kernel Module configfs.
[    5.050907] systemd[1]: modprobe@drm.service: Deactivated successfully.
[    5.058806] systemd[1]: Finished Load Kernel Module drm.
[  OK  ] Finished Load Kernel Module drm.
[    5.082619] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
[  OK  ] Finished Load Kernel Module fuse.
[  OK  ] Finished Load Kernel Modules.
[  OK  ] Finished Generate network units from Kernel command line.
[  OK  ] Finished Remount Root and Kernel File Systems.
         Mounting Kernel Configuration File System...
         Starting Flush Journal to Persistent Storage...
[    5.239074] systemd-journald[163]: Received client request to flush runtime journal.
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Finished Flush Journal to Persistent Storage.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Reached target Preparation for Local File Systems.
         Mounting /media/ram...
         Mounting /var/volatile...
[    5.437717] audit: type=1334 audit(1746515425.272:2): prog-id=5 op=LOAD
[    5.444472] audit: type=1334 audit(1746515425.276:3): prog-id=6 op=LOAD
         Starting Rule-based Manage…for Device Events and Files...
[  OK  ] Finished Coldplug All udev Devices.
[  OK  ] Mounted /media/ram.
[  OK  ] Mounted /var/volatile.
         Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Rule-based Manager for Device Events and Files.
[  OK  ] Finished Create Volatile Files and Directories.
         Starting Network Time Synchronization...
         Starting Record System Boot/Shutdown in UTMP...
[  OK  ] Finished Record System Boot/Shutdown in UTMP.
[    5.952049] ttyAct: Initializing Actuator device driver ACT version 1.01-03
[    5.983005] ttyAct: I2C Probe for Actuator device driver version 1.01-03
[    6.000584] ttyAct: DevName=ActNet IRQNum= 0 Flag= 0
[    6.020581] ActNet 0-0048: ttyAct: LSR failed val=0
[    6.050564] ActNet 0-0048: ttyAct: actnet probe failed
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target System Time Set.
[  OK  ] Reached target Timer Units.
[  OK  ] Listening on D-Bus System Message Bus Socket.
         Starting sshd.socket...
[  OK  ] Listening on sshd.socket.
[  OK  ] Reached target Socket Units.
[  OK  ] Reached target Basic System.
[  OK  ] Started Periodic Command Scheduler.
         Starting D-Bus System Message Bus...
[  OK  ] Started A minimalistic net…Pv4, rdisc and DHCPv6 support.
         Starting Print notice about GPLv3 packages...
grep: /var/lib/opkg/info/*.control: No such file or directory
         Starting IPv6 Packet Filtering Framework...
         Starting IPv4 Packet Filtering Framework...
[    6.465748] UDC core: g_mass_storage: couldn't find an available UDC
[  OK  ] Started Start usb mass storage gadg[    6.477190] random: crng init done
et.
[  OK  ] Started System Logging Service.
         Starting User Login Management...
         Starting OpenSSH Key Generation...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Print notice about GPLv3 packages.
[  OK  ] Finished IPv6 Packet Filtering Framework.
[  OK  ] Finished IPv4 Packet Filtering Framework.
[  OK  ] Finished OpenSSH Key Generation.
[  OK  ] Reached target Preparation for Network.
         Starting Network Configuration...
[  OK  ] Started User Login Management.
[  OK  ] Started Network Configuration.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
         Starting Network Name Resolution...
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Started Respond to IPv6 Node Information Queries.
[  OK  ] Started Network Router Discovery Daemon.
         Starting Permit User Sessions...
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS2.
[  OK  ] Started Serial Getty on ttyS3.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
         Starting Synchronize System and HW clocks...
         Starting Record Runlevel Change in UTMP...
[  OK  ] Finished Synchronize System and HW clocks.
[  OK  ] Finished Record Runlevel Change in UTMP.

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project am62xx-alc ttyS2

Carrier Linux Reference Distrbution nodistro.0 am62xx-alc ttyS2

am62xx-alc login: root
root@am62xx-alc:~#

Thanks,

Anil

0 Nick Saulnier 5 months ago in reply to Anil medak

TI__Guru** 101960 points

Hello Anil,

Awesome, I am glad to hear that we are making progress! So it seems like if we try to initialize the watchdog of a core that has not been powered on yet, then that can cause issues.

Are you able to get the processor to time out and reboot if the watchdog0 is initialized during uboot, and then the processor boots as usual (without petting the watchdog)?

Regards,

Nick

0 Anil medak 4 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,
So, I can only test watchdog0 since cores 1, 2, and 3 are not yet powered on. How can I check the watchdog in U-Boot using command-line prompts?

I have already verified that watchdogs 0, 1, 2, and 3 are working as expected in the kernel

Thanks,

Anil

0 Nick Saulnier 4 months ago in reply to Anil medak

TI__Guru** 101960 points

Hello Anil,

Off the top of my head, I am not sure of the "correct" way to do it through uboot drivers, but you can manually start the watchdog by manipulating the registers like I did here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1484145/processor-sdk-am62x-watchdog-issues-on-am62x-custom-board-based-on-am62x-sk-board/5799711#5799711

Regards,

Nick

0 Anil medak 4 months ago in reply to Nick Saulnier

Prodigy 50 points

Hi Nick,

Question1:
After running the commands below, U-Boot resets within a few seconds. Could you please explain what is happening or provide a reference to understand it better?

configure the watchdog to time out after about a second

Hit any key to stop autoboot: 0
// RTI0
=> mw.l 0xE0000A4 0xa 1
=> mw.l 0xE000090 0xA98559DA 1

// RTI1, RTI2, RTI3 throw an error when I try to write
// probably because those A53 cores have not been powered on yet

// MCU_RTI0 throws an error, probably because the MCU_R5 has not been
// powered on yet

// DM R5F RTI (i.e., WKUP_RTI0)
=> mw.l 0x2B0000A4 0xa 1
=> mw.l 0x2B000090 0xA98559DA 1

Question 2:

Alternative method followed:
Even after 3 minutes, the watchdog in uboot is still not being petted?

U-Boot 2023.04ALC-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)

SoC: AM62X SR1.0 HS-FS
Model: TI AM62x ALC NGZN V4
EEPROM not available at 81, trying to read at 82
Reading on-board EEPROM at 0x52 failed -121
DRAM: 1 GiB
Core: 80 devices, 30 uclasses, devicetree: separate
@@@@ rti_wdt_start() called with timeout_ms = 60000
@@@@ skipping watchdog start: not explicitly requested
WDT: Started watchdog@e000000 with servicing every 1000ms (60s timeout)
MMC: mmc@fa10000: 0
Loading Environment from nowhere... OK
Net: eth0: ethernet@8000000port@1, eth1: ethernet@8000000port@2
Hit any key to stop autoboot: 0
=> wdt list
watchdog@e000000 (rti_wdt)
=> wdt dev watchdog@e000000
=> wdt start 60000 1
@@@@ rti_wdt_start() called with timeout_ms = 60000
WDT: Started watchdog@e000000 with servicing every 1000ms (60s timeout)
=>

changes:
drivers/watchdog/rti_wdt.c b/drivers/watchdog/rti_wdt.c
static int rti_wdt_start(struct udevice *dev, u64 timeout_ms, ulong flags)
{
struct rti_wdt_priv *priv = dev_get_priv(dev);
u32 timer_margin;
int ret;

printf("@@@@ rti_wdt_start() called with timeout_ms = %llu\n", timeout_ms);

/* Only start if explicitly requested (e.g., from CLI) */
if (!(flags & BIT(0))) {
printf("@@@@ skipping watchdog start: not explicitly requested\n");
return 0;
}

if (readl(priv->regs + RTIDWDCTRL) == WDENABLE_KEY)
return -EBUSY;

Thanks,

Anil

0 Mukul Bhatnagar 1 month ago in reply to Anil medak

TI__Guru* 84075 points

Hi Nick,

Question1:
After running the commands below, U-Boot resets within a few seconds. Could you please explain what is happening or provide a reference to understand it better?

configure the watchdog to time out after about a second

Hit any key to stop autoboot: 0
// RTI0
=> mw.l 0xE0000A4 0xa 1
=> mw.l 0xE000090 0xA98559DA 1

// RTI1, RTI2, RTI3 throw an error when I try to write
// probably because those A53 cores have not been powered on yet

// MCU_RTI0 throws an error, probably because the MCU_R5 has not been
// powered on yet

// DM R5F RTI (i.e., WKUP_RTI0)
=> mw.l 0x2B0000A4 0xa 1
=> mw.l 0x2B000090 0xA98559DA 1

Question 2:

Alternative method followed:
Even after 3 minutes, the watchdog in uboot is still not being petted?

U-Boot 2023.04ALC-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)

printf("@@@@ rti_wdt_start() called with timeout_ms = %llu\n", timeout_ms);

/* Only start if explicitly requested (e.g., from CLI) */
if (!(flags & BIT(0))) {
printf("@@@@ skipping watchdog start: not explicitly requested\n");
return 0;
}

if (readl(priv->regs + RTIDWDCTRL) == WDENABLE_KEY)
return -EBUSY;

Thanks,

Anil

0 Mukul Bhatnagar 1 month ago in reply to Mukul Bhatnagar

TI__Guru* 84075 points

Hello

Is this issue still open for you?

Regards

Mukul

Processors

Processors forum

PROCESSOR-SDK-AM62X: Watchdog Issues on AM62x Custom Board Based on AM62X SK Board