TMS570LC4357: EMAC cannot receive the data

Yale Li 李耀先

Part Number: TMS570LC4357
Other Parts Discussed in Thread: TMS570LS3137

Hi Team,

My customer‘s device cannot receive the data during debug EMAC module. Receive interrupt have been registered and enabled when view VIM module.

Wanna know what reason could cause this issue?

Thanks & Regards

Yale Li

over 2 years ago

0 jagadish gundavarapu over 2 years ago

TI__Guru 71501 points

Hi Yale,

Is it possible to share a customer code?

And customer can also have a look on Active webserver examples of hercules

Thanks & Regards,
Jagadish.

0 Yale Li 李耀先 over 2 years ago in reply to jagadish gundavarapu

TI__Expert 4660 points

Hi Jagadish,

I transmitted it by private message. Pls take a look.

Thanks & Regards

Yale

0 jagadish gundavarapu over 2 years ago in reply to Yale Li 李耀先

TI__Guru 71501 points

Thanks for sharing the code Yale.

I will verify and update you.

Thanks & Regards,
Jagadish.

0 Yale Li 李耀先 over 2 years ago in reply to jagadish gundavarapu

TI__Expert 4660 points

Thanks Jagadish.

And some supplementary note from the customer:

These code are migrated from TMS570LS3137. He use EMAC module on TMS570LS3137, and use UDP to communicate. It works normally.

But after migration, EMAC module only can transmit data and cannot receive any data by using Wireshark to capture packets to check.

He doesn't use LWIP protocol stack.

Thanks & Regards

Yale

0 jagadish gundavarapu over 2 years ago in reply to Yale Li 李耀先

TI__Guru 71501 points

Hi Yale,

Can you please ask customer to make sure below things,

1. You need to select the MDIO signals in pinmux window manually. Check MII doesn't select MDIO.

2. In MPU setting, please use cache write-through

Thanks & Regards,
Jagadish.

+1 Yale Li 李耀先 over 2 years ago in reply to jagadish gundavarapu

TI__Expert 4660 points

Hi Jagadish,

Feedback from the customer:

1. Already select the MDIO signals in pinmux window:

2. The EMAC module still cannot receive data after using cache write-through:

_mpuInit_();
_mpuSetRegionTypeAndPermission_(MPU_NORMAL_OIWTNOWA_SHARED,MPU_PRIV_RW_USER_RW_EXEC);
_cacheEnable_();
__TI_auto_init();

main();
exit();

Also, there is a strange problem. The customer has two version code.

One version doesn't use LWIP protocol stack. This version cannot receive EMAC data.

Another version use the initialize function of LWIP protocol stack after use the initialize function of EMAC(EMACInit). There is no other difference. And this version can receive EMAC data.

Thanks & Regards

Yale

0 Yale Li 李耀先 over 2 years ago in reply to Yale Li 李耀先

TI__Expert 4660 points

Hi Jagadish,

I share the whole project from the customer by private message.

Receive interrupt cannot response.

Could you please take a look of it?

Thanks & Regards

Yale

0 jagadish gundavarapu over 2 years ago in reply to Yale Li 李耀先

TI__Guru 71501 points

Hi Yale,

Yale Li 李耀先 said:
Could you please take a look of it?

Sure, i will do.

And i would like to know, which board customer using is it a custom board or any TI specific board he is using?

Thanks & regards,
Jagadish.

0 Yale Li 李耀先 over 2 years ago in reply to jagadish gundavarapu

TI__Expert 4660 points

Hi Jagadish,

Thanks.

jagadish gundavarapu said:
And i would like to know, which board customer using is it a custom board or any TI specific board he is using?

Custom board, but referenced TI's board.

Thanks & Regards

Yale

+1 jagadish gundavarapu over 2 years ago in reply to Yale Li 李耀先

TI__Guru 71501 points

Hi Yale,

Yale Li 李耀先 said:
Another version use the initialize function of LWIP protocol stack after use the initialize function of EMAC(EMACInit). There is no other difference. And this version can receive EMAC data

This API Initializes the EMAC and EMAC Control modules. The EMAC Control module is reset, the CPPI RAM is cleared. also, all the interrupts are disabled. This API does not enable any interrupt or operation of the EMAC.

Arm-based microcontrollers

Arm-based microcontrollers forum

TMS570LC4357: EMAC cannot receive the data