Any idea?
Posts made by cubytus
-
RE: Restoring original Omega firmware
TL;DR: I can't upgrade or restore firmware: something needs to be done first to activate Ethernet, but what is it?
-
RE: Restoring original Omega firmware
Since I can make a comparison, curiously the same process from a working Omega also fails at this point:
********************************************* * U-Boot 1.1.4 (Sep 14 2015, 08:21:31) * ********************************************* AP121 (AR9331) U-Boot for Onion Omega DRAM: 64 MB DDR2 16-bit id read ox100000ff FLASH: 16MCLOCKS: 400/400/200/20 MHz (CPU/RAM/AHB/SPI) LED on during eth initialization... Press reset button for at least: - 3 sec. to run web failsafe mode - 5 sec. to run U-Boot console - 7 sec. to run U-Boot netconsole Reset button is pressed for: 4 Button was pressed for 4 sec... HTTP server is starting for firmware update... Link down: eth0 Link down: eth1 […] ## Error: couldn't initialize eth (cable disconnected?)!
bootm command also fails:
bootm Booting image at: 0x80800000 Image name: ???????+?#::2??+;? ????? ?;;??z*????? Image type: MIPS Linux Kernel Image (lzma compressed) Data size: 195705595 Bytes = 186.6 MB Load address: 0x3AB03A2B Entry point: 0xBAB3AAAB Uncompressing kernel image... ## Error: LZMA error num: 1
If I don't interrupt the boot, everything works fine.
So something is interfering when boot is interrupted, either manually or because the firmware is corrupted.
Let's continue the n00b analysis:
Displaying the memory content at 0x9F020000 on a working Omega:Omega> md 0x9F020000 9F020000: 01000000 4F70656E 57727400 00000000 ....OpenWrt..... 9F020010: 00000000 00000000 00000000 72343933 ............r493 9F020020: 38390000 00000000 00000000 00000000 89..............
Displaying the same memory content at the same address on the bricked Omega:
Omega> md 0x9F020000 9F020000: 27051956 89991322 57A4D684 00119D25 '..V..."W......% 9F020010: 80000000 80000000 5921F5B0 05050203 ........Y!...... 9F020020: 4D495053 204F7065 6E577274 204C696E MIPS OpenWrt Lin 9F020030: 75782D33 2E31382E 33360000 00000000 ux-3.18.36......
Environment variables are the same.
However, the boot address is different:
On a working Omega:********************************************* * U-Boot 1.1.4 (Sep 14 2015, 08:21:31) * ********************************************* AP121 (AR9331) U-Boot for Onion Omega DRAM: 64 MB DDR2 16-bit id read ox100000ff FLASH: 16MCLOCKS: 400/400/200/20 MHz (CPU/RAM/AHB/SPI) LED on during eth initialization... Hit any key to stop autobooting: 0 Booting image at: 0x9F020000
On the bricked Omega, it is trying to load 0x80800000 instead.
-
RE: Restoring original Omega firmware
Here's what I get, in case it's not clear.
********************************************* * U-Boot 1.1.4 (Sep 14 2015, 08:21:31) * ********************************************* AP121 (AR9331) U-Boot for Onion Omega DRAM: 64 MB DDR2 16-bit id read ox100000ff FLASH: 16MCLOCKS: 400/400/200/20 MHz (CPU/RAM/AHB/SPI) LED on during eth initialization... Hit any key to stop autobooting: 0 Booting image at: 0x9F020000 Image name: ??"W?ք MIPS Ope Image type: MIPS Linux Kernel Image (lzma compressed) Data size: -679527621 Bytes = 3448 MB Load address: 0x2378C2DE Entry point: 0x357D1F36 Uncompressing kernel image... ## Error: LZMA error num: 1 ## Error: failed to execute 'bootcmd'! HTTP server is starting for firmware update... Link down: eth0 Link down: eth1 […] ## Error: couldn't initialize eth (cable disconnected?)!
Ethernet has to be working before I try to push the firmware.
-
RE: Restoring original Omega firmware
I am not attempting to push Omega2+ firmware onto Omega (1).
-
Restoring original Omega firmware
Hi there,
I dug out one of my original Omega and remembered the OS got corrupted somehow. I then connected to its serial port and found out this:
Omega> bootm Booting image at: 0x80800000 Image name: ???????????????????*???? ???????????? Image type: MIPS Linux Kernel Image (lzma compressed) Data size: -1431651654 Bytes = 2730.7 MB Load address: 0xAAAAAAAA Entry point: 0xAAAAAAAA Uncompressing kernel image... ## Error: LZMA error num: 1
Probably one of my previous experiments went wrong.
I then used a breadboard dock to connect the Ethernet expansion to
+3.3V / GND / TX- / TX+ / RX- / RX+ to the corresponding pins (taken respectively from there for the Onion itself and the expansion header and my own CP2102 USBtoUART converter.The reason for this setup:
- On my original non-power full-size dock, the power switch broke and took a part of the trace with it, so I couldn't repair it with common tools and had to trash it. Seems it was a common issue in the first batches. So no built-in UART converter for me.
- There's a simpler Ethernet converter on the reference schematic usable on short runs that I can't build because it uses rare 49.9Ω value resistors that are surprisingly expensive, so have to use the Ethernet expansion.
To my surprise, even with an Ethernet cable connected to my computer (manual IP set to 192.168.1.100, router (=failed Omega) 192.168.1.1 (parameters listed in printenv)), U-Boot claims neither eth0 or eth1 is connected and refuses to launch the www server for firmware recovery.
Same result when connected to my regular LAN.
I know my connections to be correct as Ethernet works both on Omega 2+ and another, functional Omega.
Now, what am I missing to activate Ethernet connectivity?
Knowing the original firmware, while very user-friendly, is based upon an hopelessly outdated LEDE, how can I install up-to-date OpenWRT along with Omega-specific packages?
-
RE: Omega2+ can't connect to wifi network during initial setup
My Omegas are now gathering dust. They can't connect to the 802.11n network.
How would I get a hint of what's not working?
-
RE: Omega2+ can't connect to wifi network during initial setup
Well, bad news, it broke again. After I rebooted the newly installed b162 running on the Ω2+, the orange light flashed slowly for a few seconds as if booting normally, then turned off. It didn't broadcast any SSID.
I then tried to put it on the small expansion board, same result.
Tried pressing the reset button while turning it on, same result, no light and no SSID.What can I do now?
-
RE: Omega2+ can't connect to wifi network during initial setup
@Luciano-S. Actually I did contact the Onion team about the issue, they just acknowledged the problematic switch, but didn't offer an RMA. The switch is broken "away from the GPIO", i.e. OFF, and I can't move it back on. This Expansion Dock is essentially unusable until I replace the switch. I surely won't ask a professional to replace a 50cents part on a $15 board, that would cost me $50 at least (last time I asked for surface soldering service). This is a board to be tinkered with (somewhat), after all!
Indeed, I managed to get the latest, b159 version on a USB key (FAT32), and install it manually. After that, it finally connected to the router. The Onion team has some great ideas, but should really test their firmware before shipping!
For the record: I plugged the Ω2+ on the Battery Expansion Board, and didn't need the CP2102 standalone converter I had. Also, the USB key didn't mount automatically, but issuing command /etc/init.d/mountd restart mounted the key at /tmp/run/mountd/sda1, not /tmp/mounts (this directory doesn't exist)
Buggy firmware + outdated documentation…
-
RE: Omega2+ can't connect to wifi network during initial setup
Well, I did just that, attempting the upgrade from a previously downloaded image on a USB drive formatted in FAT32. I took the b157 version, the latest when I attempted to make the Ω2+ work.
However, I still can't make it connect to my router
I tried to create an unsecured, ad-hoc network on my computer for the Omega to connect to, but it also fails, and still doesn't give out any details.What would be next?
-
RE: Omega2+ can't connect to wifi network during initial setup
@Ken-Conrad said in Omega2+ can't connect to wifi network during initial setup:
@Patrick-Nou You have the tools to update your Omega to working - the broken switch on the Expansion dock has been common problem, can you use a small needle to make it work?
Actually I already tried the needle, but ended up breaking the switch further, in the OFF position. I guess I will have to replace it, but the solder points are really tiny and I may well tear away the fragile printed circuit.
From the updated instructions, should I understand nor the serial connection or the Ethernet Expenasion aren't required anymore? I do have access to the SSH server, even if the Omega isn't set up yet.
What filesystem should the USB key be formetted in?
-
RE: Omega2+ can't connect to wifi network during initial setup
@Luciano-S. I read somewhere the Battery dock didn't feature a CP2102 chip.
However, I do have a regular Expansion Dock (for the Ω) whose power switch is broken.
I also have a standalone CP2102, Breadboard Dock.The only missing information would be the full pinout of the Ethernet Expansion Board
Broken switch below:
-
RE: Omega2+ can't connect to wifi network during initial setup
@Luciano-S. Already tried regular USB charger that has no problem charging an iPad (notoriously power-hungry), already powered the Omega (non-2 version), the Raspberry Pi (also very sensitive to bad power quality).
I don't have another laptop handy, but a USB voltmeter shows it doesn't go lower than 4.75V, still within the 5% tolerance required.
The documentation pages don't state explicitly how to manually update the firmware; however, I found this old documentation page through a G search, and deducted this would be the correct path to fetch the latest image for the Ω2+: http://repo.onion.io/omega2/images/omega2p-v0.1.9-b157.bin
So the next step would be to
1- somehow put this image into the /tmp directory
Related problem: how do I perform a file transfer over SSH when SFTP is not available?2- perform:
sysupgrade -n /tmp/omega-v0.1.9-b157.binAm I correct?
What are the chances of bricking the Ω?Not sure how I should feel knowing that a device I waited for months can't even complete its own simple setup.
-
RE: Omega2+ can't connect to wifi network during initial setup
@Luciano-S. 1- Tried while connected to my laptop's USB port: FAILS.
2- None of those have any special character in them.
3- What old firmware? I can't update if I can't connect to the Internet, anyway.aps command yields:
3 Zhone 22:02:71:XX:YY:ZZ WPA2PSK/AES 89 11b/g/n NONE InAnd the last part of /etc/config/wireless shows:
config wifi-iface
option device 'ra0'
option network 'wlan'
option mode 'ap'
option encryption 'psk2'
option key '12345678'
option ApCliAuthMode 'WPA2PSK'
option ApCliEncrypType 'AES'
option ssid 'Omega-F835'
option ApCliSsid 'Zhone'
option ApCliPassWord 'Password'
option ApCliEnable '1'I don't have a picture, but this is a rather short cable, 1m long approximately.
Any idea where the problem is? No other Wifi device have any issue, not even the current Omega (non 2) that are on the same network.
-
Omega2+ can't connect to wifi network during initial setup
Hello there,
I am trying to get my new Omega2+ to connect to the Wifi network, but it fails for some reason. It is connected to a Battery Dock (without battery at the moment), has an Ethernet Expension sitting on it (no cable connected yet).
I first tried the GUI way, and it just reports being unable to connect to my WiFi router.
Then I tried to modify /etc/config/wireless, and I could see my router's SSID / password being there.
Also, it reports Ω-ware: 0.1.5 b130 on login through SSH, if that's any helpful.
But it fails to connect.
Any idea how to tackle this?
-
RE: New Omega2+ can't find wifi APs
Similar problem here: my Omega 2+ can see my router, but refuses to connect. Doesn't give any error message, but the router doesn't register any connection attempt.
It's powered through a standard USB cell phone charger.
IdeaS?
-
RE: Idea Dump
An automatic router rebooter, but one that would use the relay expansion, not the big, fat relays also available.
Oh, and make it a full monitor, display average speed, data transferred, and last 5 pings on the OLED display. Sometimes routers fail by giving enormous ping, but don't disconnect.
-
RE: Onion Omega as a fridge controller?
@WereCatf Indeed turning it on every few hours was the classical way to deal with ice build-up for 10 to 15 min at a time, only. However, this is inefficient and to save electricity, modern fridges use adaptative defrost.
I don't have any data on the current sensors, they are just enclosed in white, unmarked tubes.
I thought about enlarging the openings, but I also understood air needs to be pulled through the maximum number of loops possible for proper cooling.
-
Onion Omega as a fridge controller?
Hello there,
as I have this fridge whose parts are incredibly difficult to find, incompatible, etc, I thought about using an Onion Omega to replace the existing board whose specifications are frustratingly unknown, and where no manual is available.
Keeping the absorbing coil free of ice appears to be the most difficult part of the project: the air inlet at the bottom of the coils is tiny, and easily clogged by frost. As such, only 4 days of normal use are necessary to build enough ice the fan can't push enough cold air toward the fridge. (Conversely, when the coil is completely free of ice, it takes only 20 minutes of runtime to have it turn off for 25 to 45 minutes)
A still-unresolved question is: how does so-called "adaptative defrost" work?
Would such a project be feasible for someone who doesn't have a degree in refrigeration engineering or electronic engineering?
Is the Onion Omega the right platform for this project?Existing inputs:
Temperature sensor in the freezer (likely broken, maybe reuse wiring?)
Temperature sensor in the fresh food section (likely analog)
Control panel inside to adjust temperatureFeatures would be:
Keep fresh food section at standard fridge temperature (4C or less)
Keep coil ice-freeOptional but nicer: make a LAN-accessible graph of compartment's temperature over time
In any case, just laying the idea here…
-
Omega can't start after a power outage, flashing LED
Hello there,
I have one Omega with a Mini dock. A while ago there was a power outage while it was plugged in, then the power was restored.
Now, the orange led flashes for ages, and the Omega is inaccessible through wifi. Power supply is a good Samsung cell phone charger.
How would I this random issue?