Hello,
I'm developing an carrier board for the core1106, can I use these two GPIO4_C0(pin 26) and GPIO4_C1(pin 27) as normal analog input (1.8v) ?
I’ve seen in other discussions that one of these pins must always be pulled up. Could you please clarify why this is required?
Analog input - CORE1106 - C0 and C1
In our provided firmware images, GPIO4_C0 is configured as the BOOT key. Since it is not pulled up by default, it may randomly enter flashing mode under certain conditions.
You can modify the U-Boot configuration to release GPIO4_C0 for other purposes. However, after doing so, entering flashing mode later will become more complicated.
You can modify the U-Boot configuration to release GPIO4_C0 for other purposes. However, after doing so, entering flashing mode later will become more complicated.
I’m already actively using the SDK to configure and change other aspects of the system.Crocodile wrote: ↑2026-04-07 2:55 In our provided firmware images, GPIO4_C0 is configured as the BOOT key. Since it is not pulled up by default, it may randomly enter flashing mode under certain conditions.
You can modify the U-Boot configuration to release GPIO4_C0 for other purposes. However, after doing so, entering flashing mode later will become more complicated.
Is it possible to change the boot button to another GPIO through the SDK in order to free up the ADC?
I saw in another post that the boot pin was pin 45.
I saw in some forums that for this kind of board we can use the reboot loader command to reboot directly into maskroom mode. Unfortunately, the current kernel configuration was freezing during reboot commands.
After debugging extensively using UART logs, I discovered the problem was the restart-poweroff driver conflicting with the syscon-reboot-mode driver, preventing proper boot mode register handling.
To solve it, I modified three device tree files by commenting out or removing everything related to the restart-poweroff driver:
rv1106g-luckfox-pico-zero.dts
rv1106-evb.dtsi
rv1106.dtsi
Since the SDK doesn't provide a specific DTS file for the core board, I'm using the Pico Zero one, which is the board I use for testing my software before deploying to the core1106.
The nice part about these changes is that now the reboot and poweroff commands work normally, halting and rebooting as expected
I'm still searching for how to free the ADC port and change the boot button to another GPIO. If you have any ideas on how to do that, it would be really appreciated.
After debugging extensively using UART logs, I discovered the problem was the restart-poweroff driver conflicting with the syscon-reboot-mode driver, preventing proper boot mode register handling.
To solve it, I modified three device tree files by commenting out or removing everything related to the restart-poweroff driver:
rv1106g-luckfox-pico-zero.dts
rv1106-evb.dtsi
rv1106.dtsi
Since the SDK doesn't provide a specific DTS file for the core board, I'm using the Pico Zero one, which is the board I use for testing my software before deploying to the core1106.
The nice part about these changes is that now the reboot and poweroff commands work normally, halting and rebooting as expected
I'm still searching for how to free the ADC port and change the boot button to another GPIO. If you have any ideas on how to do that, it would be really appreciated.