In the board's board.h there are some defines that affect how the sysclk is setup. If e.g. the PLL params are off you'll see an issue like this. It should also be possible to singlestep through the very first arch init steps and see if it's taking a wrong turn somewhere.
On Wed, Oct 6, 2021 at 8:27 PM Nuno Barcellos <nunobarcel...@gmail.com> wrote: > Hi! > > I'm new to nuttx and have been trying to get it working for the first time > on a NUCLEO-L4A6ZG board. I couldn't get the nsh working at first but after > measuring a gpio + sleep signal, I found out that the clock is running 20x > slower than it should be (a sleep(1) takes 20 secs). > Then, if I configure the nsh to use an usart at a baudrate of 115200, I can > read it externally with 115200/20 = 5760. > I used the nsh config for the NUCLEO-L496ZG which has about the same > microcontroller. > I'm guessing that it is a clock misconfig given that other demos run 20x > slower as well. Where/how can I modify the clock configuration? > > Cheers >
