Release 0.2 — Replace the Angstrom uImage with Fedora 17 uIamge

As show on the previous post, Success boot up Fedroa17 on BeagleBone  base on the Angstrom Bootfs(Partition1) and Fedora 17 Rootfs(Partition2, including Ang uImage):

Message1:{

## Booting kernel from Legacy Image at 80007fc0 …
Image Name:   Angstrom/3.2/beaglebone
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3179880 Bytes = 3 MiB
Load Address: 80008000
Entry Point:  80008000
Verifying Checksum … OK
XIP Kernel Image … OK
OK
Starting kernel …

Uncompressing Linux… done, booting the kernel.
[    0.222354] _omap_mux_get_by_name: Could not find signal leds-gpio
[    0.522999] omap_hwmod: wkup_m3: wkup_m3: hwmod data error: OMAP4 does not support st_shift
systemd-fsck[64]: Angstrom: clean, 16860/218592 files, 142314/873534 blocks

Fedora release 17 (Beefy Miracle)
Kernel 3.2.16 on an armv7l (ttyO0)

fedora-arm login: [    4.912123]
[    4.912130] CPSW phy found : id is : 0x7c0f1
[    4.918881] PHY 0:01 not found

Fedora release 17 (Beefy Miracle)
Kernel 3.2.16 on an armv7l (ttyO0)
fedora-arm login: root
Password:
[root@fedora-arm ~]# pwd
/root
[root@fedora-arm ~]# ls -al
total 36
dr-xr-x—  3 root root 4096 Nov 22  2012 .
drwxr-xr-x 18 root root 4096 Dec 31 19:26 ..
-rw——-  1 root root   44 Nov 22  2012 .bash_history
-rw-r–r–  1 root root   18 Jan 14  2012 .bash_logout
-rw-r–r–  1 root root  176 Jan 14  2012 .bash_profile
-rw-r–r–  1 root root  176 Jan 14  2012 .bashrc
-rw-r–r–  1 root root  100 Jan 14  2012 .cshrc
drwxr—–  3 root root 4096 Apr 30  2012 .pki
-rw-r–r–  1 root root  129 Jan 14  2012 .tcshrc
[root@fedora-arm ~]#
}

Because I was using Angstrom kernel to boot up, so I try to use F17’s uIamge(kernel).
Replace Angstrom uImage with Fedora 17 uIamge on partition 1:

Message2:{
Loading file “/boot/uImage” from mmc device 0:2 xxa2
3179944 bytes read
## Booting kernel from Legacy Image at 80007fc0 …
  Image Name:   Angstrom/3.2/beaglebone
  Image Type:   ARM Linuxe (uncompressed)
Data Size:    3179880 By
Load Address: 80008000
Entry Point:  80008000
Verifying Checksum …OK
XIP Kernel Image … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[    0.524688] omap_hwmod: wkup_m3: wkup_m3: hwmod data error: OMAP4 does not support st_shift
systemd-fsck[64]: Angstrom: clean, 16896/218592 files, 142722/873534 blocks

Fedora release 17 (Beefy Miracle)
Kernel 3.2.16 on an armv7l (ttyO0)

[    4.929809]
[    4.929809] CPSW phy found : id is : 0x7c0f1
[    4.936706] PHY 0:01 not found

Fedora release 17 (Beefy Miracle)
Kernel 3.2.16 on an armv7l (ttyO0)

Fedora release 17 (Beefy Miral 3.2.16 on an armv7l (ttyO0)

fedora-arm login: root
Passwor

[root@fedora-arm ~]#

}

After change to F17’s kernel(uImage) on partition 1, it still log in success.
It looks good. However, look at the high light message1&2, I think it is still running the Angstrom kernel, not f17 kernel.(It looks like it booting up from the uImage file which I copied under boot directory on partition2)

So,I try to replace Angstrom uImage with Fedora 17 uIamge on partition 2 under boot file:

Disk /dev/sdb: 8166 MB, 8166309888 bytes
255 heads, 63 sectors/track, 992 cylinders, total 15949824 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63      144584       72261    c  W95 FAT32 (LBA)
/dev/sdb2          144585     7132859     3494137+  83  Linux

[root@Fedora17 jcqiu]# mount /dev/sdb2 /mnt/f17Rootfs/
[root@Fedora17 jcqiu]# cd /mnt/f17Rootfs/
[root@Fedora17 f17Rootfs]# ls
bin   dev  home  media  opt   root  sbin     srv  tmp  var
boot  etc  lib   mnt    proc  run   selinux  sys  usr
[root@Fedora17 f17Rootfs]# cd boot/
[root@Fedora17 boot]# ls
uboot  uImage
[root@Fedora17 boot]# cp /home/jcqiu/Downloads/Fedora-17-kernel/armhfp-beagle-mmcblk0/boot/uboot/uImage .
cp: overwrite `./uImage’? y
[root@Fedora17 boot]# cd
[root@Fedora17 ~]# umount /mnt/f17Rootfs
[root@Fedora17 ~]# eject /dev/sdb
#screen /dev/ttyUSB1 115200:

Message3:{
……(the same)
reading uEnv.txt

33 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc …
Loading file “/boot/uImage” from mmc device 0:2 xxa2
3974848 bytes read
## Booting kernel from Legacy Image at 80007fc0 …
Image Name:   3.4.2-3.fc17.armv7hl.omap
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3974784 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point:  80008000
Verifying Checksum … OK
XIP Kernel Image … OK
OK

Starting kernel …
}

It stop running at here. Base on the highlight message3, it seems like running f17’s kernel. However,I’m not sure it does matter or not because in this way it doesn’t run success.

As last time Peter Robson leave a comment(Issue when booting up Fedora 17 on beaglebone) for me that I should use F18’s kernel. On post (Try to make Fedora17 run on Beaglebone – 2),I download F18’s kernel(u-boot), and there are only 3 files : MLO  u-boot.bin  u-boot.img.   It does not include uImage file,  I kind of confuse…

I think whether I should change any other files to make the f17’s kernel start success.
I  replace Ang MLO with F17 MLO, it didn’t show any message, not even error message.
But when I replace with F18 MLO, it runs until “Starting kernel…” and have the same message as message3. I also replace Ang u-boot.img with f18 u-boot.img, same message…

Conclusion:
The uImage on partition 1 could be either Ang or f17 file, but if the uImage on partition 2 is f17 uIamge, it can run but can not log in. The problem of this could be f17 uImage file is not supported by Ang MLO and/or u-boot.img.

My release 0.2 include 2 versions:

First version can log in as fedora 17 success.  (include Angstrom uboot files(with f17 uImage) and F17 rootfs(with Ang uImage)
https://docs.google.com/open?id=0BxheefHomqmzZFZFdU91WEFIZGM

Second version is still in test, can boot up until “Starting kernel…”. (include Angstrom uboot files(with F18’s ML0 & u-boot.img) and F17 rootfs(with f17 uImage).
https://docs.google.com/open?id=0BxheefHomqmzS0xEWk16OEtJbGM

Advertisements

2 thoughts on “Release 0.2 — Replace the Angstrom uImage with Fedora 17 uIamge

  1. Pingback: Make F18 omap uImage and Using menuconfig | jcqiu

  2. Pingback: Final Release -0.3 | jcqiu

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s