spiderkeys / zenoh-pico-zephyr-ot-example

Example Zephyr app demonstrating Zenoh Pico over OpenThread
0 stars 0 forks source link

Setup Steps #1

Open spiderkeys opened 3 years ago

spiderkeys commented 3 years ago

Clone repo

git clone https://github.com/openthread/wpantund cd wpantund

Build

./bootstrap.sh ./configure --sysconfdir=/etc make -j3

Install

sudo make install

In a terminal, run an instance of wpantund, specifying the appropriate serial device

sudo wpantund -o Config:NCP:SocketPath /dev/ttyACM0 \ -o Config:TUN:InterfaceName wpan0 \ -o Daemon:SyslogMask " -info"

Use wpanctl to configure the network parameters and form a network that will be used to communicate with the nrf52840_mdk board.

wpanctl -Iwpan0 leave form Bristlenet -c 24 -x 109B50100E620D10 -p 0xC5E9 -k 000102030405060708090A0B0C0D0E0F permit-join 999999


After doing the above, you should be able to see status info in wpanctl similar to this:

wpanctl:wpan0> status wpan1 => [ "NCP:State" => "associated" "Daemon:Enabled" => true "NCP:Version" => "OPENTHREAD/0.01.00; NRF52840; May 21 2019 21:43:12" "Daemon:Version" => "0.08.00d (0.07.01-363-ga8f3f76; Sep 28 2021 21:29:20)" "Config:NCP:DriverName" => "spinel" "NCP:HardwareAddress" => [51D3239956E0557C] "NCP:Channel" => 26 "Network:NodeType" => "leader" "Network:Name" => "Bristlenet" "Network:XPANID" => 0x109B50100E620D10 "Network:PANID" => 0xC5E9 "IPv6:LinkLocalAddress" => "fe80::780e:66d4:cd2:831f" "IPv6:MeshLocalAddress" => "fd10:9b50:100e:0:60df:9983:d08a:c29f" "IPv6:MeshLocalPrefix" => "fd10:9b50:100e::/64" "com.nestlabs.internal:Network:AllowingJoin" => false ]

spiderkeys commented 3 years ago

Test Configuration:

Clone repo

cd bristlemouth git clone https://github.com/eclipse-zenoh/zenoh cd zenoh

Build

cargo build -j3 --all-targets

- Next, use the IPv6:MeshLocalAddress value obtained from wpanctl status to start a zenohd listener in a terminal:
```bash
# Port 7474 chosen as an example; use whatever you like
./target/debug/zenohd -l udp/fd10:9b50:100e:0:60df:9983:d08a:c29f:7474

Once this is working, switch the locators over to tcp on both sides to test that protocol (currently has issues receiving any new messages after the first 32 are received).