• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 144 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: How to hide U-Boot log from console

Paul Minh
Intellectual 605 points
Part Number: AM625


Tool/software:

Hello TI, 

WE are using Yocto SDK 9.0

Below is power log on console and the most of upper part of the log are u-boot.

We want to hide (not to show) those log on console in order to speed up boot time.

May you guide how to suppress those u-boot log in uboot source code? Thanks.

WE try below but not work:

 git diff include/configs/am62x_evm.h

+#define CONFIG_SILENT_CONSOLE
+#define CONFIG_SYS_DEVICE_NULLDEV
+#define CONFIG_SILENT_CONSOLE_UPDATE_ON_RELOC
+#define CONFIG_SILENT_CONSOLE_UPDATE_ON_SET

or 

git diff board/ti/am62x/am62x.env

+silent=1

  • 0
    TI__Guru**** 170071 points

    Hi Paul,

    The log you provided seems to be printed in u-boot.img, is it correct?

    From another E2E thread last week, I thought your project eventually will use falcon boot. If so, u-boot.img won't be in the boot flow, why do you still need to hide the u-boot.img log?

  • 0 in reply to Bin Liu
    Intellectual 605 points

    Hello Bin Liu,

    The attached log output seems from somewhere, but before kernel starts. (fyi, by now we only modify kernel for our custom board.) 

    We will proceed with two paths: one version for the final product using Falcon, and another for production line usage. The production line version will still require U-Boot for testing and verification functions—both software and hardware—as well as for meeting other testing requirements.

  • 0 in reply to Paul Minh
    TI__Guru**** 170071 points

    Hi Paul,

    I can understand the final product using falcon boot has boot time requirement, but why would you disable all the U-Boot boot log in production line? would it give you diagnosis problem if the production line ran into any problem but the console did not print much log information?