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.

add dyndbg="QUERY" boot parameter using uEnv.txt



Hi,

I'm trying to change my bootargs adding

dyndbg="file tilcdc_drv.c +p" 

in my uEnv.txt.

Problem is that: 

" character write in uEnv.txt doesn't come to the kernel parameter, so my kernel bootargs became

dyndbg=file tilcdc_drv.c +p

and doesn't work.

How can I do?

  • What is the device?

    In Sitara AM335x 3.2 kernel, 'dyndbg' is not a valid bootargs param. For AM335x in SDK6.0 u-boot, you can refer to the following to enable early dynamic debug in uEnv.txt:

    optargs='ddebug_query="file ti81xx.c +p"'

  • I'm using Sitara AM335x 3.8.13 kernel.

    OK, now I understood that I have to use optargs, but when I try to enable verbose debugging for the tilcdc_drv, stil does not work.

    I use the following "optargs" argunment:

    optargs='ddebug_query="file tilcdc_drv.c +p"'

  • TI only supports Arago 3.2 kernel for AM335x, which does not have the file 'tilcdc_drv.c'.

    Here is the few things I would check.

    1. Review your tilcdc_drv.c to see if its debug messages use dynamic debug or not;

    2. unlikely to happen, but worth to check if your kernel has the env name changed from 'ddebug_query' to something else. In 3.2 kernel, I can see Line 541 in lib/dynamic_debug.c: __setup("ddebug_query=", ddebug_setup_query);

    3. check if your uboot supports optargs, if not, you have to directly add this option 'ddebug_query=...' into your bootargs;

    4. while debugging this issue, after modified the uboot env and booted the kernel, check if you have the following in /proc/cmdline. If not, you still don't have u-boot env setup correctly.

    ddebug_query="file tilcdc_drv.c +p"

  • Finally, I obtain to switch-on verbose debug on TILCDC driver.

    This driver inherit DRM_DEBUG macro from DRM layer, then:

    optargs='debug ignore_loglevel log_buf_len=64M drm.debug=7'

    Thanks for your help.