RV1103 based project

  • Hello, our product 1103 does not come with a Wi-Fi module. We have tested the compatible external Wi-Fi module and found that it would interfere with the SD card interface. We have not tested the Wi-Fi module of W600 either. We have also not tested the other 1103 model which is not configured with a Samba server by default. Based on these reasons, I suggest you choose our 1106 series of products. This is just a few of my suggestions, and I hope they can be helpful to you.
  • Hello! I’ve encountered a similar issue with the RV1103 chip. Previously, I was developing on RV1126 and RV1109 chips. Now that I need to develop more energy-efficient devices, I’ve run into this problem.

    I’m using a Luckfox Pico Plus board based on the RV1103 chip, and I wanted to connect an external AP6256 Wi-Fi module. I checked the kernel and Buildroot—I found the mainline drivers for this chip in the system and decided to proceed.

    I started studying the schematics; initially, an SD card is included there, which uses SDMMC0. But the RV1103 processor also has a second bus, sdmmc1, with all the signals necessary for the AP6256 module.

    As a result, I changed the kernel and Buildroot configurations, and also configured the DTSI for the AP6256 module. The main problem: I reflashed the board—the sdmmc1 bus started working, but when scanning, it doesn’t find a single device. I checked all the signals with a digital oscilloscope, including LPO—everything is in place, but the module doesn’t even reach initialization; it isn’t detected on the bus. At the same time, I didn’t disable sdmmc0—the SD card remained connected to that bus and there were no issues with it. Please advise—maybe I overlooked something, and I need to change something else in the system for this module to work. Or are there any hardware limitations when connecting the Wi-Fi module, even though the processor should support it?
    Attachments
    datasheet rv1103
    datasheet rv1103
  • Third-party module adaptation is not covered under our technical support scope, as we are unable to validate and support all available modules. We can only provide general guidance.

    For SDIO device detection, only CMD, CLK, and DAT0 are required. If these signals are confirmed to be normal but the module is still not detected, the issue is typically related to the module’s startup state—such as incorrect enable pin configuration or power supply problems.