Hi Masao
As we had discussed over the remote session support, the root cause of the error here is due to the coercion dot we noticed in D2XX Open VI after passing Open flags from List Devices VI. After replacing those VIs from example VIs it got resolved and we notice no errors through these VIs below
As a recommendation, I always suggest starting the work from prooved Example VI
Reference Example VI:
- Example_FT4222H_SPI_Master_Read.vi
- Example_FT4222H_SPI_Master_Write.vi
We noticed that there are no errors in example VI as in the screenshot below from our support session
There are application-level cleanups that might be required where proper handing of sessions (and closing wherever necessary).
Thanks
Ajay