debugging M4 in STM32H7 Dual Core
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-04-20 07:41 AM
Hello,
I'm currently working with a STM32H757XI EVAL board, STM32CubeIDE 1.3.1 toolchain.
I'm following AN5361 but without success.
I tried different things like replacing
/* Wait until CPU2 boots and enters in stop mode or timeout*/
// timeout = 0xFFFF;
// while((__HAL_RCC_GET_FLAG(RCC_FLAG_D2CKRDY) != RESET) && (timeout-- > 0));
// if ( timeout < 0 )
// {
// Error_Handler();
// }
while(__HAL_RCC_GET_FLAG(RCC_FLAG_D2CKRDY) != RESET)
{
asm("nop");
}
as described here.
Debug session for M7 goes fine, but when I try to connect to the M4, the ST links gdb server reports that the device can't be identified.
I think there is an underlying issue there: I have some code blinking LED1 from M7 and LED2 from M4 but I think the M7 gets stuck is waiting for n RCC_FLAG_D2CKRDY.
What situation can make the M4 not to rise the flag RCC_FLAG_D2CKRDY?
Do you have experience on that?
Another information: When I program the M4 using STM32Programmer I can see the LED2 blinking, but when I reset the board, it's not working anymore. So I suspect the bootup process or some OB? are wrong.
I used the examples from ST so it would be great if you give me a hand.
Thanks.
- Labels:
-
DEBUG
-
STM32H7 Series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-09 03:08 AM
I have encountered the same issue on STM32H747I-DISCO board. Have you managed to solve this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-09 03:11 AM
Have a look at here see if it helps: https://github.com/STMicroelectronics/STM32CubeH7/issues/34
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-09 09:30 PM
Thanks for the link! I followed instructions mentioned on that page, but was not able to resolve the issue. But, the link you provided helped me in much deeper understanding of the issue. Thanks.