• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 322 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.

The position of 'mem=54M' in the uboot setting lead to kernel boot fail

xiao jacky
Intellectual 315 points

First , my uboot setting is below:

but No more output is seen on the console after "booting the kernel".

and  I changed the position of 'mem=54' in my uboot setting as below:

the kernel  can boot .

why?

 

 

  • 0
    TI__Intellectual 2785 points

    Jacky,

        I recognize that you are using DM365, Correct me if i am wrong. Is there any SDK or DVSDK you are using with this platform, if so what version is that.

        one of the common problem faced is that the length of bootargs is limited in certain platforms. So last few parameters are discarded. I think this could be the reason. You can see during linux boot what it has actually accepted as kernel command line from bootargs.

    ===============================================================================================

    Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 13716
    Kernel command line: console=ttyS0,115200n8 root=/dev/mmcblk0p2 rw ip=off mem=54
    M video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0
    davinci_capture.device_type=4 vpfe_capture.cont_bufsize=6291456 davinci_enc_mngr
    .ch0_output=COMPONENT davinci_enc_mngr.ch0_mode=480P-60 rootwait
    PID hash table entries: 256 (order: -2, 1024 bytes)
    Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

    =============================================================================================

    Best Regards,

    Velan

  • 0 in reply to Velan
    Intellectual 315 points

    Velan,

    Thank you for  your reply. 

    Yes,  I'm using DM365 EVM,   The version of DVSDK is 4.02.

  • 0 in reply to xiao jacky
    TI__Intellectual 2785 points

    Jacky,

          In this case stick to bootargs generated during ./setup.sh as described in section "Setting up the DVSDK" in Software Developers Guide.

    Best Regards,

    Velan