I had been using the pinguino toolchain earlier, but nothing was happening, hence my switching of compilers to see if anything worked.
With the other compilers, I only got one LED lit up, and at least according to the MPLABX debugger we were stuck in mm_addregion. Using the pinguino toolchain, 2 LEDs now light up, and the debugger at least thinks that we're in the up_idle function, so that looks promising. After switching the serial console to UART2(for the explorer16), I do now get data out of the serial port! The last message that I see is "nx_start: CPU0: Beginning Idle Loop". Nothing else is happening though - I was expecting to get some kind of shell, as USER_ENTRYPOINT is set to "nsh_main". Are there some other options that need to be set to switch nsh to use the correct UART? -Robert Middleton On Sun, Feb 21, 2021 at 11:18 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > >> * What can I do to debug early boot problems? > > You can at first try enabling debug output. (make menuconfig --> > > Build Setup --> Debug Options --> Enable Debug Features). You should > > have some information regarding what's going on. Another option is to > > enable DEBUG_SYMBOLS and debug the startup code. > > A breakpoint on up_assert should catch any early crashes as you > describe. There is a cool debug tip here if you hit the breakpoint: > *https://nuttx.events/wp-content/uploads/2019/11/DSidrane_nx2019.pdf* > >
