@crispyoz:
Thanks for the short story.
I was on cellphone browser (still am).

When a company of the size of mediatek is unable to support Linkit boards, we must appreciate onion; for onion supports the current boards plus running a forum that we can meet.

I have the same level of respect for you today, as I was reading ur first help msg months back.

Thanks..

@LightSwitch :
I do not have Dash nor ADC Exp. Still, going though various docs makes me believe that ADC Exp should work with Dash. As per:
https://onion.io/omega2-dash-guide/

"The Omega2 Dash is compatible with the existing ecosystem of plug-and-play Omega2 expansions."

Please verify that i2c pins are configured for i2c (not for gpio), in the dash.

root@Omega-745F:/tmp# omega2-ctrl gpiomux get
Group i2c - [i2c] gpio (configured for i2c)
Group i2c - i2c [gpio] (configured for gpio)

If is is configure for gpio , change to i2c
root@Omega-745F:/tmp# omega2-ctrl gpiomux set i2c i2c

As per the docs:
https://docs.onion.io/omega2-docs/using-adc-expansion.htm, ADC exp can have 0x48 or 0x49 addresses(settable).

Please see if the i2cdetect reports ADC exp at either 0x48 or 0x49:

root@Omega-745F:/tmp# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Since Omega2 has only one I2C, trying to access a bus other than 0 fails.
root@Omega-745F:/tmp# i2cdetect 1
Error: Could not open file /dev/i2c-1' or /dev/i2c/1': No such file or directory

I have connected a device with address 0x27 to the I2C bus. But any compatible I2C device shall respond to the i2cdetect.

From the opkg file listing adc-exp and python3-adc-exp install different files:

root@Omega-745F:/tmp# opkg files adc-exp
Package adc-exp (0.3-2) is installed on root and has the following files:
/usr/bin/adc-exp
root@Omega-745F:/tmp# opkg files python3-adc-exp
Package python3-adc-exp (0.3-2) is installed on root and has the following files:
/usr/lib/python3.6/OmegaExpansion/AdcExp.py

/usr/bin/adc-exp is a script that makes use of the various programs installed by i2c-tools. adc-exp can be tried as the next step.

root@Omega-745F:/tmp# adc-exp -h shall provide various options.

Thanks ..

Hi all,

This is a continuation of sharing of ideas with @crispyoz under the topic:
https://community.onion.io/topic/4266/editing-updating-the-distfeeds-conf-file-through-terminal/24.

3xOmega2 (of which 2 are 2+ models) were used to test the WiFi hanging problem while booting.

1. 3xOmega2/2+ as above with docks

2. All three were configured as STA, another AP providing gateway service.

3. USB powered hub that can take the 5V supply from an external power supply. These devices have built-in power socket and the usual USB cable that goes to the computer for data exchange. The hub is powered using a 3A PS initially, that was later changed to 1A. All the Omegas were connected to the hub and booted and then powered-down using the "poweroff" command, keeping the dock's power on/off switch in ON position. This was to power all the Omegas at the same time by pulling out/re-inserting the USB power cable from/to the PS.

4. The CP2102s used in the dock would still be registered as ttyUSBx in the Linux system, even after issuing the poweroff command.

5. minicom running in a Linux station was used for the UART0 connectivity; any similar program can be used.

6. Pull the USB power cable from the PS (keeping the PS hot) and re-insert after a few seconds.

7. All the omegas are expected to complete the boot process as seen in this video:
   https://drive.google.com/file/d/1nrGuAQSY1XoJC86iTrtRMzCxPhrsQop3/view

8. After booting, outbound connectivity is checked and then poweroff command was issued. The USB power cable was pulled out and re-inserted on the PS end to repeat the cycle.

9. Try as many times until we get a WiFi initialization problem. WiFi initialization draws considerable amount of power and it can fail, if power supply is not able to provide enough power.

10.Finally, I "overloaded" the PS by connecting USB Drives(they do draw power,right?)to the dock. This gave a boot failure for one Omega2+, which is uploaded here: https://drive.google.com/file/d/12udCFFuTlSrgCTRREVB2k_jU-_pr9Ms8/view

Bottom line is, use a good PS that can stand load. I have done many many reboots with different PS (3.0, 1.5, 1.0 A) and
the boot failure for Omega (ttyUSB2) occurred when the supply voltage dropped below 4.8 volt.

If you want to interface a lot of devices, you would typically adopt mux/demux technique, with a middle-level "device aggregator".

See this: https://www.instructables.com/id/Tims-PCA9685-Controller

One side (the micro-controller -uC- facing side) is I2C, while the "physical device" facing side is PWM. The micro-controller talks to 9685 (device aggregator), which in turn would talk to the devices connected to its 16 channels.

Note that the above URL has Atmel 8-bit uC/Arduino as the "controlling platform". The point is that, we are making use of the I2C interface which is present in almost any uC .

Further, the data sheet of the 9685 provided in the above link:
https://cdn-shop.adafruit.com/datasheets/PCA9685.pdf says that, "The
PCA9685 operates with a supply voltage range of 2.3 V to 5.5 V and the inputs and outputs are 5.5 V tolerant". So, you can drive it using 3.3v.

Picking the the right hardware to meet a "specific requirement" is an art, that takes time to get anywhere near the mastery. Getting used to the "datasheet" is the basic requirement. Luckily, the Internet has tons of resources providing implementation details of various project.

crispyoz :
300 baud and then 1200 baud..? So lucky..
Read somewhere, it was the time Kevin Mitnick was doing his research .!

I was dialing into a terminal/access server situated in a data center with 256kbps backbone over G.703 copper. The days of redhat 5 (not RHEL)..

@kottes
Looks like os.system() is not passing the result of cmd to w.

Try this:

import subprocess
cmd = "cat /sys/class/leds/input3::numlock/brightness"
ret = subprocess.check_output(cmd, shell = True).strip()
if ret == b'1':
print("NumLock ON")

Thanks.

@jimbo8098
https://archive.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/
has the onion-omega images released on Tue Mar 15 18:48:22 2016

https://downloads.openwrt.org/releases/19.07.8/targets/ar71xx/generic/
has the onion-omega images realeased on Mon Aug 2 02:29:04 2021

The 18.06.x version is available from:
https://downloads.openwrt.org/releases/18.06.9/targets/ar71xx/generic/

Thanks.

@optech
Happy to know that the intial phase is over.

So, what is next?

https://github.com/OnionIoT/omega2-lmic-lorawan
-interfacing to Omega2 through SPI-I2C bridge,library supports SX1276/8)

https://www.seeedstudio.com/LoRa-E5-Wireless-Module-p-4745.html
-Cortex-M4+SX126X(ST Micro), Comes with factory loaded AT command fw,
supports ClassA/B/C, has built-in UART/ADC/I2C/GPIO.. & programmamable using ST CubeMX)

Or any other? Curious to know which is your pick..
(I was not aware of that this chirpy thing existed .. !!)

Thanks

@victoriano :
<<
prefer mainline distros over very specialised ones.
<<

Very true, and I totally agree..

At the same time, we have to look at the value a specific implementation brings into the table. If we consider, I2C is an abstraction of 2 GPIO pins (two pins are configured to work together, either at s/w level or h/w level) to from an I2C bus, that does indeed brings in some value.

ESPs do I2C at s/w level and their I2C is limited to 100kHz max from a core running at 160MHz, while the h/w implementation of AVR 328P can support 400kHz bus @16MHz.

To my knowledge, OpenWRT is focusing on WiFi routers while Omega2 is focusing on IoT and peripheral connectivity.

Thanks..

@evelina :
This was already reported here?:
https://community.onion.io/topic/4279/onion-2s-does-not-save-any-data?_=1601466555447&lang=en-GB

I guess you have followed @crispyoz 's recommendation to check custom pcb's circuit with the reference available at:
https://github.com/OnionIoT/Omega2/blob/master/Schematics/Omega2S-Reference-Schematic.pdf

There was another problem reported in the above thread, that files that you created were vanishing after reboot. Were you able to save your files properly after following @György-Farkas 's advice?

Pls post the outcome..

Coming back to this thread, "the inserted sd card is not recognized", I have TWO images for you.

1. The standard SD card interface
   

As you can see, there are 8 wires required

1. An SD card adapter that I use (the BIGGER pads makes it easy to solder)
   

Please get an adapter, solder the wires and connect your custom pcb, making sure that you follow connection provided in the above PDF. This would simplify the debugging.

Thanks..

@Kate
Pls try the sshfs extension, to see if that works for you.
MS always makes it "awesome"..

A:
Onion side
# onion os version (just FYI)
=== Version Info ===
Omega firmware: v0.3.2 b242
onion-os - 1.0.6-1

1: Set a passwd for the omega user to connect from your workstation over ssh, passwd is the easiest way.
# passwd

B:
Workstation side

1:
Install SSH FS extension for VSCode in the VS
https://marketplace.visualstudio.com/items?itemName=Kelvin.vscode-sshfs

$ ext install Kelvin.vscode-sshfs

or DL the vsix & add to VSCode
https://open-vsx.org/api/Kelvin/vscode-sshfs/1.25.0/file/Kelvin.vscode-sshfs-1.25.0.vsix

2:
SSH-FS shall create its own icon in the left panel, under "Soucre-Control","Extensions" etc. Click on it to setup the new ssh connection/credentials (IP, username, remote folder etc), pointing to omega.

3:
Click on the "Folder+:" icon under the new connection entry.
This will effectively add the remote folder to the current workspace. You will be
prompted for the passwd, if that was left blank in #2.

The connection also gives a shell prompt.

Any file that is created under the newly added "remote" folder shall be created physically under the remote folder. "Save" to apply code changes.

The plugins (C/++, Python etc) that you have installed in your WS works as usual,
while you code.

My workstation is Linux, so there was no need to install any ssh client. If you
are on Windows, putty might work. I have not tried it.. but I guess it would work,
since I see "putty" mentioned in the configuration page of #2.

Thanks..

@kottes
Looks like os.system() is not passing the result of cmd to w.

Try this:

import subprocess
cmd = "cat /sys/class/leds/input3::numlock/brightness"
ret = subprocess.check_output(cmd, shell = True).strip()
if ret == b'1':
print("NumLock ON")

Thanks.

@jimbo8098
https://archive.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/
has the onion-omega images released on Tue Mar 15 18:48:22 2016

https://downloads.openwrt.org/releases/19.07.8/targets/ar71xx/generic/
has the onion-omega images realeased on Mon Aug 2 02:29:04 2021

The 18.06.x version is available from:
https://downloads.openwrt.org/releases/18.06.9/targets/ar71xx/generic/

Thanks.

@MarshalllGG

Sorry, I don't use docker either..

To get to know compiling process in detail, would suggest the following book to anyone:
Advanced C and C++ Compiling by Milan Stevanovic

Thanks.

@Nil
PTHREAD_MUTEX_RECURSIVE_NP is not defined

~/staging_dir/toolchain-mipsel_24kc_gcc-7.3.0_musl/include/pthread.h
has line 38 as
#define PTHREAD_MUTEX_RECURSIVE 1

Thanks.

@optech
Happy to know that the intial phase is over.

So, what is next?

https://github.com/OnionIoT/omega2-lmic-lorawan
-interfacing to Omega2 through SPI-I2C bridge,library supports SX1276/8)

https://www.seeedstudio.com/LoRa-E5-Wireless-Module-p-4745.html
-Cortex-M4+SX126X(ST Micro), Comes with factory loaded AT command fw,
supports ClassA/B/C, has built-in UART/ADC/I2C/GPIO.. & programmamable using ST CubeMX)

Or any other? Curious to know which is your pick..
(I was not aware of that this chirpy thing existed .. !!)

Thanks

@optech
These parameters are added by me
GOOS=linux GOARCH=mipsle GOMIPS=softfloat \

Equivalent to:

$ CC= CXX=
etc. that we use while compiling .c, .cpp

As you have rightly pointed out, the following was the original command line:
go build $(GO_EXTRA_BUILD_ARGS) -ldflags "-s -w -X main.version=$(VERSION)" -o build/chirpstack-gateway-bridge cmd/chirpstack-gateway-bridge/main.go

By stock 19.07, I meant the "19.07 binary image" that we can download from openwrt download area, not the image that we build, even if we are using the build config + the same compiler/tools as openwrt used.

In my observation, the hello_world and the chirpstack-gateway-bridge will work with stock 19.07.7 if the softfloat option is used; not sure about other 19.07s.

Thanks.

@optech

In the Makefile, the "build" option has parameters:
<<<
.PHONY: build clean test package serve run-compose-test
VERSION := $(shell git describe --always |sed -e "s/^v//")

build:
@echo "Compiling source"
@mkdir -p build
GOOS=linux GOARCH=mipsle GOMIPS=softfloat go build $(GO_EXTRA_BUILD_ARGS) -ldflags "-s -w -X main.version=$(VERSION)" -o build/chirpstack-gateway-bridge cmd/chirpstack-gateway-bridge/main.go
<<<

Is that how you compile?

Try running the "chirpstack .." exe from Omega2's command line with -h or --help option under stock 19.07.
If that runs, then try running the exe under the custom build.

Thanks.

@optech
Ok. Let us start simple.
Are you able to cross-compile the "hello_world.go" and run it in the 19.07 Omega2 with GOARCH,GOOS parameters set as above ?

package main
import "fmt"
func main() {
fmt.Println("Hello, World!")
}

If not, you may want to try GOMIPS=softfloat or some other options in addition to those two. Once that thing prints \"Hello, World!\", try the same options to build chirpstack-gateway-bridge.

Thanks.

@optech
Can you pls replace the /opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge in your openwrt 19.07 with this file:
https://disk.yandex.com/d/C_6-fmcDtqXIGA and then try running it?

It is a zip file, that unzips to "chirpstack-gateway-bridge" exe.

Thank you.