2026-03-10 1:38 PM - last edited on 2026-03-11 1:02 AM by mƎALLEm
I have a simple question. Is it possible to use TouchGFX+ThreadX with enabled Ethernet and NETXDuo SNTP client at a same time in STM32N6570-DK board? In other words: take the TouchGFX ClockExample then in CUBEMX enable the Ethernet port with NETXDuo-SNTP server. Will it cause pin conflict? I mean the Ethernet uses the same pins as LTDC.
I enabled the Ethernet in ClockExample project and I got blank screen and the app was frozen. After removing Ethernet from the project, the analog and digital clocks appeared again on the display.
Thanks,
Louis
Solved! Go to Solution.
2026-03-25 7:19 AM
Hello,
As mentioned by @Osman SOYKURT, using RMII mode does not create pin conflicts between peripherals, and that is the mode that should be selected.
The reason you are getting a blank screen is most likely due to Ethernet buffers overlapping with TouchGFX's. To solve this, I suggest following an STM32N6 NetXDuo example from the repository. This will add the proper function calls and configurations needed to allocate data pools, create necessary threads, and initialize protocols. An example such as NX_MQTT_Client could help. Make sure that Ethernet descriptors and buffers do not overlap with the TGFX application.
Best regards,
2026-03-16 8:48 AM
Hello @Louie88 ,
I'm not a specialist with ETH and NETXDuo but when I try to enable those from STM32CubeMX with the N6 TBS that we provide (ThreadX version), I don't get conflicts (at least when I use RMII mode for ETH, which I believe is the correct setting? @STackPointer64 could you help?)
2026-03-24 7:53 AM
Hello @Louie88 , have you been able to resolve your issue?
2026-03-25 7:19 AM
Hello,
As mentioned by @Osman SOYKURT, using RMII mode does not create pin conflicts between peripherals, and that is the mode that should be selected.
The reason you are getting a blank screen is most likely due to Ethernet buffers overlapping with TouchGFX's. To solve this, I suggest following an STM32N6 NetXDuo example from the repository. This will add the proper function calls and configurations needed to allocate data pools, create necessary threads, and initialize protocols. An example such as NX_MQTT_Client could help. Make sure that Ethernet descriptors and buffers do not overlap with the TGFX application.
Best regards,