• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 500 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.

Boot Images location..

Vijaykumar Ponugoti
Intellectual 550 points

Hi,

I am working on DRA7xx and GLSDK7.00. I am a newbie and have some basic queries on boot image files locations and linking filesystem with kernel.

1. I used GLSDK6.10 earlier. When I do ./mksdboot.sh on that SDK it used to create uboot, bootscript, kernal, dtb files in boot partition and file system on rootfs partition of sd card. But When I am using GLSDK7.00 it is creating only uboot,MLO, and uenv.txt files in boot partition and kernel image and dtb files in boot folder of the filesystem on rootfs partition. What is the difference? why they changed the location of kernel image.?

2. And I used to experiment by changing some code in kernel and copy them boot partition in GLSDK6.10 and it was working. But when I do the same thing on glsdk7.00 and copy the newly built images in boot folder of fs, it is getting stuck in between and the login prompt not coming. what could be the reason?

3. Can you please explain how the kernel and the file system are linked? Means how kernel get to know this is the filesystem it should consider for? I am confused with initrd, initramfs etc stuff. How these are linked to each other?

I hope somebody help me by answering these queries with patience.

Thanks a lot.

Rgds,

Vijay

  • 0
    TI__Guru** 116100 points
    Hi,


    1. I used GLSDK6.10 earlier. When I do ./mksdboot.sh on that SDK it used to create uboot, bootscript, kernal, dtb files in boot partition and file system on rootfs partition of sd card. But When I am using GLSDK7.00 it is creating only uboot,MLO, and uenv.txt files in boot partition and kernel image and dtb files in boot folder of the filesystem on rootfs partition. What is the difference? why they changed the location of kernel image.?


    Its modified for the customers to update their new kernel after booted the board with old kernel.
    You can update your kernel in "boot" folder so that in next boot you can boot updated kernel.


    2. And I used to experiment by changing some code in kernel and copy them boot partition in GLSDK6.10 and it was working. But when I do the same thing on glsdk7.00 and copy the newly built images in boot folder of fs, it is getting stuck in between and the login prompt not coming. what could be the reason?


    What is the problem ? Stuck means, where it got stuck ?
    Could you please share the log.

    What is the kernel version of both GLSDK6 and GLSDK7 ?


    3. Can you please explain how the kernel and the file system are linked? Means how kernel get to know this is the filesystem it should consider for? I am confused with initrd, initramfs etc stuff. How these are linked to each other?


    You may have to read lot of documents and need to study a lot on Linux booting and filesystem :-)
    No issues, we will support if any queries.

    Kernel would initialize the drivers for all the hw present in board and need to pass the control to filesystem for Flash (NAND/NOR/SPI/MMC/Hard disk etc.,) access to manage the files and folders.
    So, initrd (initial RAM disk) , initramfs (initial RAM filesystem), are temporvary filesystem, that means, you can have a some files and folders and it would present on RAM and not in flash(permanent, like SPI/NAND/NOR) , so after modification of files and folders, you wont that changes after boot when you boot via "initramfs" and "initrd".
    Initramfs and initrd are more over same with bit difference.

    Also, filesystem would run the services (network, SSH,telnet,DHCP etc.,)

    Please refer to the following TI wiki pages.

    processors.wiki.ti.com/.../Initrd

    processors.wiki.ti.com/.../Initrd

    processors.wiki.ti.com/.../Creating_a_Root_File_System_for_Linux_on_OMAP35x

    processors.wiki.ti.com/.../Filesystem_in_NOR_or_NAND