The appropriate thing to do would be to check reset signal using an oscilloscope but i don't have one here.
Anyway, I simply wanted to ask if by any chance this could be due to some oversight related to how the non-optimized build could affect this, based on someone else experience with the same problem. But I guess it is pretty specific. Thanks, Matias On Sun, Jun 21, 2020, at 18:31, Adam Feuer wrote: > Do you have GPIO available? If so you can do the equivalent of printf > debugging by using GPIO... for instance outputting a binary number using 5 > GPIOs would give you 32 possible points to mark your code with. Or just use > unary and change a different GPIO for every point you want to mark. > > -adam > > > > On Sun, Jun 21, 2020 at 2:23 PM Matias N. <mat...@imap.cc> wrote: > > > I have the serial console enabled, but this is very early in the boot. > > > > On Sun, Jun 21, 2020, at 18:02, Adam Feuer wrote: > > > (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> > > > > > > > > -- > Adam Feuer <a...@starcat.io> >
