| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
across all families
|
|
|
|
|
|
|
|
|
|
Fix broken fuzzing harness
|
|
|
|
|
|
|
|
Refactor event signal generation to limit bus signal events generated by fuzzing harnesses. The main point is that the issues listed by OSS-Fuzz does not seem to be true positives https://issues.oss-fuzz.com/issues?q=project%3Dtinyusb%20status%3Dnew
For example, the existing set up could generate USBD_EVENT_FUNC_CALL which is explicitly not a DCD event.
This fixes the harnesses so they don't run into several of the oss-fuzz open issues.
|
|
|
|
|
|
|
|
|
|
adjust CLI configuration and HIL tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
`FSDEV_BUS_32BIT` with `CFG_TUSB_FSDEV_32BIT`, adjust data/address stride macros, and refactor register/PMU access for consistency across platforms.
|
|
|
|
|
|
|
|
for clarity and flexibility
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
separate tud_mtp_data_send() and tud_mtp_data_receive()
|
|
separate tud_mtp_data_send() and tud_mtp_data_receive()
|
|
|
|
|
|
HWFIFO access-mode refactor and stride-aware FIFO fixes across FSDEV/RUSB2/MUSB
|
|
rusb use custom write
enable all hil test for ra4m1
|
|
|
|
|
