<div dir="ltr">Dear Folks<div><br></div><div>Thanks for the suggestions. Well this is how I debug </div><div><br></div><div>qemu-system-x86_64 -no-kvm -net none -bios build/coreboot.rom -s -global isa-serial.iobase=0x3f8 -serial file:/new/serial8.log -monitor stdio</div>
<div><br></div><div> (Don' t consider the 8)<br></div><div><br></div><div><br></div><div>Please correct me if Im mistaken</div><div><br></div><div>By the way by freeze I meant is that the DUET BIOS page gets displayed but it does not allow to select anything. If I use the down arrow key there is no effect.......So still facing the same problem.</div>
<div><br></div><div><br></div><div>Any suggestions...</div><div><br></div><div><br></div><div>Neo...</div><div><br></div><div><br></div><div>(Attached serial log) </div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Nov 6, 2013 at 4:58 AM, Scott Duplichan <span dir="ltr"><<a href="mailto:spambucket@notabs.org" target="_blank">spambucket@notabs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Anthony Ross wrote:<br>
<br>
]Hello Coreboot Folks,<br>
<div class="im">]<br>
]Well Thanks for the suggestions. It seems that DUET boots but now a major problem has ]cropped up. It freezes at the main<br>
DUET-BIOS page not allowing to perform any further ]operations, like booting a HDD image or fingering around the EFI BIOS options.<br>
Similarly ]If I had the .lzma to the cbfs file name I face the same problem like earlier so having ]it as myfloppy.img makes it take<br>
effect.<br>
]<br>
]<br>
]Any further Ideas about these problems.....<br>
]<br>
]<br>
]Regards..<br>
]<br>
]<br>
]Neo <br>
<br>
</div>For your freeze problem, how are you debugging? The usual way<br>
is to enable and capture debug messages written to a serial<br>
port. I believe the standard Duet settings make it write<br>
debugging messages to a serial port at 3F8 (115200,8,N,1).<br>
Because halt for assert is enabled by default on Duet, an<br>
assert is the most likely reason for a freeze. The assert<br>
will log details to the serial port.<br>
<br>
If your hardware doesn't have a serial port, you can use<br>
an emulator such as simnow or qemu. A good thing about<br>
Duet is that it is generic and in theory can run on<br>
different systems without porting. If I remember correctly,<br>
the current Duet project can boot to the UEFI shell and<br>
menu system on AMD simnow using the Solo board model.<br>
<br>
I am working on a project to allow Duet to run as a<br>
coreboot payload, and to fix the major Duet problems.<br>
It will also continue to support bootable image form.<br>
It may take me a few weeks to reach the goal of booting<br>
operating systems in UEFI mode on real hardware though.<br>
<br>
Thanks,<br>
Scott<br>
<div class="HOEnZb"><div class="h5"><br>
On Sat, Oct 26, 2013 at 8:01 PM, Kevin O'Connor <<a href="mailto:kevin@koconnor.net">kevin@koconnor.net</a>> wrote:<br>
On Thu, Oct 24, 2013 at 12:17:33AM -0500, Scott Duplichan wrote:<br>
> Scott Duplichan wrote:<br>
><br>
> <..snip..><br>
><br>
> ]I have no experience with making SeaBIOS boot an embedded floppy<br>
> ]image. I may be able to give this a try, but I would have to first overcome<br>
> ]Windows build problems that have crept into both SeaBIOS and coreboot.<br>
><br>
> I tested the SeaBIOS virtual floppy boot with EDK2 Duet and it worked<br>
> for me. I tested with the ASRock e350M1 project. Here is the cbfstool<br>
> output:<br>
Thanks for confirming.<br>
<br>
> scott@p67-2600k /D/coreboot/win-build-env-011/coreboot/build<br>
> $ cbfstool.exe coreboot.rom print<br>
> coreboot.rom: zd kB, bootblocksize 4096, romsize 1008, offset 0x400000<br>
> alignment: 0 bytes<br>
><br>
> Name Offset Type Size<br>
> cmos_layout.bin 0x0 cmos_layout 1776<br>
> pci1002,9802.rom 0x740 optionrom 57856<br>
> fallback/romstage 0xe980 stage 345432<br>
> fallback/coreboot_ram 0x62f40 stage 203312<br>
> fallback/payload 0x949c0 payload 53738<br>
> config 0xa1c00 raw 3831<br>
> (empty) 0xa2b40 null 3526744<br>
><br>
> scott@p67-2600k /D/coreboot/win-build-env-011/coreboot/build<br>
> $ cbfstool.exe coreboot.rom add -f /d/duetfloppy.img -n floppyimg/duetfloppy.img -t raw<br>
FYI, it's also possible to add an lzma compressed image (make sure the<br>
cbfs filename ends in ".lzma" then).<br>
<br>
-Kevin<br>
<br>
<br>
</div></div></blockquote></div><br></div>