Many errors with Omega2 .. opkg segfaults, unable to upgrade firmware.
-
@Findlay said in Many errors with Omega2 .. opkg segfaults, unable to upgrade firmware.:
This page lists all of the currently identified issues in the Omega OS. The issues are separated into general firmware issues and Console firmware issues.
Could you please provide the link to the page?
Thanks.
-
@tjoseph1 This is a known forum spammer. Ignore him,
I can see from your opkg update errors you have quite an old firmware version.
Run oupgrade -f to upgrade to the latest firmware
-
@crispyoz
Oh, I didn't know about Findlay.. This is my very first day in this forum :)..Thanks..I think, the web-interface at http://192.168.3.1 is not behaving the way it used to be. When I try calling the URL all I get is a text page now, with the content:
Index of /console/
../
modified: Fri, 31 Jul 2020 08:59:52 GMT
directory - 0.00 kbyte
lib/
modified: Fri, 31 Jul 2020 11:47:35 GMT
directory - 0.00 kbyte
<<<Moreover, it is not a station anymore.. I don't have the route to reach outside..I would need to figure out how to configure this to associate with my WiFi AP from the command line. No "wpa_supplicant.conf", and "interfaces".
Could you tell me if uci is the right way to go ?root@Omega-CCC9:/# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 br-wlanroot@Omega-CCC9:/# ifconfig
apcli0 Link encap:Ethernet HWaddr 42:A3:6B:00:CC:C9
inet6 addr: fe80::40a3:6bff:fe00:ccc9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1br-wlan Link encap:Ethernet HWaddr 40:A3:6B:C0:CC:CB
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fd1d:48c4:7633::1/60 Scope:Global
inet6 addr: fe80::42a3:6bff:fec0:cccb/64 Scope:Link
..
..
ra0 Link encap:Ethernet HWaddr 40:A3:6B:C0:CC:C9
inet6 addr: fe80::42a3:6bff:fec0:ccc9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
-
@tjoseph1 Welcome to the forum.
I suggest you should first do a factory reset so you are working with a device in a known state.
The documentation is here:
https://docs.onion.io/omega2-docs/factory-reset.html
Once you have completed the reset, you can connect to your wifi by using the command wifisetup and following the prompts.
Once you are connected to your wifi run oupgrade -f
That should get you sorted out.
-
@crispyoz
Thank you very much .. I followed the documentation as suggested:
https://docs.onion.io/omega2-docs/factory-reset.html
commands:
firstboot -y
sync
reboot
Surprisingly, those did not get me the webserver back to a working condition..Finally, I ended up up downloading the FW "omega2-v0.3.2-b233.bin" from http://repo.onioniot.com/omega2/images/ (that was the FW version it was trying to download, during my first attempts when I was using the WebGUI as mentioned in my original post) using web-browser. Then I "scp"ed the FW to /tmp. Basically I was following: https://docs.onion.io/omega2-docs/manual-firmware-installation.html, and did the upgrade from minicom serial terminal.root@Omega-CCC9:/tmp# sysupgrade -n omega2-v0.3.2-b233.bin
killall: watchdog: no process killed
Sending TERM to remaining processes ... avahi-daemon onion-helper udhcpc udhcpc dnsmasq mountd ntpd ubusd logd rpcd net
Sending KILL to remaining processes ...
Switching to ramdisk...
Performing system upgrade...
Unlocking firmware ...
Writing from <stdin> to firmware ...
Upgrade completed
Rebooting system...The upgrade screen resembled the one provided in the above URL After reboot, I don't have the following errors in my original post:
1 => N/A
2 => opkg does not give "Signature check failed" anymore
3 => opkg list-upgradable", it does not Segfaults.
root@Omega-CCC9:/# opkg list-upgradable
wget - 1.19.5-3 - 1.19.5-6
base-files - 192-r0 - 192-r0+7475-e6757b4765
oupgrade - 0.3-1 - 0.4-3
4 => It still gives "*** Warning - bad CRC"Board: Onion Omega2 APSoC DRAM: 64 MB
relocate_code Pointer at: 83f60000
Software System Reset Occurred
flash manufacture id: ef, device id 40 18
find flash: W25Q128BV
*** Warning - bad CRC, using default environment5: => Buggy DT error is no more.. even though spi is loaded
[ 0.370117] spi-mt7621 10000b00.spi: sys_freq: 193333333
[ 0.391878] m25p80 spi0.0: w25q128 (16384 Kbytes)root@Omega-CCC9:/# lsmod |grep -i ^spi
spidev 6336 0root@Omega-CCC9:/# ls -l /dev/spi*
crw------- 1 root root 153, 0 Dec 6 2019 /dev/spidev0.1root@Omega-CCC9:/# uname -a
Linux Omega-CCC9 4.14.81 #0 Fri Dec 6 16:28:06 2019 mips GNU/LinuxAs a side note, the "reset" button was not resetting the omega2 earlier; it is working now. Also, have noticed the earlier GUI was more "feature-rich". I remember seeing GPIO controls etc. in the old version. The newer version does not have those. So far good.
Now, my question would be:
The latest FW avaiable at http://repo.onioniot.com/omega2/images/ is omega2-v0.3.2-b244.bin. I chose omega2-v0.3.2-b233.bin, since it was the one the "automatic upgrade process" picked. I am not sure why it selected that version of FW. Can I upgrade to b244.bin?Also, it might be more helpful if the sha256sum or so is provided in the website along with the bin files.
Thanks for all your help..
-
@tjoseph1 said in Many errors with Omega2 .. opkg segfaults, unable to upgrade firmware.:
Now, my question would be:
The latest FW avaiable at http://repo.onioniot.com/omega2/images/ is omega2-v0.3.2-b244.bin. I chose omega2-v0.3.2-b233.bin, since it was the one the "automatic upgrade process" picked. I am not sure why it selected that version of FW. Can I upgrade to b244.bin?See http://docs.onion.io/omega2-docs/using-the-omega-updating.html
-
@tjoseph1 You can ignore the CRC error, there is a tech note about it somewhere, I don't have time to find the link right now, maybe someone can post it for you.
I haven't used the GUI (Onion-OS) for a long time but you can add apps to the UI, take a look at the details here:
-
Got the following outputs for "oupgrade"
root@Omega-CCC9:~# oupgrade -c
Device Firmware Version: 0.3.2 b233
Checking latest version online...
url: https://api.onioniot.com/firmware/omega2/stable
Repo Firmware Version: 0.3.2 b233
Comparing version numbers
Device firmware is up to date!Appears that b233 is the latest stable, as per the output received from " oupgrade -c". May be b244 is not marked as stable. So I would go with this.
My ultimate goal is to use Omega platform to run a C application(WiFi plus UART, SPI and I2C for interfacing). Started with Omega2 in order to make myself familiar with the platform and Omega2 was the one readily available locally. At this point, I would think going through https://github.com/OnionIoT/ shall provide a better picture; also downloaded the CPU data sheet from https://labs.mediatek.com/en/chipset/MT7688. Next is to order a few 32M/128M units and docks from digikey.
Thanks a lot, gentlemen.
-
@tjoseph1 I would suggest you look at the specs for the Omega2(+) and Omega2S(+), the 2S is the surface mounted version and exposes more resources than the plugin version.
-
@crispyoz I would order Omega2+, the 32M/128M. In fact, I read that the (+) is the recommended model for development. Still, could procure only Omega2 locally. Digikey would take take 2 weeks or so. Finally, plan to use the SMD version, with custom PCB and power.
Though I was able to boot RPi Zero W with cross-compiled OpenWRT 18.06.8 last week, Omega2S(+) will be easier from the hardware perspective. I am happy with the progress made in the past few days. Really appreciate all your help..
Thanks again.
