[OpenBIOS] Sparc64 OpenBIOS

[Nick Couchman]

>>> On 2009/11/19 at 13:14, Tarl Neustaedter <Tarl.Neustaedter at Sun.COM> wrote: 
> Nick Couchman wrote:
>> [...]
>> So, in trying to track this down further, I need some more help with the 
> debugger in OpenBIOS.  It seems that I have to go through the boot process at 
> least once before I can debug certain things.  For example, if I start up 
> qemu and immediately type "debug do-boot", I'm told "could not locate word for 
> debugging ok",
> 
> Right. do-boot is defined by the primary bootblocks, the code it reads 
> from blocks 1-15. If you're still booting from the Nevada CD, use boot 
> cdrom -H , which will cause it to halt before it executes do-boot. 
> You'll have to clean up -H from the arguments so you can get past the 
> test for halt?.
> 
> I'd suggest:
> 
> ok boot cdrom -H
> ok debug do-boot
> ok do-boot
> 
> (step through until you see the test for halt?, then enter forth and set 
> halt? to false).
> 

Unfortunately the unhandled exception occurs before this check is done:

0 > boot cdrom -H 
[sparc64] Booting file 'cdrom' with parameters '-H'
Not a bootable ELF image
Not a Linux kernel image
Not a bootable a.out image
Loading FCode image...
Loaded 7420 bytes
entry point is 0x4000
Evaluating FCode...
Unaligned access to 0x0000000000000014 from 0x00000000ffd10d9c
Unhandled Exception 0x0000000000000034
PC = 0x00000000ffd10de4 NPC = 0x00000000ffd10de8
Stopping execution

And, yes, still booting from sol-nv-b127-sparc-dvd.iso file...

-Nick



--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.