Tool/software:
On a new TMDS64EVM I tried a couple different examples unsucessfully so loaded one of the "Hello World" examples, expecting it to work for sure.
From main() the call path is:
System_init(void)
PowerClock_init()
Module_clockSetFrequency()
status = SOC_moduleSetClockFrequency(
DebugP_assertNoLog(status == SystemP_SUCCESS) <--- hangs here, status = -1
The example project: gpmc_psram_io_am64x-evm_r5ss0-0_nortos_ti-arm-clang also hangs at the same assert.
After resetting the EVM this message comes up that I didn't notice before:
[ OK ] Reached target Login Prompts. Starting Synchronize System and HW clocks... [FAILED] Failed to start Synchronize System and HW clocks. See 'systemctl status sync-clocks.service' for details. [ 12.883380] platform mdio-mux-1: deferred probe pending [ 13.044334] CAN device driver interface
There aren't any other errors or warnings during boot up.
Running the command suggested in the error:
root@am64xx-evm:~# systemctl status sync-clocks.service
x sync-clocks.service - Synchronize System and HW clocks
Loaded: loaded (/etc/systemd/system/sync-clocks.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Fri 2024-10-11 14:39:54 UTC; 5min ago
Process: 417 ExecStart=/sbin/hwclock --systohc (code=exited, status=1/FAILURE)
Main PID: 417 (code=exited, status=1/FAILURE)
CPU: 39ms
Oct 11 14:39:54 am64xx-evm systemd[1]: Starting Synchronize System and HW clocks...
Oct 11 14:39:54 am64xx-evm hwclock[417]: hwclock: Cannot access the Hardware Clock via any known method.
Oct 11 14:39:54 am64xx-evm hwclock[417]: hwclock: Use the --verbose option to see the details of our search for an access method.
Oct 11 14:39:54 am64xx-evm systemd[1]: sync-clocks.service: Main process exited, code=exited, status=1/FAILURE
Oct 11 14:39:54 am64xx-evm systemd[1]: sync-clocks.service: Failed with result 'exit-code'.
Oct 11 14:39:54 am64xx-evm systemd[1]: Failed to start Synchronize System and HW clocks.
Any ideas on what is going wrong?
