Just wondering what the return codes signify in the dispatcherEventReceive function. Currently, I can load a graph file generated using the mvNCCompile tool, but calling the allocate_with_fifos function causes the script to hang after returning the message:
dispatcherEventReceive() Read failed -4
Using 2.05.00.02 of the NCSDK, in a Virtual Box environment running Ubuntu 18.04. The hello_ncs.py sample works fine, as do other examples
In this case, the return codes passed back are generated from a call to the libusb_bulk_transfer function. The error codes can be found here:
An error of -4 suggests "no such device (it may have been disconnected)"
@Jay We are aware of this issue and are looking into them. So far it looks like there are multiple networks that cause the error mentioned above. I'll keep you updated as soon as we have a solution.
Thanks @Tome_at_Intel .. for what its worth, the issue went away when I added back in some dropout layers I'd removed earlier, and recompiled the graph. I thought they wouldn't have an effect, but perhaps they are related to this issue..
I hit this issue again today with a different network. This time it made no difference whether or not the Dropout layers were present - the graph file is generated successfully from the mvNCCompile tool, but the device seems to disconnect when setting up the fifo queues. I left a copy of everything here: https://1drv.ms/f/s!AosBHN3IHTLWhrAUKvYf1fSnzFxBzA
If you have any thoughts or suggestions, do let me know!