Missing memory layout in svd #351
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#351
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?
I'm trying to implement USB driver in rust and I cannot find endpoint and buffer controll registers. It looks like there is nothing from base 0x5010000 to 0x5011000.
I confirmed that there should be controller structures in datasheet and are used in c implementation.
Am I missing something or there is some issue with svd?
I just checked, and I guess you're asking about the
USBCTRL_DPRAMstuff? https://github.com/raspberrypi/pico-sdk/blob/master/src/rp2040/hardware_regs/include/hardware/regs/addressmap.h#L65The C SDK comprises some headers that are autogenerated (hardware_regs), and some that are manually-edited (hardware_structs) - the
hardware_structsheaders generally make use of things defined in thehardware_regsheaders. The SVD file is also autogenerated.The
USBCTRL_REGSstuff appears in the autogenerated hardware_regs headers and the SVD file, but theUSBCTRL_DPRAMstuff only appears in the hand-edited headers (and therefore not the SVD).I know nothing about the USB controller in the RP2040, so pinging @liamfraser for advice on what can / should be added to the SVD file.