TMDSCNCD263: AM2634 - required changes from Ethernet Ipv4 to Ipv6 update.

Hari krishna Kaki

Intellectual 355 points

Part Number: TMDSCNCD263

Hello Team,

I have tested EthApp demo from MCAL and it is based on Ipv4.

Now i would like to update Ethernet version from Ipv4 to Ipv6.

Could you please let me know, things to be considered regarding the update.

Or could you please provide a EthDemo on Ipv6 version.

Kind regards,

Hari

over 1 year ago

0 Shaunak Deshpande over 1 year ago

TI__Genius 16622 points

Hi Hari Krishna Kaki,

Let me check internally and get back to you by tomorrow.

Regards,

Shaunak

0 Shaunak Deshpande over 1 year ago

TI__Genius 16622 points

Hi Hari,

I tested using the sample ethapp example in the MCAL SDK.

I was able to send out IPv6 packets by only changing the FrameType from 0x8000 to 0x86DD (IPv6). (Change in mcal/examples/Eth/EthApp.c)

Attaching the wireshark snippet as well:

You can try the same on your end.

Thanks & Regards,

Shaunak

0 Hari krishna Kaki over 1 year ago in reply to Shaunak Deshpande

Intellectual 355 points

Hi Shaunak,

Thank you, I will try it.

I think with MAC base transmission, it will work.

when it comes to IP address base transmission?

Kind regards,

Hari

0 Shaunak Deshpande over 1 year ago in reply to Hari krishna Kaki

TI__Genius 16622 points

Hi Hari,

I will check and come back on this.

Regards,

Shaunak

0 Shaunak Deshpande over 1 year ago in reply to Shaunak Deshpande

TI__Genius 16622 points

Hi Hari,

Were you able to test IPv6 on your end? Since MCAL does not have any upper layer TCP/IP stack, I can't test IP based transmission on my end.

Regards,
Shaunak

0 Hari krishna Kaki over 1 year ago in reply to Shaunak Deshpande

Intellectual 355 points

Hi Shaunak,

I have tested it, and it is working similar as expected.

Q) Do we have to change any parameters in Eth or EthTrcv module regarding Ipv6 than Ipv4?

0 Shaunak Deshpande over 1 year ago in reply to Hari krishna Kaki

TI__Genius 16622 points

Hi Hari,

I had a look and from Eth or EthTrcv I don't see anything specific needed. the Ethernet packet is composed by the application, the driver doesn't mess with the L2 payload, only with the L2 header. So, your L2 payload can be IPv6 packet or something else, it's transparent to the driver.

You can try it on your end and in case something fails, please create a new E2E thread for the same.

Regards,

Shaunak

Arm-based microcontrollers

Arm-based microcontrollers forum

TMDSCNCD263: AM2634 - required changes from Ethernet Ipv4 to Ipv6 update.