none
WINCE 6.0 Device cannot connect to Windows 7.0 RRS feed

  • Question

  • Hi !!

      My device running WINCE 6.0  couldnt connect to Windows 7.0 Mobile device centre . The NK.Bin throws the exception when trying to connect . The same image works well with WIN XP Active Sync.

    Any ideas why this happens ?

    Thanks!!

    Exception 'Data Abort' (4): Thread-Id=042a0002(pth=858de000), Proc-Id=00400002(pprc=818c8308) 'NK.EXE', VM-active=04810002(pprc=858d7000) 'explorer.exe'
    PC=c0a0c9fc(sc2450usbfn.dll+0x0000c9fc) RA=c0a0c9f4(sc2450usbfn.dll+0x0000c9f4) SP=d2bdfdbc, BVA=00000007
    Exception 'Data Abort' (4): Thread-Id=042a0002(pth=858de000), Proc-Id=00400002(pprc=818c8308) 'NK.EXE', VM-active=04810002(pprc=858d7000) 'explorer.exe'
    PC=80235424(kitl.dll+0x00007424) RA=80231fd0(kitl.dll+0x00003fd0) SP=d2bdf8ac, BVA=00000010

    Friday, August 27, 2010 2:09 AM

All replies

  • The exception is in your USB function driver, which is part of the platform code.  You have access to that (assuming you are the platform developer), have you tried a debug build?
    Dean Ramsier eMVP BSQUARE Corporation
    • Proposed as answer by Michael Koster Friday, September 3, 2010 8:55 AM
    Monday, August 30, 2010 1:02 PM
  • My KITL is not working - so its difficult to debug and figure out the issue. But the USB code is working well when connected to WIN XP systems. So was wondering whats missing. Thanks!!
    Friday, September 3, 2010 1:19 PM
  • Getting KITL working should be a top priority; it's difficult to debug issues without it. 

    That said, you could manually decode the exception using the map/cod file for usbfn.dll and see where the exception is occuring.  Or put Dr Watson in the build and get a Watson dump that will also point you to the offending code.


    Dean Ramsier eMVP BSQUARE Corporation
    Tuesday, September 7, 2010 1:07 PM