A reset caused by BOR causes all but six words of EEPROM to erase to 0x00000000. A software reset with "NVIC_SystemReset();" is OK. EEPROM contents are retained, as expected.
Posted on October 31, 2017 at 19:18I'm using STM32CubeMX to generate code for a custom STM32L051R8T6 project. SysTick functions as expected when HAL drivers are selected. SysTick does not work if LL drivers are selected. Is there a reason why STM...
Posted on September 29, 2017 at 00:23I used STM32CubeMX to generate code for a STM32L051R8xx microcomputer. All I/O ports initialize correctly except PH1. If I delete the PH1 initialization code, the program executes correctly. With the PH1 code ...
I found the problem. There was a subtle timing issue with the "losing power" firmware and the startup firmware following a reset. (The product has a super-cap to allow the microcomputer to generate audio and visual "loss of AC power" alarms.)
Posted on November 02, 2017 at 15:07SysTick is working when 'void SysTick_Handler(void)' is executed once every millisecond. The HAL driver code automatically enables execution of the SysTick_Handler function. The LL driver code does not execute t...
Posted on September 29, 2017 at 17:35It was a hardware problem! Removed solder short between PH1 pin and NRST pin and now the code executes as expected.Jim R.
Posted on September 29, 2017 at 04:04Thanks Clive One! I just realized that PH1 (pin 6) is physically next to the NRST (pin 7) signal. It looks like there is a very small solder bridge between the two pins. I will remove the solder bridge and rep...
Posted on September 29, 2017 at 03:16Yes, it is a custom board with no external crystals. I'm using the IAR ARM KickStart compiler and ST-Link tool.Jim R.
