1. Home
  2. Omega Talk
  3. [solved] Omega2+ b231/b232 firmware versions - confusion.

[solved] Omega2+ b231/b232 firmware versions - confusion.

  • T

    Hi all,

    I have following observation:

    The few Omega2+ that I have, came with OS preinstalled. I have upgraded one(having id 745F) with the b232 FW (2p img) downloaded from http://repo.onioniot.com/omega2/images/

    While booting it gives the FW build date, Dec 04 2019, which agrees with:
    https://github.com/OnionIoT/source/blob/openwrt-18.06/CHANGELOG.md#build-notes

    Omega2+-745F:
    While booting:
    [0.000000] Linux version 4.14.81 (root@c1cbfc88b77b) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r0-)) #0 Wed Dec 4 20:46:12 2019

    root@Omega-745F:/# onion os version
    === Version Info ===
    Omega firmware: v0.3.2 b232
    onion-os - 1.0.6-1

    The other one (having id 6994, still uses the factory fw) provides the following info:

    Omega2+-6994:
    Booting:
    [0.000000] Linux version 4.14.81 (root@9be0ff6623b9) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r0-)) #0 Mon Aug 26 14:30:37 2019

    The build date is Aug 26 2019, which has to be B231 according to the above CHANGELOG.

    But it gives the same, identical info as the 745F,above:

    root@Omega-6994:/# onion os version
    === Version Info ===
    Omega firmware: v0.3.2 b232
    onion-os - 1.0.6-1

    The following exes differ wrt md5sum (as well as sha256sum)

    745F: (runing on the download b232 FW w/o any opkg upgrade)
    ad74c40ec90f670ca4e39f9f1dd96f92 /usr/sbin/mosquitto
    d1024de44c695679d70655cbee88a5a3 /usr/bin/mosquitto_pub
    efe2376b85f6ce19f102985e156df02c /usr/bin/mosquitto_sub
    415634fad5827a26e7d8fbbd708bc70c /usr/bin/tar
    f5c1c19dd7aae0fd4774499013502d86 /usr/bin/wget-ssl

    6994:(running factory fw)
    4eaddf2c6a6fa880345b7b4cecd5c08a /usr/sbin/mosquitto
    ed81cce1466118b1393554102b596cc9 /usr/bin/mosquitto_pub
    bd5deba86ae1313aa590403e667e786e /usr/bin/mosquitto_sub
    0860c46fd465e373c08a2f571d8e88b4 /usr/bin/tar
    8757097f6e50fc9bd46c980e9d8fd13f /usr/bin/wget-ssl

    What command should I run to get the b231 FW as the output ?
    Thanks ..

    0 G 1 Reply
  • C

    @tjoseph1 oupgrade -v will give you the version details. oupgrade -l will update to the latest version which may not be the latest stable version. oupgrade with no option will give you the details of any version you can upgrade to even if it is optional.

    0
  • T

    @crispyoz :
    I get the following outputs from the Omega2+ that has the factory FW:

    root@Omega-6994:/# oupgrade -v

    Device Firmware Version: 0.3.2 b232
    root@Omega-6994:/# oupgrade
    Device Firmware Version: 0.3.2 b232
    Checking latest version online...
    url: https://api.onioniot.com/firmware/omega2p/stable
    Repo Firmware Version: 0.3.2 b233
    Comparing version numbers
    New build of current firmware available, upgrade is optional, rerun with '-force' option to upgrade
    root@Omega-6994:/#

    Is there a possibility that, this one is b232, even though the build date is Aug 26 2019 ?

    As a side note, is there a command/mechanism that would save the entire FW from the flash to a file, that can be re-used to flash the Omega2/2+ at a later time ?

    Thanks..

    0
  • T

    @crispyoz :

    Forgot to mention:
    The Omega2+ with id 6994 was never accessed using browser at http://192.168.3.1 to do the usual setup stuff. I booted and accessed it using UART0 from the dock and did "wifisetup" to make it an STA, so that I can ssh to it from my workspace WiFi network, without having to register my workstation into the 192.168.3 network. The "wireless.ap.key" was changed from the default using uci. So, it is pretty much running the factory FW.

    Thanks..

    0
  • T

    @crispyoz :

    Ok, I reflashed 745F with the b231 FW downloaded from http://repo.onioniot.com/omega2/images/

    While booting:
    [0.000000] Linux version 4.14.81 (root@f584016057cc) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r0-)) #0 Wed Aug 21 16:01:26 2019

    It is Aug 21 2019, not Aug 26 2019 (the Factory FW of 6994)

    Now, everything looks agreeing:

    root@Omega-745F:/# onion os version
    === Version Info ===
    Omega firmware: v0.3.2 b231
    onion-os - 1.0.6-1

    Did the "wifisetup" in order to go online and check with oupgrade.

    root@Omega-745F:/# oupgrade -v
    Device Firmware Version: 0.3.2 b231
    root@Omega-745F:/# oupgrade
    Device Firmware Version: 0.3.2 b231
    Checking latest version online...
    url: https://api.onioniot.com/firmware/omega2p/stable
    Repo Firmware Version: 0.3.2 b233
    Comparing version numbers
    New build of current firmware available, upgrade is optional, rerun with '-force' option to upgrade
    root@Omega-745F:/#

    All exes otherthan wget-ssl are identical between Factory FW (Aug 26 2019, b232) and the repo FW (b231) is:
    67602c59cd5d4705963638fb830a0ecf /usr/bin/wget-ssl (repo b231)
    8757097f6e50fc9bd46c980e9d8fd13f /usr/bin/wget-ssl (Factory FW, b232)

    So, the factory FW I have is more close to repo FW b231.

    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 ? Any hint would be helpful.

    Thanks..

    0
  • G

    @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.

    1
  • C

    @tjoseph1 re using dd, it's best to learn to build your own firmware image and setup a repository, then you can tailor your firmware to your requirements and deploy updates using opkg. There is a bit to learn but once you master it, it's not rocket science.

    0
  • T

    @György-Farkas :

    Thanks a lot for the clarification.
    A single txt file that contains the hash of images be maintained in the repo under the same directory, along with the images? After downloading the b231 image today, I was not sure if image had integrity, and was bit skeptical before flashing.

    0 G 1 Reply
  • T

    @crispyoz :

    I was curious after seeing:
    $ file mtdblock4
    mtdblock4: u-boot legacy uImage, MIPS OpenWrt Linux-4.14.81, Linux/MIPS, OS Kernel Image (lzma), 1572345 bytes, Wed Dec 4 20:46:12 2019, Load Address: 0x80000000, Entry Point: 0x80000000, Header CRC: 0xCA34A2AD, Data CRC: 0xE571B8FC

    mtdblock4 was obtained by dd'ing /dev/mtdblock4.

    Thank you for suggesting to compile in order to get get more fw insight.

    0
  • G

    @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.

    0
  • T

    @György-Farkas :

    I was pointing to a possible enhancement wrt image distribution.

    Many sites distributing images such as iso, a txt file containing the checksum is usually made available. Please see the ubuntu download mirror:

    http://reflection.oss.ou.edu/ubuntu-release/20.04.1/

    The SHA256SUMS file contains the hash of the iso's.

    Once we download the image with wget, we can compare the checksum in the workstation before using the image. The checksum validation is a one time process, anyways.

    I always keep the images in my workstation for future use.

    OpenWRT provides the checksum in the page itself:
    https://archive.openwrt.org/releases/18.06.7/targets/ramips/mt76x8/ which would require redesign the Omega repo.

    The ubuntu approach is simple. Whenever a new image is released, update the txt file by adding a single line entry..

    Thanks..

    0
firmware 108 firmware versio 1
Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.