• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 302 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM625: SDK9.0 UART count in defconfig

Tony Tang
Mastermind 28912 points
Part Number: AM625

In SDK9.0 defconfig the UART count set to 4, in SDK8.x, it is set to 10.Why do this kind of change? it result in customer who use >4 UART can't initialize successfully, waste time to identify.

[    1.274555] omap8250 2860000.serial: unable to register 8250 port
[    1.280669] omap8250 2860000.serial: PM domain pd:158 will not be powered off
[    1.287826] omap8250: probe of 2860000.serial failed with error -28

In SDK9, which file is the default Kernel configuration file? is it ti_arm64_prune_config? did not find CONFIG_SERIAL_8250_NR_UART in the file, how does it configured to 4 in default?

  • 0
    TI__Guru**** 167181 points

    Hi Tony,

    Until SDK8.6, the SDK provides a defconfig for the particular device. Since SDK9.0, the SDK doesn't customize kernel unless it is really necessary, so the device specific kernel defconfig is no longer provided. Then as you found out SERIAL_8250_NR_UARTS is no longer defined in the generic defconfig, and the default value '4', which is defined in drivers/tty/serial/8250/Kconfig, is used.

  • 0 in reply to Bin Liu
    TI__Mastermind 28912 points

    Hi, Bin,

    Thank you.

    SDK9.0 on line user guide is not updated also, almost same as that of SDK8.6, for example on how go build uboot, kernel section. 

    Is there a reason doesn't provide a deconfig like before?

    at least, the SERIAL_8250_NR_UARTS caused problem without that.

    And I don't understand the command of Makefile_linux, why there are two config file in the command.

    $(MAKE) -C $(LINUXKERNEL_INSTALL_DIR) ARCH=arm64 CROSS_COMPILE=$(CROSS_COMPILE) defconfig ti_arm64_prune.config

  • 0 in reply to Tony Tang
    TI__Guru**** 167181 points

    Hi Tony,

    Tony Tang said:

    Is there a reason doesn't provide a deconfig like before?

    Now the SDK uses the defconfig provided in community kernel.

    Tony Tang said:
    at least, the SERIAL_8250_NR_UARTS caused problem without that.

    I agree, this default '4' would cause problems on TI platforms. I will discuss this with our sw dev team.

    Tony Tang said:

    And I don't understand the command of Makefile_linux, why there are two config file in the command.

    $(MAKE) -C $(LINUXKERNEL_INSTALL_DIR) ARCH=arm64 CROSS_COMPILE=$(CROSS_COMPILE) defconfig ti_arm64_prune.config

    This is how the kernel defconfig is used - 'defconfig' is the community kernel provided defconfig. 'ti_arm64_prone.config' is to remove options not needed on TI K3 platforms.