Host implementation of pico_multicore #440
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk#440
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would be nice to have a host implementation of the multicore functionality which uses threads (or processes?) in place of the two cores.
I've started on an implementation here: https://gist.github.com/jonathangjertsen/590141bc17ffb47d0f091c6ab82396f3
The test uses the Unity framework. I haven't made a PR because there is a known bug (
test_multicore_fifo_pop_timeout_usfails half the time and I don't know why), and also because I couldn't figure out how to integrate it into the pico-sdk build system. Feel free to build on it though.there is an implementation in
pico_host_sdlthat uses SDLhttps://github.com/raspberrypi/pico-host-sdl/blob/master/README.md
Yes I saw, but it is incomplete (in particular, no FIFO support) and it would be nice to avoid having to pull in SDL if you're testing something other than audio/video.
Yeah, i would probably have included threads by default were pthread available on windows; that said building with MSVC has issues anyway; not sure if there is a pthread impl for windows for use with gcc (or other)
Frankly, we are discouraging the use of the FIFOs (for most things anyway) anyway, as they are a unique resource (needed by RTOS impls, core 1 launch, and interrupting the other core)...
MinGW has it - not sure if it's included by default or if it has to be installed