MCU-PLUS-SDK-AM263PX: Getting AM263P4-CC to work with icss_emac_lwip example

Huey Duong

Part Number: MCU-PLUS-SDK-AM263PX
Other Parts Discussed in Thread: TMDSCNCD263P, SYSCONFIG

Tool/software:

Trying to get this example project to work but couldn't get the link up. Posting this question to see if I can get more answers quicker than reverse engineering the example.

Eval board: TMDSCNCD263P PROC159E2.

SDK: MCU+ SDK for AM263Px - 9.2.0.55

Example project: icss_emac_lwip_am263px-lp_r5fss0-0_freertos_ti-arm-clang

Can you help point me in the right direction on the following questions:

1) Is there any README html file to provide information on what this project does, expected outputs, hw setup

2) Is there an example for the -cc eval board?

3) Can you confirm the example uses PRU0 MII0 connected to the PHY (ie. Config #2) and that there is no change needed on the board?

4) SW changes. Please confirm these are correct and if more is needed.

a) Changed sysconfig to switch package from ZCZ_C to ZCZ_S

b) Updated Predefined Symbols from AM263PX_LP to AM263PX_CC

c) Updated lwipcfg.h to

#define USE_DHCP 1
#define USE_AUTOIP 1

5) SBL NULL programmed to flash and BOOT mode set to OSPI.

Debugging the example yielded this:

MII mode
load to PRU0 passed
load to PRU1 passed
Starting lwIP, local interface IP is dhcp-enabled
[LWIPIF_LWIP]Link is down[LWIPIF_LWIP] Interface layer handle is Initialised
[LWIPIF_LWIP] NETIF INIT SUCCESS
status_callback==UP, local interface IP is 0.0.0.0
UDP server listening on port 5001
6. 25s : CPU load = 0.79 %

Ethernet cable connected to router. RJ45 LEDs: Link is off, Activity is blinking.

Any help would be appreciated.

7 months ago

0 Huey Duong 7 months ago

Prodigy 125 points

Some updates. Found some info I was looking for, but examples still does not work.

1) solved. Found the documentation in SDK/Documents/User Guide instead of in the usual folder where the example project is.

2) Found the cc version by browsing to SDK folder. Importing project from Resource Explorer automatically downloads -lp version. No option to select -cc

3) Please confirm, no hardware change is needed on CC board

4) Since the example uses cc, i didn't make any modification to the code.

I've directly connected the EVM to PC using patch cable and configured network for 192.168.0.50/24.

Link LED is still off, but pulling the cable in and out causes TI to say link_callback==UP/DOWN.

Still the ping does not work. Any suggestions on what else I could be missing? Thanks.

INFO: Bootloader_socLoadHsmRtFw:82: Device Type : HSFS

[HSM_CLIENT] New Client Registered with Client Id = 0
INFO: Bootloader_socLoadHsmRtFw:84: HSMRT Size in Bytes : 23875
INFO: Bootloader_socLoadHsmRtFw:97: hsm runtime firmware load complete ...
Starting NULL Bootloader ...
INFO: Bootloader_runCpu:155: CPU r5f1-1 is initialized to 400000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU r5f1-0 is initialized to 400000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU r5f0-1 is initialized to 400000000 Hz !!!
[BOOTLOADER_PROFILE] Boot Media : undefined
[BOOTLOADER_PROFILE] Boot Image Size : 0 KB
[BOOTLOADER_PROFILE] Cores present :
[BOOTLOADER PROFILE] System_init : 70us
[BOOTLOADER PROFILE] Drivers_open : 40us
[BOOTLOADER PROFILE] LoadHsmRtFw : 31939us
[BOOTLOADER_PROFILE] SBL Total Time Taken : 56130us

NULL Bootloader Execution Complete...
INFO: Bootloader_loadSelfCpu:207: CPU r5f0-0 is initialized to 400000000 Hz !!!
INFO: Bootloader_runSelfCpu:217: All done, reseting self ...

MII mode
load to PRU0 passed
load to PRU1 passed
Starting lwIP, local interface IP is 192.168.0.200
[LWIPIF_LWIP]Link is Up on port 1
[LWIPIF_LWIP] Interface layer handle is Initialised
[LWIPIF_LWIP] NETIF INIT SUCCESS
status_callback==UP, local interface IP is 192.168.0.200
UDP server listening on port 5001
link_callback==UP
6. 36s : CPU load = 0.68 %
11. 36s : CPU load = 0.56 %
16. 36s : CPU load = 0.56 %
21. 36s : CPU load = 0.56 %

PS C:\Users\hd> ipconfig

Windows IP Configuration

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::3770:4112:9187:c87e%14
IPv4 Address. . . . . . . . . . . : 192.168.0.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

PS C:\Users\hd> ping 192.168.0.200

Pinging 192.168.0.200 with 32 bytes of data:
Request timed out.
Request timed out.

Ping statistics for 192.168.0.200:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),

+1 Nilabh Anand 7 months ago in reply to Huey Duong

TI__Mastermind 35292 points

Hi Huey,

Apologies you had to face this issue. This is one of the issues we discovered after SDK 9.2 release and we are already fixing it for next release. It happened because of the wrong initialization sequence of the PHY which went unnoticed during our internal test(we took action to update that)

Now for the fix please replace the original "test_icss.c" with the attached file at: MCU_PLUS_SDK_INSTALL_PATH/examples/networking/lwip/icss_emac_lwip/test_icss.c."

/cfs-file/__key/communityserver-discussions-components-files/908/2311.test_5F00_icss.c