AM2612: PN demo flash issue

Hi Holger,

Can you please help with the SDK version being used here?

Regards,
Shaunak

they use 2026.00.00.06

-Holger

Hi Nilabh,
how does customer get a Rev A board? If I order on ti.com I will get rev E2.

Regards, Holger

Hi Nilabh,

they received the Rev A board. However, it seem still be facing the same problem where the launchpad is not responding to the Proneta scan: 

This is what he did:

1. Imported a new instance of the Profinet Device Demo from the SDK and built it
2. Set the Launchpad to OSPI boot mode and flashed the images using the method described in AM261-SOM-EVM: Am261x LP: Profinet device demo issues. - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums'
3. Power cycled the board after flashing

This is the UART output from the Launchpad.

He can also see the green LED blinking on the connected PHY of the launchpad.

Is there perhaps some network configuration he has to do on windows? He is using the free version of Proneta.

Regards, Holger

Hello Holger,

would you please share the following:

1. ind_comms_sdk version
2. mcu_plus_sdk version
3. UART output
4. Wireshark trace of the message exchange between AM261x_LP and PRONETA

Kind regards,
Kamil

Hi Kamil,
here's the information:
Ind_comms_sdk version: 2026_00_00_06_eval
Mcu_plus_sdk version: 26_00_00_06

I have attached the UART output and wireshark traces.

Regards, Holger

<\r>
<\n>
Starting OSPI Bootloader ... <\r>
<\n>
KPI_DATA: [BOOTLOADER_PROFILE] CPU Clock        : 500.000 MHz <\r>
<\n>
KPI_DATA: [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH <\r>
<\n>
KPI_DATA: [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz <\r>
<\n>
KPI_DATA: [BOOTLOADER_PROFILE] Boot Image Size  : 178 KB <\r>
<\n>
KPI_DATA: [BOOTLOADER_PROFILE] Cores present    : <\r>
<\n>
r5f0-0<\r>
<\n>
KPI_DATA: [BOOTLOADER PROFILE] System_init                      :        404us <\r>
<\n>
KPI_DATA: [BOOTLOADER PROFILE] Drivers_open                     :         93us <\r>
<\n>
KPI_DATA: [BOOTLOADER PROFILE] LoadHsmRtFw                      :       6298us <\r>
<\n>
KPI_DATA: [BOOTLOADER PROFILE] Board_driversOpen                :       5091us <\r>
<\n>
KPI_DATA: [BOOTLOADER PROFILE] CPU load                         :      14756us <\r>
<\n>
KPI_DATA: [BOOTLOADER PROFILE] SBL End                          :          5us <\r>
<\n>
KPI_DATA: [BOOTLOADER_PROFILE] SBL Total Time Taken             :      26649us <\r>
<\n>
<\r>
<\n>
Image loading done, switching to application ...<\r>
<\n>
IO-Device V4.4.0.0, ID: 376a2fe9, SDK Variant:Standard
<\n>
<\r>Restore remanent memory indicated.<\r>
<\n>
Using user-defined submodule configuration (not from remanent memory).<\r>
<\n>
Restore remanent memory indicated.<\r>
<\n>
Restore remanent memory indicated.<\r>
<\n>
Restore remanent memory indicated.<\r>
<\n>
Restore remanent memory indicated.<\r>
<\n>
Restore remanent memory indicated.<\r>
<\n>
<\r>[APP] INFO: Initializing PRU instance ...
<\n>
DP83869 detected<\r>
<\n>
DP83869 detected<\r>
<\n>
PRU_PHY_detect:152 Phy 3 alive<\r>
<\n>
PRU_PHY_detect:152 Phy 12 alive<\r>
<\n>
Phy 3 : Disable RGMII mode<\r>
<\n>
Phy 3 : Disable GBit ANEG<\r>
<\n>
Phy 12 : Disable RGMII mode<\r>
<\n>
Phy 12 : Disable GBit ANEG<\r>
<\n>
Module/submodule successfully plugged into slot 0, subslot 1<\r>
<\n>
Module/submodule successfully plugged into slot 0, subslot 2<\r>
<\n>
Module/submodule successfully plugged into slot 0, subslot 3<\r>
<\n>
Module/submodule successfully plugged into slot 0, subslot 4<\r>
<\n>
Module/submodule successfully plugged into slot 1, subslot 1<\r>
<\n>
Module/submodule successfully plugged into slot 1, subslot 2<\r>
<\n>
Module/submodule successfully plugged into slot 1, subslot 3<\r>
<\n>
Restore remanent memory indicated.<\r>
<\n>

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/908/lp_2D00_am261-wireshark-trace.pcapng

Hi Holger,

the UART log shows that the device is working normally. Yet Wireshark traces show nothing from the device. 

1. Is there any difference between your setup and our out-of-the-box experience? Anything modified from the default hardware/software?
2. Would you please try to use sbl_ospi_multicore_elf.release.tiimage from Mcu_plus_sdk version: 26_00_00_03 instead of Mcu_plus_sdk version: 26_00_00_06?

Kind regards,
Kamil

Hi Kamil,
no nothing modified. He flashed it with a freshly imported example. Is it possible for a firewall to block the traffic from the launchpad?

Where can can the 26_00_00_03 be found? It does not seem to be on the website: www.ti.com/.../MCU-PLUS-SDK-AM261X
Only 26.00.00.06. is on the web.

Regards, Holger

Hi Holger,

You may find it here: https://github.com/TexasInstruments/mcu_plus_sdk_am261x/releases/tag/REL.MCUSDK.26.00.00.03

Do you have other non-TI PROFINET devices to test with? I just want to make sure that the problem isn't in your PC. 

Kind regards,
Kamil

Hi Kamil,

they did a bit more testing, and noticed that there was an additional burst of traffic on the line when the board was powered on (it's the only device connected to the port). 

Some of the packets have source address 0.0.0.0, which guess should be from the Launchpad. Maybe this is related to the issue of it not working?

In addition, the board also does not work on a separate non-corporate PC, indicating this should not be a PC issue

Regards, Holger

Hello Holger,

I don't think this message is coming from our device. I actually don't see any traffic coming from our device or PRONETA.
Would you please ask the customer to set a static IP for the PC interface, make sure the correct network interface is selected in PRONETA and capture a new trace starting from device switch on?

I will be on vacation starting from Monday so if the customer responded quickly we can hopefully manage to close this issue today.

Kind regards,
Kamil