pico-sdk icon indicating copy to clipboard operation
pico-sdk copied to clipboard

Results 538 pico-sdk issues
Sort by recently updated
recently updated
newest added

As raised in #2513, the current way of specifying stack and heap space means that on GCC the space is not included in `--print-memory-usage`, because they are not marked as...

linker scripts

## Actual problem ### Background: For some reason (I really don't know why) `clang` generates `.got` section in the `.elf` file on some scenarios even with PIE and everything related...

clang

Elsewhere we just read to clear clr_tx_abrt if the abort reason is set. Speculative fix for #1471

Add a status led library to make adapting to a "normal" led and the cyw43 led a bit easier. Bonus support for ws2812 leds.

~I unfortunately don't have any replication code to share right now, as I'm working on a project that's private for the time being.~ Edit: See next comment But the short...

documentation

I’ve encountered an issue with the current implementation of memset and memcpy in the standard library on the pico. When the SCB_CCR_UNALIGN_TRP flag is enabled to trap unaligned accesses, both...

See [here](https://github.com/raspberrypi/pico-sdk/blob/ee68c78d0afae2b69c03ae1a72bf5cc267a2d94c/src/rp2_common/hardware_watchdog/include/hardware/watchdog.h#L123C1-L133C47) The docs for the `watchdog_get_time_remaining_ms` function say it gives the time remaining in microseconds, while it should be microseconds.

hardware_watchdog

I could not find this neither in examples nor in the datasheet, but datasheet does mention that both architectures can be used at the same time, with sync primitives working...

The common pattern of while (!condition) { tud_task(); __wfe(); } which should put the processor to sleep between interrupts, becomes a busy loop by default on RP2350 due to the...

Tested with pico_cyw43_arch_lwip_sys_freertos and commit [ee68c78](https://github.com/raspberrypi/pico-sdk/commit/ee68c78d0afae2b69c03ae1a72bf5cc267a2d94c). If the thread executing _async_context_freertos_deinit()_ has higher priority than _async_context_task()_ then the _async_context_task()_ does not end immediately and _async_context_freertos_deinit()_ clears the `async_context_freertos_t` struct before...

pico_async_context