[Bug] 关于RP2040在WIN环境下使用ENV构建报错出现bs2_default_padded_checksummed.S未找到问题
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- c
- Domain
- build-system, embedded-iot
Research direction
Start in bsp/raspberry-pico/RP2040 and inspect packages/raspberrypi-pico-sdk-latest/SConstruct, especially line 65, along with whether bs2_default_padded_checksummed.S exists at the referenced path. Re-run scons in the RP2040 directory on Windows; done means the build no longer reports the missing source and completes successfully.
Written by the indexing model from the issue text.
Description
RT-Thread Version
master
Hardware Type/Architectures
RP2040
Develop Toolchain
Other
Describe the bug
(.venv) @DESKTOP-S0GUQ6A E:\RT-ThreadEnv\rt-thread\bsp\raspberry-pico\RP2040
$ scons
scons: Reading SConscript files ...
Newlib version: 4.1.0
Enter E:\RT-ThreadEnv\rt-thread\bsp\raspberry-pico\RP2040\packages\raspberrypi-pico-sdk-latest
scons: Reading SConscript files ...
scons: *** An executable should have exactly one target with the suffix: .exe
File "E:\RT-ThreadEnv\rt-thread\bsp\raspberry-pico\RP2040\packages\raspberrypi-pico-sdk-latest\SConstruct", line 65, in
scons: done reading SConscript files.
scons: Building targets ...
scons: building associated VariantDir targets: build
CC build\applications\main.o
CC build\board\board.o
CC build\kernel\components\drivers\core\device.o
CC build\kernel\components\drivers\ipc\completion_comm.o
CC build\kernel\components\drivers\ipc\completion_up.o
CC build\kernel\components\drivers\ipc\condvar.o
CC build\kernel\components\drivers\ipc\dataqueue.o
CC build\kernel\components\drivers\ipc\pipe.o
CC build\kernel\components\drivers\ipc\ringblk_buf.o
CC build\kernel\components\drivers\ipc\ringbuffer.o
CC build\kernel\components\drivers\ipc\waitqueue.o
CC build\kernel\components\drivers\ipc\workqueue.o
CC build\kernel\components\drivers\pin\dev_pin.o
CC build\kernel\components\drivers\serial\dev_serial.o
CC build\kernel\components\drivers\spi\dev_spi.o
CC build\kernel\components\drivers\spi\dev_spi_core.o
CC build\kernel\components\finsh\cmd.o
CC build\kernel\components\finsh\msh.o
CC build\kernel\components\finsh\msh_parse.o
CC build\kernel\components\finsh\shell.o
CC build\kernel\components\libc\compilers\common\cctype.o
CC build\kernel\components\libc\compilers\common\cstdlib.o
CC build\kernel\components\libc\compilers\common\cstring.o
CC build\kernel\components\libc\compilers\common\ctime.o
CC build\kernel\components\libc\compilers\common\cunistd.o
CC build\kernel\components\libc\compilers\common\cwchar.o
CC build\kernel\components\libc\compilers\newlib\syscalls.o
CC build\kernel\libcpu\arm\common\div0.o
CC build\kernel\libcpu\arm\common\showmem.o
CC build\kernel\src\clock.o
CC build\kernel\src\components.o
CC build\kernel\src\cpu_up.o
CC build\kernel\src\defunct.o
CC build\kernel\src\idle.o
CC build\kernel\src\ipc.o
CC build\kernel\src\irq.o
CC build\kernel\src\klibc\kerrno.o
CC build\kernel\src\klibc\kstdio.o
CC build\kernel\src\klibc\kstring.o
CC build\kernel\src\klibc\rt_vsnprintf_tiny.o
CC build\kernel\src\klibc\rt_vsscanf.o
CC build\kernel\src\kservice.o
CC build\kernel\src\mem.o
CC build\kernel\src\mempool.o
CC build\kernel\src\object.o
CC build\kernel\src\scheduler_comm.o
CC build\kernel\src\scheduler_up.o
CC build\kernel\src\thread.o
CC build\kernel\src\timer.o
AS build\libcpu\context_gcc.o
CC build\libcpu\cpuport.o
scons: *** [build\packages\raspberrypi-pico-sdk-latest\bs2_default_padded_checksummed.o] **Source packages\raspberrypi-pico-sdk-latest\bs2_default_padded_checksummed.S' not found,** needed by target build\packages\raspberrypi-pico-sdk-latest\bs2_default_padded_checksummed.o'.
scons: building terminated because of errors.
Other additional context
No response
- Dominant language
- C
- Stars
- 12.4k
- Forks
- 5.5k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 79
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RT-Thread/rt-thread
-
Arch: ARM/AArch64 Doc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
RT-Thread/rt-thread#12082 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
RT-Thread/rt-thread#11951 · 2 comments ·
Maintainers usually reply within 2 days
-
[Bug] [libc] timer_gettime 拆秒前将总纳秒截断为 uint32_t,剩余时间查询错误May be free again @Yunlk claimed this 28 days ago, and no pull request is open. Openin progress
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RT-Thread/rt-thread#11924 · 7 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
[Bug] dfs_v2 tmpfs: ftruncate(fd, 0) frees the file buffer but reports success — use-after-free read/write and double free from a legal POSIX callPossibly taken @remukisama claimed this 33 days ago. Openin progress
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RT-Thread/rt-thread#11902 · 4 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
[bsp][stm32][bluepill] README「快速上手」缺少重新生成 MDK 工程这一步,按文档操作无法编译通过May be free again @moment-NEW claimed this 50 days ago, and no pull request is open. Openin progress
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
RT-Thread/rt-thread#11818 · 4 comments · 1 assignee ·
Maintainers usually reply within 2 days
All issues in RT-Thread/rt-thread
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/nuttx-apps#4108 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
trezor/trezor-firmware#8357 ·
Maintainers usually reply within 2 days
-
ivorysql_ora: DBMS_SESSION lacks SLEEP (documented, not covered by #2763)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
good first issue kernel
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JackFurton/who-would-build-a-kernel-in-java#316 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
PE5PVB/TEF6686_ESP32#970 ·