1 ACCEPTED SOLUTION
Accepted Solutions
I mean option bytes. They are flash registers but so are a lot of other things. Connect with STM32CubeProgrammer and click the OB icon. There are only a few relevant ones.
One more hint. I modified a simple blinky program that used the HAL drivers and worked on the Nucleo H7A3ZI-Q from my IDE, after pushing the reset button and after power cycling so it worked on my new custom board. And good news, it worked from the IDE, after reset and after power cycling. One big difference is the simple blinky program runs from the internal HSI and the System Clock is set up by HAL_Init(). My main app runs from the external HSE and LSE and the System Clock is set up by the CubeMX generated SystemClock_Config() function. I'm particularly suspicious of the 3 endless loops in the CubeMX code that check if the LSE, PLL1 and the SysClkSource are ready. I'm not sure why it would run out of the IDE but not after reset or power cycling but I'm looking into it.
/* Wait till LSE is ready */
while (LL_RCC_LSE_IsReady() != 1)
{}
__STATIC_INLINE uint32_t LL_RCC_LSE_IsReady(void)
{
return ((READ_BIT(RCC->BDCR, RCC_BDCR_LSERDY) == (RCC_BDCR_LSERDY)) ? 1UL : 0UL);
}
while (LL_RCC_PLL1_IsReady() != 1)
{}
__STATIC_INLINE uint32_t LL_RCC_PLL1_IsReady(void)
{
return ((READ_BIT(RCC->CR, RCC_CR_PLL1RDY) == (RCC_CR_PLL1RDY)) ? 1UL : 0UL);
}
while (LL_RCC_GetSysClkSource() != LL_RCC_SYS_CLKSOURCE_STATUS_PLL1)
{}
__STATIC_INLINE uint32_t LL_RCC_GetSysClkSource(void)
{
return (uint32_t)(READ_BIT(RCC->CFGR, RCC_CFGR_SWS));
}
And per @TDK I checked the Option bytes in CubeProgrammer and nothing looked wrong to me. Here's what I think it the most pertinent part. If there's something else I should be checking, please let me know.
And I compared all the option bytes for my main app running on my custom board and the option bytes for the blinky program running on the Nucleo board and they were identical.
@TDK I don't seem to be able to send you a PM. If you're willing, can you send me a PM? thanks
