You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finally, I saw 'suceed' terms from the serial port log.
But my purpose is to develop a programmable SSD, in other words, I'd like to do some additional functions on NVMe controller.
This project seems no storage backends, so I was wondering that how your firmware works like a SSD? Where the storage part? And what the size of it? I can not see any block devices in the OS.
Another question is that, is it support for Windows?I run your firmware and reboot the PC to Windows,however I got a blue screen if I modify vendor IDs to 144D (SAMSUNG) , which is caused by stornvme.sys driver.
Sincerely,
Brian
The text was updated successfully, but these errors were encountered:
Glad to hear that!
Our NVMe Controller is not integrated with the storage backend and the FTL firmware, so it cannot work as an SSD.
This controller is verified in the Linux OS and not in the Windows.
Hi,
Finally, I saw 'suceed' terms from the serial port log.
But my purpose is to develop a programmable SSD, in other words, I'd like to do some additional functions on NVMe controller.
This project seems no storage backends, so I was wondering that how your firmware works like a SSD? Where the storage part? And what the size of it? I can not see any block devices in the OS.
Another question is that, is it support for Windows?I run your firmware and reboot the PC to Windows,however I got a blue screen if I modify vendor IDs to
144D
(SAMSUNG) , which is caused by stornvme.sys driver.Sincerely,
Brian
The text was updated successfully, but these errors were encountered: