mirror of
https://github.com/espressif/esp-idf.git
synced 2024-09-27 01:23:26 -04:00
216 lines
11 KiB
Markdown
216 lines
11 KiB
Markdown
| Supported Targets | ESP32-S2 | ESP32-S3 |
|
|
| ----------------- | -------- | -------- |
|
|
|
|
# TinyUSB Mass Storage Device Example
|
|
|
|
(See the README.md file in the upper level 'examples' directory for more information about examples.)
|
|
|
|
Mass Storage Devices are one of the most common USB devices. It use Mass Storage Class (MSC) that allow access to their internal data storage.
|
|
This example contains code to make ESP based device recognizable by USB-hosts as a USB Mass Storage Device.
|
|
It either allows the embedded application i.e. example to access the partition or Host PC accesses the partition over USB MSC.
|
|
They can't be allowed to access the partition at the same time.
|
|
|
|
This example supports storage media of two types:
|
|
1. SPI Flash
|
|
2. SD MMC Card
|
|
|
|
Data is read/written from/to SPI Flash through wear-levelling APIs. Wear leveling is a technique that helps to distribute wear and tear among sectors more evenly without requiring any attention from the user. As a result, it helps in extending the life of each sector of the Flash memory.
|
|
|
|
As a USB stack, a TinyUSB component is used.
|
|
|
|
## How to use example
|
|
|
|
### Scenarios
|
|
1. USB which accesses the ESP MSC Partition is unplugged initially and the board is powered-on.
|
|
- Result: Host PC can't access the partition over USB MSC. Application example can perform operations (read, write) on partition.
|
|
2. USB which accesses the ESP MSC Partition is already plugged-in at boot time.
|
|
- Result: Host PC recongnize it as removable device and can access the partition over USB MSC. Application example can't perform any operation on partition.
|
|
3. USB which accesses the ESP MSC Partition is plugged-in at boo-up. After boot-up, it is ejected on Host PC manually by user.
|
|
- Result: Host PC can't access the partition over USB MSC. Application example can perform operations (read, write) on partition.
|
|
4. USB which accesses the ESP MSC Partition is plugged-in at boot-up. It is then unplugged(removed) from Host PC manually by user.
|
|
- Result: The behaviour is different for bus-powered devices and self-powered devices
|
|
- (a) Bus-Powered devices - Both Host PC as well as application example can't access the partition over USB MSC. Here, the device will be Powered-off.
|
|
- (b) Self-Powered devices - Here, the device can be powered-on even after unplugging the device from Host PC. These behaviour can be further categorize in two ways:
|
|
- (i) Self-Powered Devices without VBUS monitoring - Both Host PC as well as application example can't access the partition over USB MSC.
|
|
- (ii) Self-Powered Devices with VBUS monitoring - Host PC can't access the partition over USB MSC. Application example can perform operations (read, write) on partition. Here, in ``tinyusb_config_t`` user must set ``self_powered`` to ``true`` and ``vbus_monitor_io`` to GPIO number (``VBUS_MONITORING_GPIO_NUM``) that will be used for VBUS monitoring.
|
|
|
|
### Hardware Required
|
|
|
|
1. If the storage media is SPI Flash, any ESP board that have USB-OTG is supported.
|
|
2. If the storage media is SD MMC Card, any ESP board with SD MMC card slot and an SD card is required. For Ex - ESP32-S3-USB-OTG
|
|
|
|
### Pin Assignment
|
|
|
|
_Note:_ In case your board doesn't have micro-USB connector connected to USB-OTG peripheral, you may have to DIY a cable and connect **D+** and **D-** to the pins listed below.
|
|
|
|
See common pin assignments for USB Device examples from [upper level](../../README.md#common-pin-assignments).
|
|
|
|
Next, for Self-Powered Devices with VBUS monitoring, user must set ``self_powered`` to ``true`` and ``vbus_monitor_io`` to GPIO number (``VBUS_MONITORING_GPIO_NUM``) that will be used for VBUS monitoring.
|
|
|
|
### Additional Pin assignments for ESP32-S3 for accessing SD MMC Card
|
|
|
|
On ESP32-S3, SDMMC peripheral is connected to GPIO pins using GPIO matrix. This allows arbitrary GPIOs to be used to connect an SD card. In this example, GPIOs can be configured in two ways:
|
|
|
|
1. Using menuconfig: Run `idf.py menuconfig` in the project directory, open "USB DEV MSC Example Configuration" and select "SDMMC CARD" for "Storage Media Used".
|
|
2. In the source code: See the initialization of ``sdmmc_slot_config_t slot_config`` structure in the example code.
|
|
|
|
The table below lists the default pin assignments.
|
|
|
|
When using an ESP32-S3-USB-OTG board, this example runs without any extra modifications required. Only an SD card needs to be inserted into the slot.
|
|
|
|
ESP32-S3 pin | SD card pin | Notes
|
|
--------------|-------------|------------
|
|
GPIO36 | CLK | 10k pullup
|
|
GPIO35 | CMD | 10k pullup
|
|
GPIO37 | D0 | 10k pullup
|
|
GPIO38 | D1 | not used in 1-line SD mode; 10k pullup in 4-line mode
|
|
GPIO33 | D2 | not used in 1-line SD mode; 10k pullup in 4-line mode
|
|
GPIO34 | D3 | not used in 1-line SD mode, but card's D3 pin must have a 10k pullup
|
|
|
|
By default, this example uses 4 line SD mode, utilizing 6 pins: CLK, CMD, D0 - D3. It is possible to use 1-line mode (CLK, CMD, D0) by changing "SD/MMC bus width" in the example configuration menu (see `CONFIG_EXAMPLE_SDMMC_BUS_WIDTH_1`).
|
|
|
|
Note that even if card's D3 line is not connected to the ESP chip, it still has to be pulled up, otherwise the card will go into SPI protocol mode.
|
|
|
|
### Build and Flash
|
|
|
|
1. By default, the example will compile to access SPI Flash as storage media. Here, SPI Flash Wear Levelling WL_SECTOR_SIZE is set to 512 and WL_SECTOR_MODE is set to PERF in Menuconfig.
|
|
2. In order to access SD MMC card as storage media, configuration has to be changed using `idf.py menuconfig`:
|
|
- i. Open "USB DEV MSC Example Configuration" and select "SDMMC CARD" for "Storage Media Used"
|
|
- ii. Open "SD/MMC bus width" and select between "4 lines (D0 - D3)" or "1 line (D0)"
|
|
- iii. Select the GPIO Pin numbers for SD Card Pin.
|
|
- iv. Save the configuration.
|
|
|
|
Build the project and flash it to the board, then run monitor tool to view serial output:
|
|
|
|
```bash
|
|
idf.py -p PORT flash monitor
|
|
```
|
|
|
|
(Replace PORT with the name of the serial port to use.)
|
|
|
|
(To exit the serial monitor, type ``Ctrl-]``.)
|
|
|
|
See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects.
|
|
|
|
## Example Output
|
|
|
|
After the flashing you should see the output at idf monitor:
|
|
|
|
```
|
|
I (311) cpu_start: Starting scheduler on PRO CPU.
|
|
I (0) cpu_start: Starting scheduler on APP CPU.
|
|
I (332) gpio: GPIO[4]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
|
|
I (332) example_msc_main: Initializing storage...
|
|
I (342) example_msc_storage: Initializing wear levelling
|
|
I (350) example_main: Mount storage...
|
|
I (350) example_sdmmc: Initializing FAT
|
|
I (372) example_msc_main: USB MSC initialization
|
|
I (372) tusb_desc:
|
|
┌─────────────────────────────────┐
|
|
│ USB Device Descriptor Summary │
|
|
├───────────────────┬─────────────┤
|
|
│bDeviceClass │ 239 │
|
|
├───────────────────┼─────────────┤
|
|
│bDeviceSubClass │ 2 │
|
|
├───────────────────┼─────────────┤
|
|
│bDeviceProtocol │ 1 │
|
|
├───────────────────┼─────────────┤
|
|
│bMaxPacketSize0 │ 64 │
|
|
├───────────────────┼─────────────┤
|
|
│idVendor │ 0x303a │
|
|
├───────────────────┼─────────────┤
|
|
│idProduct │ 0x4002 │
|
|
├───────────────────┼─────────────┤
|
|
│bcdDevice │ 0x100 │
|
|
├───────────────────┼─────────────┤
|
|
│iManufacturer │ 0x1 │
|
|
├───────────────────┼─────────────┤
|
|
│iProduct │ 0x2 │
|
|
├───────────────────┼─────────────┤
|
|
│iSerialNumber │ 0x3 │
|
|
├───────────────────┼─────────────┤
|
|
│bNumConfigurations │ 0x1 │
|
|
└───────────────────┴─────────────┘
|
|
I (532) TinyUSB: TinyUSB Driver installed
|
|
I (532) example_msc_main: USB MSC initialization DONE
|
|
I (552) example_msc_main:
|
|
ls command output:
|
|
README.MD
|
|
.fseventsd
|
|
|
|
Type 'help' to get the list of commands.
|
|
Use UP/DOWN arrows to navigate through command history.
|
|
Press TAB when typing command name to auto-complete.
|
|
esp32s3> I (912) example_msc_main: tud_mount_cb MSC START: Expose Over USB
|
|
I (912) example_msc_main: Unmount storage...
|
|
I (2032) example_msc_main: tud_msc_scsi_cb() invoked: SCSI_CMD_PREVENT_ALLOW_MEDIUM_REMOVAL
|
|
I (2032) example_msc_main: tud_msc_capacity_cb() size(1024000), sec_size(512)
|
|
esp32s3>
|
|
esp32s3>
|
|
esp32s3> help
|
|
help
|
|
Print the list of registered commands
|
|
|
|
read
|
|
read BASE_PATH/README.MD and print its contents
|
|
|
|
write
|
|
create file BASE_PATH/README.MD if it does not exist
|
|
|
|
size
|
|
show storage size and sector size
|
|
|
|
expose
|
|
Expose Storage to Host
|
|
|
|
status
|
|
Status of storage exposure over USB
|
|
|
|
exit
|
|
exit from application
|
|
|
|
esp32s3>
|
|
esp32s3> read
|
|
E (19102) example_msc_main: storage exposed over USB. Application can't read from storage.
|
|
Command returned non-zero error code: 0xffffffff (ESP_FAIL)
|
|
esp32s3> write
|
|
E (22412) example_msc_main: storage exposed over USB. Application can't write to storage.
|
|
Command returned non-zero error code: 0xffffffff (ESP_FAIL)
|
|
esp32s3> size
|
|
E (24962) example_msc_main: storage exposed over USB. Application can't access storage
|
|
Command returned non-zero error code: 0xffffffff (ESP_FAIL)
|
|
esp32s3> status
|
|
storage exposed over USB: Yes
|
|
esp32s3>
|
|
esp32s3>
|
|
esp32s3> I (49692) example_msc_main: tud_msc_scsi_cb() invoked: SCSI_CMD_PREVENT_ALLOW_MEDIUM_REMOVAL
|
|
I (49692) example_msc_main: tud_msc_start_stop_cb() invoked, power_condition=0, start=0, load_eject=1
|
|
I (49702) example_msc_main: tud_msc_start_stop_cb: MSC EJECT: Mount on Example
|
|
I (49712) example_msc_main: Mount storage...
|
|
I (49712) example_msc_storage: Initializing FAT
|
|
I (49712) example_msc_main:
|
|
ls command output:
|
|
README.MD
|
|
esp32s3>
|
|
esp32s3>
|
|
esp32s3> status
|
|
storage exposed over USB: No
|
|
esp32s3> read
|
|
Mass Storage Devices are one of the most common USB devices. It use Mass Storage Class (MSC) that allow access to their internal data storage.
|
|
In this example, ESP chip will be recognised by host (PC) as Mass Storage Device.
|
|
Upon connection to USB host (PC), the example application will initialize the storage module and then the storage will be seen as removable device on PC.
|
|
esp32s3> write
|
|
esp32s3> size
|
|
storage size(1024000), sec_size(512)
|
|
esp32s3>
|
|
esp32s3> expose
|
|
I (76402) example_msc_main: Unmount storage...
|
|
esp32s3> I (76772) example_msc_main: tud_msc_scsi_cb() invoked: SCSI_CMD_PREVENT_ALLOW_MEDIUM_REMOVAL
|
|
I (76772) example_msc_main: tud_msc_capacity_cb() size(1024000), sec_size(512)
|
|
esp32s3>
|
|
esp32s3> status
|
|
storage exposed over USB: Yes
|
|
esp32s3>
|
|
esp32s3>
|
|
```
|