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.

Compilation Not taken place

Hi Experts,

I am new bee to Linux based compilation and had downloaded the SDK package 7.0 for AM335x linux.

Consider the folder is installed  in /home/user/ti_sdk_7/


I tried to modify the code in  /home/user/ti_sdk_7/board_support/linux_3.12_src/

Then i compile it with make command "make all" from the path /home/user/ti_sdk_7/

Then i updated the generated zImage file from /home/user/ti_sdk_7/board_support/linux_3.12_src/arch/arm/boot/zImage into the sdcard's boot partition.


But the changes doesn't takes place in the actual target validation. What could be the reason ?

Also I changed few configurations in /home/user/ti_sdk_7/arch/arm/configs/ti_am335x***.config file and compiled. That also not taken effect.

  • The zImage should be placed in the SD card's rootfs partition under the /boot folder, not in the SD card's boot partition.

    Best regards,
    Miroslav

  • Hi Miroslav,

    The path /rootfs/ contains as follows

    MLO (shortcut)

    u-boot.img (shorcut)

    uImage (shortcut)

    MLO-am335x-evmxxx

    u-boot-am335x-xxx.img

    uImage-3.2.0

    vmlinux-3.2.0

    Which of the above file need to be replaced ?

    What is the diff between zImage and uImage ?

    Regards,

    Lyf

  • lyf sci said:
    The path /rootfs/ contains as follows

    Do you mean the /boot folder under the "rootfs" SD card partition?

    This is what I have by default, when using Sitara SDK v7:

    root@am335x-evm:~# ls -la /boot/
    drwxr-sr-x    2 root     root          4096 Jul 18  2014 .
    drwxr-sr-x   20 root     root          4096 Jul 30  2014 ..
    lrwxrwxrwx    1 root     root            34 Mar 31 02:34 _am335x-evmsk.dtb -> devicetree-zImage-am335x-evmsk.dtb
    lrwxrwxrwx    1 root     root            27 Mar 31 02:34 _zImage -> zImage-3.12.10-ti2013.12.01
    lrwxrwxrwx    1 root     root            33 Mar 31 02:34 am335x-bone.dtb -> devicetree-zImage-am335x-bone.dtb
    lrwxrwxrwx    1 root     root            38 Mar 31 02:34 am335x-boneblack.dtb -> devicetree-zImage-am335x-boneblack.dtb
    lrwxrwxrwx    1 root     root            32 Mar 31 02:34 am335x-evm.dtb -> devicetree-zImage-am335x-evm.dtb
    -rw-r--r--    1 root     root         38060 Jul 18  2014 am335x-evmsk.dtb
    -rw-r--r--    1 root     root         33206 Mar 31 01:58 devicetree-zImage-am335x-bone.dtb
    -rw-r--r--    1 root     root         34352 Mar 31 01:58 devicetree-zImage-am335x-boneblack.dtb
    -rw-r--r--    1 root     root         41564 Mar 31 01:58 devicetree-zImage-am335x-evm.dtb
    -rw-r--r--    1 root     root         38048 Mar 31 01:58 devicetree-zImage-am335x-evmsk.dtb
    -rw-r--r--    1 root     root     107236262 Mar 31 01:56 vmlinux-3.12.10-ti2013.12.01
    -rwxr-xr-x    1 root     root       4117880 Aug  5  2014 zImage
    -rw-r--r--    1 root     root       4117616 Mar 31 01:56 zImage-3.12.10-ti2013.12.01

    Regarding the difference between uImage and zImage:

    zImage is a regular kernel compressed image, which doesn't have a header with included load address, so the load address has to be provided using the bootz command. This means that the zImage can be loaded anywhere.

    uImage is a kernel with a modified header for the U-Boot bootloader, which includes a U-Boot header which contains the load address that the kernel should be loaded to. This makes this entire kernel specific to that load address.

    Best regards,
    Miroslav

  • Hi Miroslav,


    Thanks for the reply.


    Yeah as you said you chose the package /sdk_7_install_dir/filesystem/arago-base-tisdk-image-am335x-evm whereas I chose /sdk_7_install_dir/filesystem/tisdk-rootfs-image-am335x-evm.tar.gz

    Well is it ok that I replace the

    -rw-r--r--    1 root     root       4117616 Mar 31 01:56 zImage-3.12.10-ti2013.12.01

    with zImage generated in the arch/arm/boot/zImage  ?

     

    Regards

    Lyf

  • Yes.

    Best regards,
    Miroslav