2022-03-07 11:26 AM
problem:
2022-03-07 11:36 AM
Suggests it is reading 0xFFFFFFFF from one of the vector tables, as you've written FLASH section for one of the cores, and not the other.
Other tools merge the M4 .HEX into the M7 .HEX before writing the combined image.
2022-03-07 11:39 AM
hi Tesla,
thank you for replay, i where can i find the option to write FLASH selection for the second core?
i have been struggling with this problem for 2 weeks.
2022-03-07 11:49 AM
#define VECT_TAB_OFFSET 0x00000000UL /*!< Vector Table base offset field.
This value must be a multiple of 0x300. */
is it this one?
2022-03-07 11:57 AM
i even tried using only single core but still the problem comes back
2022-03-07 02:31 PM
In Keil the some project builds in two halves, you Build the M4, Download/Flash it
Built the M7 side, Download and Debug
Perhaps there are some video, tutorials or manuals for CubeIDE
Perhaps look at STM32H745I-DISCO board level examples. Project structure, meta-data settings, etc.
2022-03-11 04:27 AM
Hi,
Have a look at this app note on how to setup a project for STM32H7 dual-core debug:
I think this is a good first step, it covers also how to load both elf-files in one debug configuration.
Then, let's see if your own configuration in MX actually impacts the behavior.