Linux/DRA745: How to enable debug print into u-boot?

Hello Yordan,

As you said, there is no "include/common.h" file in Processor SDK v03.04 which one we are using currently.

We have define "#define DEBUG" in below files: (as per this Link: processors.wiki.ti.com/.../Early_Boot_and_Late_Attach_in_Linux
board/ti/dra7xx/lateattach.c.
common/elf_remoteproc.c
common/spl/spl.c

With above changes, still we are not getting debug() print messages.

Could you please tell us where to change to get those debug() print messages?

Thanks,
Chetan

Hi Chetan,

I have pinged an expert to provide further help.

Regards,
Yordan

DRA7xx_SD_Boot_Log.txtHello Shravan,

Please find my inline comments:

The file 'include/common.h' is present in the u-boot repository even for PSDK-LA 3.04. As indicated by Yordan adding the line #define DEBUG

should enable all debug prints.

>>> Yes we tried this. And logs comes on UART console.

The debug prints aren't displayed until serial_init() method is called. This method is called in common/spl/spl.c.

>>> Yes, you are right. The logs display after serial initialization. But we are trying to debug code before serial

   initialization. e.g. In the file "arch/arm/cpu/armv7/omap-common/clocks-common.c", the API setup_dplls(), includes

   debug("setup_dplls\n"); prints. As per our understanding this debug prints will not display on console before

   serial initalization. We verified in debug log prints. (Please find attached log for your reference)

Note: We have verified with the help of emulator that setup_dplls() get invoked during MLO execution.

So, we want to know how to get those debug prints.

Thanks,

Chetan

Hi Chetan,

Are you using single or two stage boot? The logs aren't printed unless the 'setup_dplls()' call happens from SPL since UART isn't initialized. Alson, early UART init isn't validated.

You can redirect the logs to a global array and access these logs by connecting a debugger.

Regards

Shravan