What are the requirements for running coap_server on a board?


seems.deviant@...
 

Hello,

I'd like to check for radio connectivity between two of my ST B-L072Z-
LRWAN1 boards.

Each of those boards has a SX1276 LoRa radio transceiver connected over
SPI1. For the test purposes, I'd like Zephyr coap_server and
coap_client applications use that interface to exchange messages.

The SPI1 is enabled and configured on both boards. I've tried to run a
coap_server on a board with configured SPI1, but I got error
"join_coap_multicast_group: Could not get te default interface".

Obviously, a default network interface definition is missing from my
board configuration. As far as I understand, a networking interface is
to be defined and picked up by a particular driver - e.g Bluetooth,
Ethernet, IEEE 802.15.4.

So, How do I define a default networking interface and make it accept,
say, Ethernet packets?


Jukka Rissanen
 

Hi,

in order the upper IP stack to send packets to radio network, there
must be a network interface in the system. All IP network traffic goes
through this network interface. A network interface gets created by
NET_DEVICE_INIT() macro, typically this is located in network device
driver. There needs to be a L2 driver that depends on your network
technology, the name of the L2 is given to NET_DEVICE_INIT(). You can
see existing ethernet driver in drivers/ethernet/eth*.c for some
examples.


Cheers,
Jukka

On Fri, 2018-09-28 at 15:15 +0300, seems.deviant@... wrote:
Hello,

I'd like to check for radio connectivity between two of my ST B-
L072Z-
LRWAN1 boards.

Each of those boards has a SX1276 LoRa radio transceiver connected
over
SPI1. For the test purposes, I'd like Zephyr coap_server and
coap_client applications use that interface to exchange messages.

The SPI1 is enabled and configured on both boards. I've tried to run
a
coap_server on a board with configured SPI1, but I got error
"join_coap_multicast_group: Could not get te default interface".

Obviously, a default network interface definition is missing from my
board configuration. As far as I understand, a networking interface
is
to be defined and picked up by a particular driver - e.g Bluetooth,
Ethernet, IEEE 802.15.4.

So, How do I define a default networking interface and make it
accept,
say, Ethernet packets?



Rissanen, Jukka <jukka.rissanen@...>
 

Hi,

in order the upper IP stack to send packets to radio network, there
must be a network interface in the system. All IP network traffic goes
through this network interface. A network interface gets created by
NET_DEVICE_INIT() macro, typically this is located in network device
driver. There needs to be a L2 driver that depends on your network
technology, the name of the L2 is given to NET_DEVICE_INIT(). You can
see existing ethernet driver in drivers/ethernet/eth*.c for some
examples.


Cheers,
Jukka


On Fri, 2018-09-28 at 15:15 +0300, seems.deviant@... wrote:
Hello,

I'd like to check for radio connectivity between two of my ST B-
L072Z-
LRWAN1 boards.

Each of those boards has a SX1276 LoRa radio transceiver connected
over
SPI1. For the test purposes, I'd like Zephyr coap_server and
coap_client applications use that interface to exchange messages.

The SPI1 is enabled and configured on both boards. I've tried to run
a
coap_server on a board with configured SPI1, but I got error
"join_coap_multicast_group: Could not get te default interface".

Obviously, a default network interface definition is missing from my
board configuration. As far as I understand, a networking interface
is
to be defined and picked up by a particular driver - e.g Bluetooth,
Ethernet, IEEE 802.15.4.

So, How do I define a default networking interface and make it
accept,
say, Ethernet packets?


---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.