• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 163 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

SK-TDA4VM: Using the SK-TDA4VM with QNX OS and PTP

SK-TDA4VM: Does my hardware have a PTP Hardware Clock?

shyluboy
Prodigy 30 points
Part Number: SK-TDA4VM
Other Parts Discussed in Thread: DP83867E,

I am running the ptpd2 daemon on my QNX Neutrino 7.1.0 system, and I am seeing the following output:

netInitTimestamping: hw time support - 0

Does this mean that my hardware does not have a PTP Hardware Clock?
I am using SK-TDA4VM hardware that has DP83867E Ethernet PHY.


Detailed logs: 
# ptpd2 -d --ptpengine:preset=masteronly --ptpengine:interface=cpsw0 --global:verbose_foreground=1
1970-01-01 00:41:33.331792 ptpd2[278561].startup (info) (___) Configuration OK
1970-01-01 00:41:33.332792 ptpd2[278561].startup (info) (___) Successfully acquired lock on /dev/shmem/ptpd2.pid
1970-01-01 00:41:33.332792 ptpd2[278561].startup (notice) (___) PTPDv2 started successfully on cpsw0 using "masteronly" preset (PID 278561)
1970-01-01 00:41:33.333792 ptpd2[278561].startup (info) (___) TimingService.PTP0: PTP service init
# Timestamp, State, Clock ID, One Way Delay, Offset From Master, Slave to Master, Master to Slave, Observed Drift, Last packet Received
1970-01-01 00:41:33.333792, init,
1970-01-01 00:41:33.335792 ptpd2[278561].cpsw0 (notice) (init) Checking for HW support
1970-01-01 00:41:33.335792 ptpd2[278561].cpsw0 (notice) (init) netInitTimestamping: hw time support - 0
1970-01-01 00:41:33.336792 ptpd2[278561].cpsw0 (warning) (init) netShutdown
1970-01-01 00:41:33.338792 ptpd2[278561].cpsw0 (notice) (init) Checking for HW support
1970-01-01 00:41:33.339792 ptpd2[278561].cpsw0 (notice) (init) netInitTimestamping: hw time support - 0
1970-01-01 00:41:33.440792 ptpd2[278561].cpsw0 (notice) (lstn_init) Now in state: PTP_LISTENING
1970-01-01 00:41:33.440792, lstn_init, 1
1970-01-01 00:41:43.334792 ptpd2[278561].cpsw0 (notice) (lstn_init) TimingService.PTP0: elected best TimingService
1970-01-01 00:41:43.334792 ptpd2[278561].cpsw0 (info) (lstn_init) TimingService.PTP0: acquired clock control
1970-01-01 00:41:45.441792 ptpd2[278561].cpsw0 (notice) (mst) Now in state: PTP_MASTER, Best master: 02eec6fffeeec494(unknown)/1 (self)
1970-01-01 00:41:45.441792, mst, 02eec6fffeeec494(unknown)/1

  • 0
    TI__Mastermind 33461 points

    Hello

    Above log show the ptpd2 time-sync daemon app is interacting with the  "cpsw0" network interface , which is the interface supported by using the QNX io-sock driver.,

    The hardware does support the CPTS module part of the CPSW2G and CPSW9G ethernet peripheral, but the network driver must support reading CPTS timestamp and get the synchronized time from the PTP server running on the network.

    Please note that this io-sock driver is delivery from Blackberry QNX and we suggest you contact them regarding PTP support in the driver.

    We are closing this ticket.

    Thanks.