[OpenBIOS] Sparc64 OpenBIOS

[Nick Couchman]

>>
>> 0 > boot cdrom 
>> [sparc64] Booting file 'cdrom' with parameters ''
>> 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
> This still very much looks like it's using the size of a string as an
> address somewhere :-(
> 
> Stefan
> 

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", and, when I try to boot, it doesn't allow me to step through do-boot - it just continues on.  If I let the boot fail once, then try "debug do-boot" it allows me to step through it.  Unfortunately, with this most recent error - the Unhandled Exception - the first time I boot is also the last time until I restart Qemu, making it very difficult to make it stop at the correct place in order to debug.  So, is there a way that I can load the words before I actually attempt the boot so that OpenBIOS knows where to stop and so that I can track down where this unhandled exception is occurring?

-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.