CFG_TUSB_OS as cmake parameter #1326
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#1326
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?
Hi,
Could you add a cmake parameter to set the CFG_TUSB_OS
This way we can use the SDK's tinyusb lib in freertos programs as well...
see:
https://www.eevblog.com/forum/microcontrollers/rp2040-how-to-use-freertos-with-tinyusb/
Doesn't this require a change to tinyusb and not pico-sdk?
I am not an expert, but i see it as a mix, because the tinyusb is both used as a part of SDK usage and final program....
I think it is a user config, the SDK set behind the user program....
Another way is to not use any Tinyusb from sdk, and link in your own version, but think it would be a pitty...
/Kasper
What I mean is, you can already define CFG_TUSB_OS on the cmake command line. The issue is that the tinyusb cmake file won't use it. I guess we can raise a PR against tinyusb to fix this.
https://github.com/hathach/tinyusb/discussions/1951
Without intending to derail the topic - I'm a bit surprised that FreeRTOS isn't provided as part of the pico-sdk by default. It's a very common framework, and the rp2040 is particularly unique in that it provides possibility of SMP FreeRTOS. I think it would make sense to include it out of the box.
@liamfraser just in case you are passing; though enabling it may not be much help until we go and check FreeRTOS support is integrated properly