RTOS/PROCESSOR-SDK-AM57X: timeSync example don't work on PRU2.1 on SDK 05.01.00.11

Hi Alex, do you get an error when using TIMESYNC_TEST_PORT_NUM=1; or what exactly is the behavior?. Also, are you trying Out-Of-Box timeSync_BasicExample_idkAM572x_wSocLib_armExampleproject project or a modified version? Are you testing it with 2 AM5728 IDK boards? or which boards are you using?

From code inspection both ports should work OK.. Let me know about above questions to see if I can reproduce the issue.

thank you,

Paula

 

Hi Paula,

Paula Carrillo said:

do you get an error when using TIMESYNC_TEST_PORT_NUM=1; or what exactly is the behavior?

I have no error messages, but when I use TIMESYNC_TEST_PORT_NUM=0, all is good (and sync starts on PRU2.0). When I set TIMESYNC_TEST_PORT_NUM=1, device is working, but time cannot start to sync (I saw that by LED indication & debug UART). Debug uart output you can find by link: https://pastebin.com/fcw9qNXF

Paula Carrillo said:

Also, are you trying Out-Of-Box timeSync_BasicExample_idkAM572x_wSocLib_armExampleproject project or a modified version?

I'm using Out-Of-Box version of timeSync_BasicExample_idkAM572x_wSocLib_armExampleproject, but I change IP addresses to 192.168.3.3 and 192.168.4.3. My network card has 2 IPs of required ranges and it works correctly with other example projects. With that project I can ping only 1 interface (with IP 192.168.3.3) with TIMESYNC_TEST_PORT_NUM=0, but cannot ping no one with TIMESYNC_TEST_PORT_NUM=1.

Paula Carrillo said:

Are you testing it with 2 AM5728 IDK boards? or which boards are you using?

I'm testing it with second network card on my PC. I'm using PTPd as master with that config (see it by link): gist.github.com/.../bceb73f9f4f99955312c12d74766a5fc . AM572x IDK board was as slave device.

Paula Carrillo said:

Let me know about above questions to see if I can reproduce the issue.

I need to make PRU2.1 sync work.

My working environment: Ubuntu x64 16.04.5 LTS, TI-RTOS SDK v05.01.00.11, CCS v8.1.0.00011, compiler GNU v7.2.1 (Linaro).

With regards,

Alex

Alex, my apology, I was away from my desk few days and I missed your reply. I will come back to you soon.

thank you,
Paula

Hi Alex, do you need to use both Interfaces w PTP at the same time? If so, I am not sure this use case is covered by test application. I will double check though.

If not, then, I believe it actually works OK. If I ran timeSync_BasicExample_idkAM572x_wSocLib_armExampleproject as PTP slave and connect PRU2.Eth0 with my Linux machine (Running PTPd as P2P master) then from UART and LEDs it seems to work OK. If I unplugged the cable, I see stats increments "Num Sync Missed". But, after I connected to PRU.Eth1 things seems to work OK again.

I am using OOB demo.

thank you,
Paula

Hi Paula

I need to use PRU2.ETH1 only as PTP slave. Are you checking interfaces in dual mac mode? I need a dual mac mode. And, please, when you test it, connect a cable to PRU2.ETH1 port only (PTP slave must work with one connected cable only).

Paula Carrillo said:

I am using OOB demo.

What is the OOB demo?

Regards,
Alex

Hi Alex, thanks for your confirmation. One more thing, when you have a chance could you please share with me used configuration for PTPd as a master?. Currently, we use two boards for testing master-slave. A Linux machine would be better.

thank you and happy holidays,
Paula

Hello Paula

As I said in that post, I'm using that github gist config.

Copy of that config:

; /etc/ptpd.conf
; ==============================================================================
; This is a recommended configuration for a PTPv2 slave
; For a full list of options run ptpd2 -H or see the documentation and man pages
; ==============================================================================

; interface has to be specified (see with ifconfig)
ptpengine:interface=enp6s0

; PTP domain
ptpengine:domain=0
;ptpengine:domain=42

; available presets are slaveonly, masteronly and masterslave (full IEEE 1588 implementation)
ptpengine:preset=masteronly

; multicast for both sync and delay requests - use hybrid for unicast delay requests
ptpengine:ip_mode=multicast

; when enabled, instead of sockets, libpcap is used to receive (sniff) and send (inject) packets.
; on low latency hardware such as 10GE NICs this can provide results close to hardware-assisted PTP
ptpengine:use_libpcap=y

; go into panic mode for 10 minutes instead of resetting the clock
ptpengine:panic_mode=y
ptpengine:panic_mode_duration=10

; uncomment this to enable outlier filters
;ptpengine:sync_outlier_filter_enable=y
;ptpengine:delay_outlier_filter_enable=y

; store observed drift in a file
clock:drift_handling=file

; update online statistics every 5 seconds
;global:statistics_update_interval=30

; wait 5 statistics intervals for one-way delay to stabilise
;ptpengine:calibration_delay=5

; log file, event log only. if timing statistics are needed, see statistics_file
global:log_file=/var/log/ptpd2.log
; log file up to 5M
global:log_file_max_size=5000
; rotate logs up to 5 files
global:log_file_max_files=5

; status file providing an overview of ptpd's operation and statistics
global:log_status=y

; required if ip_mode is set to hybrid
;ptpengine:log_delayreq_interval=0

; uncomment this to log a timing log like in previous ptpd versions
; global:statistics_file=/var/log/ptpd2.stats

; Specify log level (only messages at this priority or higer will be logged).
; The minimal level is LOG_ERR. LOG_ALL enables debug output if compiled with
; RUNTIME_DEBUG.
; Options: LOG_ERR LOG_WARNING LOG_NOTICE LOG_INFO LOG_ALL
; global:log_level = LOG_ALL

; Maximum statistics log file size (in kB) - log file will be truncated
; if size exceeds the limit. 0 - no limit.
global:statistics_file_max_size = 1000

; on multi-core systems it is recommended to bind ptpd to a single core
global:cpuaffinity_cpucore=0

; use DSCP 46 for expedited forwarding over ipv4 networks
ptpengine:ip_dscp=46

; always keep a new line in the end

; Set ptpd transport
;   ipv4 => IPv4/UDP
;   ethernet => Raw ethernet
ptpengine:transport=ethernet
;ptpengine:transport=ipv4

; Delay detection mode used - use DELAY_DISABLED for syntonisation only
; (no full synchronisation).
; Options: E2E P2P DELAY_DISABLED
ptpengine:delay_mechanism=P2P

; ========= newline required in the end ==========

Regards
Alex

Alex, thank you!
Paula