how to modify run level in zed board

Hi Srinivas,

Okay, I think I see what you are doing.

What I am getting at is that you should be able to modify your RAM disk image (in your case it is the rootfs.cpio file) from your PetaLinux development machine.

Here are the steps that I used to unpack, modify, and repack one on my development system:

1)  Create a temporary folder to hold your root file system so that it can be unpacked in the next step:

mkdir tmp_mnt

2)  Unpack the cpio archive to the temporary folder:

cd tmp_mnt/
sudo cpio -i < ../rootfs.cpio

3)  Make the desired modifications to the root file system files (in this step I did my edits to tmp_mnt/etc/inittab and created the autologin.sh script in tmp_mnt/home/root/).

4)  Once the modifications are complete, repack the cpio archive (starting from the tmp_mnt/ working directory):

cd ..
rm rootfs.cpio
sh -c 'cd tmp_mnt/ && sudo find . | sudo cpio -H newc -o' > rootfs.cpio

Now copy the updated rootfs.cpio image to your SD card and boot ZedBoard, you should see the modifications to the root file system in place at this point.

The bottom line is that yes you are correct in that any changes you make to the file system while it is loaded into RAM on ZedBoard will not persist between reboots.  However, you should be able to modify that file system image on your development machine to suit your needs.

Regards,

-Kevin

Hi kevin,


i have done as per previous information.

root@pradeep-desktop:/home/pradeep~#mkdir rootfs
root@pradeep-desktop:~#cd rootfs/
root@pradeep-desktop:/home/pradeep/rootfs#

i copied rootfs.cpio gile in this folder

root@pradeep-desktop:/home/pradeep/rootfs~#cpio -i < rootfs.cpio

root@pradeep-desktop:/home/pradeep/rootfs~#vim /home/root/autologin.sh

#!/bin/sh
exec /bin/login -f root

root@pradeep-desktop:/home/pradeep/rootfs/home/root~#chmod a+x autologin.sh

Modified my /etc/inittab file

#PS0:2345:respawn:/sbin/getty -L 115200 ttyPS0 vt100
PS0:2345:respawn:/sbin/getty -l /home/root/autologin.sh -n -L 115200 ttyPS0 vt100

root@pradeep-desktop:/home/pradeep/rootfs~#rm rootfs.cpio

root@pradeep-desktop:/home/pradeep/rootfs~#cd ..
root@pradeep-desktop:/home/pradeep~#sh -c 'cd rootfs/ && sudo find . | sudo cpio -H newc -o' > rootfs.cpio


everything clear upto this


these are  mtd parititions

0x000000000000-0x000000500000 : "boot"
0x000000500000-0x000000520000 : "bootenv"
0x000000520000-0x000000fa0000 : "kernel"
0x000000fa0000-0x000002000000 : "spare"

//............................... mtd3 partition...........................................//

flash_eraseall -j /dev/mtd3
flashcp -v  rootfs.cpio /dev/mtd3

//.........................my uboot commands...............................................//

bootargs=console=ttyPS0,115200 root=/dev/mtd3 rw earlyprintk 5
qspiboot_test=sf probe 0 0; sf read 0xfa0000 0x520000 0xa80000 && sf read 0x2000000 0xfa0000 0x1060000 && bootm 0xfa0000 0x2000000

//..........i am getting like this ....................................//

U-Boot-PetaLinux> run qspiboot_test
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
SF: 11010048 bytes @ 0x520000 Read: OK
SF: 17170432 bytes @ 0xfa0000 Read: OK
## Loading kernel from FIT Image at 00fa0000 ...
   Using 'conf@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  PetaLinux Kernel
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x00fa00f0
     Data Size:    7150584 Bytes = 6.8 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00008000
     Entry Point:  0x00008000
     Hash algo:    crc32
     Hash value:   5d7f745d
   Verifying Hash Integrity ... crc32+ OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
U-Boot-PetaLinux>


can you tell me  where i did the mistake.


Thanks & Regards,
srinivas Rao

Hi kevin,


i have done as per previous information.

root@pradeep-desktop:/home/pradeep~#mkdir rootfs
root@pradeep-desktop:~#cd rootfs/
root@pradeep-desktop:/home/pradeep/rootfs#

i copied rootfs.cpio gile in this folder

root@pradeep-desktop:/home/pradeep/rootfs~#cpio -i < rootfs.cpio

root@pradeep-desktop:/home/pradeep/rootfs~#vim /home/root/autologin.sh

#!/bin/sh
exec /bin/login -f root

root@pradeep-desktop:/home/pradeep/rootfs/home/root~#chmod a+x autologin.sh

Modified my /etc/inittab file

#PS0:2345:respawn:/sbin/getty -L 115200 ttyPS0 vt100
PS0:2345:respawn:/sbin/getty -l /home/root/autologin.sh -n -L 115200 ttyPS0 vt100

root@pradeep-desktop:/home/pradeep/rootfs~#rm rootfs.cpio

root@pradeep-desktop:/home/pradeep/rootfs~#cd ..
root@pradeep-desktop:/home/pradeep~#sh -c 'cd rootfs/ && sudo find . | sudo cpio -H newc -o' > rootfs.cpio


everything clear upto this


these are  mtd parititions

0x000000000000-0x000000500000 : "boot"
0x000000500000-0x000000520000 : "bootenv"
0x000000520000-0x000000fa0000 : "kernel"
0x000000fa0000-0x000002000000 : "spare"

//............................... mtd3 partition...........................................//

flash_eraseall -j /dev/mtd3
flashcp -v  rootfs.cpio /dev/mtd3

//.........................my uboot commands...............................................//

bootargs=console=ttyPS0,115200 root=/dev/mtd3 rw earlyprintk 5
qspiboot_test=sf probe 0 0; sf read 0xfa0000 0x520000 0xa80000 && sf read 0x2000000 0xfa0000 0x1060000 && bootm 0xfa0000 0x2000000

//..........i am getting like this ....................................//

U-Boot-PetaLinux> run qspiboot_test
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
SF: 11010048 bytes @ 0x520000 Read: OK
SF: 17170432 bytes @ 0xfa0000 Read: OK
## Loading kernel from FIT Image at 00fa0000 ...
   Using 'conf@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  PetaLinux Kernel
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x00fa00f0
     Data Size:    7150584 Bytes = 6.8 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00008000
     Entry Point:  0x00008000
     Hash algo:    crc32
     Hash value:   5d7f745d
   Verifying Hash Integrity ... crc32+ OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
U-Boot-PetaLinux>


can you tell me  where i did the mistake.


Thanks & Regards,
srinivas Rao