@Enrico-Bermudez I had a similar problem after installing a cross-compiled image.
The way I got my Omega back to the standard image was as follows:
Downloaded the file omega-v0.0.5-b259.bin from http://repo.onion.io/omega/images/
Copied omega-v0.0.5-b259.bin to /tmp directory on my Omega
On the Omega, cd to /tmp
Run the command: sysupgrade omega-v0.0.5-b259.bin
This should have you back to a standard 0.0.5-b259 version of the Omega code image.
@Onion-Rings The firewall is currently configured to route traffic back and forth between the AP and the home wifi. To allow forwarding of packets between ethernet and AP, you first need to create a new network under /etc/config/network by adding the following block:
@Boken-Lin Thanks - that information clarifies things. Thanks :-)
Look forward to future developments in relation to generating Omega specific images - it would be a good thing - mainly to make life simpler.
however, i am now successfully building packages for the Omega which I can install using opkg so am currently happy with what we have :-)
Here's a picture of a dock with broken switch. The part pointed by the red arrow is where the switch has broken off. Can you try taking a pin, poke it a bit into the broken off part and pull it to the right.
Hi @Josh-Rosenthal, you can actually change the IP address of your Omega to something else to avoid conflict with your router. Just edit /etc/config/network, you should be able to find a block that looks like this:
Sorry - the list of usable pins was supposed to read "0, 1, 6, 7, 13, 14, 18, 19, 23, 26". These are also the only pins clickable in the Console's GPIO Tool, along with pins 8 and 9, which while clickable they resort to Direction: Output and - respectively - Value: 1 and Value 0. Are schematics for these modules available anywhere for the community? These would help immensely!
Thanks for the reply. The device must indeed have been running some processor-intensive stuff, though I don't know what! I have not yet figured out how to run anything yet, and the device was well past boot-up. Since the thing only acted weird that one time, I'll consider it a fluke.