Support usb with cherryusb #1057
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#1057
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?
Dear raspberrypi friends,
I have ported rp2040 usb ip with cherryusb, and provide all the device class demos, see rp2040 device demo, and host driver and demo is on going.
But i do not know if i have the chance to pr cherryusb lib in pico-sdk, can someone review and tell me? If no , i will add the custom cmake script in my repo. Thank you!
nice. we might consider adding a wrapper library that uses CherryUSB if a CMake var is set (or via find_package) (if not as a submodule) ... it will be a while before we get a chance to look at it though.
@liamfraser fyi
Thanks a lot.This can be a slow thing to do, just use your free time.
Hey @sakumisu ... we tend to have a lot going on, so sometimes it takes us a while to get back to things! We would like to add CherryUSB support to the Pico SDK in an upcoming release if you still have interest
Really? Yeah, i have interest. We will reschedule support for pico sdk, our pico sdk support is too old, and we will consider how to add cmake easily, now way is that we have the cherryusb.cmake and set some cmake variables to use.
Yeah, feel free to share a branch as you go on the CMake front - we had some similar fun with TinyUSB, because both.
I build a simple project, could you have a time to review? About demo position and library position? If you think LGTM, i will pr for them, thank you!
https://github.com/CherryUSB/pico-examples
https://github.com/CherryUSB/pico-sdk
Excellent; thank you - i will have a little play offline to get the feel of things
So now I know, it is
0rather thatUSBCTRL_REGS_BASEas areg_baselike here: https://github.com/CherryUSB/pico-examples/blob/master/usb/cherryusb/device/cdc_msc/main.c#L15. Didn't try, but maybe this was holding RISC-V back.PS. Nope :D Time tu use "debugprobe" finally for the first time :D
Because regbase is fixed in port, so init with rebase is useless.
https://github.com/raspberrypi/pico-sdk/pull/2212
https://github.com/raspberrypi/pico-examples/pull/603
move to 2.1.2 as i may add it as "pre-release" there
moving to 2.2.1 as more work is needed on the pico_stdio_usb stuff and picking between TinyUSB and CherryUSB for that