Other Parts Discussed in Thread: SYSCONFIG
Tool/software:
Hello
I am using the AM64x MCU+ SDK (version 09.02.01) to implement the ICSSG LWIP TCP ECHO SERVER and facing multiple issues that appear to be discrepancies between the actual behavior and the SDK documentation. These issues persist across both static and dynamic IP configurations.
SDK Version: 09.02.01
ICSSG LWIP TCP ECHO SERVER
Core Issues
1. Assertion Failure in Both Configurations: Regardless of using static or DHCP IP configuration, I encounter an assertion error:
```
Assertion @ Line: 111 in /nightlybuilds/mcupsdk_internal/jenkins/mcu_plus_sdk_am64x_09_02_01_05/source/networking/enet/core/src/core/enet_queue.c: node != NULL
```
2. Documentation vs. Actual Behavior:
- The example code documentation states that out-of-the-box, the code should operate in "Switch mode," yet the Sysconfig indicates it's set to "Dual MAC mode."
- The log outputs from the example do not match the expected outputs as per the SDK documentation, particularly concerning network initialization and IP address assignment.
3. Difficulty Switching from DHCP to Static IP:
- The documentation instructs to disable DHCP and AUTOIP by removing `dhcp_start` and `autoip_start` calls. However, I am unable to locate these calls in the codebase, making it impossible to follow the prescribed steps for setting up a static IP.
1. How can I resolve the assertion error that occurs in both the static and dynamic IP configurations? Are there known bugs or patches for this issue?
2. Can you clarify the operational mode discrepancy? Why does the Sysconfig indicate "Dual MAC mode" when the documentation states "Switch mode" should be default?
3. Where exactly should I look to find and remove the `dhcp_start` and `autoip_start` calls within the ICSSG LWIP TCP ECHO SERVER example or related files in the SDK?
4. Are there additional steps or corrections in the documentation regarding setting up a static IP that I should be aware of?
