STM32N657X0H3Q: NetXDuo Ethernet Some Drivers Files Not Generated for UDP Server.

[SITARAM]

Hello,

I'm working with the STM32N657X0H3Q MCU and trying to implement a UDP server . I enabled the Ethernet peripheral and selected NetXDuo in STM32CubeMX(6.14.1), then generated the code for MDK-ARM (Keil). However, two important driver files were not generated:

• nx_stm32_phy_driver.c
• nx_stm32_eth_driver.c

I noticed that in your example here:
"https://github.com/STMicroelectronics/STM32CubeN6/tree/main/Projects/NUCLEO-N657X0-Q/Applications/NetXDuo/Nx_UDP_Echo_Server"
the two files mentioned above are included, but this example does not contain a .ioc file, so I couldn't verify how they were configured.

To troubleshoot, I looked for another example with a similar configuration and found the STM32H5 series UDP example here:
"https://github.com/STMicroelectronics/STM32CubeH5/tree/main/Projects/NUCLEO-H563ZI/Applications/NetXDuo/Nx_UDP_Echo_Server"

This H5 example includes a .ioc file, and I observed that under NetXDuo > Network Interface, we can select:

1. Ethernet Interface.
2. LAN8742 PHY Driver.

But in STM32N6 (STM32CubeN6 package), the only option available is a "Custom Interface". I'm wondering if this is the reason why nx_stm32_phy_driver.c  and  nx_stm32_eth_driver.c are not being generated in my case.

My Questions:

• Is the limited option (only "Custom Interface") in STM32N6 the reason these two  files are not being generated?
• If yes, what is the correct way to generate or integrate them?
• If not, what is the actual reason, and how can I resolve the issue?

Also, could you please provide the .ioc files for both UDP Server and UDP Client examples for STM32N6 ? That would help clarify the necessary configuration.

Thanks in advance!

[Mahmoud Ben Romdhane]

Hello @SITARAM ,

First let me thank you for posting and welcome to the ST Community.

Your request is under investigation, and I will get back to you ASAP.

Thanks.

Mahmoud

[SITARAM]

hii   Mr.@Mahmoud Ben Romdhane .

    Thank you for responding and looking into my issue.

• I would also like to report another problem I’ve encountered: under sys_s / sys_ns in CubeMX, I’m unable to select any timer for the Timebase Source   —  neither SysTick nor None are selectable.  Even if i enabled the ThreadX and Ethernet, and some more Peripherals.

If this issue is resolved, could you please inform me as well? It is critical for us to track when and how the issue was fixed. I also believe this update will be valuable for many other users in the ST Community who might face the same problem.

Thank you again for your support.

[Mahmoud Ben Romdhane · Accepted solution]

Hello @SITARAM ,

The same topic was discussed in this Post.  An internal ticket 208214 has been submitted to the dedicated team for fix.

For the second question and in order to enable the Time base source in the secure context as TIM1, you should activate it in the same context.

I will be waiting for your feedback.

Thanks.

Mahmoud