Posts made by György Farkas

@Cartographer
http://repo.onion.io/omega2/images/
http://repo.onioniot.com/
Both links are OK. (2020-09-28 16:35:00 CEST)
Firefox Web Browser 80.0.1 (64-bit) on Ubuntu 18.04.5 LTS

You wrote

I need a copy of the firmware

Which one?

@crispyoz
Omega2 Dash now available! You wrote proudly:

I was lucky enough to join the Beta for this product.

@crispyoz Because I know that you have an Omega2 DASH board.
Thank you.

@LightSwitch @crispyoz
Please let us know the output of an i2cdetect -y 0 command on your Omega2 DASH board without an Onion ADC Expansion board.

@Lazar-Demin

ADC Expansion
The ADS1115 analog-to-digital controller chip has one address pin (ADDR) that configures the I2C address of the device.
On the Onion's board this pin can be connected to GND or VDD with the Address Switch.

ADS1115 I2C device address
A6 A5 A4  A3 A2 A1 A0
 1  0  0   1  0  0  ?
 1  0  0   1  0  0  0   0x48 (ADDR = GND)
 1  0  0   1  0  0  1   0x49 (ADDR = VDD)

# -----------------------------------------------------------------------------------------------------------------------------------------

Omega2 DASH
The XPT7603 resistive touch screen controller chip (MSOP10 package) has one address pin (A0) that configures the I2C address of the device.
According to Onion's schematic this pin is NC (??? - so the schematic may be wrong).

XPT7603 I2C device address (MSOP10 package)
A6 A5 A4  A3 A2 A1 A0   
 1  0  0   1  0  0  ?
 1  0  0   1  0  0  0   0x48 (A0 = GND)
 1  0  0   1  0  0  1   0x49 (A0 = VDD)

If the above is correct users should be warned a possible I2C address conflict.

@victoriano This '*** Warning - ...' is related to U-Boot only.
Please read this post and a few older post(s)
or The DENX U-Boot and Linux Guide

@apoorvamanjunath Are you really running some OpenWrt 19.07 based stuff on your Omega2 Pro?

@evelina You should separate your issues.
You have an Onion2S+ module on your custom board, your firmware is v0-3-2 b239.

Your filesystem is corrupted.
These are the outputs of a few commands of a well working Omega2+ with FW v0-3-2 b239:

# Omega2+ FW v0-3-2 b239 without SD Card

root@Omega-5BE1:/# 
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "factory"
mtd3: 01f30000 00010000 "firmware"
mtd4: 0018a0e3 00010000 "kernel"
mtd5: 01da5f1d 00010000 "rootfs"
mtd6: 01610000 00010000 "rootfs_data"
mtd7: 00080000 00010000 "user"

root@Omega-5BE1:/# ls -l /
drwxr-xr-x    2 root     root           853 Apr  9 14:46 bin
drwxr-xr-x    5 root     root          2580 Apr  9 14:50 dev
drwxr-xr-x    1 root     root             0 Apr  9 14:50 etc
drwxr-xr-x    1 root     root             0 Apr  9 14:47 lib
drwxr-xr-x    1 root     root             0 Sep 23 22:56 mnt
drwxr-xr-x    5 root     root             0 Jan  1  1970 overlay
dr-xr-xr-x   57 root     root             0 Jan  1  1970 proc
drwxr-xr-x   16 root     root           223 Apr  9 14:46 rom
drwxr-xr-x    2 root     root             3 Apr  9 14:46 root
drwxr-xr-x    2 root     root           862 Apr  9 14:46 sbin
dr-xr-xr-x   11 root     root             0 Jan  1  1970 sys
drwxrwxrwt   16 root     root           520 Sep 24 09:57 tmp
drwxr-xr-x    1 root     root             0 Apr  9 14:46 usr
lrwxrwxrwx    1 root     root             3 Apr  9 14:46 var -> tmp
drwxr-xr-x    4 root     root            63 Apr  9 14:46 www

root@Omega-5BE1:/tmp# df -hT
Filesystem           Type            Size      Used Available Use% Mounted on
/dev/root            squashfs        7.8M      7.8M         0 100% /rom
tmpfs                tmpfs          60.9M     96.0K     60.8M   0% /tmp
/dev/mtdblock6       jffs2          22.1M    696.0K     21.4M   3% /overlay
overlayfs:/overlay   overlay        22.1M    696.0K     21.4M   3% /
tmpfs                tmpfs         512.0K         0    512.0K   0% /dev
/dev/mtdblock7       jffs2         512.0K    224.0K    288.0K  44% /mnt/mtdblock7

If the output of the cat /proc/mtd command is correct and the bootlog contains these lines:

 ...
[    0.387513] 5 fixed-partitions partitions found on MTD device spi0.0
[    0.393973] Creating 5 MTD partitions on "spi0.0":
[    0.398840] 0x000000000000-0x000000030000 : "u-boot"
[    0.404852] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.411059] 0x000000040000-0x000000050000 : "factory"
[    0.417112] 0x000000050000-0x000001f80000 : "firmware"
[    0.502999] 2 uimage-fw partitions found on MTD device firmware
[    0.509048] 0x000000050000-0x0000001da0e3 : "kernel"
[    0.515027] 0x0000001da0e3-0x000001f80000 : "rootfs"
[    0.520853] mtd: device 5 (rootfs) set to be root filesystem
[    0.528136] 1 squashfs-split partitions found on MTD device rootfs
[    0.534476] 0x000000970000-0x000001f80000 : "rootfs_data"
[    0.540898] 0x000001f80000-0x000002000000 : "user"
 ...

(without an inserted SD card) try to perform a Factory Reset.

Otherwise - without an iserted SD card - please reinstall your b239 firmware. For example:
cd /tmp
wget http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b239.bin

Check the downloaded file:
md5sum omega2p-v0.3.2-b233.bin
45d6b0be4eb3fb4a0396f417c087d838 omega2p-v0.3.2-b239.bin

sysupgrade -n omega2p-v0.3.2-b239.bin

Repeat the First Time Setup again please.

You can install the b233 (the stable ?!) or the b244 (the latest) image instead of b239 of course:

wget http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b233.bin
md5sum omega2p-v0.3.2-b233.bin
9616a502010ddd4793dbd5b31499b3e3 omega2p-v0.3.2-b233.bin
sysupgrade -n omega2p-v0.3.2-b233.bin

wget http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b244.bin
md5sum omega2p-v0.3.2-b244.bin
d990a68d131a635985adb60861cabca1 omega2p-v0.3.2-b244.bin
sysupgrade -n omega2p-v0.3.2-b244.bin

Good luck.

@tjoseph1 Unfortunately Onion doesn't provide any checksum for the Omega2 image files.

# Omega2+ FW v0.3.2 b244

# ------------------------------------------------------------------------------------------------------
# repo
# 2019-08-21T17:21:47.000Z        9.3 MB         omega2p-v0.3.2-b231.bin

root@Omega-5BE1:~# wget http://repo.onioniot.com.s3.amazonaws.com/omega2/images/
omega2p-v0.3.2-b231.bin
--2020-09-12 22:34:27--  http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b231.bin
Resolving repo.onioniot.com.s3.amazonaws.com... 52.217.43.108
Connecting to repo.onioniot.com.s3.amazonaws.com|52.217.43.108|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9699494 (9.2M) [application/octet-stream]
Saving to: 'omega2p-v0.3.2-b231.bin'

omega2p-v0.3.2-b231 100%[===================>]   9.25M   105KB/s    in 95s     

2020-09-12 22:36:03 (100 KB/s) - 'omega2p-v0.3.2-b231.bin' saved [9699494/9699494]

root@Omega-5BE1:~# md5sum omega2p-v0.3.2-b231.bin
7e4f8abdec01cddfdeb95613ee936529  omega2p-v0.3.2-b231.bin

# ------------------------------------------------------------------------------------------------------
# repo
# 2019-12-04T21:57:51.000Z        9.3 MB         omega2p-v0.3.2-b232.bin

root@Omega-5BE1:~# wget http://repo.onioniot.com.s3.amazonaws.com/omega2/images/
omega2p-v0.3.2-b232.bin
 ...
2020-09-12 22:43:51 (52.9 KB/s) - 'omega2p-v0.3.2-b232.bin' saved [9699494/9699494]

root@Omega-5BE1:~# md5sum omega2p-v0.3.2-b232.bin
55be86b40eed56b2acac5948e70765c0  omega2p-v0.3.2-b232.bin

I downloaded these files with my desktop again and verified them with the above MD5 checksums.

@tjoseph1
Onion Software Repository
@Lazar-Demin uploaded the omega2p-v0.3.2-b232.bin file on 2019-08-26 15:49 UTC.
MD5: 55be86b40eed56b2acac5948e70765c0 *omega2p-v0.3.2-b232.bin

Later - without any notice - he removed and replaced with another omega2p-v0.3.2-b232.bin file on 2019-12-04 21:57 UTC.
MD5: b39c323360fc6fe033c1b4d5f81aba82 *omega2p-v0.3.2-b232.bin

BTW he uploaded the omega2p-v0.3.2-b231.bin file on 2019-08-21 17:21 UTC.
MD5: 7e4f8abdec01cddfdeb95613ee936529 *omega2p-v0.3.2-b231.bin

I think he actualizes the Omega Firmware Changelog file manually so it's not always up-to-date.

The only question remaining is, saving a flash-able image from an Omega to to a file. Can we use dd with /dev/mtdblockX and combine those ?

The short answer is: no.

@tjoseph1
You wrote: "For me, the "poweroff" works identically. Please see the screens from Omega2 and Omega2+."

# Omega2 FW v0.3.2 b232 (http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2-v0.3.2-b232.bin)

root@Omega-5533:/# poweroff
root@Omega-5533:/# [  131.321902] br-wlan: port 1(ra0) entered disabled state
[  131.347949] device ra0 left promiscuous mode
[  131.352403] br-wlan: port 1(ra0) entered disabled state
[  135.868857] Removing MTD device #6 (rootfs_data) with use count 1
[  135.908124] reboot: System halted

# Omega2+ FW v0.3.2 b232 (http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b232.bin)

root@Omega-5BE1:/# poweroff
root@Omega-5BE1:/# [  259.968334] br-wlan: port 1(ra0) entered disabled state
[  259.984850] device ra0 left promiscuous mode
[  259.989372] br-wlan: port 1(ra0) entered disabled state
[  264.510098] Removing MTD device #6 (rootfs_data) with use count 1
[  264.546232] reboot: System halted

After a couple of minutes touch their shielding please.
Are their power really off?

@tjoseph1 said in Youtube post:

For the records:

1. Onion Omega2/2+ are Linux(MIPS) based, single core MT7688@580Mhz, SoC (with 16M/32M Flash and 64M/128M SPI RAM, for the 2/2+ models respectively).

Onion Omega2/2+ modules have a MediaTek MT7688AN SoC (embedded MIPS24KEc @580 MHz MIPS CPU among many other things) with onboard 16M/32M SPI NOR Flash and 64M/128M DDR2 RAM

1. The "reboot" and "poweroff" commands work as of today (You need to upgrade the FW to b232 or later, that is what I am using)

The poweroff command don't work on Omega2.

1. Power consumption: ... Omega2/2+ takes 120mA with WiFi ON, from the 5V DC supply, when powered through the Expansion dock.

120 mA ?! Are you sure?

@Nagendra-yedem
I'm afraid the commands of Onion I2C Python Module are not able to interpret a 2 byte / 16 bit wide register address.
In these command readBytes(devAddr, addr, size), writeByte(devAddr, addr, value), writeBytes(devAddr, addr, values) 'addr' can be only 1 byte.

@luz
How to detect... "locally"?

It is fairly easy since there is an Onion Omega2+ / Onion Omega2 sticker on the device

If you don't believe the sticker a reboot command and the bootloader messages on the Serial Console can help.
For example - please watch the 'find flash: ' line:

# HW Omega2+
# FW v0.3.2 b240
# http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2-v0.3.2-b240.bin
# U-Boot 1.1.3 (Oct 18 2016 - 17:29:05)

root@Omega-5BE1:/# reboot

   ____       _             ____
  / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
 / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
 \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
 W H A T  W I L L  Y O U  I N V E N T ? /___/"

Board: Onion Omega2 APSoC DRAM:  128 MB
relocate_code Pointer at: 87f60000
******************************
Software System Reset Occurred
******************************
flash manufacture id: c2, device id 20 19
find flash: MX25L25635E
============================================ 
Onion Omega2 UBoot Version: 4.3.0.3
 ---

root@Omega-5BE1:/# ubus call system board
{
	"kernel": "4.14.81",
	"hostname": "Omega-5BE1",
	"system": "MediaTek MT7688 ver:1 eco:2",
	"model": "Onion Omega2",
	"board_name": "omega2",
	"release": {
		"distribution": "OpenWrt",
		"version": "18.06-SNAPSHOT",
		"revision": "r0+7471-90181760c3",
		"target": "ramips\/mt76x8",
		"description": "OpenWrt 18.06-SNAPSHOT r0+7471-90181760c3"
	}
}

# HW Omega2+
# FW v0.3.2 b240
# http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b240.bin
# U-Boot 1.1.3 (Oct 18 2016 - 17:29:05)

root@Omega-5BE1:/# reboot

   ____       _             ____
  / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
 / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
 \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
 W H A T  W I L L  Y O U  I N V E N T ? /___/"

Board: Onion Omega2 APSoC DRAM:  128 MB
relocate_code Pointer at: 87f60000
******************************
Software System Reset Occurred
******************************
flash manufacture id: c2, device id 20 19
find flash: MX25L25635E
============================================ 
Onion Omega2 UBoot Version: 4.3.0.3
 ---

root@Omega-5BE1:/# ubus call system board
{
	"kernel": "4.14.81",
	"hostname": "Omega-5BE1",
	"system": "MediaTek MT7688 ver:1 eco:2",
	"model": "Onion Omega2+",
	"board_name": "omega2p",
	"release": {
		"distribution": "OpenWrt",
		"version": "18.06-SNAPSHOT",
		"revision": "r0+7471-90181760c3",
		"target": "ramips\/mt76x8",
		"description": "OpenWrt 18.06-SNAPSHOT r0+7471-90181760c3"
	}
}

#  HW Omega2
# FW v0.3.2 b240
# http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2-v0.3.2-b240.bin
# U-Boot 1.1.3 (Oct 18 2016 - 17:30:55)

root@Omega-5533:/# reboot

   ____       _             ____
  / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
 / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
 \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
 W H A T  W I L L  Y O U  I N V E N T ? /___/"

Board: Onion Omega2 APSoC DRAM:  64 MB
relocate_code Pointer at: 83f60000
flash manufacture id: ef, device id 40 18
find flash: W25Q128BV
============================================ 
Onion Omega2 UBoot Version: 4.3.0.3
 ---

root@Omega-5533:/# ubus call system board
{
	"kernel": "4.14.81",
	"hostname": "Omega-5533",
	"system": "MediaTek MT7688 ver:1 eco:2",
	"model": "Onion Omega2",
	"board_name": "omega2",
	"release": {
		"distribution": "OpenWrt",
		"version": "18.06-SNAPSHOT",
		"revision": "r0+7471-90181760c3",
		"target": "ramips\/mt76x8",
		"description": "OpenWrt 18.06-SNAPSHOT r0+7471-90181760c3"
	}
}

How to detect... "remotely"?
That is the question.

@CoffeeCat DS18B20 is a 1-Wire device. You should connect it to Omega2's 1-Wire Bus - ie. directly to an Omega2(+) GPIO.
Have you ever read this Reading a 1-Wire Temperature Sensor

@victoriano Serial ports of Omega2S+ on Omega2 DASH
Unfortunately I don't have such device so according to the schematic:

• UART0 (/dev/ttyS0) - Serial Console (via an on-board CP2104 USB-to-Serial chip - Micro USB port)
  TXD0 GPIO12 - CP2104 RXD0
  RXD0 GPIO13 - CP2104 TXD0

• UART1 (/dev/ttyS1)
  TXD1 GPIO45 - Expansion Header GPIO45
  RXD1 GPIO46 - Expansion Header GPIO46

• UART2 (/dev/ttyS2)
  TXD2 GPIO20 - not exposed
  RXD2 GPIO21 - drives LEDA via the Q3 PNP inverter

You could connect a USB-to-Serial converter/cable to the USB Host Port to get one more serial line.

@Marko-Lukat said in How can I pass one GPIO pin to an other?:

@Radek

Pin 16 and 17 (UART2) is connected AT_RX and AT_TX respectively. The UART2 doesn't work by the way.

Let's take a step back. Just short pin 16/17 (jumper wire), start a terminal of your choice on /dev/ttyS2 (on the Omega), disable local echo and start typing. Do you see any response (i.e. remote echo)?

root@Omega-5BE1:~# picocom -b 9600 /dev/ttyS2
picocom v1.7

port is        : /dev/ttyS2
flowcontrol    : none
baudrate is    : 9600
parity is      : none
databits are   : 8
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,

Terminal ready
Yes, when I short GPIO16 and GPIO17 (UART2) with a jumper wire then I can see what I type... :-)

@Marko-Lukat Please let's continue in @Radek's original thread Enable UART2. Or use UART0

@Radek How do you use the A9G board with Omega2's UART1 (/dev/ttyS1)? Is that config working well?

@Radek
Proof of Concept (unfortunately I don't have an A9G board)

Serial communucation between

• a desktop PC Ubuntu 18.04.4 LTS with an FTDI232 USB-to-Serial module
  communication program: picocom -b 9600 /dev/ttyUSB0 (or picocom -b 115200 /dev/ttyUSB0 - 115200 on both device of course)
• and an Omega2+ FW v0.3.2 b240 UART2 (/dev/ttyS2)

root@Omega-5BE1:~# omega2-ctrl gpiomux set spi_s pwm01_uart2
set gpiomux spi_s -> pwm01_uart2

root@Omega-5BE1:~# omega2-ctrl gpiomux get
Group i2c - [i2c] gpio 
Group uart0 - [uart] gpio 
Group uart1 - [uart] gpio pwm01 
Group uart2 - [uart] gpio pwm23 
Group pwm0 - pwm [gpio] 
Group pwm1 - pwm [gpio] 
Group refclk - refclk [gpio] 
Group spi_s - spi_s gpio [pwm01_uart2] 
Group spi_cs1 - [spi_cs1] gpio refclk
Group i2s - i2s [gpio] pcm 
Group ephy - [ephy] gpio 
Group wled - wled [gpio]

communication program: picocom -b 9600 /dev/ttyS2 (or picocom -b 115200 /dev/ttyS2 - 115200 on both device of course)

• HW connections: FTDI RX to Omega2 GPIO16 (TX2), FTDI TX to Omega2 GPIO17 (RX2), GND to GND

It seems this serial communication is working well.

@Radek What was your next step?