Heya guys, following up from my question yesterday about using fliplink and memory.x files, I have found that smoltcp network task doesn't seem to work if I run from DTCMRAM, but it works fine if I run from AXISRAM. This is on an STM32H7. It gets to the point where it starts the network task and applies the config (DHCP in this instance but also doesnt work with a static IP), but it never returns from that. If I disconnect and reconnect my ethernet cable, I see messages from defmt showing the link up or down, so eveything is still running.

Simply changing the linker scrip from using DTCMRAM as the `RAM` alias to AXISRAM and it works straight away.

I am just running one of the examples from the embassy repo, and with 128k of space for stack in DTCMRAM, I don't think I am running into stack overflows (also I'd expect a Hard fault due to the way its configured).

Has anyone seen this before? Is this to do with specific memory regions allowed by the ethernet peripheral or something?