[Qemu-devel] qemu-system-m68k and booting m68k images

[Qemu-devel] qemu-system-m68k and booting m68k images

[Ian Graeme Hilt]

Two questions:

1. Why does qemu-system-m68k require a kernel image?

2. Is support planned for booting m68k bootable images, e.g. floppy
   images, harddrive images?

--
Ian Graeme Hilt

Re: [Qemu-devel] qemu-system-m68k and booting m68k images

[Rob Landley]

On Saturday 06 October 2007 8:59:02 pm Ian Graeme Hilt wrote:
> Two questions:
>
> 1. Why does qemu-system-m68k require a kernel image?

I'd actually be pretty happy if I could figure out which kernel image I could 
build that the sucker would boot.

"qemu-system-m68k -M ?" lists two boards: the mcf5208evb and arnewsh 5206 are 
both coldfire board.  I got gcc to build an m68k toolchain and want to run an 
actual m68k kernel, but the only Kconfig entries mentioning those are in the 
m68knommu architecture...

> 2. Is support planned for booting m68k bootable images, e.g. floppy
>    images, harddrive images?

First, is support planned for booting an m68k system at all, rather than a 
coldfire one?

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

Re: [Qemu-devel] qemu-system-m68k and booting m68k images

[Ian Graeme Hilt]

On Wed, Oct 10, 2007 at 06:20:57PM -0500, Rob Landley wrote:
> On Saturday 06 October 2007 8:59:02 pm Ian Graeme Hilt wrote:
> > Two questions:
> >
> > 1. Why does qemu-system-m68k require a kernel image?
> 
> I'd actually be pretty happy if I could figure out which kernel image I could 
> build that the sucker would boot.

Have you tried

<http://fabrice.bellard.free.fr/qemu/coldfire-test-0.1.tar.bz2>

> 
> "qemu-system-m68k -M ?" lists two boards: the mcf5208evb and arnewsh 5206 are 
> both coldfire board.  I got gcc to build an m68k toolchain and want to run an 
> actual m68k kernel, but the only Kconfig entries mentioning those are in the 
> m68knommu architecture...
> 
> > 2. Is support planned for booting m68k bootable images, e.g. floppy
> >    images, harddrive images?
> 
> First, is support planned for booting an m68k system at all, rather than a 
> coldfire one?
> 
> Rob
> -- 
> "One of my most productive days was throwing away 1000 lines of code."
>   - Ken Thompson.

-- 
Ian Graeme Hilt

Re: [Qemu-devel] qemu-system-m68k and booting m68k images

[Rob Landley]

On Wednesday 10 October 2007 10:20:41 pm Ian Graeme Hilt wrote:
> On Wed, Oct 10, 2007 at 06:20:57PM -0500, Rob Landley wrote:
> > On Saturday 06 October 2007 8:59:02 pm Ian Graeme Hilt wrote:
> > > Two questions:
> > >
> > > 1. Why does qemu-system-m68k require a kernel image?
> >
> > I'd actually be pretty happy if I could figure out which kernel image I
> > could build that the sucker would boot.
>
> Have you tried
>
> <http://fabrice.bellard.free.fr/qemu/coldfire-test-0.1.tar.bz2>

Er, yes.  "coldfire".  Not m68k.  Says so right on the tin.

Back in July, Andreas Schwab posted a patch to upgrade the coldfire support to 
full m68k support (or at least the instructions output by gcc):
http://lists.gnu.org/archive/html/qemu-devel/2007-07/msg00015.html

I thought it would have been merged by now (or that there would at least be 
some kind of follow up on it), but apparently not.

Coldfire is a subset of m68k (plus some weird floating point instructions and 
probably some other stuff).  There doesn't seem to be a way to get a coldfire 
toolchain from unmodified gcc source code, instead you go download a 
different gcc source tarball from code sourcery:
http://www.codesourcery.com/gnu_toolchains/coldfire

If there's a way to build a coldfire toolchain from the gcc 4.1.2 release, 
Google isn't finding it.  gcc 4.1.2 was released Febuary 13, 2007, and the 
gcc developers announced the integration of coldfire support on March 9, 2007 
so maybe it's in 4.2...

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

Re: [Qemu-devel] qemu-system-m68k and booting m68k images

[Ian Graeme Hilt]

On Thu, Oct 11, 2007 at 02:15:25AM -0500, Rob Landley wrote:
> On Wednesday 10 October 2007 10:20:41 pm Ian Graeme Hilt wrote:
> > On Wed, Oct 10, 2007 at 06:20:57PM -0500, Rob Landley wrote:
> > > On Saturday 06 October 2007 8:59:02 pm Ian Graeme Hilt wrote:
> > > > Two questions:
> > > >
> > > > 1. Why does qemu-system-m68k require a kernel image?
> > >
> > > I'd actually be pretty happy if I could figure out which kernel image I
> > > could build that the sucker would boot.
> >
> > Have you tried
> >
> > <http://fabrice.bellard.free.fr/qemu/coldfire-test-0.1.tar.bz2>
> 
> Er, yes.  "coldfire".  Not m68k.  Says so right on the tin.

Ok.

In my case, the target's processor is a MC68030 with a VME bus.
It was built by Microware back in the late 80s to early 90s and
has OSK (OS-9 for a MC680x0) installed.

> Back in July, Andreas Schwab posted a patch to
> upgrade the coldfire support to full m68k support
> (or at least the instructions output by gcc):
> http://lists.gnu.org/archive/html/qemu-devel/2007-07/msg00015.html
> 
> I thought it would have been merged by now (or that there would
> at least be some kind of follow up on it), but apparently not.
 
I've tried building QEmu current with gcc-3.4.6 and this patch
applied.  qemu-system-m68k hung when attempting to boot the kernel
image in coldfire-test-0.1.tar.bz2.

[...] 
 
> If there's a way to build a coldfire toolchain from the gcc 4.1.2
> release, Google isn't finding it.  gcc 4.1.2 was released Febuary
> 13, 2007, and the gcc developers announced the integration of
> coldfire support on March 9, 2007 so maybe it's in 4.2...

I think the Linux kernel supports a MC68030 and the VME option.
Even if gcc was capable of creating a kernel image for this
specific arch, I don't think this would help me(?) since I want
to boot the OSK OS floppy and harddrive images.

I've used OS9Exec from sourceforge to boot these images and it
works rather well.  A problem with it is when an OS9 command tries
to access hardware a bus error is generated.

The reason I was inquiring about the rationale behind the kernel
image is that I was going to try writing code to boot the floppy
images I have with QEmu.  Unfortunately I have very little
programming experience, so any information is helpful. 

-- 
Ian Graeme Hilt

Re: [Qemu-devel] qemu-system-m68k and booting m68k images

[Rob Landley]

On Thursday 11 October 2007 2:15:25 am Rob Landley wrote:
> Back in July, Andreas Schwab posted a patch to upgrade the coldfire support
> to full m68k support (or at least the instructions output by gcc):
> http://lists.gnu.org/archive/html/qemu-devel/2007-07/msg00015.html

Has there been any progress or follow-up on this?  (I'm interested.  I have a 
m68k target building at http://landley.net/hg/firmware but don't know how to 
test it with the current qemu development branch...)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.