(printf debugging only works if you can get far enough through the boot sequence to initialize a serial console. But that can happen pretty early.)
On Sun, Jun 21, 2020 at 2:01 PM Adam Feuer <a...@starcat.io> wrote: > Do you have a serial console available? If so, you could use printf > debugging <https://www.cs.colostate.edu/~fsieker/misc/debug/DEBUG.html> > to determine where in the boot sequence it fails. I've done this with NuttX > successfully on the SAMA5. > > -adam > > On Sun, Jun 21, 2020 at 12:13 PM Matias N. <mat...@imap.cc> wrote: > >> I've been having a very weird problem and I thought to ask if anyone else >> suffered this by any chance. I have a board with reset line with pull-up >> and a switch to tie the line to ground (with a capacitor in parallel) as >> per typical STM32 circuit. This line also is exposed to the SWD connector. >> When I build without size optimizations, the board works as expected: it >> comes up normally and can be reset with the button. SWD also is able to >> reset it for debugging. When I disable optimizations, the board does not >> boot again even when pressing the reset button. It only boots normally if I >> start debugging with OCD, which issues the reset from there. Since with the >> debugger it boots normally this is impossible to debug. >> Any similar experience? >> >> Best, >> Matias > > > > -- > Adam Feuer <a...@starcat.io> > -- Adam Feuer <a...@starcat.io>
