@György-Farkas Now I am back from deploying the project. The second Omega2s+ continued to work beautifully. The first one did work beautifully, in the lab, until it croaked. As you suggest it may have been a victim of soldering other parts of the system, ESD, that sort of thing.
I have tried the SW_RST (software reset button) as you suggest. It makes no perceptible action at the console serial port or anywhere else visible. Perhaps it has hardware damage.
The console serial port is working. It still produces the boot start message pictured above. (ending 7ff70000)
Is there a schematic for connecting USB storage to the Omega2s+ for reflashing?
Just connect to pins 61-63 and give the USB storage device some +5v?
But I think I should be seeing bootloader messages at the console port. None are there. Does this mean the device is really dead and my boss is correct in saying I should just buy another one and not waste my time on one that I have killed?
@Ian-Smith I think your best option is to download and install the current firmware release. There are several methods to achieve this, probably the easiest is using the USB method, as describes in the docs here:
root@Omega-5286:~# opkg install kmod-usb-net-cdc-ether
Installing kmod-usb-net-cdc-ether (4.14.81-1) to root...
* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-net-cdc-ether:
* kernel (= 4.14.81-1-4d99ecc9745adb4d8a275d8e3a38961b) * kernel (= 4.14.81-1-4d99ecc9745adb4d8a275d8e3a38961b) * kernel (= 4.14.81-1-4d99ecc9745adb4d8a275d8e3a38961b) *
* opkg_install_cmd: Cannot install package kmod-usb-net-cdc-ether.
> Device Firmware Version: 0.3.2 b233
> Checking latest version online...
> Repo Firmware Version: 0.3.2 b233
> Comparing version numbers
> Device firmware is up to date!
root@Omega-5286:~# wget http://repo.onioniot.com/omega2/packages/core/kmod-usb-net-cdc-ether_4.14.81-1_mipsel_24kc.ipk
root@Omega-5286:~# opkg install kmod-usb-net-cdc-ether_4.14.81-1_mipsel_24kc.ipk --nodeps
Package kmod-usb-net-cdc-ether (4.14.81-1) installed in root is up to date.
To enable netconsole logging, you will specify the interface used to reach the syslog server, the IP and port of the syslog server, and optionally the MAC address of that server www.mcdvoice.com thank you
I will attempt to upgrade my image and pip install it. Pip install failed last time I tried. If you are interested in my use case, or have done something similar, here the talk : https://www.youtube.com/watch?v=mxyziRuSefI . Please let me know if there is something I have missed, hopefully I will have a working solution with the Onion as the high level processor soon.
@Peter-Carr I aggree, with some common sense I was able do it, but I would urgently ask the Onion team to update their documentation. Obviously there are some differences in newer firmware versions like b233
I added a 1 GB SD-card. it was already formatted and automatically mounted. So I only had to start the slightly modified tar command and then I had to modify /etc/config/fstab file
(But before that it took me hours and several firmware resets)