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.
Hi,
I'm using the mcu_plus_sdk_am243x_08_05_00_24 SDK with AM243-LP board. I was trying out the Enet CPSW TimeSync PTP Demo based on the steps mentioned in this page.
But the UART output seems to be different than expected, am attaching the output below:
Starting NULL Bootloader ... DMSC Firmware Version 8.5.3--v08.05.03 (Chill Capybar DMSC Firmware revision 0x8 DMSC ABI revision 3.1 INFO: Bootloader_runCpu:155: CPU r5f1-0 is initialized to 800000000 Hz !!! INFO: Bootloader_runCpu:155: CPU r5f1-1 is initialized to 800000000 Hz !!! INFO: Bootloader_runCpu:155: CPU m4f0-0 is initialized to 400000000 Hz !!! INFO: Bootloader_loadSelfCpu:207: CPU r5f0-0 is initialized to 800000000 Hz !!! INFO: Bootloader_loadSelfCpu:207: CPU r5f0-1 is initialized to 800000000 Hz !!! INFO: Bootloader_runSelfCpu:217: All done, reseting self ... ========================== L2 Multi-channel Test ========================== Init all peripheral clocks ---------------------------------------------- Enabling clocks! Create RX tasks ---------------------------------------------- cpsw-3g: Create RX task Open all peripherals ---------------------------------------------- cpsw-3g: Open enet Init all configs ---------------------------------------------- cpsw-3g: init config Mdio_open: MDIO Manual_Mode enabled cpsw-3g: Open port 1 EnetPhy_bindDriver: PHY 3: OUI:080028 Model:0f Ver:01 <-> 'dp83869' : OK PHY 3 is alive PHY 15 is alive Attach core id 1 on all peripherals ---------------------------------------------- cpsw-3g: Attach core cpsw-3g: Open DMA initQs() freePktInfoQ initialized with 16 pkts initQs() freePktInfoQ initialized with 16 pkts cpsw-3g: Waiting for link up... Cpsw_handleLinkUp: Port 1: Link up: 1-Gbps Full-Duplex MAC Port 1: link up cpsw-3g: MAC port addr: f4:84:4c:fb:c1:45 TimeSync PTP enabled Enet Multi-channel Menu: 'c' - GetCurrentTime 't' - Toggle Printing timestamps 's' - Print statistics 'r' - Reset statistics 'm' - Show allocated MAC addresses 'p' - Enable Policer for rate limiting 'x' - Stop the test Doing first adjustment CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024) CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024, as 0 is less than minimum value (1024)
In the expected output the `CpswCpts_ioctl_handler_ENET_TIMESYNC_IOCTL_ADJUST_TIMESTAMP: Setting PPM to 1024` message seem to appear a few times and then the demo should run, Im not sure why its repeated continously afterwards.
Broadcaster is a Linux PC (linuxptp) with NIC as Ethernet Connection (17) I219-LM
Thanks
Hello Tony Josi,
We have added industry grade gPTP 802.1AS standard stack in our 9.0 SDK and we have a dedicated example for this https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EXAMPLES_ENET_CPSW_TSN_GPTP.html. I request you to please use this latest 9.0 SDK instead. The PTP demo in 8.5 SDK, as part of the multi-channel example, is just for reference and will be removed in our upcoming SDKs.
We are working on providing a production grade standard TSN stack starting from our 9.0 SDK. We have further improvements and features planned for the gPTP stack on top of 9.0 SDK in our upcoming releases. So, it is recommended to use the latest gPTP stack.
Regards
Susheel