<![CDATA[[Onion Omega 2S] Boot failing/stuck for "minimal connection" of module (UART0+VCC+GND)]]>I have an "Onion Omega 2S" module (no dock, breadboard version etc. - just the bare module itself) and used the "Reference Schematics" here and here (github.com/OnionIoT/Omega2) to come up with a basic "circuit":

Bildschirmfoto 2021-12-27 um 12.44.35.png

As a USB<->UART bridge I'm using a cheap FT232RL

But I've two main problems:

  1. It does not always boot after power-up -- In the case it does not boot, it prints \0 characters to the UART at 115200 BAUD. In the reference docs I read that "GPIO_12 / UART_TXD0 must be floating or pulled-down". Maybe this is here the case, because my USB<->UART bridge pulls it high to early? This would be supported by the fact, that if I wait a specific time after plugging it in via USB and then open the serial monitor it always works. Too fast or slow will cause the \0-print-issue. Can somebody confirm this? Are there any further workarounds to circumvent this?
  2. It get's stuck when booting -- When it starts up, it loads the kernel and starts executing fine (Onion Omega2 UBoot Version: 4.3.0.3, Image Name: MIPS OpenWrt Linux-4.14.81). But after the line MTK MSDC device init. it get's "stuck" and prints \0 characters forever. I digged a little bit around and found this kernel "patch" indicating to me that it is something related to SD-Card memory etc., so I pulled GPIO_23 or SD_CD to VCC as the datasheet specified to indicate no SD-Card. But this does not help me. Any ideas on that?

Bildschirmfoto 2021-12-27 um 12.29.32.png

Merry Christmas!

]]>http://community.onion.io/topic/4633/onion-omega-2s-boot-failing-stuck-for-minimal-connection-of-module-uart0-vcc-gndRSS for NodeSun, 09 Aug 2026 22:25:02 GMTMon, 27 Dec 2021 11:49:50 GMT60<![CDATA[Reply to [Onion Omega 2S] Boot failing/stuck for "minimal connection" of module (UART0+VCC+GND) on Mon, 27 Dec 2021 11:51:31 GMT]]>I have an "Onion Omega 2S" module (no dock, breadboard version etc. - just the bare module itself) and used the "Reference Schematics" here and here (github.com/OnionIoT/Omega2) to come up with a basic "circuit":

Bildschirmfoto 2021-12-27 um 12.44.35.png

As a USB<->UART bridge I'm using a cheap FT232RL

But I've two main problems:

  1. It does not always boot after power-up -- In the case it does not boot, it prints \0 characters to the UART at 115200 BAUD. In the reference docs I read that "GPIO_12 / UART_TXD0 must be floating or pulled-down". Maybe this is here the case, because my USB<->UART bridge pulls it high to early? This would be supported by the fact, that if I wait a specific time after plugging it in via USB and then open the serial monitor it always works. Too fast or slow will cause the \0-print-issue. Can somebody confirm this? Are there any further workarounds to circumvent this?
  2. It get's stuck when booting -- When it starts up, it loads the kernel and starts executing fine (Onion Omega2 UBoot Version: 4.3.0.3, Image Name: MIPS OpenWrt Linux-4.14.81). But after the line MTK MSDC device init. it get's "stuck" and prints \0 characters forever. I digged a little bit around and found this kernel "patch" indicating to me that it is something related to SD-Card memory etc., so I pulled GPIO_23 or SD_CD to VCC as the datasheet specified to indicate no SD-Card. But this does not help me. Any ideas on that?

Bildschirmfoto 2021-12-27 um 12.29.32.png

Merry Christmas!

]]>http://community.onion.io/post/24195http://community.onion.io/post/24195Mon, 27 Dec 2021 11:51:31 GMT<![CDATA[Reply to [Onion Omega 2S] Boot failing/stuck for "minimal connection" of module (UART0+VCC+GND) on Wed, 29 Dec 2021 10:59:25 GMT]]>Hi，1. you can add a pull-up resistor to the Omega2S HW_RST pin and add a pull-down resistor to the SW_RST pin. 2.the current supply of VCC need at least 500mA.

]]>http://community.onion.io/post/24199http://community.onion.io/post/24199Wed, 29 Dec 2021 10:59:25 GMT<![CDATA[Reply to [Onion Omega 2S] Boot failing/stuck for "minimal connection" of module (UART0+VCC+GND) on Sun, 02 Jan 2022 17:39:47 GMT]]>@JeffZhou Thanks a lot, for your response!

I think that the 2nd point (VCC current) was the root cause of my issues: I used an AWG30 wire for all VCC lines which was too thin to carry the current.

Regarding the UART <-> USB-Bridge the issue still persists, it requires a little fiddling: opening the serial connection after counting to three after plugging in. Then it worked booted in 100% correctly so far.

Best Regards!

]]>http://community.onion.io/post/24207http://community.onion.io/post/24207Sun, 02 Jan 2022 17:39:47 GMT