The kernel objects in the Linux OS' are very capricious thing and one of the biggest problem. So... kernel object will work only in the same kernel version and build number, well I want to say these are likely static feature than dynamical as it give us.
We (users) can't append sound driver or TFT-display (frame buffer driver and his friends), PCI Express->SATA controller, etc.!
To append your own kernel object you have to build you own firmware - it's not convenient. Second way - build kernel objects on the omega (direct compilation), but it needs special tools, like linux-headers-*, that's out of repositories too.
Let's type code in Python! ((
-dev(...elopment) files install only inside SDK. Runtime OS doesn't have and need that, you can find only dynamic libraries (*.so). Static libs (*.a) don't install too.
You have to manual compile lib in the SDK, then you can see all files. But why your Python project need c-headers, It seems incorrect?!
I hadn't finished and it submitted somehow.
The Python code is:
bytes = [0xAA, 0, 0]
print "write failed"
y0 = i2c.read(0x18,4)
This returns a status byte, but zeros for the pressure data. The i2c waveforms which I captured from an oscilloscope look different enough to matter. Can I upload them here somehow?
The command bytes to read the pressure [0xAA, 0x00, 0x00} for Arduino and Onion:
And the two responses showing that the sensor only returns zeros on the Onion
The oscilloscope interprets all of the i2c bus traffic correctly, but it appears that the sensoe is never getting triggered by the [0xAA...] command to start digitizing. So it only sends back zeros. Does anybody know why the i2c waveforms are different and how to make the Onion i2c library behave as the Arduino does which works properly. I am not having any trouble with other i2c communication from the Onion, only this sensor.
Thanks to anyone who is up on this.
I'm using golang, for MQTT over ssl. The solution in our code was to use tcps for the connector and port 8333.
Granted, we're using certificates already in the ca-bundle (Amazon) for the upstream message broker, so we don't need to finagle self-signed certs.
What language are you using?
I'm going to pass on watching the video, but instead here are some tips on the setup scripts.
If you're just interested in how the wifi is configured, take a look at /usr/bin/wifisetup for the guts of the process.
If you're interested in all of the backend behind the web first-time configuration, examine the content under /www/OnionOS/static/js.
I wanted to configure IPv6 on my omega2+ - after fruitless searches on the interwebs, I decided to put into practice what I learned when making a dumb AP in openwrt. I'd say it was a case of trial and error, except there was no error, nailed it first go
First, you'll want to set up a interface to use dhcpv6 with:
uci set network.wwan6="interface"
uci set network.wwan6.proto="dhcpv6"
uci set network.wwan6.ifname="@wwan"
uci set network.wwan6.reqprefix="no"
uci commit network
then run the following:
uci show firewall | grep network
and take note of the zone that contains wwan
my output had:
So, using zone:
uci -q delete firewall.@zone.network
uci add_list firewall.@zone.network="wwan"
uci add_list firewall.@zone.network="wwan6"
uci commit firewall
service network restart
service firewall restart
You should now have a fully functional ipv6 client
@crispyoz Thanks, seems to have worked, that you! Now I just need to figure out how to import a c crc engine into my project as crcmod in python is ridiculously slow - if you've any ideas I've started a new topic.