We have upgraded the community system as part of the upgrade a password reset is required for all users before login in.

Problem after firmware upgrade



  • Hi,

    After a very long time, I booted by Omega2+.

    I started out by running opkg update.
    I then downloaded the latest firmware into the tmp folder.

    wget http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.3-b251.bin
    

    and updated using sysupgrade omega2p-v0.3.3-b251.bin command.

    Got the following output before the Omega2 rebooted

    root@Omega-2FA5:/tmp# sysupgrade omega2p-v0.3.3-b251.bin
    Saving config files...
    killall: watchdog: no process killed
    Sending TERM to remaining processes ... onion-helper udhcpc mountd ntpd rpcd shellinaboxd ubusd askfirst logd netifd odhcpd dnsmasq uhttpd device-client avahi-daemon
    Sending KILL to remaining processes ... askfirst
    Switching to ramdisk...
    Performing system upgrade...
    Unlocking firmware ...
    
    Writing from <stdin> to firmware ...
    Appending jffs2 data from /tmp/sysupgrade.tgz to firmware..
    .
    Writing from <stdin> to firmware ...
    Upgrade completed
    Rebooting system...
    umount: can't unmount /dev/pts: Resource busy
    umount: can't unmount /dev: Resource busy
    umount: can't unmount /tmp: Resource busy
    Timeout, server 192.168.3.1 not responding.
    

    After rebooting, I am not longer finding the AP that Omega gave!

    I then connected to it using the serial port and I am getting the following message on console in continuous loop:

        ____       _             ____
      / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
     / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
     \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
     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
    flash manufacture id: c2, device id 20 19
    find flash: MX25L25635E
    

    What's happening? Am I screwed? Is it bricked?

    Following was my original firmware:

    BusyBox v1.26.2 () built-in shell (ash)
    
       ____       _             ____
      / __ \___  (_)__  ___    / __ \__ _  ___ ___ ____ _
     / /_/ / _ \/ / _ \/ _ \  / /_/ /  ' \/ -_) _ `/ _ `/
     \____/_//_/_/\___/_//_/  \____/_/_/_/\__/\_, /\_,_/
     W H A T  W I L L  Y O U  I N V E N T ? /___/
     -----------------------------------------------------
       Ω-ware: 0.1.10 b160
     -----------------------------------------------------
    


  • Hi @Prashant-Kamdar your device is not bricked, it's just confused.

    When your device boots it tells you what it is "Board: Onion Omega2"

    The firmware you installed was named "omega2p-v0.3.3-b251.bin" which means it is for an Omega2+. So when it's booting it is expecting to find double the flash and double the RAM (https://onion.io/omega2/)

    You can fix this by doing a factory reset, the procedure for which can be found in the documentation here:

    https://docs.onion.io/omega2-docs/factory-reset.html#with-the-reset-button-1

    Once you have completed the factory reset then you can update again, but this time download the firmware with the nomenclature "omega2-vxxxxx" or alternatively, you can use oupgrade command detailed here:

    https://docs.onion.io/omega2-docs/using-the-omega-updating.html



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