Michael van Elst wrote:
On Sun, Feb 04, 2024 at 10:37:59AM +0200, Staffan Thomen wrote:
[ 214.0188739] umass0: NXP (0x1fc9) LPC1XXX IFLASH (0x000b), rev 2.00/7.04,
[ 214.0288745] sd0(umass0:0:0:0): sense debug information:
[ 214.0288745] code 0x70 valid 0
[ 214.0288745] seg 0x0 key 0x2 ili 0x0 eom 0x0 fmark 0x0
[ 214.0288745] info: 0x0 0x0 0x0 0x0 followed by 10 extra bytes
[ 214.0288745] extra (up to 10 bytes): 0x0 0x0 0x0 0x0 0x30 0x1 0x0 0x0
0x0 0x0
That's what the device answers, but I cannot tell why. Maybe
the device is not (yet) in the correct mode to accept USB
access.
The product code 0x1fc9:0x000b seems to be a LPC11U24,
there is an application note AN11305 from NXP for
"USB In-System Programming with th LPC11U3X/LPC1U2X",
but I didn't find any hints in that document.
I found this document and as it seemed from it I could just copy the
file in windows, I did this and it still boots so I guess it's updated.
While I was fiddling around with it, I booted a FreeBSD-14 thumbdrive
and there it does work as well, and their driver helpfully tells you
what quirks it uses. This is what I found:
umass quirks: 0xc104
0x0004 - NO_START_STOP, "The drive does not support START STOP"
0x0100 - NO_GETMAXLUN, "No GetMaxLun call"
0x4000 - NO_SYNCHRONIZE_CACHE, "Deice cannot handle a SCSI synchronize
cache command."
0x8000 - NO_PREVENT_ALLOW, "Device does not support PREVENT/ALLOW MEDIUM
REMOVAL"
da: quirks: 0x2
0x2 NO_6_BYTE - use SBC (10-byte) commands instead of RBC (6-byte) commands
Might something here be the culprit? If so, how do I tell NetBSD to do
these things? Is there a umass quirks table somewhere?
Staffan
