Omega Talk

How to Ask for Help on this Forum

Lazar Demin — Fri, 10 Jul 2020 18:37:38 GMT

HOW TO ASK FOR HELP

This community forum is a place for Omega2 users to share knowledge and help each other out.

Before asking for help

Try looking at the Technical FAQs section to see if your issue is frequently encountered.
If not, try searching the forum to see if other users have experienced something similar in the past.

Making a Post

If you can't find any relevant posts, feel free to start a new thread. Keep in mind that if you're asking for help, you will get better results if you do a good job explaining your issue or question well.

Other community users cannot offer helpful feedback if we cannot fully understand the issue you're experiencing or the context behind it.

A Good Post Includes...

To properly explain your problem and give context, here are some ideas of what you should include in your post:

Product being used
- For Omega2, Omega2+, Omega2S, or Omega2S+, please provide some details about the carrier board being used. Is it an Omega2S Dev Kit, an Omega2 Dock, or is it custom hardware?
Firmware version
- If it's custom firmware, let us know what it's based on (for example Onion's OpenWRT fork or vanilla OpenWRT, and which release)
Description of the issue and context
Expected Behavior
Observed Behavior
Steps to reproduce the issue
What's been attempted to resolve the issue
What kind of help are you looking for?
Attachments (if any)

Onion Community Guidelines & Terms of Service

György Farkas — Sat, 04 Jul 2020 09:07:49 GMT

@Lazar-Demin Would it be possible to pin your HOW TO ASK FOR HELP post?

Help with bricked Omega 2+

Florian Heigl — Mon, 02 Mar 2026 01:18:00 GMT

@Zendog said in Help with bricked Omega 2+: @Lazar-Demin thanks! I thought as much. Many thanks for looking into this either way. Luckily, I was a KS backer of the Onion Omega 2+ and got a bundle of 8 of them off the back of enjoying having bought 2 of the first Omegas to be released. 1 down, 7 to go... So, as a parting shot, can you please point me in the right direction? I plan to upgrade all the others and hopefully not run into the same issues. Should my upgrade process for each be: Upgrade uboot image first with the latest version, then Upgrade the firmware Omega .bin file with the latest version ... Then reboot. That's the right thing to do to get it to the latest version, right? Do both of the above points in one go or reboot after uboot is update? for the record/clarity, you can sysupgrade into the new image from an old Omega2 firmware. I tried today, using the 'beta firmware' instructions via archive.org (couldn't find any working link otherwise) https://web.archive.org/web/20250213213028/https://documentation.onioniot.com/firmware/installing-firmware/ used that with the latest 23.05 image from the repo http://repo.onioniot.com/omega2/images/openwrt-23.05/ (no https is available)

Help Crash GPIO43

luz — Wed, 25 Feb 2026 23:57:15 GMT

@jossvall said in Help Crash GPIO43: why does it restart with version 18, but with version 23 the board remains off? My guess was that the drop might be a bit less with version 18, just because the current draw of the SoC in idle might be different due to different (or less) things going on in v18 vs v23. Do you actually see the same size voltage drop when running the device with v18? Is there a parameter that allows the Omega to restart in case of a voltage drop or to shut down? I am not aware of any configuration, so I think the voltage threshold that makes the SoC reset is fixed, but I found nothing that would detail it in the MT7688 datasheet.

Question Regarding Security Updates and CRA Compliance

DocHardinger — Fri, 13 Feb 2026 08:31:00 GMT

Hi everyone especially @Zheng-Han ,

I have a question regarding security updates for the Omega2S.
Currently, the device is being shipped with OpenWrt 23.05.x. As far as I understand, this branch has reached end-of-life upstream and no longer receives ongoing security updates from the OpenWrt project.
Since Onion Corporation is selling products into the EU market, I would like to ask how this aligns with the requirements of the Cyber Resilience Act, which requires manufacturers of products with digital elements to provide security updates for a defined support period.

Specifically:
Are there plans to provide ongoing security patches for the Omega2S firmware?
Will there be an upgrade to a currently supported OpenWrt release?
Is there an official security support timeline for the Omega2S?

I’m asking purely from a security and compliance perspective, as long-term patch availability is becoming increasingly important for commercial deployments within the EU.

Thank you for any clarification.

How to Write uboot Environment Variables on system runtime?

mulu553 — Thu, 08 Jan 2026 07:54:48 GMT

@luz Yes, I used the openwrt-imagebuilder-wrapper from onion's GitHub repo to generate my own customized firmware. Thank you very much for your suggestion.

⭐️ New U-Boot v2025.04 available for the Omega2 ⭐️

Moonshiner — Sun, 21 Dec 2025 15:42:50 GMT

@Lazar-Demin ethernet and serial links are invalid, - "Page Not Found"

Omega 2S+ "No Space Left on Device" after Ethernet connection error

MK — Thu, 11 Dec 2025 13:20:27 GMT

Has anyone got an idea?

OpenWrt 24.10.2

luz — Sun, 07 Dec 2025 14:11:01 GMT

@crispyoz regarding user space DT overlays: there's a much more convenient solution by now (actually, it seems to have existed for a long time already), the dtbocfg loadable kernel module by Ichiro Kawazome, which I packaged for OpenWrt here. The only thing required for that to work is that the kernel is compiled with CONFIG_OF_OVERLAY=y. Much easier than patching the kernel sources. This all works fine, but I have a general problem with 24.10 on the MT7688 (not on other targets): it consumes waaaay to much CPU time doing I/O, and I could not yet track it down. Performance is normal for everything else, but when there is only a bit more of I/O going on, say a network download AND a serial output streaming some data, it sometimes stalls for seconds. I have no idea yet what that is. Does 24.10 run smoothly for you?

Hardware Reset issue on v23.05.3

luz — Sun, 07 Dec 2025 13:58:13 GMT

@crispyoz, @matiaslao: sorry for not responding. Unfortunately this forum does not have an RSS feed, so I sometimes forget checking regularily. Anyway, I hope your reset issue could be sorted out in the meantime. If I remember the difference between v23.5 and older versions correctly, the broken-flash-reset in the device tree has become a standard feature of the mtd/spi-nor subsystem, while before the workaround was a specific patch with no DT option, and implemented differenty. In the new driver (if I am reading drivers/mtd/spi-nor/core.c correctly), the chip is kept in 4-byte mode most of the time, and only reverted to 3-byte when the device is removed or a shutdown occurs. echo c >> /proc/sysrq-trigger crashes the kernel immediately, so the spi-nor driver will not get a chance to switch back to 3-byte and the reboot will fail. The old workaround probably switched forth and back between 4-byte and 3-byte for every flash access, so a HW reset or kernel crash while no flash access was actually ongoing was fine.

Red light after firmware upgrade (oupgrade)

crispyoz — Thu, 11 Sep 2025 04:20:43 GMT

@javadesigner You have there an Omega2Pro, this device uses the Omega2S+ SoC on a board that also incorporates additional 8K storage LiPO etc. The LED behaviour you report is a known behaviour of this device, you need to update u-boot to version 1.1.3 or above. Here is the documentation on how to do this.

OnionOS v0.0.1 Upgrade

Michael Vowles — Wed, 03 Sep 2025 10:10:05 GMT

@jimbo8098 sorry for digging up old thread but did you update using 18? If so, how?

how to properly remove python2 after pip installed it

crispyoz — Fri, 15 Aug 2025 09:30:45 GMT

@magouero opkg is not particularly sophisticated which is why OpenWrt are changing over to APK package manager. I would do it this way: opkg remove python3 --force-removal-of-dependent-packages opkg remove python --force-removal-of-dependent-packages Then opkg list 'python' to see if there is anything left to clean up. See the docs https://documentation.onioniot.com/packages/opkg-package-manager ```

Omega 2+ with Arduino Dock 2

magouero — Sun, 03 Aug 2025 10:56:07 GMT

@Lazar-Demin Hello, i have the same boards and probably will have the same issue than him soon. What about the last part of his question: "Is it necessary to use it to communicate with the Arduino Dock 2?" if not, how to ?

Onion bricked? SQUASHFS error...

naveen_kumar — Fri, 25 Jul 2025 04:51:28 GMT

@Lazar-Demin always my web recovery ended up like HTTP upload is complete. Upgrading... FIRMWARE UPGRADING * DO NOT POWER OFF DEVICE! * .................................................................................................................................................... .................................................................................................................................................... blocksize write incorrect block#=0! Error: HTTP ugrade failed! Bringing Eth0 (10/100-M) up... HTTP server starting at 192.168.8.8 ... HTTP server is up and running. Boot Linux from Flash NO RESET PRESSED. Booting image at bc050000 ... Image Name: MIPS OpenWrt Linux-4.14.81 Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1617567 Bytes = 1.5 MB Load Address: 80000000 Entry Point: 80000000 Verifying Checksum ... Bad Data CRC Any Idea How to solve this. I have used 5V 3A adaptor and 3.3.V LDO with 800mA current. 100uF cap to manage the current spikes.

Segmentation fault in Omega2P+Python Library installations

naveen_kumar — Thu, 24 Jul 2025 16:19:27 GMT

@Zheng-Han I did one experiment. I did firstboot -y sync reboot As I understand, the device is in factory reset. After reboot, I login. Installed python-light python-pip I tested Python command root@Omega-236B:~# python Python 2.7.18 (default, Sep 09 2024, 15:48:40) [GCC 7.3.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. reboot I tested the python command BusyBox v1.28.3 () built-in shell (ash) / __ ___ ()__ ___ / __ _ _ ___ ___ ____ _ / // / _ / / _ / _ \ / // / ' / -) _ / _ / _/////___//// _////_/_, /_,/ W H A T W I L L Y O U I N V E N T ? /__/ Ω-ware: 0.3.4 b259 root@Omega-236B:~# python Segmentation fault root@Omega-236B:~# I got segmentation fault. I did not install any extra libraries. Any Idea why it is happening.

Omega2P Boot Issue

naveen_kumar — Mon, 21 Jul 2025 12:53:04 GMT

I have onboard Ethernet. This is custom board. all My devices are working. Few are having this issue. I get some weird Memory issues. I am not able to upload new firmware too. HTTP upload is complete. Upgrading... FIRMWARE UPGRADING * DO NOT POWER OFF DEVICE! * .................................................................................................................................................... .................................................................................................................................................... blocksize write incorrect block#=125! Error: HTTP ugrade failed! Bringing Eth0 (10/100-M) up... HTTP server starting at 192.168.8.8 ... HTTP server is up and running. Web failsafe mode aborted! I suspect this issue is related to Memory.

Avahi demon removed in 23.05

Lazar Demin — Thu, 10 Jul 2025 22:15:04 GMT

Circling back here: avahi daemon is now included in the beta firmware as of version 23.05.3-20250709!

Can't find bluetooth packages

Lazar Demin — Fri, 04 Jul 2025 16:17:50 GMT

@zital-debian Support for the bluetooth packages was dropped in firmware v0.3.0. If you would like to use them, try installing an older firmware on your Omega. I recommend v0.2.2-b200 from http://repo.onion.io/omega2/images/

Add DTS for PCA9635 LED Driver

thomasderbauer — Thu, 26 Jun 2025 11:35:25 GMT

So I figured it out by now. It didn't really work with overlay but using the main .dtsi file worked. pca9635.dtsi &i2c { pca9635@8 { compatible = "nxp,pca9635"; reg = <0x08>; #address-cells = <1>; #size-cells = <0>; status = "okay"; led@0 { label = "led0"; reg = <0>; default-state = "off"; }; led@1 { label = "led1"; reg = <1>; default-state = "off"; }; led@2 { label = "led2"; reg = <2>; default-state = "off"; }; led@3 { label = "led3"; reg = <3>; default-state = "off"; }; led@4 { label = "led4"; reg = <4>; default-state = "off"; }; led@5 { label = "led5"; reg = <5>; default-state = "off"; }; led@6 { label = "led6"; reg = <6>; default-state = "off"; }; led@7 { label = "led7"; reg = <7>; default-state = "off"; }; led@8 { label = "led8"; reg = <8>; default-state = "off"; }; led@9 { label = "led9"; reg = <9>; default-state = "off"; }; led@10 { label = "led10"; reg = <10>; default-state = "off"; }; led@11 { label = "led11"; reg = <11>; default-state = "off"; }; led@12 { label = "led12"; reg = <12>; default-state = "off"; }; led@13 { label = "led13"; reg = <13>; default-state = "off"; }; led@14 { label = "led14"; reg = <14>; default-state = "off"; }; led@15 { label = "led15"; reg = <15>; default-state = "off"; }; }; }; placed in the build folder /home/thomas/openwrt-wallcontroller/target/linux/ramips/dts and lastly adding an include to the omega .dtsi mt7628an_onion_omega2.dtsi #include "mt7628an.dtsi" #include "pca9635.dtsi" #include #include

web page broken link

Lazar Demin — Thu, 12 Jun 2025 17:58:35 GMT

Hi @Dennis-German this is actually for the original Omega. You can find the wiki from the original omega days at https://onioniot.github.io/wiki/ The specific link you're looking for is https://onioniot.github.io/wiki/Tutorials/Bluetooth-Streaming-Audio

Relay Expansion replacement?

Lazar Demin — Tue, 03 Jun 2025 14:37:25 GMT

@Shimon-Mor No plans to release a new Relay Expansion. Any 3.3V compatible relay will work with the Omega2!

Python3 is only 3.6

Lazar Demin — Tue, 03 Jun 2025 14:36:29 GMT

@Ravi please avoid resurrecting super old posts See the response here: https://community.onion.io/topic/5115/unable-to-upgrade-python3-6-to-python3-7-on-omega2-device/2

Unable to upgrade python3.6 to python3.7 on omega2+ device

Lazar Demin — Thu, 22 May 2025 19:55:32 GMT

Hey @Ravi, you can try using the openwrt-23.05 beta firmware, it supports python 3.11 First read about the key changes in the beta firmware, and then you can follow the procedure to installi the beta firmware Documentation specific to the beta firmware can be found at: https://documentation.onioniot.com/

Omega2 LTE with openwrt 23.05 gnss read from /dev/ttyUSB1

Michael Bock — Thu, 22 May 2025 15:37:52 GMT

I have the Omega2 LTE running new openwrt 23.05.3 firmware and I have successfully made a package with a c-program to read gnss positions and write these to a sqlite3 database.
I had this program working fine before on the old firmware reading from /dev/ttyUSB1

On the new firmware, /dev/ttyUSB1 is not assigned
(I can see /dev/ttyUSB2 assigned as the control interface)

I have installed the omega2-lte-base package and o2lte gnss enable looks like its working.
I have tried to install the ugps package, but i does not seem to make any difference.

how can i get reading from /dev/ttyUSB1 to work (like on the old firmware) ?

thanks

Michael

23.05.3 iwinfo scan disconnects AP

DocHardinger — Mon, 12 May 2025 07:49:16 GMT

@crispyoz Oh, okay — so you really did physically fall into a hole and got hurt? Luckily, you managed to get out again! Yes issue is still there but we ignoring it for now and see if later updates will solve it. Most of the time we only need connection to an mobile phone and that is no problem. And for the other issue were continously pinging the AP to keep the connection as a workaround.