ohhh yes.... ,115200n8 did the trick. I every time missed it because the older driver CONFIG_SERIAL_OMAP worked just with console=ttyO0. Looks default baud is not 115200n8 in CONFIG_SERIAL_8250_OMAP. However, other TI driver CONFIG_SERIAL_OMAP seem to have default set to 115200n8.
Thanks for help. Last question to complele this post: In case of CONFIG_DEBUG_LL which config option should I use out of below for BBB: CONFIG_DEBUG_OMAP2UART1 DEBUG_AM33XXUART1 CONFIG_DEBUG_LL_UART_8250 Cheers Nagla On Thursday, November 26, 2015 at 1:10:41 AM UTC+5:30, RobertCNelson wrote: > > On Wed, Nov 25, 2015 at 1:34 PM, gnu gnu <[email protected] <javascript:>> > wrote: > > I guess I have already tried out this yesterday, with no bootup logs > printed > > on console. Although at later stage after logging into buildroot, I can > use > > dmesg. > > > > Below was the bootargs, I tried: > > > > setenv bootargs root=/dev/nfs rw ip=192.168.0.100 console=ttyS0 > > nfsroot=192.168.0.1:/home/xxx/nfsroot > > add the baud rate: (don't remember what it's default is) > ,115200n8 > > > > > I've triggered a build to recheck it. > > > > BTW, I'm on a slow machine(almost biblical era... 1GB ram) and a single > > change starts 1 hr of module building. Which I do not use anyway :-( > > Is there anyway I can avoid and just build the kernel. A small defconfig > > like omap2plus_defconfig. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
