Using poky qemy for powerpc

Using poky qemy for powerpc

[sachin kumar]

[-- Attachment #1: Type: text/plain, Size: 144 bytes --]

Dear All:

Please let me know if there is proper documentation of using poky qemu for
running linux on powerpc platform.

Regards
Sachin

[-- Attachment #2: Type: text/html, Size: 158 bytes --]

Re: Using poky qemy for powerpc

[Scott Garman]

On 11/24/2010 08:26 AM, sachin kumar wrote:
> Dear All:
>
> Please let me know if there is proper documentation of using poky qemu
> for running linux on powerpc platform.

Hi Sachin,

Our Quick Start guide has been updated to reflect the addtional 
arguments required by the poky-qemu script; see the end of:

http://www.yoctoproject.org/docs/yocto-quick-start/yocto-project-qs.html

and let me know if you are still having issues. I realize you've been 
having troubles with this and I'd like to help right them.

Thanks,

Scott

-- 
Scott Garman
Embedded Linux Distro Engineer - Yocto Project

Re: Using poky qemy for powerpc

[sachin kumar]

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

Hello Scott:

I want to run linux on powerpc on qemu. My host machine is running Fedora13.

For that i have downloaded following from yocto project website.

Disk Image: yocto-image-minimal-qemuppc-0.9.rootfs.ext3
Kernel Image : zImage-2.6.34-qemuppc-0.9.bin
Toolchain: yocto-eglibc-i586-powerpc-toolchain-sdk-0.9.tar.bz2

I have installed toolchain in /opt/poky

I have also copied Disk "yocto-image-minimal-qemuppc-0.9.rootfs.ext3" and
"Kernel Image : zImage-2.6.34-qemuppc-0.9.bin" in the /opt/poky directory


To run qemu i am using following commands


[sachin@sachinlinux poky]$ source environment-setup-ppc603e-poky-linux


[sachin@sachinlinux poky]$ poky-qemu qemuppc zImage-2.6.34-qemuppc-0.9.bin
yocto-image-minimal-qemuppc-0.9.rootfs.ext3
In order for this script to dynamically infer paths
to kernels or filesystem images, you either need
bitbake in your PATH or to source poky-init-build-env
before running this script


So i am not able to run poky-qemu command.

Please suggest what to do next.

Regards
Sachin

On Thu, Nov 25, 2010 at 2:49 AM, Scott Garman <scott.a.garman@intel.com>wrote:

> On 11/24/2010 08:26 AM, sachin kumar wrote:
>
>> Dear All:
>>
>> Please let me know if there is proper documentation of using poky qemu
>> for running linux on powerpc platform.
>>
>> Regards
>> Sachin
>>
>
> Hi Sachin,
>
> I'm a Yocto Project developer at Intel and was responsible for making some
> significant changes to the poky-qemu script for our 0.9 release.
>
> I wanted to follow-up with you off-list to see if you are still having
> issues after following Jessica's advice and let you know that I'm available
> as a resource to resolve any further problems you're having with that
> script.
>
> Scott
>
> --
> Scott Garman
> Embedded Linux Distro Engineer - Yocto Project
>

[-- Attachment #2: Type: text/html, Size: 2478 bytes --]

Re: Using poky qemy for powerpc

[Zhang, Jessica]

[-- Attachment #1.1: Type: text/plain, Size: 10721 bytes --]

Kumar,
 
I just download the exact same set on my Ubuntu 10.04 (I know many people
are using F13, so I'm sure it's a pretty stable distro for Yocto to be run
on) and everything works, here's my output:
 
jzhang@jzhang-desktop:/opt/poky$ source environment-setup-ppc603e-poky-linux

jzhang@jzhang-desktop:/opt/poky$ poky-qemu qemuppc
/home/jzhang/Downloads/zImage-2.6.34-qemuppc-0.9.bin
/home/jzhang/Downloads/yocto-image-minimal-qemuppc-0.9.rootfs.ext3 ext3
 
Continuing with the following parameters:
KERNEL: [/home/jzhang/Downloads/zImage-2.6.34-qemuppc-0.9.bin]
ROOTFS: [/home/jzhang/Downloads/yocto-image-minimal-qemuppc-0.9.rootfs.ext3]
FSTYPE: [ext3]
Acquiring lockfile for tap0...
Warning: Stale lock file detected, deleting /tmp/qemu-tap-locks/tap0.lock
Using preconfigured tap device 'tap0'
Starting distccd...
Running qemu-system-ppc...
/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/qemu-system-ppc -kernel
/home/jzhang/Downloads/zImage-2.6.34-qemuppc-0.9.bin -net nic,vlan=0 -net
tap,vlan=0,ifname=tap0,script=no,downscript=no -cpu 603e -M prep -bios
powerpc_rom.bin -hda
/home/jzhang/Downloads/yocto-image-minimal-qemuppc-0.9.rootfs.ext3
-no-reboot -show-cursor -usb -usbdevice wacom-tablet -nographic -no-reboot
--append "root=/dev/hda console=ttyS0 console=tty0
ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=128M "
Using QEMU machine description
Linux version 2.6.34.7-wr-standard (pokybuild@autobuilder) (gcc version
4.5.0 20100729 (prerelease) (GCC) ) #1 PREEMPT Sun Oct 24 08:14:18 PDT 2010
PCI host bridge /pci@80800000 (primary) ranges:
  IO 0x0000000080000000..0x00000000807fffff -> 0x0000000000000000
 MEM 0x00000000c0000000..0x00000000c0ffffff -> 0x0000000000000000 
bootconsole [udbg0] enabled
qemu_find_bridges: config at fd400000
arch: exit
Zone PFN ranges:
  DMA      0x00000000 -> 0x00008000
  Normal   empty
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00008000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: root=/dev/hda console=ttyS0 console=tty0
ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=128M 
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 124600k/131072k available (4808k kernel code, 6472k reserved, 200k
data, 311k bss, 180k init)
Kernel virtual memory layout:
  * 0xfffdf000..0xfffff000  : fixmap
  * 0xfd400000..0xfe000000  : early ioremap
  * 0xc9000000..0xfd400000  : vmalloc & ioremap
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:512 nr_irqs:512
i8259 legacy interrupt controller initialized
clocksource: timebase mult[2800000] shift[22] registered
Console: colour dummy device 80x25
console [tty0] enabled, bootconsole disabled
             
Using QEMU machine description
Linux version 2.6.34.7-wr-standard (pokybuild@autobuilder) (gcc version
4.5.0 20100729 (prerelease) (GCC) ) #1 PREEMPT Sun Oct 24 08:14:18 PDT 2010
PCI host bridge /pci@80800000 (primary) ranges:
  IO 0x0000000080000000..0x00000000807fffff -> 0x0000000000000000
 MEM 0x00000000c0000000..0x00000000c0ffffff -> 0x0000000000000000 
bootconsole [udbg0] enabled
qemu_find_bridges: config at fd400000
Zone PFN ranges:
  DMA      0x00000000 -> 0x00008000
  Normal   empty
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00008000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: root=/dev/hda console=ttyS0 console=tty0
ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=128M 
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 124600k/131072k available (4808k kernel code, 6472k reserved, 200k
data, 311k bss, 180k init)
Kernel virtual memory layout:
  * 0xfffdf000..0xfffff000  : fixmap
  * 0xfd400000..0xfe000000  : early ioremap
  * 0xc9000000..0xfd400000  : vmalloc & ioremap
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:512 nr_irqs:512
i8259 legacy interrupt controller initialized
clocksource: timebase mult[2800000] shift[22] registered
Console: colour dummy device 80x25
console [tty0] enabled, bootconsole disabled
Security Framework initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing PCI hardware
pci 0000:00:0c.0: BAR 0: assigned [mem 0xc0800000-0xc0ffffff pref]
pci 0000:00:0c.0: BAR 0: set to [mem 0xc0800000-0xc0ffffff pref] (PCI
address [0x800000-0xffffff]
pci 0000:00:0d.0: BAR 0: assigned [mem 0xc0000000-0xc00000ff]
pci 0000:00:0d.0: BAR 0: set to [mem 0xc0000000-0xc00000ff] (PCI address
[0x0-0xff]
bio: create slab <bio-0> at 0
vgaarb: device added: PCI:0000:00:0c.0,decodes=io+mem,owns=none,locks=none
vgaarb: loaded
Switching to clocksource timebase
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Registering unionfs 2.5.4 (for 2.6.34-rc0)
msgmni has been set to 243
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
LTT : ltt-relay init
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
console [ttyS0] enabled
brd: module loaded
Uniform Multi-Platform E-IDE driver
ide_generic: please use "probe_mask=0x3f" module parameter for probing all
legacy ISA IDE ports
hda: QEMU HARDDISK, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 13
hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive
ide1: disabled, unable to get IRQ 13
ide1: failed to initialize IDE interface
ide1: disabling port
ide-gd driver 1.18
hda: max request size: 512KiB
hda: 173634 sectors (88 MB) w/256KiB Cache, CHS=172/255/63
hda: cache flushes supported
 hda: unknown partition table
ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0x300:52:54:00:12:34:56
eth0: NE2000 found at 0x300, using IRQ 9.
console [netcon0] enabled
netconsole: network logging started
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: multipath personality registered for level -4
md: faulty personality registered for level -5
device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised:
dm-devel@redhat.com
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
IP-Config: Complete:
     device=eth0, addr=192.168.7.2, mask=255.255.255.0, gw=192.168.7.1,
     host=192.168.7.2, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
EXT3-fs (hda): warning: feature flags set on rev 0 fs, running e2fsck is
recommended
EXT3-fs (hda): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) readonly on device 3:0.
Freeing unused kernel memory: 180k init
kjournald starting.  Commit interval 5 seconds
EXT3-fs (hda): warning: updating to rev 1 because of new feature flag,
running e2fsck is recommended
EXT3-fs (hda): using internal journal
 
Yocto Linux (Built by Poky 4.0) 0.9 qemuppc ttyS0
 
qemuppc login: root
root@qemuppc:~# 


  _____  

From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org]
On Behalf Of sachin kumar
Sent: Wednesday, November 24, 2010 6:30 PM
To: Garman, Scott A
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Using poky qemy for powerpc


Hello Scott:

I want to run linux on powerpc on qemu. My host machine is running Fedora13.

For that i have downloaded following from yocto project website.

Disk Image: yocto-image-minimal-qemuppc-0.9.rootfs.ext3
Kernel Image : zImage-2.6.34-qemuppc-0.9.bin
Toolchain: yocto-eglibc-i586-powerpc-toolchain-sdk-0.9.tar.bz2

I have installed toolchain in /opt/poky

I have also copied Disk "yocto-image-minimal-qemuppc-0.9.rootfs.ext3" and
"Kernel Image : zImage-2.6.34-qemuppc-0.9.bin" in the /opt/poky directory


To run qemu i am using following commands


[sachin@sachinlinux poky]$ source environment-setup-ppc603e-poky-linux


[sachin@sachinlinux poky]$ poky-qemu qemuppc zImage-2.6.34-qemuppc-0.9.bin
yocto-image-minimal-qemuppc-0.9.rootfs.ext3 
In order for this script to dynamically infer paths
to kernels or filesystem images, you either need
bitbake in your PATH or to source poky-init-build-env
before running this script


So i am not able to run poky-qemu command.

Please suggest what to do next.

Regards
Sachin


On Thu, Nov 25, 2010 at 2:49 AM, Scott Garman <scott.a.garman@intel.com>
wrote:


On 11/24/2010 08:26 AM, sachin kumar wrote:


Dear All:

Please let me know if there is proper documentation of using poky qemu
for running linux on powerpc platform.

Regards
Sachin



Hi Sachin,

I'm a Yocto Project developer at Intel and was responsible for making some
significant changes to the poky-qemu script for our 0.9 release.

I wanted to follow-up with you off-list to see if you are still having
issues after following Jessica's advice and let you know that I'm available
as a resource to resolve any further problems you're having with that
script.

Scott

-- 
Scott Garman
Embedded Linux Distro Engineer - Yocto Project




[-- Attachment #1.2: Type: text/html, Size: 14034 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 8455 bytes --]

Re: Using poky qemy for powerpc

[Scott Garman]

On 11/24/2010 06:30 PM, sachin kumar wrote:
> Hello Scott:
>
> I want to run linux on powerpc on qemu. My host machine is running Fedora13.
>
> For that i have downloaded following from yocto project website.
>
> Disk Image: yocto-image-minimal-qemuppc-0.9.rootfs.ext3
> Kernel Image : zImage-2.6.34-qemuppc-0.9.bin
> Toolchain: yocto-eglibc-i586-powerpc-toolchain-sdk-0.9.tar.bz2
>
> I have installed toolchain in /opt/poky
>
> I have also copied Disk "yocto-image-minimal-qemuppc-0.9.rootfs.ext3"
> and "Kernel Image : zImage-2.6.34-qemuppc-0.9.bin" in the /opt/poky
> directory
>
>
> To run qemu i am using following commands
>
>
> [sachin@sachinlinux poky]$ source environment-setup-ppc603e-poky-linux
>
>
> [sachin@sachinlinux poky]$ poky-qemu qemuppc
> zImage-2.6.34-qemuppc-0.9.bin yocto-image-minimal-qemuppc-0.9.rootfs.ext3
> In order for this script to dynamically infer paths
> to kernels or filesystem images, you either need
> bitbake in your PATH or to source poky-init-build-env
> before running this script
>
>
> So i am not able to run poky-qemu command.

Hi Sachin,

You are missing the filesystem type argument. Please add ext3 to the 
argument list:

poky-qemu qemuppc zImage-2.6.34-qemuppc-0.9.bin 
yocto-image-minimal-qemuppc-0.9.rootfs.ext3 ext3

HTH,

Scott

-- 
Scott Garman
Embedded Linux Distro Engineer - Yocto Project

Re: Using poky qemy for powerpc

[sachin kumar]

[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]

Dear Scott:

Thanks for your support i am able to use it.

One more request, please provide me link or any doc which describe using
poky-qemu for powerpc processor.

Kind Regards
Sachin Dhiman


On Thu, Nov 25, 2010 at 8:52 AM, Scott Garman <scott.a.garman@intel.com>wrote:

> On 11/24/2010 06:30 PM, sachin kumar wrote:
>
>> Hello Scott:
>>
>> I want to run linux on powerpc on qemu. My host machine is running
>> Fedora13.
>>
>> For that i have downloaded following from yocto project website.
>>
>> Disk Image: yocto-image-minimal-qemuppc-0.9.rootfs.ext3
>> Kernel Image : zImage-2.6.34-qemuppc-0.9.bin
>> Toolchain: yocto-eglibc-i586-powerpc-toolchain-sdk-0.9.tar.bz2
>>
>> I have installed toolchain in /opt/poky
>>
>> I have also copied Disk "yocto-image-minimal-qemuppc-0.9.rootfs.ext3"
>> and "Kernel Image : zImage-2.6.34-qemuppc-0.9.bin" in the /opt/poky
>> directory
>>
>>
>> To run qemu i am using following commands
>>
>>
>> [sachin@sachinlinux poky]$ source environment-setup-ppc603e-poky-linux
>>
>>
>> [sachin@sachinlinux poky]$ poky-qemu qemuppc
>> zImage-2.6.34-qemuppc-0.9.bin yocto-image-minimal-qemuppc-0.9.rootfs.ext3
>> In order for this script to dynamically infer paths
>> to kernels or filesystem images, you either need
>> bitbake in your PATH or to source poky-init-build-env
>> before running this script
>>
>>
>> So i am not able to run poky-qemu command.
>>
>
> Hi Sachin,
>
> You are missing the filesystem type argument. Please add ext3 to the
> argument list:
>
> poky-qemu qemuppc zImage-2.6.34-qemuppc-0.9.bin
> yocto-image-minimal-qemuppc-0.9.rootfs.ext3 ext3
>
> HTH,
>
>
> Scott
>
> --
> Scott Garman
> Embedded Linux Distro Engineer - Yocto Project
>

[-- Attachment #2: Type: text/html, Size: 2327 bytes --]