I've found this topic from @Maximilian-Gerhardt (Thank you for your excellent guide), explaining how to build kernel module for Omega2. I've found this in his topic:
It conveniently compiled the hello-world.ko file and even created an ipk package.
Unfortunetly, trying to installing that package will give you a kernel mismatch error
because the kernel hashes differ (see this link). Loading the .ko file directly will still work though.
So, I'm able to compile the kernel modules I need (copying the .ko files in /lib/modules/4.4.74/, but the ipk still does not match.
Any suggestions to compile ipk kernel modules for official firmware?
@steve-burk I like Steve's suggestion for your own problem as it will absolutely work, but in the hope of making things needlessly complex, this is what I'd do:
Create a shell script that is comprised of the commands you need to provision the route.
In your installation script (you have one, don't you? ;^), check rc.local for a reference to the script. Insert a call to rc.local if it's not in there.
Also in your install script, copy the route provisioning script to somewhere sensible, such as /usr/bin/. This directory is in the path and need not be "spelled out" in rc.local.
Perhaps you could write a script that takes routes as a command line parameter. As such you could easily call the command multiple times from rc.local to configure multiple routes or perhaps better yet, pass along not a route but a config file path that contains the routes you desire. If the latter, you just mod the route config file and reboot - voila!
If you're dabbling, this suggestion is overkill. If you're trending toward production, this is a bit more important and ought to be considered. Your mileage may vary.
i'd suggest a power supply of 5V 2A minimum. usb lines from computers and/or phone chargers most of the time do not supply the current that the omega2 needs to boot up. especially at the point where the omega2 attempts to connect to a wifi router and can generally require for a brief period of time current in excess of what a usual usb line or phone charger can provide.
Does anybody else have ... a real hard reset solution?
Here you are a "brute force" solution by Onion for the HW_RST button problem of Omega2S+.
It should work theoretically if you put a resistor between the base (1) and emitter (2) of the Q2 PNP transistor. ;-)
I wonder what about in practice because I do not have such devices. Omega2S-Dev-Board.pdf
I am guessing you are programming in python with pyserial installed. It seems that the readline() would return a empty line, and therefore its printing nulls. This is because of the timeout being passed with 1. The print statement adds a newline at the end, so it will keep printing newlines. This is why you would see your text momentarily.
You may want to use print(data, end="") if you don't want to add newlines at every print statement.
You may want to check if there is data on the returned readline() before passing to print(data), as it would keep printing empty strings.
Which firmware are you running? In the latest builds (b176 and up) we've done an overhaul of the wifi driver and the wifisetup script. You can install the latest firmware by running oupgrade --latest