LP-AM261: Enet Lwip TCP Client Example not working?

Hi Paul,

1. Is your AM261x an E1 revision launchpad or E2 revision launchpad? You can find the label on the board near the J6/J8 Boosterpack headers (from the logs I assume it is E1 board)

2. What is the Ethernet-connector label on which you have connected your Add-on-board for ethernet?

For e.g, if it is E1 AM261x launchpad , the MAC Port-0 is mapped to the Ethernet Connector-2 and MAC Port-1 is mapped to the Ethernet Connector-1. If your example uses MAC Port-0, then make sure you have the add-on ethernet phy board connected to the Ethernet Connector-2.

3. Is this an out-of-box application, or are there any modifications made to the applicaiton/syscfg? Also, do you use RGMII or MII or RMII?

Regards,
Shaunak

Hi Shaunak,

1) Near J6/J8, it's labeled "PROC193E2 (001)".

2) The port is labeled "Ethernet Connector 1", but I also tried the other one.

3) I didn't change anything, I just built and flashed the application in CCStudio.

Regards,
Paul

Hi Paul,

I see some mismatch here. The application logs check the board rev and print it out as "E1"

Paul Höhn said:

Assuming Board Version as E1

Paul Höhn said:

1) Near J6/J8, it's labeled "PROC193E2 (001)".

This can occur if the EEPROM is wrongly written since that is how the board revision is checked.

Do you have any other Launchpads or can you let me know if any changes were made to the EEPROM?

Regards,
Shaunak

Unfortunately, this is the only LaunchPad we have at the moment. I’m trying to determine whether the EEPROM contents have been modified. Is there a way to reprogram the EEPROM?

Regards,
Paul

I double checked, and the launchpad is brand new.

In the debugger I temporarily set:

• boardVer[0] = 'E'

• boardVer[1] = '2'

and everything works now. However, the EEPROM itself still isn’t programmed.

Is there a supported way to permanently program the EEPROM with the correct board revision so it’s detected as E2? If so, could you point me to the recommended tool/script?

Thanks and regards,
Paul

Hi Paul,

Yes you can write the EEPROM using EEPROM APIs, but i'm not exactly aware of ALL the content that is supposed to be in EEPROM, let me check with some hardware experts and get back. We do have EEPROM related APIs in the SDK at mcu_plus_sdk/source/board/eeprom/ that can be used.

Regards,
Shaunak

Hi Paul,

I recommend getting a EEPROM dump using a I2C application. (https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/latest/exports/docs/api_guide_am261x/EXAMPLES_DRIVERS_I2C_READ_V1.html)

For now, if the "E1/E2" marking is only an issue, we can bypass that check in the ethernet application, but if other data is also corrupt/missing in EEPROM (for e.g. the MAC Address), then that might cause system failures later.

The i2c_read application reads some EEPROM Bytes, you can modify this application and get a whole EEPROM dump, or use the direct EEPROM_read APIs from the EEPROM.c file in the SDK.

Regards,
Shaunak

Is there maybe documentation how the EEPROM should look like?