I recently upgraded to 1.5.1 and it seems I am now unable to look at the ram memory anymore for some mysterious reason . Eg I wanted to check the stacks of my freertos tasks but the memory shows up as all ???????? from 0x200003F0 onwards (between 0x2000000 and 0x200003F0 it seems to be ok). I am doing this on an STM32F745ZGTX, it should have 320kb internal memory from 0x2000000 till 0x20050000 so I am definitely in the valid memory range (and my tasks work so their stacks are in valid memory) . I did this before on 1.5.0 or 1.4.0 and don't remember having problems with it, so I am not sure what is going wrong, coincidence or something in 1.5.1 ? Picture below, am I doing something wrong here ?
I also just noticed that from 0x200006f0 the memory is populated normally again (not sure if there are other gaps). And as far as I can see there are no "reading *** bytes @ address xxxxx" statements in the console panel for the problematic region so it is like the memory viewer does not even try to read the memory in that block, and just prints the ? marks everywhere.
The same gap exists in the memory browser tool as well btw
Faced the same problem with
STM32CubeIDE on MacOS
Version: 1.13.1
Build: 17479_20230728_0839 (UTC)
Board: STM32F407G-DISC1
