Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

driver/mrf24j40: blocks shell input with auto_init_gnrc_netif #12943

Open
BastogneBas opened this issue Dec 13, 2019 · 1 comment
Open

driver/mrf24j40: blocks shell input with auto_init_gnrc_netif #12943

BastogneBas opened this issue Dec 13, 2019 · 1 comment
Assignees
Labels
Area: drivers Area: Device drivers Area: network Area: Networking Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)

Comments

@BastogneBas
Copy link

BastogneBas commented Dec 13, 2019

Description

When using a nucleo-f401re board and a mrf24j40 transceiver, the shell is broken and does not accept any user input. It works again when I remove the line USEMODULE += auto_init_gnrc_netif in the Makefile. After some investigation I discovered that it is caused by the mrf24j40 specific initialization.

I am able to run the shell commands manually with the function handle_input_line defined in sys/shell.c. The communication between the board and the transceiver does work perfectly. It is just the shell which doesn't see any input.

Steps to reproduce the issue

I did only have the nucleo-f401re and the mrf24j40 connected to it.
Compile and run examples/gnrc_networking with options USEMODULE=mrf24j40 and BOARD=nucleo-f401re
Then try to run commands in the shell.

Expected results

The shell sees the input and executes the commands

Actual results

RIOT network stack example application
All up, running the shell now
> ifconfig
help

Versions

OS: Linux
Build environment: arm-none-eabi-gcc version 9.2.0 (Arch Repository)

@aabadie aabadie added Area: network Area: Networking Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Area: drivers Area: Device drivers labels Jan 3, 2020
@miri64 miri64 added this to the Release 2020.07 milestone Jul 6, 2020
@benpicco
Copy link
Contributor

benpicco commented Aug 17, 2020

Does it still get stuck if you add CFLAGS += -DCONFIG_MRF24J40_TEST_SPI_CONNECTION=1?
Sounds like a wiring issue.

@MrKevinWeiss MrKevinWeiss removed this from the Release 2021.07 milestone Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: drivers Area: Device drivers Area: network Area: Networking Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

No branches or pull requests

6 participants