Omega v1 install package kernel issue
-
Hello, I have a Omega V1 running Chaos Calmer, and while trying to install some packages I'm getting:
- satisfy_dependencies_for: Cannot satisfy the following dependencies for openvpn-openssl:
*kernel (= 3.18.23-1-b2f200610f46d20ef52d269421369d0c) *
I'm running Linux Omega-1468 3.18.36
What should I do here, compile the package for this kernel, or recompile the image with the module included?
- satisfy_dependencies_for: Cannot satisfy the following dependencies for openvpn-openssl:
-
In any case, I can't seem to find any information about crosscompiling for V1
-
First of all, I don't have Omega1.
For your compilation need, there is some documentation:
https://onioniot.github.io/wiki/Tutorials/Cross-Compile.htmlStep 2 doesn't work since, there is no
git://git.openwrt.org/15.05/openwrt.git any more.You can grab the chaos_calmer by replacing the above with
git clone https://github.com/openwrt/chaos_calmer.gitI am not sure about adding "src-git onion https://github.com/OnionIoT/OpenWRT-Packages.git"
to feeds.conf.default. You can give it a try.My experience with chaos_calmer is solely based on that I was able to cross-compile chaos_calmer for a Linkit MT7688 board (which is ramips, not Atheros), by following a dated documentation for the board. The source was pulled from https://github.com/openwrt/chaos_calmer, as above.
One other thing: You need an Ubuntu 16.04 system for cross-compiling, which is still possible to install. Ubuntu 16.04 will be EOL in this April.
Update: I just downloaded the src from github did a make with no errors; it has built toolchain-mips_34kc_gcc-4.8-linaro_uClibc-0.9.33.2 under staging_dir that resembles the toolchain under staging_dir of the SDK downloadable from:
https://archive.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/HTH
ThanksThomas.
-
@ArgusR The docs for the original Omega are here:
https://onioniot.github.io/wiki/
Support for this device is not included in the build system
-
@crispyoz
The spec section of the wiki says
400 MHz MIPS 24Kc Big-Endian ProcessorIsn't that to be 34?
Thanks.
-
-
@crispyoz :
One sentence answer would require me to read the long story. This is not any crispy, to my very limited knowledge
Thanks, I will go through it.
-
@tjoseph1 I aim to be crispy
Long story short. Omega 1 is what it is, it will never be more than that.
An IoT device kickstarted in 2015 cannot be expected to be supported 5 / 6 years later. A startup that allows that kind of drag on its development strategy and/or resources will soon close its doors. I for one want Onion to continue to push forward.
-
@crispyoz:
Thanks for the short story.
I was on cellphone browser (still am).When a company of the size of mediatek is unable to support Linkit boards, we must appreciate onion; for onion supports the current boards plus running a forum that we can meet.
I have the same level of respect for you today, as I was reading ur first help msg months back.
Thanks..
-
@tjoseph1 We're all just doing our best and contributing as much as we can.
-
Thank you guys for the reply, I manage to update the firmware to 19.07.6 and then all package installation worked fine thru opkg. I have now a Omega 1 running with OpenVPN client, ser2net and 4G dongle.
Regards
-
@ArgusR Congratulations on getting it working. Not sure how useful it is long-term but an interesting academic exercise.
-
Thank you. The idea is to remote to a device over Serial, so this v1 board did the trick. But I'm looking in upgrading this, using the Omega2 LTE, but I was looking at the specs and it doesn't seems to offer the USB Host port, it's been used by the LTE module?
-
I checked the datasheet of the MediaTeck MT7688 (chip that uses the omega2 and omega2s) and I confirm that it incorporates a USB 2.0 host.
-
Hello @jossvall, I didn’t doubt that the CPU offers, but the board doesn’t seems to, my guess is that the port is been used by the LTE module incorporated. If that is the case my solution would be making my own pcb adding a hub between CPU and LTE module, so I can add more devices.
Thanks for the input.
-
Looking at the schematics I don't see anything between CPU and LTE module, so that answer my question. I will have to build my own module then.
https://github.com/OnionIoT/Omega2-LTE/blob/master/Hardware/R1.1/Omega2-LTE-v1.1-Schematic.pdf
-
@jossvall is right, the Omega2 modules do have 1x USB 2.0 Host
@ArgusR the Omega2S+ and LTE module on the Omega2 LTE are connected by USB (see the USBD+ and USBD- nets in the schematic), that's why there's no host port.
-
What I'd like to see is not continued support for legacy products, but when a device is discontinued all of the materials (docs, software, etc) are moved to a discontinued products section of the website where they are clearly marked as legacy. This might allow community support for as long as anyone is interested, and anyone has a number of devices that for some reason they are continuing to run, can build the old code and flash as they might want to until they upgrade to supported devices.
As for me I have both v1 and v2 devices (2 of each) that I recently decided to reuse and either version might do for what I had in mind, so in the case of the v1 just flashing to the final release might be advantageous. Of course I realize that any legacy devices that used a cloud service that has been shutdown, will have reduce functionality, but that is fair game.
-
Did you flash the OpenWRT version as posted on the OpenWRT site? I checked and I see the v1 is a supported device, and it actually has more RAM than other devices I am running OpenWRT on. Also the v1 is similar to other AR9331 devices, which are still supported by OpenWRT (flash size seems to be the main limiting factor).
Is your v1 stable following your update? If my Onions get used for some IoT application I hope they will run a long time. since they are basically router chips, uptimes of a year+ should be common.
-
@bill The old docs are here: https://onioniot.github.io/wiki/
-
Thanks. Poking about in the forums I found the latest builds for the v1, so I have the docs and the images:
http://repo.onion.io/omega/images/
That is enough to get my old device to the latest from whatever it happens to be running now.
I won't be making a big commitment to the v1, if it does what I want that is great. If not I have my v2s and can try a standard OpenWRT install on the v1 whenever I am inclined.
