View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000407 | PicoMOD6 | SD/MMC | public | 2010-09-15 14:01 | 2010-09-15 14:09 |
| Reporter | Assigned To | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | V1.05 | ||||
| Target Version | V1.06 | Fixed in Version | V1.06 | ||
| Summary | 0000407: sdbus exception on bootup. | ||||
| Description | This problem has not occured on PicoMOD6 yet, but I have noticed this issue on PicoCOM3. SD driver for slot 0 is beeing loaded at the same order as the sdbus driver. This might lead into race conditions in some cases. | ||||
| Steps To Reproduce | On PicoCOM3 it sometimes(!) appeared after saveing the registry. | ||||
| Additional Information | Debug version of SDBUS2.dll sais following: [USBH:INF] InitializeOHCI() : USB Host Cap : 0x00000004 SDBusDriver: PROCESS_ATTACH SDHCDGetHCFunctions: +InitSDHCDGetHCFunctions: -InitHSMMC0: Version 1.1, ActiveKey = Drivers\Active\14 Unknown: DEBUGCHK failed in file c:\wince600\platform\picomod6\src\drivers\hsmmc\sdbus\sdbus.hpp at line 231 Exception 'Data Abort' (4): Thread-Id=01260002(pth=834869d8), Proc-Id=00400002(pprc=81621308) 'NK.EXE', VM-active=00400002(pprc=81621308) 'NK.EXE' PC=c003b894(k.coredll.dll+0x0001b894) RA=c06c5e24(sdbus.dll+0x00015e24) SP=d053e868, BVA=00000004 Exception 'Raised Exception' (-1): Thread-Id=01260002(pth=834869d8), Proc-Id=00400002(pprc=81621308) 'NK.EXE', VM-active=01af0002(pprc=8343a648) 'udevice.exe' PC=c003bb58(k.coredll.dll+0x0001bb58) RA=802214c8(kernel.dll+0x000064c8) SP=d053e104, BVA=ffffffff SDBusDriver: PROCESS_DETACH SDBusDriver: PROCESS_ATTACH SDBusDriver: +SDC_InitSDBusDriver: Bus Driver instance created : 0xD040D8E0 ! -SDC_Init AX88796: driver v01.05 for WinCE 6.0 WAV: Version 2.0, ActiveKey = Drivers\Active\19 | ||||
| Forum Link | |||||
| Found Driver Version | |||||
| Fixed Driver Version | |||||
