Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Crash before boot script: (3 Items)
   
Crash before boot script  
I'm working on a MIPS r4k based BSP and I believe I'm close to getting the kernel up and running but it's still crashing
 before it executes the boot script.  I've set breakpoints on nano_clock and verified that the clock is working.  

It seems to be crashing at imagefs_mount_mounter() in the bootimage_init() function.  Any ideas on what to look for?

Also, in the BSP, does "startup_memory_map" in lib/mips/map_startup.c require a "tlb_bypass" function in cases where the
 address to be mapped is in kseg1 (unmapped and uncached area)?  This is what I did to get around problems with 
accessing the serial debug port.


Re: Crash before boot script  
Actually the crash is not before the boot script.  The "Welcome to QNX" banner is printed from the boot script but the 
first app that is executed causes a crash (first app was serial driver originally but tried other apps including a 
simple hello world).  Shutdown memory dump info is printed on the debug screen (log attached).

Setting a break before "shutdown" function shows it was called from "usr_fault".

Any suggestions on where to look for the cause of the crash?
Attachment: Text qnx_crash.log 1.4 KB
Re: Crash before boot script  
You would probably benefit from using the kernel debugger.

At least generate a procnto-32_g.sym (add [+keeplinked] to the procnto 
line in your buildfile), then you can examine the instruction
at 0x80172ff0

David Alessio wrote:
>
> Actually the crash is not before the boot script.  The "Welcome to 
> QNX" banner is printed from the boot script but the first app that is 
> executed causes a crash (first app was serial driver originally but 
> tried other apps including a simple hello world).  Shutdown memory 
> dump info is printed on the debug screen (log attached).
>
> Setting a break before "shutdown" function shows it was called from 
> "usr_fault".
>
> Any suggestions on where to look for the cause of the crash?
>
>
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post2048
>
>  
>

-- 
cburgess@qnx.com