Luckfox Core1106 - GPIO1_A2 as normal GPIO

2026-07-20 21:20

Hi,

I'm developing a custom carrier board using the Luckfox Core1106 SOM.

I'm building my own firmware image based on the rv1106g-luckfox-pico-zero.dts device tree. Is this the correct DTS for the Core1106 module?

I've already modified several parts of the DTS to match my hardware, so making additional changes is not a problem if needed.

My main goal is to free GPIO1_A2 (pin 67 / Linux GPIO34) and use it as a normal GPIO output.

Currently, the DTS contains:

dts

Code: Select all

sdio_pwrseq: sdio-pwrseq {
    compatible = "mmc-pwrseq-simple";
    reset-gpios = <&gpio1 RK_PA2 GPIO_ACTIVE_LOW>;
};

wireless_bluetooth: wireless-bluetooth {
    BT,wake_host_irq = <&gpio1 RK_PA2 GPIO_ACTIVE_HIGH>;
};

I tried removing the pwrseq_simple control and driving GPIO34 manually from userspace. When I drive it LOW, both Wi-Fi and Bluetooth stop working until the board is rebooted.

My questions are:

1. Is rv1106g-luckfox-pico-zero.dts the correct DTS for the Core1106 SOM?
2. Is it possible to modify the DTS (or any other configuration) so that GPIO1_A2 can be used as a normal GPIO?
3. Or is GPIO1_A2 physically connected to the onboard Wi-Fi/Bluetooth module, making it impossible to use as a general-purpose GPIO?
4. If it is physically dedicated to the wireless module, should it be considered reserved and unavailable for user applications?

My objective is simply to determine whether this GPIO can be released by changing the software configuration, or whether the limitation is due to the hardware design of the Core1106 SOM.

Thanks!

2026-07-21 6:13

On the core1106, GPIO1_A2 is already connected to the enable pin of the wireless module. If it is used as a general-purpose GPIO, the wireless module will become non-functional.
Therefore, if you need to modify the device tree, it is recommended to base your changes on the device tree of the Luckfox Pico Pi, which serves as an application example for the Core1106.