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.

How to select Flash boot on K2X EVM?

Hi

I am using a XTCIEVMK2X board and MCSDK 3.0.4.18. I have set the dip switches for ARM SPI boot and the board is booting from TFTP.  How should I modify the U-boot bootcmd script to select Flash boot?

Currently, the bootcmd script is:

boot=ramfs

bootcmd=run init_${boot} get_fdt_${boot} get_mon_${boot} get_kern_${boot} run_mon run_kern

BR

David

  • Hi David,

    David said:
    How should I modify the U-boot bootcmd script to select Flash boot?

    Using setenv and printenv, you can change and view the command scripts on environmental variables. For SPI booting, you can try like below:-

    K2HK EVM # setenv bootcmd 'run ${burn_uboot}'

    K2HK EVM # saveenv

    Use printenv to see the list of varaibles and it's expansion.

     K2HK EVM #printenv burn_uboot

    Regards,

    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • Hi

    There seems to be something wrong with E2E at the moment. I am getting notification emails at odd times and, for this thread, I am getting notifications about answers that I can't see in the browser, eg for Shankari's reply.

    David

  • Hi Shankari

    After I wrote my last post, your reply appeared. E2E seems to be behaving oddly at the moment.

    I understand how to use setenv. What I want to understand is the meaning of the predefined U-boot scripts such as init_ramfs.

    BR

    David

  • Hi David,

    In your first post you asked for a SPI boot. That's why I have given setting the env for burning uboot into SPI flash.

    K2HK EVM # setenv bootcmd 'run ${burn_uboot}'

    When you expand the "burn_uboot", you will get like below.  

    2HK EVM # printenv burn_uboot
    burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}

    For example, when we want to know about the pre-defined U-boot Scripts, we have to expand and see like below to understand the meaning of them ( init_ramfs, args_all e.t.c).

    K2HK EVM # printenv init_ramfs
    init_ramfs=run set_fs_none args_all args_ramfs get_fs_ramfs
    K2HK EVM # printenv set_fs_none
    set_fs_none=setenv addr_uinitrd -
    K2HK EVM # printenv args_all
    args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1

     

    ( Note: Whenever you get a reply to your post, you will immediately get email notification to yourmailbox irrespective of time. By the time, you looked into the post, actually I had deleted and reposted my reply. Hope this clarifies that the E2E doesnot have any problem!.)

    Regards,

    Shankari.

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------