topic Re: S32K344 + Marvel 88Q6113 Initialize and communicate in S32K

S32K344 + Marvel 88Q6113 Initialize and communicate

caesar_song — Fri, 09 Jun 2023 09:45:00 GMT

I am the DFAE of avnet,out key customers Weichai used S32K344 design a gateway for their car ,

S32K344 + Marvel 88Q6113 ,bud in the initialize they met the question as attachment ,pls help

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

lukaszadrapa — Tue, 13 Jun 2023 08:00:19 GMT

Hi @caesar_song

could you tell me which versions of the following SW are used:

S32 Design Studio

RTD package

FreeRTOS package

TCPIP package

Was the original lwip example running?

Regards,

Lukas

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

LiekLi — Wed, 14 Jun 2023 03:01:01 GMT

Hi Carsar,

The log you attached is very little, it is just Jlink download log. There is no code running log.

From your word, you can check rx_er pin, you did not use it. please check PTC14 or PTC16.

For the StartSchduler(), it is FreeRTOS OS start call, the code should doer not go over it, you see it is handling, but usually the task is running. Please break, and see if the code is running, or check the OS task exectuion. You can also use PC to ping the MCU.

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

yilei — Fri, 16 Jun 2023 02:21:44 GMT

I'm going to check the rx_er pin；
I have used PC to ping S32 while the program is running，but it didn't work。
thank you

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

yilei — Fri, 16 Jun 2023 02:37:39 GMT

S32 Design Studio:S32DS.3.4;
RTD package:2.00
FreeRTOS:SW32K3_FreeRTOS_10_4_6_UOS_2_0_0_DS_updatesite_D2204
TCPIP package:D2205
Was the original lwip example running?: yes

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

LiekLi — Mon, 19 Jun 2023 02:36:46 GMT

Hi yilei,

I just searched, Marvel 88Q6113 is switch, not phy. The two chips are on mac to mac mode, there could be some differences.

Please try this code, it is mac to mac and verified with NXP switch SJA1110. Don't forget to change the pinmux and ip address.

Regards,

Liek

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

yilei — Wed, 21 Jun 2023 02:08:09 GMT

I have run the program you mentioned on the MCU, and at the same time, I also used the pc to ping the mcu, but the ping failed

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

yilei — Thu, 29 Jun 2023 07:08:42 GMT

In mac mode of Marvel 88Q6113 switch, there is no clock output, so we configure switch to phy mode, which can output clock to mcu. At this point we run the S32K3_T_BOX_LWIP_for_S32K3 program, and after initialization, we stop at the position （void）sys_sem_wait(&init_sem)。

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

caesar_song — Thu, 06 Jul 2023 00:54:43 GMT

Hi Good moring

Would you help to check we have a customer with this successful use case? S32K344 + Marvel 88Q6113 ,This project is still pending in this state, do you have any better suggestions? thanks.

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

LiekLi — Thu, 06 Jul 2023 02:55:36 GMT

Hi Yilei,

For mac to mac mode, the 50Mhz clock must be provided by Marvel 88Q6113.

If you can choose Marvel 88Q6113 to work in PHY mode, you can also try official lwip demo.

I saw you stop at the position （void）sys_sem_wait(&init_sem), this means the init is not succeed. The semephore 'init_sem' is post in callbacks as test_init() in tcpip_init(test_init, (void*)&init_sem) --> tcpip_thread(). You can further debug the init code to find the root cause.

Regards,

Liek

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

yilei — Tue, 11 Jul 2023 01:20:45 GMT

Hi，LiekLi

First of all, thank you very much for your patience in answering my questions

We tested the Marvel 88Q6113 PHY mode to communicate with the S32K344. In lwip, the phy mode of the switch will initialize the program, but there will be many problems later, for example, the program will run and stop in a certain place.

Have you ever tried to communicate the mcu mac with the switch phy before? If so, what needs to be changed in lwip's example program, if not complicated, can help me？

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

LiekLi — Tue, 11 Jul 2023 02:51:58 GMT

Yilei,

The code I post here, it is for mac to mac. I verified it on NXP EVB, it can work with SJA1110 which is NXP switch. This code does not include the initPhy function, so you can see it is commented.

For NXP official code, it works with NXP phy TJA110x. If you use mac to phy mode, you should use this one. I did not test MCU mac with switch phy. But for all the Phy, the basic function is standard. You can first check the initPhy to see if it can work on Marvel phy.

I suggest you to compare the code I post here with NXP official lwip demo, to check the difference of Config Tool and code. Your board is difference with EVB, you can also check BSP like pinmux\clock.

Regards,

Liek

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

yilei — Thu, 13 Jul 2023 07:34:15 GMT

Hi，LiekLI

I'm sorry, maybe I didn't describe it clearly before. We virtualized the phy using the maverl switch, and then tested Ethernet communication with the S32k344's mac. I couldn't communicate with an mcu mac from a maverl switch because my switch couldn't output a clock in mac mode.

Based on my current hardware architecture, if I want to use the code you post, what do I need to change? Can I uncomment this line of code that initPhy？

Re: S32K344 + Marvel 88Q6113 Initialize and communicate

LiekLi — Thu, 20 Jul 2023 07:27:09 GMT

Yilei,

No matter it is mac to mac or mac to phy, S32K344 always need 50Mhz clock input. If mavel switch cannot output the clock, the system cannot work.

So bases on the current HW, to provide the clock, marvell switch must run on Phy mode. The initPhy() cannot be commented. You can see it is used to config the phy reg. Most reg is standard which means all the phy is the same. I suggest you read the doc of Marvel switch to check how to work on phy mode.