There have been some discussions: viewtopic.php?t=384468&start=25#p2297923
Also: https://github.com/raspberrypi/pico-sdk/issues/2340
For me it works with *libg.a:*libc_a-mem*.o, not *libc.a:*lib_a-mem*.o, neither *libg.a:*lib_a-mem*.o (typos?)
as it seems to come from here:
../lib/gcc/arm-none-eabi/14.2.1/thumb/v8-m.main+fp/softfp\libg.a(libc_a-memset.o)
../lib/gcc/arm-none-eabi/14.2.1/thumb/v8-m.main+fp/softfp\libg.a(libc_a-memcpy.o)
and now it goes in RAM,
(it could be faster running form SCRATCH sections, separate copies for each core, though I don't know if it breaks something, or it's feasible)Maybe it's a typo, probably worth reporting.
Also: https://github.com/raspberrypi/pico-sdk/issues/2340
For me it works with *libg.a:*libc_a-mem*.o, not *libc.a:*lib_a-mem*.o, neither *libg.a:*lib_a-mem*.o (typos?)
as it seems to come from here:
../lib/gcc/arm-none-eabi/14.2.1/thumb/v8-m.main+fp/softfp\libg.a(libc_a-memset.o)
../lib/gcc/arm-none-eabi/14.2.1/thumb/v8-m.main+fp/softfp\libg.a(libc_a-memcpy.o)
and now it goes in RAM,
(it could be faster running form SCRATCH sections, separate copies for each core, though I don't know if it breaks something, or it's feasible)
Code:
20000704 <memcpy>:20000704:4684 movip, r020000706:ea41 0300 orr.wr3, r1, r02000070a:f013 0303 ands.wr3, r3, #32000070e:d149 bne.n200007a4 <memcpy+0xa0>20000710:3a40 subsr2, #64@ 0x4020000712:d323 bcc.n2000075c <memcpy+0x58>20000714:680b ldrr3, [r1, #0]20000716:6003 strr3, [r0, #0]20000718:684b ldrr3, [r1, #4]2000071a:6043 strr3, [r0, #4]2000071c:688b ldrr3, [r1, #8]...Statistics: Posted by gmx — Tue Feb 24, 2026 2:23 am