This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Why can't tests be built for pc target?
On 2008-03-17, Andrew Lunn <andrew@lunn.ch> wrote:
>> I'll check that out. I guess I'll have to add a hard drive to
>> the target.
>
> Might be worth checking the grub documentation. It might be
> able to load from the floppy.
It can, but if I'm going to have to generate a disk image,
generating a hard-drive one is just as easy as generating a
floppy one, and then I don't have the 1.44MB limit either. I'm
running stuff on a virtual machine using Qemu and being able to
point it at the bootable floppy images generated by the eCos
"make" was awfully handy. I'll write a shell-script to
generate a bootable hard-drive image with grub and the
application on it.
>> In the meantime, I can't even get a simple "hello world" app
>> (which is smaller than 640K) to generate any output. The
>> RedBoot floppy image generated with basically the same
>> configuration works fine, but hello world doesn't. :/
>
> RedBoot will use all available consoles, ie com1, com2, and
> the screen if you have it enabled. diag_printf will just the
> use the first. So it could be you are looking at the wrong
> serial port.
Yup, that was it. I was just looking at the "vga screen". When
I "hooked up" the first serial port, then I saw the output from
[diag_]printf(). I thought that I was running with Qemu
connecting the first serial port to the vga-screen and
keyboard, but that was a misunderstanding on my part.
I think Qemu is going to be a pretty slick way to test stuff...
--
Grant
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss