Greg, Ok, I used the menuconfig system to set the serial console to UART1, 57600 baud rate.
The system boots, hits the nsh_main breakpoint, I can continue to fputs, and then if I continue, then break, the system stops in the idle loop. So it seems like it's running, but the serial console isn't working, at least on the DEBUG port. If I boot into Linux, I can get a console login on the DEBUG port at 115200 baud. When I boot NuttX, I don't get any response from the serial terminal. I can see I'm transmitting because the lights on my FTDI console blink. The SAMA5D27 pinout definitely says that UTXD1 is UART1; and that's what the embedded debugger is connected to... so I'm confused. Any more ideas? cheers adam On Thu, Dec 26, 2019 at 4:52 PM Adam Feuer <a...@starcat.io> wrote: > Greg, > > Thanks, I'll try this. Sorry about the two emails with the same question, > after I sent the first question, I thought the subject line and question > might have been unclear. > > -adam > > On Thu, Dec 26, 2019 at 4:37 PM Gregory Nutt <spudan...@gmail.com> wrote: > >> >> > In the menuconfig system I looked for a way to get an NSH prompt on >> UART2,but didn't find it. Is there a way to do that? If so, how? >> >> The standard NSH output goes to /dev/console. For serial devices that >> is controlled by the setting: >> >> CONFIG_SERIAL_UARTn_CONSOLE=y >> >> this is in the drivers/serial configuration menu. In that schematic, I >> see that the connection to the CDC/ACM VCOM is vis DBGU_UXTD1_PD3 and >> DBGU_URXD1_PD2. So 'n' must be one in the above. >> >> I also notice that the default BAUD is 57600 which is unusual. That >> means you will also need: >> >> CONFIG_SERIAL_UART_BAUD=57600 >> >> > Or can I put an NSH prompt on a USB interface? >> >> Yes, but that is a lot more complex. >> >> Greg >> > > > -- > Adam Feuer <a...@starcat.io> > -- Adam Feuer <a...@starcat.io>
