How do I prevent the kernel from pivoting and overwriting the initial file system?
What switches do I pass to the kernel?
Do I need to add any code to the initramfs?
I cross-compiled busybox and installed it into the default directory of
Then I pointed to this directory in the kernel menuconfig (CONFIG_INITRAMFS_SOURCE).
My zImage now contains the cpio file known as initramfs.
When I boot (
u-boot bootm 0xkernel - 0xdtbBlob) the kernel will error out with "Unable to mount rootfs on unknown block device".
As I understand it, the kernel is looking for the "real file system" to overwrite the "initial file system". I think this is called a 'pivot'.
I think I want to keep my initial file system intact, at least for now.
I want to use the initramfs I created and included in the zImage.
It seems that everything I have read so far is for:
a ramdisk (block device). I do not want to use because I only have 8M of memory.
a real file system. No mmc,sd,network available. I load all files into memory wrapped into a sb file.
a older kernel or way of doing things. I am using kernel 4.x and u-boot 2015.x
* Freescale imx233 embedded
* 8M sdram
* Loading zero keyed sb file to sdram via recovery mode.
* No mmc, sd, network
To create a small kernel and file system with only the tools required:
* debug and get the rest of the hardware working such as the LCD screen and USB port.
* To flash nand with files from usb.