We have upgraded the community system as part of the upgrade a password reset is required for all users before login in.

Omega v1 install package kernel issue

  • @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?

  • @ArgusR

    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.

  • administrators

    @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.

  • @crispyoz

    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.

  • @ArgusR

    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/

  • @crispyoz

    Thanks. Poking about in the forums I found the latest builds for the v1, so I have the docs and the 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.

Looks like your connection to Community was lost, please wait while we try to reconnect.