How to use LWIP demo app for MPC5748G from RTM1.0.0 into S32DS PA RTM 3.0.0

[hims8111]

Hello,

I have been able to establish TCP/IP communication from MPC5748G GW board (DoIP) to other device via ethernet port. However, demo application that I used is from RTM1.0.0 for S32 Design studio 2017. I would like to use it in S32DS PA1.2 with RTM3.0.0. I think there is a huge repository difference but I am not sure whether is it possible to use or not. Could you please guide if its possible? In case, there are any demo apps for LWIP in RTM3.0.0 using MPC5748G, it will be helpful.

Thanks

[lukaszadrapa]

Hi,

it's always highly recommended to use the latest RTM version. There are two demo applications:

c:\NXP\S32DS_Power_v2.1\S32DS\software\S32_SDK_S32PA_RTM_3.0.3\examples\MPC5748G\demo_apps\lwip\

and

c:\NXP\S32DS_Power_v2.1\S32DS\software\S32_SDK_S32PA_RTM_3.0.3\examples\MPC5748G\demo_apps\usb_cdc_lwip\

Description can be found in the user manual:

c:\NXP\S32DS_Power_v2.1\S32DS\software\S32_SDK_S32PA_RTM_3.0.3\doc\S32SDK_MPC5748G_UserManual.pdf

See sections:

14.3.7 lwIP TCP/IP stack

14.3.12 USB CDC LWIP MPC5748G

Notice that you need device with HSM firmware for the first example (it's also mentioned in the manual). HSM firmware is not present in standard devices, you need to explicitly request it at your local sales office if needed.

Regards,

Lukas

[hims8111]

Hi Thanks for your reply. I have tried the examples from the RTM3.0.3 as you suggested. For the First example, I disabled SSL (wolf SSL) as no requirement of HSM at the moment. However, TCP IP SOCKET API application gets stuck during lwip_connect(s, (struct sockaddr*)&addr, sizeof(addr)) in socket_example_test. Please find the attached image where it gets stuck. 

I am using local NXP board static ip : 10.10.7.15 (Subnet 255.255.0.0) GW10.10.7.1 as my other device running server on same subnet (with ip 10.10.7.10)

I am using NXP's MPC5748G-GW board (not DEVKIT). However, I have modified the pinMUX configuration, middleware patch as suggested in earlier release for target board ENET1 requirement. (using DoIP port)

Could you please help me with above mentioned issue? Please find attached image pointing the location where it gets stuck and doesn't come out. I am not sure whether its middleware issue or configuration issue.

Thanks in advance.

[lukaszadrapa]

Hi,

there is a clue that is related to lock_tcpip_core mutex used in LOCK_TCPIP_CORE() function.

Please check how that mutex is used in the application.

Regards,

Lukas