This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

about omapl138 sdk linux-2.6.37-psp03.21.00.04.sdk serial console can not put message

Other Parts Discussed in Thread: OMAPL138

Now I use this sdk to boot, but the console can not show anything, This sdk use da850 evm, I found the serial only call "davinci_serial_init" function in arch/arm/mach-davinci/serial.c, but don't  call "early_serial_setup" function,  is there a problem?

  • Hi user4529167,
    Which board are you using ?
    LogicPD EVM or LCDK board or custom board ?

    You can see some serial driver initialization in board-da850-evm.c file.
  • register_console(&serial8250_console) in driver/serail/8250.c -->serial8250_console_setup, based on 'co->index' to get uart_port, then check 'port->iobase' and 'port->membase', but 'port->membase' is null, it only can be evaluated 'early_serial_setup' api. I have scaned the source code in sdk, but can not find evaluate omapl138 uart port to 'serial8250_ports[UART_NR]' array
  • Yes, I see the source code in board-da850-evm.c, it only init serial(such as interrupt, clk and so on), but can't find the code associated with the console
  • Hi user4529167,
    I never heard such issues.

    I presume that you are using custom board with different UART console.
    In EVM board, UART2 is used.

    I'm able to get UART output on OMAPL138 LogicPD EVM with this SDK linux kernel.


    Yes, I see the source code in board-da850-evm.c, it only init serial(such as interrupt, clk and so on), but can't find the code associated with the console

    No, you can find the "da850_evm_console_init" function for the UART2 console.

  • Now I had boot the kernel, the uart can not output because the console init is after unpacking rootfs. My rootfs is unpack failed. Thanks.

  • Hi user4529167,
    Can you please attach the linux boot log ?

    Where is your filesystem stored ?
    NAND flash or NFS or SD card or any other media ?

    Please make sure that you have used bootargs correcly.

    u-boot's bootargs for NFS boot:
    setenv bootargs mem=32M console=/dev/ttyS2,115200 ip=dhcp nfsroot=192.168.2.29:/usr/local/filesystem_omapl138 root=/dev/nfs rw rootwait