Re: USBFN => data abort in Windows Embedded CE6.0
- From: "Silver" <moc.liamtoh@gnirrevliseht>
- Date: Tue, 20 May 2008 09:40:35 -0700
If you build your image with the debugger enabled it should halt the CPU when the exception occurs and allow you too see more information about what is happening.
Basically you have a NULL pointer exception somewhere in "mv8760usbfn.dll."
If you want to figure out the particular instruction manually then you will need to know where the DLL is loaded and the disassembly (link /dump /disasm <yourdllname>) OR the .cod file if you want source code (WINCECOD=1)
Subtract the load address from the PC (PC=c0978d18 - LoadAddress) then use that number to offset into the disassembly dump. Scroll up until you find a function name.
Geoff
--
.
- References:
- USBFN => data abort in Windows Embedded CE6.0
- From: okayhj
- USBFN => data abort in Windows Embedded CE6.0
- Prev by Date: Re: DriverEntry not being called
- Next by Date: Re: USBFN => data abort in Windows Embedded CE6.0
- Previous by thread: USBFN => data abort in Windows Embedded CE6.0
- Next by thread: Re: USBFN => data abort in Windows Embedded CE6.0
- Index(es):
Relevant Pages
|
Loading