@CoffeeCat DS18B20 is a 1-Wire device. You should connect it to Omega2's 1-Wire Bus - ie. directly to an Omega2(+) GPIO.
Have you ever read this Reading a 1-Wire Temperature Sensor
Hi crispyoz,
one of onion omega developer(Lazar Demin) said below reasons
Hi Nagarjuna,
Since SPI flash cannot be easily connected and disconnected like USB storage or SD cards, the Linux kernel does not support automatic detection of SPI flash devices or partitions on the devices.
Instead, the SPI flash must be defined in the Kernel Device Tree.
See how the Omega's internal flash device and partitions are defined in the device tree specification (DTS) here: https://github.com/OnionIoT/source/blob/openwrt-18.06/target/linux/ramips/dts/OMEGA2.dtsi#L103
To support an external flash, you'll need to:
Add the SPI flash & it's partitions to the DTS
build a new firmware with the modified DTS.
I have verified it clearly. but I am worrying about onion guys are saying(Onion Corporation is not responsible for any damage to your device caused by using custom firmware or packages not built and released by Onion Corporation).
can you please help me sir how to add SPI code in custom firmware for detection of external SPI bus device.
Go-to resource for frequently asked technical questions
41
Topics
62
Posts
The existing firewall on the OS can be used to enable/disable network traffic from specific interfaces
Taking a look at /etc/config/firewall, you'll notice it has zones that control traffic flow of the network interfaces defined in /etc/config/firewall
By default, the wan firewall zone is attached to the wwan network interface.
Looking at /etc/config/network you'll see that the wwan network interface is apcli0, the Omega's WiFi client interface
We can change the wan firewall zone configuration to enable or disable traffic through this interface.
To start, my Omega is connected to WiFi and can ping the internet:
root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
64 bytes from 172.217.164.196: seq=0 ttl=115 time=18.968 ms
64 bytes from 172.217.164.196: seq=1 ttl=115 time=22.639 ms
...
Then, I'll run these commands to REJECT input and output traffic for the wan zone:
uci set firewall.@zone[1].output='REJECT'
uci set firewall.@zone[1].input='REJECT'
uci commit firewall
Note: these changes can also be made by modifying the /etc/config/firewall file directly
And restart the firewall:
/etc/init.d/firewall restart
I can no longer access the internet. The WiFi client interface is still associated with the network, but no traffic can go through:
root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
ping: sendto: Operation not permitted
root@Omega-F195:/# ping www.google.com
PING www.google.com (172.217.164.196): 56 data bytes
ping: sendto: Operation not permitted
A few notes:
The default firewall configuration only has zones for the WiFi AP and WiFi Client network interfaces. You'll need to add more zones to the firewall to control the ethernet network interface, or other network interfaces like cellular modems.
The firewall also supports creating Rules. For a deeper dive into the firewall and rules, take a look at the openwrt firewall documentation: https://openwrt.org/docs/guide-user/firewall/firewall_configuration
