The Omega2 Dash is a touch screen device based on the Omega2 platform.
This topic is for Omega2 Dash beta testers to track progress and share ideas.

Get Started

Follow instructions on the following GitHub repo to get started on using the Omega2 Dash
https://github.com/OnionIoT/Omega2-Dash

Bug report & Feature suggestions

Use the GitHub Issues page to report bugs or suggest features
https://github.com/OnionIoT/Omega2-Dash/issues

Become Beta Tester

If you would like to participate in beta testing this project you can apply here

Updates

Dec 6 2019 - Official Firmware Available

Official firmware for the Omega2 Dash is now available!

If you have a beta unit, follow these instructions to upgrade to the official firmware:

• Make sure your Omega2 Dash is connected to the internet
• Back up any files that you don't want to lose! The upgrade will erase everything on the filesystem
• Run the following commands:

cd /tmp
wget http://repo.onioniot.com/omega2/images/omega2dash-v0.3.2-b233.bin
sysupgrade -F -n -v omega2dash-v0.3.2-b233.bin

Dec 6 2019

We've put together an program that can serve as the starting for Omega2 Dash programs using the LittleV Graphics Library.

• Learn more about the example program here: https://github.com/OnionIoT/Omega2-Dash#littlevgl-example-program
• See the repo here: https://github.com/OnionIoT/lv_example

Out of the box it supports:

• The Linux Framebuffer - will draw to the Omega2 Dash display
• The XPT7603 touch input device on the Omega2 Dash
• A makefile and instructions to build it as an OpenWRT package
• A small demo

Use this to get started with your own lvgl programs!

Dec 5 2019

Displaying image files on the Omega2 Dash. Learn more here

Nov 6 2019

Compiled demo of LittleV Graphics Library with touch input. See how to run it on your Omega2 Dash [here]
(https://github.com/OnionIoT/Omega2-Dash#littlevgl-ui-demo)

Nov 4 2019

Running the Omega's terminal on the display:

Run sh > /dev/tty0 on your Omega2 Dash. Everything you type from then on will show up on the display and not in your terminal window.
Hit ctrl+c to exit.

you can check out this tutorial

https://onion.io/2bt-omega-bittorrent-machine/

You need to edit the file /etc/config/wireless
Under config wifi-iface sta
set option disabled '0' to option disabled '1'

reboot your omega2+ and it will not try to scan or connect to any WiFi.

@William-Scott

My only concern with using a FET as the power supply is depending on the model it may not supply enough pick current for the normal boot process. I like your suggested setup if we can find a FET that works in normal boot.

Breadboard dock would be a idea dock for the setup. would you mind coming up with a block diagram of the setup?

@György-Farkas

In our test we used a 1000uF polarized capacitor. The power supply is the one used in a the Expansion Dock. Check out the schematics here.

Here is another tutorial you an follow
https://onion.io/2bt-single-command-losantomega/

We have done some internal testing by manually adding a large capacitor between 3.3V and GND while the system is running to emulate a large load. This is enough to introduce a brownout.

What kind of setup do you have in mind so we can programmatically change input voltage?

@William Scott

We are happy to collaborate in coming up with an automated tests procedure. Doing it publicly here on the community is definitely the way to go. This way more people can contribute of rip the benefit of the test result.

Can you share what test setup you have in mind and specifically what input do you need from Onion side?

how are you connecting to WiFi? wifisetup command? Can you share you console log?

Nice project, we will get you on Onion news letter in the coming weeks and you will be able to get some free Omegas for being featured

Lately there has been a lot of discussions about the Omega2+ not being able to boot after unexpected reset. We did some digging and found a solution.

The Problem

In short here is what we have identified as the root of the issue.

• By default both the Omega2+ CPU and Flash memory boots from a 3 Byte address mode
• During boot loader the CPU upgrades both Flash memory and itself to a 4 Byte address mode in order to access higher memory addresses
• During an unexpected reset (brownout) the CPU resets but the memory remains in the 4 Byte address mode.
• The mismatch in the address mode prevent the CPU from booting normally.
• A power cycle at this point will reset the Flash memory back to 3 Byte mode and the system will boot normally

Here is a table summarizing different boot conditions:

Boot State	GPIO 6 (SPI CS1) State	CPU address mode	Flash address mode	Boot Result
Cold boot	Default (pull down)	3 Byte	3 Byte	Success
Hot boot	Default (pull down)	3 Byte	4 Byte	Fail
Cold boot	Pull Up	4 Byte	3 Byte	Fail
Hot boot	Pull Up	4 Byte	4 Byte	Success

The Fix

According to the above table we need to build a solution to have GPIO 6 pulled sown during cold boot and pulled up in at hot boot in order for the system to boot successfully in both conditions. The following circuit does just that.

• During a cold boot GPIO 11 starts as LOW
• GPIO 6 is reads LOW
• During boot the boot loader sets GPIO 11 High (Originally used to provide power to the user pushbutton on Omega2 docks)
• This will charge up the capacitor to 3.3V
• During an unexpected reset or hot boot, the capacitor will temporarily pull GPIO 6 High setting the CPU to boot from a 4 Byte address mode

Please let us know if this setup helps with your situation. We would also like to hear if anyone have came up with a software only solutions. So far we have not yet figured out a way to make the flash memory to cold boot from a 4 Byte address mode.

Here is the Flash memory data sheet for those who are interested in dig deeper MX25L25635E.pdf

Yes you can. The battery management chip on the power dock is smart enough to not over charge the battery.

@György-Farkas yes, Omega2S+ has the same spec as Omega2+ in terms of CPU, RAM and Flash

@Sebastien-Thiry
Seems like the version of motion you are using does not support direct video output . A simple workaround is to let motion output image series and then use ffmpeg to compile the images into a video afterwards.

Here is a some what related tutorial on capturing time-lapse video with Omega2 hope it helps
https://docs.onion.io/omega2-project-book-vol1/timelapse-camera.html

Here is how the final video looks like
https://vimeo.com/230518247

Here is a tutorial on how to expand Omega's storage with SD card or USB flash drive
https://docs.onion.io/omega2-docs/boot-from-external-storage.html

@CAP-33 Sorry I was wrong before, you shouldn't include http:// in ping. What happens if you run opkg update after ping is successful

If you don't need to use WiFi you can turn it off by editing /etc/config/wireless and change config wifi-iface 'sta' -> option disabled '0' to option disabled '1'

save the file and run wifi. This will stop the Omega form trying to connect to nearby WiFi

Usually when the Omega status LED is flashing that means it is still initializing. It will take a few minutes on the first boot.

Make sure when you run uci show system, you see system.@led[0].trigger='default-on'

You can't. But you can try USB to Ethernet adaptors they may work.

@Elther-Marco said in Serial Console pain...:

br-wlan: port 1(ra0) entered forwarding state

This message indicates your Omega is re-establishing connection to your router. You will lose internet for a few seconds. This might due to weak wifi signal.