none
SDIO based Wifi driver is unloading on reset the target device?? RRS feed

  • Question

  • Dear Developers,

    We are using AM335x based BSP with Wince 7 and we are using Redpine RS9110-N-11-02 module. We have both debug and release moude drivers binaries. DHCP and Static Ip feature, MTU 1500 etc are working fine. We are near to close the WIfi for our board but we are facing one issue related to driver of wifi moudle. We have some following observations-

    Case 1: DMA enabled & DHCP enabled and stick is inserted in the SDIO slot(0).

    In this case, when we press reset button  and the board boots again, we found that the driver LED is continuously on as it was blinking before reset. When we see the logs, we found that the driver is loading and immediately unloading. Here we have some logs

     7761 PID:400002 TID:9e0006 OSAXST1: >>> Loading Module 'rwlpsdio.dll' (0x9E438000) at address 0xA7C90000-0xA7D47000 in Process 'NK.EXE' (0x87FDFAD0)
    PB Debugger Loaded 'rwlpsdio.dll', no matching symbolic information found.
       7771 PID:400002 TID:9e0006 Warning! Kernel DLL 'rwlpsdio.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside D
       7774 PID:400002 TID:9e0006 DriverEntry!!!!!!!!!!!!!
       7777 PID:400002 TID:9e0006 SDIO not initialized, returning!!!!!!!!!!!!!!
       7778 PID:400002 TID:9e0006 OSAXST1: <<< Unloading Module 'rwlpsdio.dll' (0x9E438000) at address 0xA7C90000-0xA7D47000 in Process 'NK.EXE' (0x87FDFAD0)
    PB Debugger Unloaded symbols for 'rwlpsdio.dll'

    Case 2: DMA enabled & DHCP enabled and stick is inserted in the SDIO slot(0) & we remove and reinsert the power adaptor

    Here we have another log, when we remove power adaptor and again insert the power adaptor-

    8168 PID:400002 TID:9e0006 NDIS:: CE_DeleteBusFriendlyNames() failed deleting [HKLM\Comm\BusFriendlyNames] 8177 PID:400002 TID:9e0006 OSAXST1: >>> Loading Module 'rwlpsdio.dll' (0x9E438000) at address 0xA7C90000-0xA7D47000 in Process 'NK.EXE' (0x87FDFAD0) PB Debugger Loaded 'rwlpsdio.dll', no matching symbolic information found. 8186 PID:400002 TID:9e0006 Warning! Kernel DLL 'rwlpsdio.dll' is registered for thread creation/deletion notification. To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside D 8191 PID:400002 TID:9e0006 DriverEntry!!!!!!!!!!!!! 8191 PID:400002 TID:9e0006 SDIO not initialized, returning!!!!!!!!!!!!!! 8192 PID:400002 TID:9e0006 OSAXST1: <<< Unloading Module 'rwlpsdio.dll' (0x9E438000) at address 0xA7C90000-0xA7D47000 in Process 'NK.EXE' (0x87FDFAD0) PB Debugger Unloaded symbols for 'rwlpsdio.dll'

    9159 PID:400002 TID:2920006 OSAXST1: >>> Loading Module 'rwlpsdio.dll' (0x9E460EF8) at address 0xA8530000-0xA85E7000 in Process 'NK.EXE' (0x87FDFAD0)
    PB Debugger Loaded 'RWLPSDIO.DLL', no matching symbolic information found.
       9165 PID:400002 TID:2920006 Warning! Kernel DLL 'rwlpsdio.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside D
       9167 PID:400002 TID:2920006 DEVICE!InitDeviceContent: can not Init Device content for 'Drivers\BuiltIn\RSIMON,error code 2404'
       9168 PID:400002 TID:2920006 Pine1: +NDL_Init
       9169 PID:400002 TID:2920006 LoadMiniport: RegPath \Drivers\SDCARD\ClientDrivers\Custom\MANF-041B-CARDID-0201-FUNC-1
       9169 PID:400002 TID:2920006 LoadMiniport: Tokenizing instance information: RWLPSDIO:RWLPSDIO1 
       9172 PID:400002 TID:2920006 LoadMiniport: Miniport instance path \Comm\RWLPSDIO1\Parms 
       9173 PID:400002 TID:2920006 LoadMiniport: Storing ActiveKey Path Drivers\Active\18 
       9174 PID:400002 TID:2920006 DriverEntry!!!!!!!!!!!!!
       9175 PID:400002 TID:2920006 Loading RedPine Ganges SDIO WLAN driver VER-3.2.12.1
       9176 PID:400002 TID:2920006 +DriverEntry
       9176 PID:400002 TID:2920006 DriverEntry: Master opps is A85E0D50
       9177 PID:400002 TID:2920006 ganges_fill_miniport_structure: Calling NdisMRegisterMiniportDriver...


    We have observed that in the last case, the driver loaded twice, in the first time, the scenario is same as the case 1 but when the driver loads in the second time, it loads accurately.

    Is the driver is not unloaded properly and releases the SDIO interface.??

    Or some other issue??

    Is this the responsibility of wifi driver to take care of SDIO interface??

    Friday, April 3, 2015 5:57 AM

All replies

  • Hi,

    You should try contacting the binary vendor. Does the WiFi module have an external power source?. This might keep it on even during reset. 

    Is the driver is not unloaded properly and releases the SDIO interface.??

    Or some other issue??

    Is this the responsibility of wifi driver to take care of SDIO interface??

    Both seem likely. The driver would have been developed to use SDBus APIs.

    Regards,

    Balaji. 

    Friday, April 3, 2015 8:23 AM
  • Dear Balajitrv,

    Thanks for reply!!!!

    No, the wifi moudle is not using any external power source.

    We are already in the touch with the vendor. I just want to confirm the issue, either it is from driver side or BSP side. If it from BSP side then only we have to take care about that and if not then definitely, its the vendor responsibility to implement the functionality in the driver so that the issue can be resolved.

    But any how, its not confirmed and I am putting efforts to dig out the source...

    Friday, April 3, 2015 9:24 AM