@Luciano-S. You keep quoting the same line. Do you work for Onion? Why are you defending their lack of support?
I fail to see why an issue with the current software requires us to wait for after the new campaign has finished.
The fix is very simple. Give us the options used in the production build environment. Just a simple cut and paste. Doesn't need a huge amount of time.
Support has been asked for this information and has not even bothered to answer. Stop promising vaporware.
@Lazar-Demin said in The Onion App SDK is here!:
Also, regarding the kernel issues, the Omega's firmware follows the head of the OpenWRT CC repo, we add customizations on top of it. After the campaign, we'll make it a priority to fix that nagging kernel version issue.
Really? We have to wait for a new product to be completed before you fix the current product?
Come on! All someone has to do is tell your build environment to build all the kmod packages against your kernel version and put the packages into your custom repo. You already build some custom modules and packages, so it can't be that hard.
One of your customers has reported that iptables cannot be installed. This is basic linux security for internet connected things.
@Kit-Bishop The one-wire protocol is a standard from Maxim/Dallas-Semi who make the devices.
The packages to support the protocol are a standard part of openWRT, so I would look on their website for information (and the source code).
There are also 1-wire implementations for the Arduino. That will be a lower level methodology and might be the information you are looking for.
I hope this points you in the right direction.
--
KCH
@Luciano-S. You keep quoting the same line. Do you work for Onion? Why are you defending their lack of support?
I fail to see why an issue with the current software requires us to wait for after the new campaign has finished.
The fix is very simple. Give us the options used in the production build environment. Just a simple cut and paste. Doesn't need a huge amount of time.
Support has been asked for this information and has not even bothered to answer. Stop promising vaporware.
Onion Omega support folks.
Please can we have instructions/information on how to produce a full onionio factory branded image.
I have created a build environment and can make images for standard openwrt. what I am struggling on is building an image that is functionally the same as the factory image, except with the additional modules that I require for my project.
Basically, this is my solution to the kmod modules not being the correct version for your supplied images.
There are multiple requests I have found in the forums for this information, but so far, no answers. There is even a comment on your Omega2 kickstarter thread from a user saying he will back your new campaign once you provide this sort of information.
If you feel this information is your proprietary code, then please add that information to the wiki article on creating the build environment.
@Lazar-Demin said in The Onion App SDK is here!:
Also, regarding the kernel issues, the Omega's firmware follows the head of the OpenWRT CC repo, we add customizations on top of it. After the campaign, we'll make it a priority to fix that nagging kernel version issue.
Really? We have to wait for a new product to be completed before you fix the current product?
Come on! All someone has to do is tell your build environment to build all the kmod packages against your kernel version and put the packages into your custom repo. You already build some custom modules and packages, so it can't be that hard.
One of your customers has reported that iptables cannot be installed. This is basic linux security for internet connected things.
I am trying to use a USB wifi dongle which is based on the rt5370 chipset.
The driver for this is not in the default image and when you try to install it via opkg, then the install fails with a kernel version mismatch.
What is the suggestion from tech support for resolving this issue?
From my point of view, if you are going to supply a new kernel with your custom images, then you need to make sure the matching kernel drivers are available in your repo as well.
This is the command I am trying to run:
opkg install kmod-rt2800-lib kmod-rt2800-usb kmod-rt2x00-lib kmod-rt2x00-usb