Matias, Thanks for the help. It was an incorrect master clock setting for the board. I updated the Giant Board clock settings, and while I still can't fully boot NuttX, but I am getting some logging lines and stack traces on the serial port now. No garbage. :)
-adam On Wed, Aug 19, 2020 at 10:41 PM Adam Feuer <a...@starcat.io> wrote: > Matias, > > Thanks, I have a logic analyzer and will try that when I pick it up again. > The weird thing about this is that I can use U-Boot on the serial console > on the Giant Board – it knows how to use the UART correctly. But NuttX > doesn't. > > Ah, that might be it– the two boards run at different frequencies. I am > trying to use a nuttx.bin compiled for the SAMA5-XULT. I will check out the > clock configuration and make one specifically for the Giant Board and its > frequency. > > -adam > > On Wed, Aug 19, 2020 at 10:32 PM Matias N. <mat...@imap.cc> wrote: > >> When I had this problem of the serial giving garbage I used a logic >> analyzer with pulseview and then try to hunt for a baud rate on the uart >> protocol decoder which would give a valid interpretation. Often I found the >> rate to be a multiple of the expected one which helped me figure out what >> was set incorrectly. >> >> But yeah, without real debugging it will be painful to use. >> >> Best, >> Matias >> > > > -- > Adam Feuer <a...@starcat.io> > -- Adam Feuer <a...@starcat.io>
