-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
raspberrypi-pico:nshsram
configuration gets "ERROR: A RAM binary should have an entry point at the beginning: 20000001 (not 200000c1)"
#11956
Comments
In case it matters, the host system is Windows Subsystem for Linux Ubuntu 22.04 LTS. |
Same issue confirmed on Linux:
@YuuichiNakamura any idea? |
It fails the same way on a Raspberry Pi 32-bit Debian 11 and 64-bit Ubuntu 22.04. |
@masayuki2009 could you please ping Yuichi Nakamura? He is the author of nshsram board profile. |
@znmeb
|
Host is Ubuntu 22.04 LTS "jammy" on NuttX is version 12.4.0, acquired via gcc-multilib; g++-multilib:
cross-compilers - these are installed by the Raspberry Pi Pico SDK installer:
|
I can try this on Debian 12 "bookworm" if you wish - the tools that ship with it are slightly newer than the ones on Ubuntu 22.04 LTS. I can also try it on the beta of Ubuntu 24.04 LTS; I'm doing everything in containers. |
Summary: - This commit fixes apache#11956. - The issue was introduced by apache#6118. Impact: - None Testing: - Tested with raspberrypi-pico. - NOTE: the ci should be fixed later. Signed-off-by: Masayuki Ishikawa <[email protected]>
Summary: - This commit fixes #11956. - The issue was introduced by #6118. Impact: - None Testing: - Tested with raspberrypi-pico. - NOTE: the ci should be fixed later. Signed-off-by: Masayuki Ishikawa <[email protected]>
@znmeb |
Tests are done ... there's still one error. By the way, if you want to look at the scripts, they're here at the moment: https://github.com/AlgoCompSynth/CLAMS/tree/forth-itc/RPI-Pico-W-Dev-Setup |
OK, I need to change raspberrypi-pico-w:nshsram as well.
|
OK - in progress. It turns out the clone operation is
I can expand the test suite to look at other rp2040 boards. However, I don't have any of them, so I was only testing Pico and Pico W. I do have some ESP32-C3 and ESP32-S3 hardware I can test on. |
OK ... both of them work now. |
Summary: - This commit fixes apache#11956. - The issue was introduced by apache#6118. Impact: - None Testing: - Tested with raspberrypi-pico. - NOTE: the ci should be fixed later. Signed-off-by: Masayuki Ishikawa <[email protected]>
Summary: - This commit fixes #11956. - The issue was introduced by #6118. Impact: - None Testing: - Tested with raspberrypi-pico. - NOTE: the ci should be fixed later. Signed-off-by: Masayuki Ishikawa <[email protected]>
I'm getting this error with the
raspberrypi-pico:nshsram
configuration. See attached script and logfiles for the details. It fails the same way withraspberrypi-pico-w:nshsram
. None of the other Pico or Pico W configurations do this.test-error.zip
The text was updated successfully, but these errors were encountered: