CFG_TUSB_OS as cmake parameter #1326

Open
opened 2023-03-26 16:41:22 -05:00 by rapzak · 6 comments
rapzak commented 2023-03-26 16:41:22 -05:00 (Migrated from github.com)

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/

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/
peterharperuk commented 2023-03-27 04:39:24 -05:00 (Migrated from github.com)

Doesn't this require a change to tinyusb and not pico-sdk?

Doesn't this require a change to tinyusb and not pico-sdk?
rapzak commented 2023-03-27 05:15:09 -05:00 (Migrated from github.com)

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

> 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
peterharperuk commented 2023-03-27 05:21:23 -05:00 (Migrated from github.com)

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.

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.
rapzak commented 2023-03-27 05:31:02 -05:00 (Migrated from github.com)
https://github.com/hathach/tinyusb/discussions/1951
mablinov commented 2023-03-27 11:03:44 -05:00 (Migrated from github.com)

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.

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.
kilograham commented 2024-07-19 22:03:08 -05:00 (Migrated from github.com)

@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

@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
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-raspberrypi/pico-sdk#1326
No description provided.