[OE-core] How do I configure OpenBMC kernel boot logs to be displayed on a specific UART?

[Basil Varghese]

Hi,
I am using OpenBMC-1.0 (phosphor).
On an AST2500-based board, the boot-logs get stuck at
*           Uncompressing Linux… done, booting the kernel.*

The u-boot uses the correct UART console because its logs are displayed.
But after that, the kernel boot logs are not seen. I am sure it is booting,
but the problem is that the kernel seems to be configured to use the wrong
serial console.
I tried changing the *'device' *variable in obmc-console.conf from
*device=ttyS5 * to different values, but it's no use.
Could someone please suggest how to make the kernel boot logs be displayed
on the correct UART?

------------------------------------------- FYI the boot logs:
 -----------------------------------------

DRAM Init-V0B-DDR4
0abc1-4Gb-Done
Read margin-DL:0.3509/DH:0.3803 CK (min:0.35)


U-Boot 2016.05 (Jul 06 2016 - 17:22:40 +0100)

DRAM:  496 MiB
Flash: 32 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   MAC0 : RGMII
MAC1 : RGMII
FTGMAC100#0
Error: FTGMAC100#0 address not set.
, FTGMAC100#1
Error: FTGMAC100#1 address not set.

Hit any key to stop autoboot:  0
## Booting kernel from Legacy Image at 20080000 ...
   Image Name:   Phosphor OpenBMC (Phosphor OpenB
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2004098 Bytes = 1.9 MiB
   Load Address: 80001000
   Entry Point:  80001000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 20300000 ...
   Image Name:   obmc-phosphor-image
   Image Type:   ARM Linux RAMDisk Image (lzma compressed)
   Data Size:    1670931 Bytes = 1.6 MiB
   Load Address: 81000000
   Entry Point:  81000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
-------------------------------------------------------------------------------------------------------

Thanks,
*Basil Varghese*
*______________________________________*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160707/d3eaf5bd/attachment-0002.html>