Thanks Robert. But I do not quite follow it. You mean I should switch back my bootargs to ttyO0 while /etc/inittab should be ttyS0 ? While in omap2plus_defconfig case I had ttyO0 at both places(bootargs and inittab). Why this has to be this way ?
Regards nagla On Thursday, November 26, 2015 at 12:14:16 AM UTC+5:30, RobertCNelson wrote: > > On Wed, Nov 25, 2015 at 12:37 PM, gnu gnu <[email protected] > <javascript:>> wrote: > > okay... so I got it partially resolved. The board was booting earlier as > > well, but since console was not there, I thought its not booting at all. > > Error was that I forgot to make change in /etc/inittab from ttyO0 to > ttyS0. > > in addition to the bootargs > > > > So now I am able to get serial console. > > > > But I need to enable the bootup console logs. Can someone help how to do > it > > ? > > U-Boot# setenv bootargs root=/dev/nfs rw ip=192.168.0.100 > console=ttyO0 nfsroot=192.168.0.1:/home/xxx/nfsroot > > Well, if you want a serial boot log, you should add it: > > U-Boot# setenv bootargs console=ttyO0,115200n8 root=/dev/nfs rw > ip=192.168.0.100 console=ttyO0 nfsroot=192.168.0.1:/home/xxx/nfsroot > > > > > > I tried comparing .config of TI BSP and that of omap2plus_defconfig > > generated by vanilla kernel. > > Looks like TI BSP uses > > CONFIG_SERIAL_8250_OMAP=y > > CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=y > > > > while omap2plus_defconfig uses: > > > > CONFIG_SERIAL_OMAP=y > > CONFIG_SERIAL_OMAP_CONSOLE=y > > "CONFIG_SERIAL_OMAP" is on it's way out being replaced by > "CONFIG_SERIAL_8250_OMAP".. > > 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.
