BB
BB copied to clipboard
fhorinek
[D.272.0.0] unable to eject drive from windows by software
on windows: no eject drive no eject usb
only physical unplug of the usb is possible and works
in fact, it was an usb drive, with the new firmwares, it became a device. working as a drive was less fashion but that was working very well.
You can just change the driver in windows. Your description is affected by the driver windows defaults to, which is depending on the file system of the attached device. Change the driver to whatever you prefer - bonus: you get the safe removal option back, too!
in fact, it was an usb drive, with the new firmwares, it became a device. working as a drive was less fashion but that was working very well.
The fashion was not the reason for the changed behavior. We were using FatFs as our storage file system (Fat32). Problem is that FAT is very easy to corrupt and the corruption is not detectable easily on the MCU. Most common causes were crashes and unejected usb transfers. Random errors are then lingering on the storage and are causing random errors.
We have decided to use more modern FS for the storage called Reliance Edge (RED for short). It guarantees that the data on the storage are always valid.
Problem is that with (old) massstorage usb driver you are accessing whole storage as memory pool and it is up to operating system to read/write and govern the filesystem structure. Unfortunately no operating system understand the RED FS.
So the solution is to use the MTP usb driver that present the data on the device as object instead of whole memory. (Same as android devices that are using ext fs).
Problem is that this kind of change is affecting whole device and we need time to stabilize it to the same level as before.
ok understood. that say ext2fs can be used to put back a valid firmware ? :-p