amz2740 wrote: ↑
Sun Aug 22, 2021 3:08 pm
calnorth wrote: ↑
Sun Aug 22, 2021 12:44 pm
Attempted a test with a SANDISK ImageMate All-in-One USB 2.0 Reader/Writer (SDDR-189). Using a 32GB Sandisk Ultra Micro SDHC card.
Result was complete fail....dead. The headunit was unable to power the reader/writer. However, this is a reader/writer and not reader only.
As regards the readers I see on eBay. I have no idea whats in them..anything from 4 wires to a small interface ...don't know.
The rig I used..reader/writer/sd card/USB cable (1mtr) works perfectly on Windows/Linux. So I have to say this appears to be a headunit power weakness and meaning its under specified for standard USB operation. Causing USB stick recognition failures?
The iPhone test uses a device powering itself..not so the writer/reader.
Anybody that has a reader only that works...let us know please.
Thanks for trying this, sorry it didn't work though. Going to buy a cheap SanDisk cruzer 8gb and see how I get on with that. Failing that I will try a small all in one usb such as this:
Will let you know how I get on.
As a follow up I have been testing some of my USB sticks 4GB, 8GB and 32GB
The 4 & 8GB sticks are Sandisk Cruzer Blade USB 2.0 (Highspeed) as illustrated above by @gloucester
The 32GB sticks are Kingston DataTraveler USB 3.0 (Superspeed)
Both Sandisks are quickly recognised by the Nissan headunit. The Kingstons are not.
Sandisk current draw is 100ma (correct per USB specs)
Kingston current draw is 500ma (correct per USB specs)
Both makes work flawlessly on Win10 and Linux Mint 20.2 (Ubuntu)
The Sandisks work on the Nissan headunit. The Kingston types do not.
Apart from the power (current draw), I note on examination of two registers (VID & PID) stored on the Kingston sticks, errors are flagged.
*** ERROR: Invalid wMaxPacketSize. Max 64 bytes allowed in full speed mode.
Microsoft OS Descriptor is not available. Error code: 0x0000001F
Whether those errors stop the Nissan headunit recognising the sticks I don't know. Certainly WIN10 and Linux manage them ok..or perhaps discard them and proceed normally.
VID & PID registers are examined by the embedded USB hosts (Win10, Linux, Nissan) when the USB stick is plugged in. This enables the correct driver to be selected and handle the type of USB device present. In this case USB sticks.
Errors in power budget, VID & PID will cause a Not Recognised Message (Reject) message after some timeout period. Perhaps no message at all...dead.
I have other sticks at 64GB and 128GB to test. Sandisks, so will likely add to this post later.