Hi Martine,

Maybe [1] could help: I had to fix similar things for it to pass the CI.

Alex

[1] https://github.com/RIOT-OS/RIOT/pull/12304

----- Le 13 Jan 20, à 12:33, Martine Lenders m.lend...@fu-berlin.de a écrit :

> Hi there,
> 
> last week I ported the Adafruit Feather nRF52840 as the first board to
> use `stdio_cdc_acm` for its stdio (so stdio over USB natively). However,
> I'm facing some problems for our applications that use ethos, as it is
> only supporting `stdio_uart`. I would like to avoid to blacklist the
> board for all those applications, as it would be counter-productive to
> the work going on in [1]. It also doesn't make sense to port `ethos` for
> `stdio_cdc_acm`, as we have `usbus_cdc_ecm` (which presents the RIOT
> device to the host operating system as an Ethernet device over which the
> host can communicate with RIOT). So the ideal situation would be to use
> that instead of `ethos`. I thought that would be easy, as for e.g.
> tests/gnrc_rpl_srh I could just adapt the
> `tests/gnrc_rpl_srh/Makefile.board.dep` as follows
> 
> ```
> # Put board specific dependencies here
> ifeq (native,$(BOARD))
>  USEMODULE += netdev_tap
> else
>  ifneq (,$(filter stdio_cdc_acm,$(USEMODULE)))
>    USEMODULE += usbus_cdc_ecm
>  else
>    USEMODULE += stdio_ethos
>  endif
> endif
> ```
> 
> and compile-time-wise this works.
> 
> However, when trying to connect to the terminal the `ethos` tool is of
> course still selected [2] and I'm not sure how we would deal with this.
> I *could* just add the board to the check there, but that wouldn't scale
> for long, as I expect there to be more boards of that kind in the
> future. Moving this block to `Makefile.board.dep` helps, but I'm not
> sure it was intended that way.
> 
> How would you guys solve this?
> 
> Best regards,
> Martine
> 
> [1] https://github.com/RIOT-OS/RIOT/pull/12724
> [2]
> https://github.com/RIOT-OS/RIOT/blob/4524fb1f1ed08455bc922ecd77bc0c981c2b16a8/tests/gnrc_rpl_srh/Makefile#L12-L21
> _______________________________________________
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Reply via email to