tinyusb.git/examples/device/msc_dual_lun, branch 0.13.0Unnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/tinyusb.git/atom/examples/device/msc_dual_lun?h=0.13.02022-02-15T15:40:08Zmsc example response PREVENT_ALLOW_MEDIUM_REMOVAL command as unsupported command2022-02-15T15:40:08Zhathachthach@tinyusb.org2022-02-15T15:40:08Zurn:sha1:391edc7afb06359c7064752b1374550d1b526901
LUN1 of msc_disk_dual will be set to not ready to simulate medium not
present (e.g SD card removed)
Unify skip and only logic for build scripts2022-01-05T23:44:23ZScott Shawcroftscott@tannewt.org2022-01-05T23:44:23Zurn:sha1:7b27b8f498a185d8a7c1bea5dac8f43e7030ebd7
And switch to a single file that can include mcu, family or board.
msc examples: Extend serial number to 12 digits2021-10-15T12:07:40ZJerzy Kasenbergjerzy.kasenberg@codecoup.pl2021-10-15T11:47:49Zurn:sha1:9a688224d0b19a7b4d33c8bb767d0486d5b1bccd
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).
fix msc example with out of bound lba (due to compliant test)2021-08-28T13:26:56Zhathachthach@tinyusb.org2021-08-28T13:26:56Zurn:sha1:54013737d5949152959e470d3df3d0465296e251correct msc example return type of tud_msc_scsi_cb()2021-08-27T18:23:20Zhathachthach@tinyusb.org2021-08-27T18:23:20Zurn:sha1:a53839ef44345377e863e4635909c2dacc81f059update msc driver to pass MSC BOT error recovery compliant test2021-08-27T05:38:41Zhathachthach@tinyusb.org2021-08-27T05:38:41Zurn:sha1:9394de6ae74cf01ba8c8f1dab57dbbdfad6d6407TD 9.12 remote wakeup test2021-08-26T10:08:22Zhathachthach@tinyusb.org2021-08-26T10:08:22Zurn:sha1:ed4602158bb4e19f4dba122383be1c4845914bde
remove TUSB_DESC_CONFIG_ATT_REMOTE_WAKEUP attribute from non-hid
examples
Make examples standalone buildable via CMake2021-06-10T15:11:20Zgraham sandersongraham.sanderson@raspberrypi.com2021-06-10T15:11:20Zurn:sha1:fd7b18a4f6417c214b2b8880b3a640c39f587019Rework rp2040 examples and CMake build:2021-05-31T01:13:47Zgraham sandersongraham.sanderson@raspberrypi.com2021-05-30T23:41:07Zurn:sha1:95f2478146ef83d18b52408c0692222bf2a15053
- 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.
cmake cleanup2021-04-19T06:30:04Zhathachthach@tinyusb.org2021-04-19T06:30:04Zurn:sha1:59f0fa1e5e6767602c346bdd9371bf7d6caa9d08