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

[BUG] Recent modification broke raspberry pi pico nsh #15162

Open
1 task done
acassis opened this issue Dec 12, 2024 · 6 comments
Open
1 task done

[BUG] Recent modification broke raspberry pi pico nsh #15162

acassis opened this issue Dec 12, 2024 · 6 comments
Labels
Arch: arm Issues related to ARM (32-bit) architecture Area: Board support Board support issues OS: BSD Issues related to *BSD OSes (building system, etc) OS: Linux Issues related to Linux (building system, etc) OS: Mac Issues related to MacOS (building system, etc) OS: Other Issues related to other OS (not Linux, Mac or Win) OS: Windows Issues related to Windows (building system, etc) Type: Bug Something isn't working

Comments

@acassis
Copy link
Contributor

acassis commented Dec 12, 2024

Description / Steps to reproduce the issue

Yashvi Shah reported me that she wasn't getting the nsh working on RaspberryPi Pico, then I tested here and in fact some recent modification broke the NSH.

@lupyuen is it possible to add RaspberryPi Pico to the automated test as well?

$ git clone -b 2.0.0 https://github.com/raspberrypi/pico-sdk.git

$ export PICO_SDK_PATH=/home/alan/pico-sdk

$ cd nuttxspace/nuttx

$ make distclean

You can use this script to find the board name after configure.sh just typing the inicial name of the board and pressing TAB

$ . tools/configure_completion.bash

$ ./tools/configure.sh raspberrypi-pico:nsh

$ make -j
flash: 144 KB 2 MB 7.03%
sram: 8224 B 264 KB 3.04%
Generating: nuttx.uf2
Done

Copy nuttx.uf2 to the virtual disk of raspberrypi pico and use a USB/Serial connected to GP0, GP1 and GND and reset the board, you will see the nsh is not accepting text and there is trash after the nuttx entry message (see attached image)
rp_pico_broken

On which OS does this issue occur?

[OS: BSD], [OS: Linux], [OS: Mac], [OS: Windows], [OS: Other]

What is the version of your OS?

24.04

NuttX Version

12.7 mainline

Issue Architecture

[Arch: arm]

Issue Area

[Area: Board support]

Verification

  • I have verified before submitting the report.
@acassis acassis added the Type: Bug Something isn't working label Dec 12, 2024
@github-actions github-actions bot added Arch: arm Issues related to ARM (32-bit) architecture Area: Board support Board support issues OS: BSD Issues related to *BSD OSes (building system, etc) OS: Linux Issues related to Linux (building system, etc) OS: Mac Issues related to MacOS (building system, etc) OS: Other Issues related to other OS (not Linux, Mac or Win) OS: Windows Issues related to Windows (building system, etc) labels Dec 12, 2024
@acassis
Copy link
Contributor Author

acassis commented Dec 12, 2024

@hujun260 @xiaoxiang781216 please add RaspberryPi Pico to your automated test. Does your test verify if the board nsh> is working? As you can see in this case the nsh> was displayed but the communication is not working

@acassis
Copy link
Contributor Author

acassis commented Dec 12, 2024

I tested "usbnsh" and it is working! So it is only related to UART... I have a suspect now! ;-)

Update: although the "nsh>" is working, I noticed the line feeding (breaking line) sometimes is failing, normally for commands like "free", "help", "uname", normally "ls" works fine.

@yashvi-05
Copy link

Thank you for helping me.....

@acassis
Copy link
Contributor Author

acassis commented Dec 12, 2024

Thank you for helping me.....

You are welcome @yashvi-05 ! Your test help us to discover an issue caused by recent modifications.

@hujun260
Copy link
Contributor

I tested "usbnsh" and it is working! So it is only related to UART... I have a suspect now! ;-)

Update: although the "nsh>" is working, I noticed the line feeding (breaking line) sometimes is failing, normally for commands like "free", "help", "uname", normally "ls" works fine.

Can you help us verify which commit caused it?

@acassis
Copy link
Contributor Author

acassis commented Dec 13, 2024

@hujun260 sure! I will do git bisect to find the guilt commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Arch: arm Issues related to ARM (32-bit) architecture Area: Board support Board support issues OS: BSD Issues related to *BSD OSes (building system, etc) OS: Linux Issues related to Linux (building system, etc) OS: Mac Issues related to MacOS (building system, etc) OS: Other Issues related to other OS (not Linux, Mac or Win) OS: Windows Issues related to Windows (building system, etc) Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants