03-13-2014 05:46 AM
03-13-2014 09:07 AM
03-18-2014 01:17 AM
1- Is the rootfs formed by petalinux-config -c rootfs saved in Xilinix-14.../images as rootfs.cpio? if no then where ?
2- Where is the source code of rootfs that gets compiled when petalinux-build runs ?
03-19-2014 09:40 AM
A1) Yes, the rootfs.cpio file is the root filesystem in a packaged format
A2) I am not sure what you're asking for this one. For non-custom binaries, the files are drawn out of the binaries repo located in $PETALINUX/components/packages-repo/plnx-repo/dists/default/main/<architecture>
03-20-2014 05:42 AM
Thanks for your reply.
In 2) I am just asking that if .cpio file is the result of compilation (the output file from the compiler), there must be a source code (the input to the compiler) corresponding to this.
I will look into the location you mentioned, though.
03-20-2014 11:17 AM
As I mentioned, they are not compiled on-the-fly. For the default apps/libraries/modules available in the RootFS menuconfig, they are pre-built binaries that come from the apt repository location I mentioned. These are assembled into the final RootFS that comes out of the petalinux-build process.
Again, as of 2013.04, nothing is compiled from source other than the following:
2) Linux kernel
3) your own custom apps/libs/modules
04-01-2014 12:09 PM
How do you modify the size of the RootFS? Is there a setting in Petalinux menuconfig or the size is adapted according to the packages selected to be inserted in the file system? I am trying to fit a Petalinux in a reduced RAM system (~32MB).
10-05-2017 02:11 PM
@tmcdowe I am crossing my fingers that you are still around, get wind of this post, and are able to help me.
I have a legacy PetaLinux 2012.12 system that I'm trying to deal with. I can't upgrade. I have to stay with 2012.12. Furthermore, this legacy system seems to be designed not at all like any doc I can find. (I can't even remember at this point if I ever found 2012.12 doc.)
My GOAL is to update the file system on the target, which of course comes from flash and into a ramdisk. I have figured out how to build a romfs.cpio file with new content. Now I need to know how to get that onto the target hardware flash. Any guidance?
(Note that I already figured out how to get a new bitstream into the flash. It involved "petalinux-package-firmware" on my linux host VM, and "upgrade-firmware" on the target. I had thought the image.ub file going into "petalinux-package-firmware" contained the file system, but now I'm doubting this. I went so far as now I can make image.ub from MyProject.dts, via "petalinux-create-bootimage". But, again, I now think this doesn't contain the ramdisk image. Today I realized romfs.cpio really contains the file system. I built one successfully. But now I don't see any clues how to get it onto the target flash. What's worse, the test target is no longer in my lab, but remote, so I can't simply look at it again to get clues.)
Thanks VERY much.