Despite actually getting the Ethernet running, I am still stumped with the same stability issues. A template, compiled using the directives described in my previous post (sans the LWIP_NETIF_API and LWIP_NETIF_LINK_CALLBACK options), crashed after about 6-7 hours of working. I'm attaching the entire project for inspection, if someone wants to take a crack at it. The linker file is STM32H743ZI_FLASH.ld (it was modified according to the STM32Cube_FW_H7_V1.3.0 examples) and the MPU_Config() was copied from the FAQ ( https://community.st.com/s/article/FAQ-Ethernet-not-working-on-STM32H7x3 ). All the project option can be inspected in the STM32CubeMX project file (*.ioc). I would also appreciate if @Joerg Wagner could share his MWE. I would actually be able to check the differences between the two. Cheers!
Did you mean 16 kB for RX buffers starting at 0x30040200?
And one more interesting thing.. why we need to protect the 16kB block starting at 0x30044000? I'm just copypasted the config of this block from the LwIP_HTTP_Server_Netconn_RTOS. I can't find any code using this block of RAM.
It would be nice to have the DHCP capabilities though. I think that I can revamp my project for a static network for the time being. I will try to create a local network and run some test on it. It would be a shame if DHCP is buggy. I might try some tests on older series (F7) just to see how they cope with DHCP.
It seems that your code is somewhat similar (apart from the missing MPU code block, as indicated by Joerg).
I think that I might stick with RTOS for a while (even though I am not a huge fan of it). A couple of processes in my project will benefit from running in threads (even though RTOS and HAL are the usual culprits that hinder device performance).
