Final Release -0.3

Hi all, today I gonna post my final release-0.3 for my project: Running Fedora on BeagleBone.

Before I show you the final release, I would like to tell you what did I did recently.

So far, I already get F17 userspace working with the Angstrom kernel on BeagleBone. How I made it works, you can go through my previous post –Release 0.2

Now, I’m on the way to change the kernel configuration file and rebuild the kernel.

——————————————————————————————————————

I compared the Angstrom’s and F18’s kernel config file:

Here is the Angstrom’s kernel config file: http://matrix.senecac.on.ca/~jcqiu/SBR600/Ang-config.txt
Here is the F18’s kernel config file: http://matrix.senecac.on.ca/~jcqiu/SBR600/Fedora-18-arm-Configfile%20(copy).txt

By comparing these two files, I most focus on the “OMAP” and “Kernel”  part,

Here is the change rule I followed:
if something is include in Ang kernel file, and not include in the F18′s, make it include in the F18′s config file if it is important.
for example: in Ang kernel config file: there is a line:  “CONFIG_OMAP_MCBSP=y”    but not in F18′s. I google it and/or use the Make menuconfig to search the meaning of this line. if it is important, it could be the problem which causes the F18 kernel not running success in BB. If so, I just add this line to the F18′s kernel config file.

Here are the lines I add in the F18 kernel config file:

CONFIG_OMAP_MCBSP=y
CONFIG_OMAP3_EDMA=y
CONFIG_SPI_OMAP24XX=y
CONFIG_OMAP2_VRAM=y
CONFIG_FB_OMAP2=m
CONFIG_FB_OMAP2_DEBUG_SUPPORT=y
CONFIG_FB_OMAP2_NUM_FBS=3
CONFIG_RTC_DRV_OMAP=y
CONFIG_OMAP_IOVMM=y
CONFIG_OMAP_IOMMU_DEBUG=y
CONFIG_THUMB2_KERNEL=y

Here is the final f18’s config file: http://matrix.senecac.on.ca/~jcqiu/SBR600/Fedora-18-arm-Configfile.txt

——————————————————————————————————————

After I done the compare part. I did some research and go to channel to ask people how to build a kernel use this updated F18 kernel config file.  However, didn’t catch the useful information.

I go to talk to Raymond Chan, and he suggest to download a Kernel source code and have a look first. It would be helpful if I gonna build a kernel.

last night, Chris give me some useful information in channel. He tell me how to build a kernel for BB.

I download a kernel source from http://www.kernel.org/
I untar this tar ball, and it give me a folder named “linux-3.6.9”:

[jcqiu@Fedora17 linux-3.6.9]$ ls
arch     crypto         fs       Kbuild   MAINTAINERS  README          security  virt
block    Documentation  include  Kconfig  Makefile     REPORTING-BUGS  sound
COPYING  drivers        init     kernel   mm           samples         tools
CREDITS  firmware       ipc      lib      net          scripts         usr

I run the “make menuconfig” command as root under this folder.

——————————————————————————————————————

Because I don’t have enough time(Due on today) to continue work on it, so I just test on what I already have. and there is the boot up message I got when I run the BB base on F18 kernel(uImage), and F17 userspace:

U-Boot SPL 2011.09-00000-gf63b270-dirty (Apr 24 2012 – 09:51:01)
Texas Instruments Revision detection unimplemented
No AC power, disabling frequency switch
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2011.09-00000-gf63b270-dirty (Apr 24 2012 – 09:51:01)

I2C:   ready
DRAM:  256 MiB
No daughter card present
NAND:  HW ECC Hamming Code selected
nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x10, Chip ID: 0x10
No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning – readenv() failed, using default environment

Net:   cpsw
Hit any key to stop autoboot:  0
SD/MMC found on device 0
reading uEnv.txt

418 bytes read
Loaded environment from uEnv.txt
Importing environment from mmc …
Loading file “/boot/uImage” from mmc device 0:2 xxa2
3760680 bytes read
## Booting kernel from Legacy Image at 80007fc0 …
Image Name:   Linux Kernel
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3760616 Bytes = 3.6 MiB
Load Address: 80008000
Entry Point:  80008000
Verifying Checksum … OK
XIP Kernel Image … OK
OK

Starting kernel …

——————————————————————————————————————

Here is my Final Release 0.3:
https://docs.google.com/open?id=0BxheefHomqmzTmMxeXJ6Tk5ZTjg

Make F18 omap uImage and Using menuconfig

Hi all,

I recently download a new f18 kernel file from http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=102410
the file name: kernel-omap-3.6.7-5.fc18.armv7hl.rpm

In this case, I want to updatekernel on BeagleBone.

Boot up BeagleBone with my release 0.2-version 1.  before login, go to uboot mode, change the env of mmc_root  from ro to rw
the command:
U-Boot# setenv mmc_root /dev/mmcblk0p2 rw
U-Boot# saveenv
U-Boot# boot

when log in as root:

# rpm -Uvh kernel-omap-3.6.7-5.fc18.armv7hl.rpm
# cd /boot/

you will find some new files there.

# file *                              to see the file format( run this on BB or host(copy file to host) is kind of different.Run in host has better result)
you will see the file “vmlinuz-3.6.7-5.fc18.armv7hl.omap” is executable zImage file. Which means we can create uImage file base on this file.

[root@Fedora17 Backup-P2-Bootfile]# file vmlinuz-3.6.7-5.fc18.armv7hl.omap
vmlinuz-3.6.7-5.fc18.armv7hl.omap: Linux kernel ARM boot executable zImage (little-endian)
{
[root@Fedora17 Backup-P2-Bootfile]# file *
config-3.6.7-5.fc18.armv7hl.omap:        ASCII text
initramfs-3.6.7-5.fc18.armv7hl.omap.img: gzip compressed data, from Unix, last modified: Fri Dec 31 20:03:14 1999, max compression
System.map-3.6.7-5.fc18.armv7hl.omap:    ASCII text
uImage:                                  u-boot legacy uImage, Angstrom/3.2/beaglebone, Linux/ARM, OS Kernel Image (Not compressed), 3179880 bytes, Tue May  8 02:46:13 2012, Load Address: 0x80008000, Entry Point: 0x80008000, Header CRC: 0xC3138F6B, Data CRC: 0x33B5CFFE
vmlinuz-3.6.7-5.fc18.armv7hl.omap:       Linux kernel ARM boot executable zImage (little-endian)
}

For make the uImage, I did some preparation:
#yum install uboot-tools
#man mkimage

Now let’s Make uImage:

[root@Fedora17 Backup-P2-Bootfile]# mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n “Linux Kernel” -d vmlinuz-3.6.7-5.fc18.armv7hl.omap uImage
Image Name:   Linux Kernel
Created:      Wed Dec  5 18:57:34 2012
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3760616 Bytes = 3672.48 kB = 3.59 MB
Load Address: 80008000
Entry Point:  80008000
[root@Fedora17 Backup-P2-Bootfile]# ls
config-3.6.7-5.fc18.armv7hl.omap         uImage
initramfs-3.6.7-5.fc18.armv7hl.omap.img  vmlinuz-3.6.7-5.fc18.armv7hl.omap
System.map-3.6.7-5.fc18.armv7hl.omap
[root@Fedora17 Backup-P2-Bootfile]# ll
total 16804
-rw-r–r–. 1 root root  102287 Dec  5 17:18 config-3.6.7-5.fc18.armv7hl.omap
-rw-r–r–. 1 root root 7924129 Dec  5 17:18 initramfs-3.6.7-5.fc18.armv7hl.omap.img
-rw——-. 1 root root 1649126 Dec  5 17:18 System.map-3.6.7-5.fc18.armv7hl.omap
-rw-r–r–. 1 root root 3760680 Dec  5 18:57 uImage
-rwxr-xr-x. 1 root root 3760616 Dec  5 17:18 vmlinuz-3.6.7-5.fc18.armv7hl.omap
[root@Fedora17 Backup-P2-Bootfile]# file uImage
uImage: u-boot legacy uImage, Linux Kernel, Linux/ARM, OS Kernel Image (Not compressed), 3760616 bytes, Wed Dec  5 18:57:34 2012, Load Address: 0x80008000, Entry Point: 0x80008000, Header CRC: 0x98D3A8D2, Data CRC: 0xEDA678B2

replace the Ang uImage

[root@Fedora17 jcqiu]# mount /dev/sdb2 /mnt/f17Rootfs/
[root@Fedora17 jcqiu]# cd Documents/
[root@Fedora17 Documents]# cd Backup-P2-Bootfile/
[root@Fedora17 Backup-P2-Bootfile]# ll
total 16804
-rw-r–r–. 1 root root  102287 Dec  5 17:18 config-3.6.7-5.fc18.armv7hl.omap
-rw-r–r–. 1 root root 7924129 Dec  5 17:18 initramfs-3.6.7-5.fc18.armv7hl.omap.img
-rw——-. 1 root root 1649126 Dec  5 17:18 System.map-3.6.7-5.fc18.armv7hl.omap
-rw-r–r–. 1 root root 3760680 Dec  5 18:57 uImage
-rwxr-xr-x. 1 root root 3760616 Dec  5 17:18 vmlinuz-3.6.7-5.fc18.armv7hl.omap
[root@Fedora17 Backup-P2-Bootfile]# ll /mnt/f17Rootfs/boot/uImage
-rw-r–r–. 1 root root 3179944 Dec  4 17:15 /mnt/f17Rootfs/boot/uImage
[root@Fedora17 Backup-P2-Bootfile]# cp uImage /mnt/f17Rootfs/boot/
cp: overwrite `/mnt/f17Rootfs/boot/uImage’? y
[root@Fedora17 Backup-P2-Bootfile]# umount /dev/sdb2
[root@Fedora17 Backup-P2-Bootfile]# eject /dev/sdb

}

Compare the kernel config files:

I went to IRC #fedora-arm channel to ask people how to use the menuconf

and here is the way to use it:

# cd /usr/src/kernel/3.6.3-1.fc17.86×64
# make menuconfig
The GUI interface is coming out!!

That’s it for the day!

Fedora omap kernel config file

Tonight, I go to IRC #fedora-arm channel to ask people about the Fedora 17 omap kernel config file again.

Maste give me a f18’s config file, and says this file has many difference with f17’s. He suggest me to use this one which is better version.  And he tell me to use mkimage tool to make f18’s uIamge if I can’t find it. 

Here is the sample command to run: ” mkimage -A sh -O linux -T kernel -C gzip -a 0x8C001000 -e 0x8C002000 -n “Linux 2.6” -d vmlinux.bin.gz vmlinux.ub “

The addresses for the two parameters “-a” (load address) and “-e” (execute address) depend of the specific target board that is being used, and they also depend on the SE mode.

Get Angstrom kernel config file (config.gz)

Because I want to compare and know the difference between Angstrom kernel config file and Fedora17 arm config file. I burn the Angstrom image on SD card and boot it up to find the config file.

Gloria IP shared me a link to download Angstrom image file: http://downloads.angstrom-distribution.org/demo/beaglebone/  and the file is “Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.09.12.img.xz”

After download, run command:
# xz -dkc Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.09.12.img.xz > /dev/sdX          (write the image to your SD card, X should be replace to your SD card)

# sync

Copy file to out side:

directory: /proc/
root@beaglebone:/proc#scp config.gz jcqiu@matrix.senecac.on.ca:/home/jcqiu/SBR600/

Host ‘matrix.senecac.on.ca’ is not in the trusted hosts file.
(fingerprint md5 20:23:07:dd:63:81:d0:7f:39:81:0b:43:a4:60:38:e5)
Do you want to continue connecting? (y/n) y
Login for jcqiu@matrix.senecac.on.ca
Password:
config.gz                                     100%   21KB  21.2KB/s   00:00   

Show contents:
zcat config.gz | more

 

Here is the file I upload: http://matrix.senecac.on.ca/~jcqiu/SBR600/config.gz

Current Status of Project

I have success run fedora 17 on BeagleBone base on Angstrom kernel(on partition2). The more detail info you can check my previous post.

When I try to boot up the Fedora 17’s kernel, it only runs until the message”Starting kernel…”

Therefore, I did some research and ask people in IRC Channel, still can’t find out the solution.

And I asked Chris Tyler for help on Nov27. He try to see the error message, but wasn’t working.

So, he suggest me to compare Angstrom’s kernel configuration file with Fedora 17’s kernel configuration file. And then I may can do some change on it.

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

Try to make Fedora17 run on Beaglebone – 3

Use minicom to see the connection message (when SD card include Angstrom Bootfs(kernel) and Fedora 17 Rootfs):

{

Welcome to minicom 2.5
OPTIONS: I18n
Compiled on Jan 14 2012, 12:40:23.
Port /dev/ttyUSB1

Press CTRL-A Z for help on special keys
U-Boot SPL 2011.09-00000-gf63b270-dirty (Apr 24 2012 – 09:51:01)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2011.09-00000-gf63b270-dirty (Apr 24 2012 – 09:51:01)

I2C:   ready
DRAM:  256 MiB
No daughter card present
NAND:  HW ECC Hamming Code selected
nand_get_flash_type: second ID read did not match 10,10 against 00,00
No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning – readenv() failed, using default environment

Net:   cpsw
Hit any key to stop autoboot:  0
SD/MMC found on device 0
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
** File not found /boot/uImage
Booting from nand …

no devices available
Wrong Image Format for bootm command
ERROR: can’t get kernel image!
U-Boot#

}

The error message shows a file not found. So I  copy the Ang uImage to F17 boot/uImage

{
U-Boot#
U-Boot SPL 2011.09-00000-gf63b270-dirty (Apr 24 2012 – 09:51:01)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2011.09-00000-gf63b270-dirty (Apr 24 2012 – 09:51:01)

I2C:   ready
DRAM:  256 MiB
No daughter card present
NAND:  HW ECC Hamming Code selected
No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning – readenv() failed, using default environment

Net:   cpsw
Hit any key to stop autoboot:  0
SD/MMC found on device 0
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
3179944 bytes read
## 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

}

It log in success.

Try to make Fedora17 run on Beaglebone – 2

Last time, I already replaced Angstrom’s rootfs with Fedora 17 rootfs and replaced Angstrom’s uImage file with Fedora 17 uImage (BeagleBoard XM version). It was not boot up success.

Today, I will replace the boot files with the F18’s kernel(u-boot) file.

Find the resource:http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=98609

download it and umpackage it:
rpm2cpio uboot-beaglebone-2012.10-1.fc18.armv7hl.rpm | cpio -idmv

[root@Fedora17 uboot-beaglebone]# pwd
/home/jcqiu/Downloads/usr/share/uboot-beaglebone
[root@Fedora17 uboot-beaglebone]# ls
MLO  u-boot.bin  u-boot.img

cp all files and replace the SD card uboot file.

boot up BeagleBone,

$ fdisk -l    can not see the device.

display message:

[root@Fedora17 uboot-beaglebone]# dmesg | tail
[ 3314.486128] usb 2-5.1: Setting MaxPacketSize 512
[ 3314.486663] usb 2-5.1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3314.486679] ftdi_sio 2-5.1:1.1: FTDI USB Serial Device converter detected
[ 3314.486713] usb 2-5.1: Detected FT2232H
[ 3314.486715] usb 2-5.1: Number of endpoints 2
[ 3314.486717] usb 2-5.1: Endpoint 1 MaxPacketSize 512
[ 3314.486718] usb 2-5.1: Endpoint 2 MaxPacketSize 512
[ 3314.486720] usb 2-5.1: Setting MaxPacketSize 512
[ 3314.486976] usb 2-5.1: FTDI USB Serial Device converter now attached to ttyUSB1
[ 3314.486985] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver

Reset BeagleBone, message not chance.

Disconnect BeagleBone, message changed:
[root@Fedora17 uboot-beaglebone]# dmesg | tail
[ 3314.486718] usb 2-5.1: Endpoint 2 MaxPacketSize 512
[ 3314.486720] usb 2-5.1: Setting MaxPacketSize 512
[ 3314.486976] usb 2-5.1: FTDI USB Serial Device converter now attached to ttyUSB1
[ 3314.486985] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[ 3396.019237] usb 2-5: USB disconnect, device number 4
[ 3396.019242] usb 2-5.1: USB disconnect, device number 5
[ 3396.019464] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 3396.019484] ftdi_sio 2-5.1:1.0: device disconnected
[ 3396.019612] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[ 3396.019627] ftdi_sio 2-5.1:1.1: device disconnected

Reconnect BeagleBone.
[root@Fedora17 uboot-beaglebone]# dmesg | tail
[ 3411.232058] usb 2-6.1: Endpoint 2 MaxPacketSize 512
[ 3411.232060] usb 2-6.1: Setting MaxPacketSize 512
[ 3411.232461] usb 2-6.1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3411.234616] ftdi_sio 2-6.1:1.1: FTDI USB Serial Device converter detected
[ 3411.234642] usb 2-6.1: Detected FT2232H
[ 3411.234644] usb 2-6.1: Number of endpoints 2
[ 3411.234647] usb 2-6.1: Endpoint 1 MaxPacketSize 512
[ 3411.234649] usb 2-6.1: Endpoint 2 MaxPacketSize 512
[ 3411.234652] usb 2-6.1: Setting MaxPacketSize 512
[ 3411.234902] usb 2-6.1: FTDI USB Serial Device converter now attached to ttyUSB1

Try to make Fedora17 run on Beaglebone – 1

For now, my SD card include Angstrom Boot files and Fedora 17 Root files.

Connect BeagleBone(inserted SD card) to my desktop(F17),  can’t find any partition mounted.

Use command # screen /dev/ttyUSB1 115200, try to connect BeagleBone.
conncet to U-Boot     Which is not right.

 

Found the F17 OMAP Kernel of beagleboard xm (Page:http://fedoraproject.org/wiki/Architectures/ARM/Fedora_17_GA ,Download: http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-beagle-mmcblk0-kernel.tar.xz)  and try to replace this uImage file to Angstrom uImage files on Boot partition.
After replace the file, try to boot up.

Here is the connection message:

Reset BeagelBone
[root@Fedora17 jcqiu]# dmesg | tail
[ 6129.268191] usb 2-5.1: Setting MaxPacketSize 512
[ 6129.268478] usb 2-5.1: FTDI USB Serial Device converter now attached to ttyUSB1
[ 6129.268487] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[ 6144.230016] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 6144.231743] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 6144.231747] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 6148.680082] usb 2-1: reset high-speed USB device number 2 using ehci_hcd
[ 6196.964515] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 6196.966024] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 6196.966028] sd 4:0:0:0: [sdb] Assuming drive cache: write through

display later
[root@Fedora17 jcqiu]# dmesg | tail
[ 7189.327082] usb 2-1: reset high-speed USB device number 2 using ehci_hcd
[ 7241.444261] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7241.445762] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7241.445765] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7293.668900] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7293.670389] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7293.670393] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7345.892655] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7345.894149] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7345.894153] sd 4:0:0:0: [sdb] Assuming drive cache: write through

Disconnect from Computer
[root@Fedora17 jcqiu]# dmesg | tail
[ 7398.233054] usb 2-1: reset high-speed USB device number 2 using ehci_hcd
[ 7450.340430] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7450.341938] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7450.341942] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7477.193331] usb 2-5: USB disconnect, device number 4
[ 7477.193335] usb 2-5.1: USB disconnect, device number 5
[ 7477.193637] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 7477.193653] ftdi_sio 2-5.1:1.0: device disconnected
[ 7477.193945] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[ 7477.193961] ftdi_sio 2-5.1:1.1: device disconnected

Reconnect
[root@Fedora17 jcqiu]# dmesg | tail
[ 7505.084988] usb 2-5.1: Endpoint 2 MaxPacketSize 512
[ 7505.084991] usb 2-5.1: Setting MaxPacketSize 512
[ 7505.085434] usb 2-5.1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 7505.087570] ftdi_sio 2-5.1:1.1: FTDI USB Serial Device converter detected
[ 7505.087596] usb 2-5.1: Detected FT2232H
[ 7505.087598] usb 2-5.1: Number of endpoints 2
[ 7505.087601] usb 2-5.1: Endpoint 1 MaxPacketSize 512
[ 7505.087604] usb 2-5.1: Endpoint 2 MaxPacketSize 512
[ 7505.087606] usb 2-5.1: Setting MaxPacketSize 512
[ 7505.087859] usb 2-5.1: FTDI USB Serial Device converter now attached to ttyUSB1

display later
[root@Fedora17 jcqiu]#
[root@Fedora17 jcqiu]# dmesg | tail
[ 7607.012492] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7607.014012] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7607.014016] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7659.236512] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7659.237993] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7659.237997] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7659.346068] usb 2-1: reset high-speed USB device number 2 using ehci_hcd
[ 7711.460489] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7711.461972] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7711.461976] sd 4:0:0:0: [sdb] Assuming drive cache: write through

 

Still cannot booting up success, I probably will try to use the f18.

Release 0.1

Preparation:

when I connect BeagleBone(Angstrom system) to computer, I can only find one partition /sdd mounted ( by command: fdisk -l ; dmesg | tail; and open computer file to see)
when I connect Fedora 17 SD card (which is not compatible for BeagleBone yet) to computer, I can find two partitions /sdb1 and /sdb2 mounted
So, I disconnect BeagleBone, and take the Angstrom SD card out, and directory connect to computer. Now, I can see two partitions /sdb1 and /sdb2.

when I use command: screen /dev/ttyUSB1 115200; to connect Angstrom on Beaglebone, it works. username: root, password: blank.    exit by: ctrl a then ctrl z.
Run command: dmesg | grep FTDI | grep “now attached to” | tail -n 1 | awk ‘{ print $NF }’; to find out what /dev/ttyUSB# the BeagleBone is connected to.  usually USB1

Release 0.1: Keep the partition 1 of Angstrom (boot files), and replace partition 2 with Fedora 17 userspace(“rootfs”).

Mount /dev/sdb2 and check files:
[root@Fedora17 jcqiu]# mkdir /mnt/AngRootfs
[root@Fedora17 jcqiu]# mount /dev/sdb2 /mnt/AngRootfs
[root@Fedora17 jcqiu]# ls /mnt/AngRootfs/
bin   boot2  etc   lib         media  opt  proc  sbin  tmp  var
boot  dev    home  lost+found  mnt    p1   run   sys   usr

Delete all Angstrom root files:
[root@Fedora17 jcqiu]# rm -rf /mnt/AngRootfs/*

Download the F17 rootfs from: http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images/armhfp/Fedora-17-armhfp-console.tar.xz

yum install p7zip, and unzip the download file.
and then tar the file to /mnt/AngRootfs/
However, there is error when I tar the file:
[root@Fedora17 Downloads]# tar -xvzf ./Fedora-17-armhfp-console.tar /mnt/AngRootfs/
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Find out I should not use -z here. Try again:
[root@Fedora17 Downloads]# tar -xvf Fedora-17-armhfp-console.tar /mnt/AngRootfs/
tar: /mnt/AngRootfs: Not found in archive
tar: Exiting with failure status due to previous errors

Find out use -C option to specify in which directory you want the files extracted.
[root@Fedora17 Downloads]# tar -xvf Fedora-17-armhfp-console.tar -C /mnt/AngRootfs/

Eject SD card: eject /dev/sdb;
put SD card back in BeagleBone, and connect to computer.
Nothing happen….
run command: dmesg | tail;
[root@Fedora17 Downloads]# dmesg | tail
[ 7878.610758] usb 2-6.1: Endpoint 1 MaxPacketSize 512
[ 7878.610761] usb 2-6.1: Endpoint 2 MaxPacketSize 512
[ 7878.610763] usb 2-6.1: Setting MaxPacketSize 512
[ 7878.610995] usb 2-6.1: FTDI USB Serial Device converter now attached to ttyUSB1
[ 7925.988647] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7925.990142] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7925.990146] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 7978.212420] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7978.213912] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7978.213915] sd 4:0:0:0: [sdb] Assuming drive cache: write through

Click reset button:
[root@Fedora17 Downloads]# dmesg | tail
[ 7978.212420] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 7978.213912] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 7978.213915] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 8030.436060] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 8030.437539] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 8030.437543] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 8030.550059] usb 2-1: reset high-speed USB device number 2 using ehci_hcd
[ 8082.660439] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 8082.661919] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 8082.661923] sd 4:0:0:0: [sdb] Assuming drive cache: write through

fdisk -l not showing /dev/sdb;

Botting not success for now!

——————————————————————–

I will continue work on it.
Here is the final tar file include both partitions files: https://docs.google.com/open?id=0BxheefHomqmzbGxJeFNyOG5sVlU