• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 118 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMDS64EVM: TMDS64EVM Technical Inquiry

Dong Gyun GIL
Prodigy 145 points

Part Number: TMDS64EVM

I am wondering why the [FAILED] log appears in the Linux boot log as shown below when following the TI webpage Quick Guide with the TMDS64EVM.

[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS2.
[ OK ] Reached target Login Prompts.
Starting Synchronize System and HW clocks...
[ OK ] Started LLDP daemon.
[FAILED] Failed to start Synchronize System and HW clocks.
See 'systemctl status sync-clocks.service' for details.
[ 12.690159] CAN device driver interface
[ 12.774781] omap-mailbox 29020000.mailbox: omap mailbox rev 0x66fc9100
[ 12.786145] omap-mailbox 29040000.mailbox: omap mailbox rev 0x66fc9100
[ 12.797572] omap-mailbox 29060000.mailbox: omap mailbox rev 0x66fc9100
[ 12.930817] at24 0-0050: supply vcc not found, using dummy regulator
[ 13.002670] at24 0-0050: 131072 byte 24c1024 EEPROM, writable, 1 bytes/write
[ 13.118624] davinci_mdio 300b2400.mdio: Configuring MDIO in manual mode
[ 13.167541] davinci_mdio 300b2400.mdio: davinci mdio revision 1.7, bus freq 1000000
[ OK ] Started Simple Network Management Protocol (SNMP) Daemon..

  • 0
    TI__Guru**** 179926 points

    Hi Dong Gyun,

    Dong Gyun GIL said:
    I am wondering why the [FAILED] log appears in the Linux boot log as shown below when following the TI webpage Quick Guide with the TMDS64EVM.

    This type of errors is generated from systemd when it fails to start any of systemd services. In general, these failures mean the Linux system misses dependencies for running the systermd services.

    Dong Gyun GIL said:
    [FAILED] Failed to start Synchronize System and HW clocks.
    See 'systemctl status sync-clocks.service' for details.

    However, I booted my TMDS64EVM with SDK11.02 default wic image, I don't see any of systemd failure.

    sync-clocks.service doesn't exist in the SDK11.02 Linux image:

    root@am64xx-evm:~# systemctl status sync-clocks.service
    Unit sync-clocks.service could not be found.