Debugging of wifi module ar6102 in WinCE

Today I debugged an sdio wireless network card ar6102. Because the chip is onboard, I wrote an application.ProgramSimulate the insertion and unplugging of the wireless network card, then modify the sdhc driver, detect the simulated card insertion and unplugging Action sent by the application, and control the PWR and RST pins of the chip. Fortunately, after the change, you can use it. After simulating the insertion of the wireless network card through the application, the print information of the wireless network card driver is displayed on the Super Terminal, and the WiFi device, ar6k_sd1, is also displayed in the network connection of the control panel.

The Wireless AP used for testing is Cisco, And the encryption method is WPA-Personal. Based on the router settings, select the encryption method and enter the network key, as shown in.

Click OK to connect to the Wireless AP normally, but the signal strength is extremely low, which may be related to the antenna.

The IP address of ar6k_sd1 after connecting to the AP is shown in.

 

 

 

 

 

Shows the logs in the connection process.

The following describes the debugging methods. We know that the SD card driver under wince is mainly composed of three parts: bus driver, host controller driver and client drivers. Shows the relationship between the three and applications and the operating system.

We can see that the bus driver is an abstract management layer between the client driver and the host controller driver. It provides a standard API for the client driver to run on different wince systems. The real existence of the bus driver is s5. DLL. This partCodeIt is provided by Microsoft and has nothing to do with platforms and applications. Therefore, no modification is required during driver porting.

The client driver controls and operates the SD device through the abstract interface provided by the bus driver. The client driver types of sdio in wince include memory, Bluetooth, GPS, and WiFi. These drivers vary depending on the device type. When an SD device is inserted, the bus driver loads the corresponding client driver according to the Registry configuration. The client driver is generally provided by the module vendor and can be used without modification.

The host controller driver is a hardware abstraction layer between the bus driver and the host controller. This part of the Code varies with the platform and chip. When debugging the SD device, modify the device accordingly.

According to the above analysis, when debugging the ar6102 driver, only the host controller driver code is modified. In fact, the factory did not provide the client driver code, but only gave the DLL file.