Hi Team,
My platform is TI AM62x processor . Linux kernel is 6.1.33, driver version is v5.2.1.2, use the sdio interface
After I insert the driver, the initialization function returns 0, indicating that there is no error in initialization.
But the probe function did not run . What could be the reason?
Hi St,Thank you for posting your question online.Could you please share more information?Are you working with a DA16200 Dev Kit or a custom board?Have you followed our UM-WI-059 DA16200 DA16600 Linux Driver Getting Started Guide (renesas.com)?Could you please share the full UART logs?Could you please probe a logic analyzer on the SDIO lines to get an understanding of the communication?Best Regards,OV_Renesas
The UART log after startup is as follows:
Hi St,Thank you for the replies.Yes, for the UART0 you will need 230400 Baudrate. This is mentioned on UM-WI-056 DA16200 DA16600 FreeRTOS Getting Started Guide (renesas.com), on section 4.4.1 Configuring DA16200/DA16600 Serial debug Interface.
st said:The UART log after startup is as follows:
st said: I have a question to confirm: Is the Flash erase operation mentioned in the Start Guide mandatory?
I have a question to confirm: Is the Flash erase operation mentioned in the Start Guide mandatory?
Based on the UART0 logs you are using a really old SDK version (which is not supported0 and should have been erased in order to use the Linux Driver.The ThreadX SDK has not been supported since 2020-2021. We officially only support the FreeRTOS SDK v3.2.x.x , the Matter SDK and the Linux Driver.Please follow the steps on 4.1.1 How to Erase Flash and make sure you issue the following:
sflash erase 0 400000
Hi,
1. After erasing the Flash, do we need to rewrite the SDK into it? Currently, after erasing the Flash, the system reports a "Boot Err" during startup.
2. The RZ/G2L Linux System mentioned in the Starter Guide is the system build environment you are using, correct? If we use our own Yocto environment, which configurations do we need to port?
3. After following the kernel configuration steps in the documentation, I compiled rswlan.ko. Although the system indicates that the firmware has been loaded after module insertion, the device's probe function still hasn't been executed.
rswlan.ko
As shown below, the driver successfully registered DA16200_sdio_fw_download and DA16200_sdio, with both functions returning rtn as zero, indicating that the registration was successful. However, the probe function was invoked when registering sdio_fw, but it was not called when registering sdio.
DA16200_sdio_fw_download
DA16200_sdio
rtn
probe
sdio_fw
sdio
Hi ST,Thank you for the reply.I am checking on this with the Wi-Fi Support Team and I will get back to you as soon as possible.I have also reached out to you directly, please check your PM.Best regards,OV_renesas