| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
-Wuninitialized, -Wunused, -Wredundant-decls
|
|
CFG_TUSB_RHPORT0_MODE
|
|
|
|
remove the usage of TUD_OPT_RHPORT in class driver
|
|
- BOARD_DEVICE/HOST_RHPORT_NUM to BOARD_TUD/H_RHPORT
- BOARD_DEVICE/HOST_RHPORT_SPEED to BOARD_TUD/H_MAX_SPEED
|
|
|
|
LUN1 of msc_disk_dual will be set to not ready to simulate medium not
present (e.g SD card removed)
|
|
update comment for unit not ready 3a-00 additional sense
|
|
|
|
And switch to a single file that can include mcu, family or board.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
USB3CV tool complains about too short serial number being used
in MSC device.
This just extends serial number to 12 characters, it makes it
easier to analyze USB3CV logs where this unnecessary warning
made output red.
Offending warning:
Serial Number string for MSC device : iSerialNumber = 0x3
Checking iSerialNumber String Descriptor: index = 0x03.
String Descriptor : "123456". (ENGLISH_US)
Using Language ID 0x409
MSC Serial Number length = 14
Invalid MSC Serial Number length : should be >= 26
*************************
Invalid MSC Serial Number length
*************************
*************************
(MSC: 5.1.2) Serial number must be a string, 12 characters or longer
(if the device supports a BOT interface, bInterfaceProtocol = 0x50),
or exactly 12 characters long (if the device supports a CBI interface,
bInterfaceProtocol = 0x00 or 0x01, and has a serial number).
|
|
|
|
Add in endpoint definitions for the Bridgetek devices in usb_descriptors.c and allow high speed in tusb_config.h.
|
|
tud_descriptor_other_speed_configuration_cb()
example implement tud_descriptor_device_qualifier_cb() and
tud_descriptor_other_speed_configuration_cb() on high speed device to
fully compliant to usbcv
|
|
|
|
|
|
|
|
remove TUSB_DESC_CONFIG_ATT_REMOTE_WAKEUP attribute from non-hid
examples
|
|
|
|
|
|
Signed-off-by: MasterPhi <[email protected]>
|
|
Signed-off-by: Rafael Silva <[email protected]>
|
|
|
|
|
|
- Examples should be CMake buildable from their own subdirectory; such a build will error out based on
matching .skip.MCU_xxx or a mismatched .only.MCU_
- It should be possible to build from a higher level and use .skip.MCU_ and .only.MCU_ to filter which
examples get built
- The intention is for the CMakeLists.txts in the examples to be non family specific and without MCU based IFs. I have
started this work, but am not really sure the state of the esp32 stuff; in any case the plan is to have
everything encapsulated in the FAMILY/family.cmake
- pico_examples now just includes examples/device/CMakeLists.txt and examples/host/CMakeLists.txt directly, as they
also build correctly when included from there.
Note that .skip.MCU_ for esp32 in the directories it wasn't previously avaiable has not been added, as the .skip is common to the regular Makefile builds also. It isn't clear whether these examples should build for esp32, but if not .skip should be added.
|
|
|
|
`hw\bsp` separate one family folder to esp32s2, esp32s3
add board specific board.cmake file to override board specific options(features)
fix examples and test scripts to use new family approach
|
|
add support of new esp32s3 target and the board
update the roles.mk wrapper to allow dfu flashing of espressif chip
update examples to allow compilation for esp32s3_addax_1 board
once the code is tested the PR to original tinyusb repo will be submitted
|
|
also try to update ci
|
|
|
|
- also use boot2_generic_03h for now for itsy bitsy and qt rp2040
- change default flash target for rp2040 to flash-pyocd
|
|
|
|
- move target_link_libraries() to family.cmake
- enable pico_bootsel_via_double_reset
|
|
|
|
- PICO_RP2040_USB_DEVICE_ENUMERATION_FIX=1
- target linke pico_fix_rp2040_usb_device_enumeration
|
|
|
|
Update Spresense SDK and fix dcd issues
|
|
|
|
|
|
|
|
|