Dear
1. The original project was developed based on S32DS3.5 + RTD5.0.0, Build OK & Run OK
2. Development requires basic RTD 6.0.0. Development environment: S32DS 3.6.2 + RTD 6.0.0 + TCPIP_STACK_3.0.0 + FreeRTOS_11.1.0_6.0.0
3. RTD5.0.0 and RTD6.0.0 have significant differences, so projects based on the original RTD5.0.0 cannot be used. Instead, refer to the example code provided in the forum ( Example: S32K388 GMAC0 lwIP FreeRTOS S32DS 3.6.1 RTD600 ).
4. Modify the corresponding PIN according to your hardware platform as follows:
5. Debugging the example code revealed that some initialization steps failed, as follows:
6. If the corresponding code is masked, the program can run, but the PHY address cannot be found.
The attached file contains a debug example. I'm not sure if the reference example provided on the forum has been modified, or if I only modified the PIN definition, or if there's some other configuration error.
Hi, Petrs
Hello, you are absolutely right.
I am indeed using my own hardware platform. During RTD 5.0.0 debugging, I was able
to ping successfully using the example code provided on the official website. When using RTD 6.0.0 in person, I followed the same approach, mainly changing the PIN and discovering the code.The program failed to run. The attached file is based on my own hardware RTD 5.0.0 (S32DS3.5 + RTD 5.0.0 + TCPIP_STACK_2.0.0) and can ping.
The example code is OK, but I'm not sure if the clock configuration is incorrect. Could you please provide some assistance?
Hi,
It seems you only changed the MDIO/MDC pins compared to the community example you referred to.
Does this mean you are using your own custom-designed board?
I tested your project on the S32K388EVB-Q289, and the MCU initialization completed successfully.
The PHY address was not detected because the MDIO/MDC signals are connected to different pins on the EVB. After changing the MDIO/MDC pins to PTD16/PTD17, the PHY address was correctly obtained.
BR, Petr