You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [ChipIdea] rename Transdimension to more popular ChipIdea Highspeed,
162
+
- [ChipIdea] rename Transdimension to more popular ChipIdea Highspeed,
163
163
- [RP2040] various update/fix for hcd/dcd
164
164
- [FT9XX] new DCD port for Bridgetek FT90x and FT93x devices
165
165
- [DA1469X] Fix resume
@@ -246,7 +246,7 @@ RP2040
246
246
^^^^^^
247
247
248
248
- Add RP2040 suspend & resume support
249
-
- Implement double buffer for both host and device (#891). However device EPOUT is still single buffered due to techinical issue with short packet
249
+
- Implement double buffer for both host and device (#891). However device EPOUT is still single buffered due to techinical issue with short packet
250
250
251
251
Device Stack
252
252
------------
@@ -267,7 +267,7 @@ DFU
267
267
^^^
268
268
269
269
- Enhance DFU implementation to support multiple alternate interface and better support bwPollTimeout
270
-
- Rename CFG_TUD_DFU_MODE to simply CFG_TUD_DFU
270
+
- Rename CFG_TUD_DFU_MODE to simply CFG_TUD_DFU
271
271
272
272
HID
273
273
^^^
@@ -287,7 +287,7 @@ UAC2
287
287
^^^^
288
288
289
289
- Fix bug and enhance of UAC2
290
-
290
+
291
291
Vendor
292
292
^^^^^^
293
293
@@ -479,7 +479,7 @@ Host Controller Driver (HCD)
479
479
- Move echi/ohci files to portable/
480
480
- Rename hcd_lpc18_43 to hcd_transdimension
481
481
- Sub hcd API with hcd_ehci_init(), hcd_ehci_register_addr()
482
-
482
+
483
483
- Update NXP transdimention hcd_init() to reset controller to host mode
484
484
485
485
- Ported hcd to rt10xx
@@ -529,13 +529,13 @@ Device Controller Driver
529
529
530
530
- ESP32-S2:
531
531
- Add bus suspend and wakeup support
532
-
532
+
533
533
- SAMD21:
534
534
- Fix (walkaround) samd21 setup_packet overflow by USB DMA
535
-
535
+
536
536
- STM32 Synopsys:
537
537
- Rework USB FIFO allocation scheme and allow RX FIFO size reduction
538
-
538
+
539
539
- Sony CXD56
540
540
- Update Update Spresense SDK to 2.0.2
541
541
- Fix dcd issues with setup packets
@@ -554,17 +554,17 @@ USB Device
554
554
555
555
- CDC
556
556
- Allow to transmit data, even if the host does not support control line states i.e set DTR
557
-
557
+
558
558
- HID
559
559
- change default CFG_TUD_HID_EP_BUFSIZE from 16 to 64
560
-
560
+
561
561
- MIDI
562
562
- Fix midi sysex sending bug
563
-
563
+
564
564
- MSC
565
565
- Invoke only scsi complete callback after status transaction is complete.
566
566
- Fix scsi_mode_sense6_t padding, which cause IAR compiler internal error.
567
-
567
+
568
568
- USBTMC
569
569
- Change interrupt endpoint example size to 8 instead of 2 for better compatibility with mcu
570
570
@@ -614,20 +614,20 @@ Device Controller Driver
614
614
- Fix FIFO flush during stall
615
615
- Implement dcd_edpt_close() API
616
616
- Support F105, F107
617
-
617
+
618
618
- Enhance STM32 fsdev
619
619
- Improve dcd fifo allocation
620
620
- Fix ISTR race condition
621
621
- Support remap USB IRQ on supported MCUs
622
622
- Implement dcd_edpt_close() API
623
-
623
+
624
624
- Enhance NUC 505: enhance set configure behavior
625
625
626
626
- Enhance SAMD
627
627
- Fix race condition with setup packet
628
628
- Add SAMD11 option `OPT_MCU_SAMD11`
629
629
- Add SAME5x option `OPT_MCU_SAME5X`
630
-
630
+
631
631
- Fix SAMG control data toggle and stall race condition
632
632
633
633
- Enhance nRF
@@ -659,7 +659,7 @@ USB Device
659
659
- `usbd_driver_open()` add max length argument, and return length of interface (0 for not supported). Return value is used for finding appropriate driver
660
660
- Add application implemented class driver via `usbd_app_driver_get_cb()`
Some TinyUSB examples also requires external submodule libraries in ``/lib`` such as FreeRTOS, Lightweight IP to build. Run following command to fetch them
47
+
Some TinyUSB examples also requires external submodule libraries in ``/lib`` such as FreeRTOS, Lightweight IP to build. Run following command to fetch them
48
48
49
49
.. code-block::
50
50
51
51
$ git submodule update --init lib
52
52
53
-
Some ports will also require a port-specific SDK (e.g. RP2040) or binary (e.g. Sony Spresense) to build examples. They are out of scope for tinyusb, you should download/install it first according to its manufacturer guide.
53
+
Some ports will also require a port-specific SDK (e.g. RP2040) or binary (e.g. Sony Spresense) to build examples. They are out of scope for tinyusb, you should download/install it first according to its manufacturer guide.
54
54
55
55
Build
56
56
^^^^^
57
57
58
-
To build example, first change directory to an example folder.
58
+
To build example, first change directory to an example folder.
59
59
60
60
.. code-block::
61
61
@@ -118,7 +118,7 @@ To compile for debugging add ``DEBUG=1``\ , for example
118
118
Log
119
119
~~~
120
120
121
-
Should you have an issue running example and/or submitting an bug report. You could enable TinyUSB built-in debug logging with optional ``LOG=``. LOG=1 will only print out error message, LOG=2 print more information with on-going events. LOG=3 or higher is not used yet.
121
+
Should you have an issue running example and/or submitting an bug report. You could enable TinyUSB built-in debug logging with optional ``LOG=``. LOG=1 will only print out error message, LOG=2 print more information with on-going events. LOG=3 or higher is not used yet.
122
122
123
123
.. code-block::
124
124
@@ -127,7 +127,7 @@ Should you have an issue running example and/or submitting an bug report. You co
127
127
Logger
128
128
~~~~~~
129
129
130
-
By default log message is printed via on-board UART which is slow and take lots of CPU time comparing to USB speed. If your board support on-board/external debugger, it would be more efficient to use it for logging. There are 2 protocols:
130
+
By default log message is printed via on-board UART which is slow and take lots of CPU time comparing to USB speed. If your board support on-board/external debugger, it would be more efficient to use it for logging. There are 2 protocols:
131
131
132
132
133
133
* `LOGGER=rtt`: use `Segger RTT protocol <https://www.segger.com/products/debug-probes/j-link/technology/about-real-time-transfer/>`_
@@ -178,12 +178,12 @@ IAR Project Connection files are provided to import TinyUSB stack into your proj
178
178
179
179
180
180
* Take example of STM32F0:
181
-
181
+
182
182
- You need `stm32l0xx.h`, `startup_stm32f0xx.s`, `system_stm32f0xx.c`.
183
183
184
184
- `STM32L0xx_HAL_Driver` is only needed to run examples, TinyUSB stack itself doesn't rely on MCU's SDKs.
185
185
186
-
* Open `Tools -> Configure Custom Argument Variables` (Switch to `Global` tab if you want to do it for all your projects)
186
+
* Open `Tools -> Configure Custom Argument Variables` (Switch to `Global` tab if you want to do it for all your projects)
187
187
Click `New Group ...`, name it to `TUSB`, Click `Add Variable ...`, name it to `TUSB_DIR`, change it's value to the path of your TinyUSB stack,
0 commit comments