even if you want to keep trying to find a solution , i would put in a ticket to get a replacement. put a link to this thread so they can read what you have tried. i have not seen a diagram of which pins are used for the oled. i think it is an i2c device, not positive though. but you could use male/female jumper wire to get the oled out of the expansion header to test components on reverse side of screen. i see a few traces from the pins but not well enough to determine which pin they are from.
OP wants to connect to some Wifi AP (a "router", some solar panel equipment, etc) which doesn't have Internet connection
using the web based Setup Wizard.
2nd step: he will choose that AP's network - set SSID, Security, Password and click Configure Wi-Fi.
Omega's response: Configuring ... and after a while ... Unable to connect to SSID Please try again
Meanwhile APCLI LINK UP, connection established, ifconfig OK, /etc/config/wireless OK although every Please try again attempt appends a record to the file.
It seems this config can be set manually by wifisetup or UCI or editing the /etc/config/wireless file - without problem.
I don't know - is this "reverse" config worse than the usual one (when that solar panel equipment's client connects to Omega's AP) or not?
i think b162 was causing a lot of issues so it was withdrawn. unless i am looking at the wrong list, b160 is the current newest firmware. this is the list that i'm using, http://repo.onion.io/omega2/images/
The i2cdetect doesn't work properly but you can still use the i2c on omega2. if you are looking for sample code to use MCP23017 you can find them over here MCP23017 python lib
I have been using Omega 2 i2c to control relay, read sensors and ADC without any problems.
Hope this helps.
@luz Maybe your system does use the environment; I've never seen it anything but blank and recall that trying to set things there didn't work for me, but I'm running a patched mediatek u-boot not an onion one.
It really depends what your demands are regarding WiFi.
If you can live with mediocre WiFi performance (for now), then use LEDE. You can build everything that is on the original Omega FW that way, except for the wifi driver. Onion uses a proprietary driver they can't publish, stock LEDE uses the fully open sourced, but not yet fully fine tuned, mt76 driver.
For all of my Omega2 based applications I built my own distro / FW image from LEDE, tailored to the use case. There is a learning curve to LEDE, but once you get a feel for it, it's a really nicely organized distro builder for tiny platforms.
For example you can start here, read about LEDE on their site and of course search this forum, which has a lot about custom FW builds.
In case anyone stumbled upon this issue or something related to this.
Since I do not have a linux machine, I decided to spin up a cheap 1cpu, 512MB ram, $5 digital ocean droplet to setup my toolchain and compile some code for the onion. The above issue occurred on a fresh ubuntu 16 and ubuntu 17 droplet. A friend did some googling and pointed out that these type of issues could be memory related and he was spot on.
After setting up 2GB swap space using this guide: Adding Space on Ubuntu the compile has completed successfully on both Ubuntu 16 and 17.
Hope this helps someone experiencing this frustration.
With regard to CC0 vs GPL, it may (not sure) be possible that you can incorporate CC0 code into a GPL project and license the result as GPL. However is it definitely prohibited to use GPL code literally or via derivation in something licensed CC0. That is because a CC0 offering of a combined result would not preserve the irrevocable obligation to make a GPL license grant for derivative works of your derivative, hence such use cannot be permitted.
With regard to documentation, since you are aiming for bare metal, the culprit for your specific difficulty is more Mediatek than Onion. I'm not sure if the Onion boards are perfectly documented, but that would be easy to reverse engineer, and besides, they'd be a bad choice of MT7688 platform, since you have access to neither the flash chip nor the JTAG pins without a very tricky operation of removing the shield can.