If no board is selected, `gnrc_border_router` would be build for `samr21-xpro`.
This seems rather arbitrary.
Select `native` instead as it is done for other examples.
This ensures that the default `make all term` works with no hardware connected.
Add ATmega328P Xplained Mini board. The board is an official
development kit from MCHP based on the Arduino UNO, reduced
hardware, with a xplainedmini debugger and CDC ACM serial
converter.
Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
Add atxmega-a1u-xpro board to BOARD_INSUFFICIENT_MEMORY list to
exclude examples since board don't have enough data memory.
Signed-off-by: Gerson Fernando Budke <nandojve@gmail.com>
If `native` is compiled with `USEMODULE=socket_zep` and networking,
don't also include `netdev_tap` automatically.
This mirrors the behavior on nrf52 and esp* where the default netdev
can be 'overwritten' by another option.
stm32mp157c-dk2 has not enough memory to build this apps.
However as the stm32mp157xx cpu line has no flash, a part of RAM
is considered as ROM. Thus ROM size could be extend to suit this
apps needs.
Signed-off-by: Gilles DOFFE <gilles.doffe@savoirfairelinux.com>
This changes the prefixes of the symbols generated from USEMODULE and
USEPKG variables. The changes are as follow:
KCONFIG_MODULE_ => KCONFIG_USEMODULE_
KCONFIG_PKG_ => KCONFIG_USEPKG_
MODULE_ => USEMODULE_
PKG_ => USEPKG_
The other applications using `sock_dns` do it too
(`tests/gnrc_sock_dns` and `tests/gnrc_ipv6_nib_dns`) and besides it
doesn't make much sense to include RDNSS option support
(aka `gnrc_ipv6_nib_dns`) just because someone uses the DNS client
(aka `sock_dns`). This dependency will be removed in a later commit.
Optionally executes pyterm from CDC-ECM start_network.sh
The shell script exits and cleans up instantly unless there is a
blocking program running at the end. Users can supply a serial port to
display in pyterm, or alternatively just wait if it is a "headless"
deployment.
Native supports multiple ZEP devices, so add a config option for it to
gnrc_border_router.
This allows for easier testing of border routers with multiple interfaces.
This adds an example configuration to use the gnrc_border_router to route
between a regular WiFi network and an esp_now network.
All you need is an esp based board (esp8266, esp32).
Configure the access data for your WiFi network in `Makefile.esp.conf`,
then run
make BOARD=esp32-wroom-32 USE_ETHOS=0 USE_ESP=1 flash term
to turn a e.g. `esp32-wroom-32` into a boarder router.
You can use other esp based boards as nodes in the network by flashing
e.g. the `gnrc_networking` example.
Be sure to add `CFLAGS += -DGNRC_IPV6_NIB_CONF_SLAAC=1` as otherwise
your esp_now node will not receive a link-local IP address.
