-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
mps2_an521: no input to shell from Windows qemu host #30770
Labels
area: UART
Universal Asynchronous Receiver-Transmitter
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Comments
cmake/emu/qemu.cmake uses After changing line 17 as follows, setting NAMES qemu-system-${QEMU_binary_suffix} qemu-system-${QEMU_binary_suffix}.exe |
Serial input is working with board |
sw
changed the title
no input to shell from Windows qemu host
mps2_an521: no input to shell from Windows qemu host
Dec 22, 2020
FFIW this is not related to Windows. |
galak
added a commit
to galak/zephyr
that referenced
this issue
Feb 15, 2021
The CMSDK uart interrupts for TX and RX can either be treated as a signel interrupt line or distinct interrupts for TX & RX. In the case that they were distinct we didn't get the ifdef correct based on DTS. If we have 2 interrupts in DTS we assume they are for TX & RX and thus build the interrupt support for distinct TX & RX ISRs. Also, cleanup handling of UART_2..UART_4 to be similar to how UART_0/UART_1 code is using DT_INST_IRQN(x). Fixes zephyrproject-rtos#30770 Fixes zephyrproject-rtos#25601 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
nashif
pushed a commit
that referenced
this issue
Feb 15, 2021
The CMSDK uart interrupts for TX and RX can either be treated as a signel interrupt line or distinct interrupts for TX & RX. In the case that they were distinct we didn't get the ifdef correct based on DTS. If we have 2 interrupts in DTS we assume they are for TX & RX and thus build the interrupt support for distinct TX & RX ISRs. Also, cleanup handling of UART_2..UART_4 to be similar to how UART_0/UART_1 code is using DT_INST_IRQN(x). Fixes #30770 Fixes #25601 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
zephyrbot
pushed a commit
that referenced
this issue
Apr 7, 2021
The CMSDK uart interrupts for TX and RX can either be treated as a signel interrupt line or distinct interrupts for TX & RX. In the case that they were distinct we didn't get the ifdef correct based on DTS. If we have 2 interrupts in DTS we assume they are for TX & RX and thus build the interrupt support for distinct TX & RX ISRs. Also, cleanup handling of UART_2..UART_4 to be similar to how UART_0/UART_1 code is using DT_INST_IRQN(x). Fixes #30770 Fixes #25601 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
galak
added a commit
that referenced
this issue
Apr 8, 2021
The CMSDK uart interrupts for TX and RX can either be treated as a signel interrupt line or distinct interrupts for TX & RX. In the case that they were distinct we didn't get the ifdef correct based on DTS. If we have 2 interrupts in DTS we assume they are for TX & RX and thus build the interrupt support for distinct TX & RX ISRs. Also, cleanup handling of UART_2..UART_4 to be similar to how UART_0/UART_1 code is using DT_INST_IRQN(x). Fixes #30770 Fixes #25601 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: UART
Universal Asynchronous Receiver-Transmitter
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Describe the bug
Trying to run a sample with shell functionality and have it work in an emulated ARM machine on a Windows host.
The sample runs and prints the shell prompt, but no input from keyboard is possible.
To Reproduce
Run in Windows command prompt (cmd):
Expected behavior
I expect to be able to enter shell commands and have them executed.
Impact
Prevents manual use of shell for testing/dev purposes
Logs and console output
Environment (please complete the following information):
Windows 10
QEMU version 5.1.92 (v5.2.0-rc2-11843-gf571c4ffb5-dirty)
Additional context
What's the correct way of specifying the Qemu path? Setting the
QEMU_BIN_PATH
environment variable doesn't seem to work.We are using the board
mps2_an521
because that seems to be the only emulated board with a Cortex-M33 processor. We would really like to emulate an nRF5340.The text was updated successfully, but these errors were encountered: