search

Freescale / Documentation

This project hosts the documentation of Freescale Community BSP and related repositories
http://freescale.github.io
Creative Commons Attribution Share Alike 4.0 International
26 stars 19 forks source link

Include rootfs.tar.gz Method In Build And Boot Steps #26

Closed TafThorne closed 7 years ago

TafThorne commented 7 years ago

Many Yocto build systems, including the one for the ls1021a-twr do not generate .sdcard bianry images. This changeset adds some instructions on inflaiting a tar'ed and gzip'ed root filesystem image onto an SD card and then copying over the kernel and device tree bianry files too.

This also reflects the more recent documentation from the Yocto project which no longer mentions pre-formated SD Card images.

TafThorne commented 7 years ago

As with pull requests #24 and #25, this similar to my (Thomas Thorne of Net2Edge Limited) earlier attempt to update the community documentation via email patches. As getting my emails sorted out is not going to be quick I am trying via the GitHub method.

@angolini reviewed this patch via email and said:

0001-Include-rootfs.tar.gz-Method-In-Build-and-boot-steps.patch

I like this patch! Thanks for documenting this.

I would only add a note saying the sdcard may not be partitioned, and which would be the expected partition table to your procedure (would it be 2 partitions, one for rootfs and one for kernel?)

Another point, you don't copy any bootloader, would it be a problem?

Based on this comment I expanded the notes to include a section that reads:

        # If you will use U-Boot from the SD Card it will need to be placed on 
        # a small partition at the start of the card.  If you will use U-Boot 
        # from flash or elsewhere you can have a single exfs2 parition on the 
        # whole card.

I cannot provide more detailed instructions than that. The current process does not generate the U-Boot binary for the target board. I could expand it to include those steps, some examples of possible SD Card layouts and so forth but it would be repeating a lot of what is available from the Yocto project documentation. I feel the current content is enough to demonstrate the differences when using the Freescale Community SDK instead of the vanilar Yocto SDK in a manner that would allow a user to blend the two sets of instructions easily. My motivation for adding the "pre-formed root filesystem archive, kernel and device tree binary image" method was that it better matches the more recent Yocto documentation.