OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

> Alarmz On Qemu
TheWalt
post Dec 7 2015, 07:42 AM
Post #1





Group: Members
Posts: 178
Joined: 11-August 05
Member No.: 7,836



Ok so I thought this would be easy but I am (probably) one step in over my head so maybe someone can help.

QEMU has native support for the Zaurus line of product under ARM emulation. After a little google search it seemed running a debian install worked good so why not get ALARMZ going.

So the steps I have done so far is as follows.

I had to create a raw disk image to run from, so did this to make a 6gig image.

CODE
dd if=/dev/null of=alarm.img bs=1M seek=6114


Then I had to format the image.

CODE
mkfs.ext4 -F alarm.img


Then I mounted it and untar the file system just like you would on real hardware.

CODE
mkdir /mnt/alarm
mount -t ext4 -o loop alarm.img /mnt/alarm
bsdtar xvf alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz -C /mnt/alarm/


Now I thought that would be it, start up the VM and watch the magic happen. Unfortunately no such luck.

CODE
qemu-system-arm -machine spitz alarm.img

qemu: fatal: Trying to execute code outside RAM or ROM at 0x00800000

R00=00000000 R01=00000000 R02=00000000 R03=00000000
R04=00000000 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=00000000 R14=00000000 R15=00800000
PSR=400001d3 -Z-- A svc32
FPSCR: 00000000
Aborted


So I'm not sure where to go from here. Looking at other start-up strings it does seem like I might be missing -kernel and -initrd files but have no idea where to get them.

If anyone can point me in a direction I'll try to do the leg work
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
TheWalt
post Dec 9 2015, 06:34 AM
Post #2





Group: Members
Posts: 178
Joined: 11-August 05
Member No.: 7,836



HA!

I was running from 2.0.0 and when I updated to 2.4.1 it worked!

Now to get networking and should be good to go. Thanks for the heads up on the QEMU version, considering how old the Z is I'd never thougth that would be the issue.
Go to the top of the page
 
+Quote Post
greguu
post Dec 14 2015, 09:56 PM
Post #3





Group: Moderators
Posts: 376
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



QUOTE(TheWalt @ Dec 9 2015, 03:34 PM) *
HA!

I was running from 2.0.0 and when I updated to 2.4.1 it worked!

Now to get networking and should be good to go. Thanks for the heads up on the QEMU version, considering how old the Z is I'd never thougth that would be the issue.


Hi TheWalt.

did you have any success with the network?

I realized the qemu-system-arm does not allow the use of the virtual pcnet driver (pcnet is included as kernel module in ALARMZ)

If you found a way to get it working let me know, I guess I there might be a limitation and additional kernel modules may be required.

Cheers!
Go to the top of the page
 
+Quote Post
greguu
post Dec 14 2015, 11:40 PM
Post #4





Group: Moderators
Posts: 376
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



Hi,
just as a note. ArchLinuxArm does not support qemu at all. I searched the alarm forums about qemu and the response is "not supported".
Saying that , there might be still a way to get networking going and I will put some effort in, but it is not my priority.
I only use qemu to test new build kernels boot process, not to test apps or network.
For testing apps etc, I recommend to use a SD card with alarm on it, so you test on SD first before going "production" on the CF card.
This way you can keep your main alarm on the CF "clean". I hope this makes sense, as there is no speed benefit from running qemu
and compiling applications under qemu is not recommended.
Cheers!
Go to the top of the page
 
+Quote Post
TheWalt
post Dec 15 2015, 10:01 AM
Post #5





Group: Members
Posts: 178
Joined: 11-August 05
Member No.: 7,836



QUOTE(daalnroti @ Dec 15 2015, 02:40 AM) *
Hi,
just as a note. ArchLinuxArm does not support qemu at all. I searched the alarm forums about qemu and the response is "not supported".
Saying that , there might be still a way to get networking going and I will put some effort in, but it is not my priority.
I only use qemu to test new build kernels boot process, not to test apps or network.
For testing apps etc, I recommend to use a SD card with alarm on it, so you test on SD first before going "production" on the CF card.
This way you can keep your main alarm on the CF "clean". I hope this makes sense, as there is no speed benefit from running qemu
and compiling applications under qemu is not recommended.
Cheers!


I unfortunately came to the same realization with networking, only loopback and IR (irda0) seems supported / detected. I really only wanted to get this working so anyone who did not own physical hardware could still compile for the Z.

But I got to thinking, really all someone would need is a system that compiled against the armv5 right? I wonder what other low end system would be compatible that could be purchased.
Go to the top of the page
 
+Quote Post
greguu
post Dec 16 2015, 09:46 PM
Post #6





Group: Moderators
Posts: 376
Joined: 14-November 05
From: New Zealand
Member No.: 8,535



QUOTE(TheWalt @ Dec 15 2015, 07:01 PM) *
QUOTE(daalnroti @ Dec 15 2015, 02:40 AM) *
Hi,
just as a note. ArchLinuxArm does not support qemu at all. I searched the alarm forums about qemu and the response is "not supported".
Saying that , there might be still a way to get networking going and I will put some effort in, but it is not my priority.
I only use qemu to test new build kernels boot process, not to test apps or network.
For testing apps etc, I recommend to use a SD card with alarm on it, so you test on SD first before going "production" on the CF card.
This way you can keep your main alarm on the CF "clean". I hope this makes sense, as there is no speed benefit from running qemu
and compiling applications under qemu is not recommended.
Cheers!


I unfortunately came to the same realization with networking, only loopback and IR (irda0) seems supported / detected. I really only wanted to get this working so anyone who did not own physical hardware could still compile for the Z.

But I got to thinking, really all someone would need is a system that compiled against the armv5 right? I wonder what other low end system would be compatible that could be purchased.


I guess any hardware that supports ALARM would be suitable. Preferably a faster ARM CPU , like armv6/7. You would be able to chroot into the ALARMZ rootfs and compile applications, as to my understanding all new ARM CPUs are backward compatible. However I do not own any other than Xscale armv5. Danboid did some compiling on a ARM board I think.
Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st January 2020 - 09:35 PM