Posts made by Denys Makogon

@György-Farkas kernel was corrupted for sure, that's something I can tell you with honesty. The device was literally dead, only after inserting a microSD card with a new firmware my device was able to update itself and become functional.

@György-Farkas Okay. I did the following steps:

Please let us know how did you write the image to the Flash from that microSD card.

1. Took my microSD card and formatted, in FAT.
2. Downloaded an image from an Onion Omega official firmware repository.
3. Renamed a file to omega2.bin
4. Moved omega2.bin to the microSD card.
5. Mounted (physically) a card to its slot.
6. Turned on Omega 2+ chip with pressed restore button.
7. Picked restore from USB storage device.
8. Voila, the device was updated and functions correctly.

Please let us know how did you mount the microSD card on UBoot

I didn't do that on my own. Just followed the steps I mentioned above.

The problem was solved. The device can be restored from a microSD card, see description: https://community.onion.io/topic/3019/how-to-fix-device-firmware-with-a-microsd-card

@Marc-André-Fleischmann Hopefully, you were wrong. If you have Omega 2+ that has microSD card slot you can restore the firmware, just substitute "USD device" onto "microSD card". Going to write up an article.

@Marc-André-Fleischmann well, I don't have ethernet extension, because there was no need purchasing that one, thought.

@Marc-André-Fleischmann, since i have Omega 2+, would that work with a microSD card?

@Marc-André-Fleischmann When I started it the LED kept blinking as it supposes to do during ordinary boot and then stopped doing so, looked like dead.

I haven't tried installing new OS from USB because I don't have one at this particular moment, however, I'd try that later today. Is there any other way to make it work without USD drive at this moment?

Been trying to reset Omega 2+ chip using factory button. But it appeared to become dead.
Tried to do multiple recovery steps found across this forum, but didn't help. I tried to get debugging information from the serial port and here what I have:

[   27.629441] =====================================================
[   27.635625] Channel 1 : Dirty = 780, False CCA = 0, Busy Time = 3909, Skip Channel = FALSE
[   27.644023] Channel 2 : Dirty = 652, False CCA = 0, Busy Time = 1623, Skip Channel = FALSE
[   27.652419] Channel 3 : Dirty = 668, False CCA = 0, Busy Time = 1426, Skip Channel = FALSE
[   27.660815] Channel 4 : Dirty = 684, False CCA = 0, Busy Time = 1454, Skip Channel = FALSE
[   27.669205] Channel 5 : Dirty = 700, False CCA = 0, Busy Time = 3033, Skip Channel = FALSE
[   27.677583] Channel 6 : Dirty = 1150, False CCA = 0, Busy Time = 3913, Skip Channel = FALSE
[   27.686065] Channel 7 : Dirty = 760, False CCA = 0, Busy Time = 1967, Skip Channel = FALSE
[   27.694461] Channel 8 : Dirty = 756, False CCA = 0, Busy Time = 1824, Skip Channel = FALSE
[   27.702857] Channel 9 : Dirty = 752, False CCA = 0, Busy Time = 316, Skip Channel = FALSE
[   27.711165] Channel 10 : Dirty = 748, False CCA = 0, Busy Time = 995, Skip Channel = FALSE
[   27.719554] Channel 11 : Dirty = 1000, False CCA = 0, Busy Time = 4141, Skip Channel = FALSE
[   27.728105] =====================================================
[   27.734296] Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 2
[   27.743036] Min Dirty = 652
[   27.745865] ExChannel = 0 , 0
[   27.748879] BW        = 20
[   28.551976] device eth0.1 entered promiscuous mode
[   28.556855] device eth0 entered promiscuous mode
[   28.588837] br-wlan: port 1(eth0.1) entered forwarding state
[   28.594681] br-wlan: port 1(eth0.1) entered forwarding state
[   30.588807] br-wlan: port 1(eth0.1) entered forwarding state
[   32.028929] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944
[   32.028929]
[   32.042988] Rebooting in 3 seconds..

So, any recommendations about how to get the device back to life?

@Chris-Stratton yeah, that'll be a platform based Go 1.8 with server and agent (on each device), once device gets up it registers itself by sending its IP address, geocode if available, etc. And using server you can distribute configuration, software updated among registered devices.

As far as we all know each Omega ships with its own app named OnionConsole, that is represented as web app with pretty UI to allow remote Onion management.

But think of a use case when you need to manage simultaneously more than one device. My idea is to build a self-service platform that is responsible for device discovery, centralized configuration and software updates.

Thoughts?

@José-Luis-Cánovas will do, if you can do it faster, feel free to make a pull request.

Hello to All.
Recently i was able to perform cross-compiling for Onion Omega 2 with Golang go1.8rc3.
Full article you can find here. FYI, official Go 1.8 release will happen in next 8-10 days.
Thanks.

@simon with recent Go 1.8 release i was able to compile and run code (mux simple server) on my MacBook Pro late '15. So, there's no need to have gccgo toolchain or whatever you've need before.
Take a look at this https://github.com/denismakogon/OnionIoT-Omega2

I've been developing a lot code on Go and recent release 1.8 (it would happen in 10 days) and it would support cross-compiling for MIPS32 arch:

Go now supports 32-bit MIPS on Linux for both big-endian (linux/mips) and little-endian machines (linux/mipsle) that implement the MIPS32r1 instruction set with FPU or kernel FPU emulation. Note that many common MIPS-based routers lack an FPU and have firmware that doesn't enable kernel FPU emulation; Go won't run on such machines.

See more info here.

But here's a problem MIPS32 24k doesn't have FPU:

It’s a MIPS 24Kc CPU and supports up to the mips32r2 ISA, so far good. But what you don’t see is that the chip doesn’t have a FPU. So while a primitive Hello World C application runs just fine, once you start using Floating Point (FP) instructions it’ll crash with the aforementioned exception.

See this article.

So, my question is, does Omega2 support FPU or it doesn't?

The reason why i don't want to mess with gccgo is that i'd need to build custom firmware and would need to support it for a long time.