Dear all,
I am using QCA4020 to do Zigbee development on Windows.
I try to follow the JTAG debug mode (3.7.2) on QCA402x (CDB2x) Development Kit User Guide.
In 3.7.2.2 debugging through GDB, I tried to run the openocd -f qca402x_openocd.cfg. It shows the result as
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'
I have changed the cfg file a little to fix the previous problems until I got this one.
What can I do to fix this problem? And what is libsub() actually?
Best Regards
Xian Wang
libusb_open() failed error occurs when the remote machine is not able to detect the USB device.
Make sure the USB is plugged in, jumper settings are accurate and reset the board to run "openocd -f qca40x_openocd.cfg"
Thank you for the reply,
I think I just plug in the USB and setting the jumper on J31 (1 and 2) as the user guide said.
Since there are 2 plug ins in QCA4020, I tried both of them with J31 jumper, only the below one can be recognized by the device manager.
And I can see the interface from Zadig as shown in user guide (Dual RS232 HS (interface 0)), the only difference with the user guide is the driver in my computer shows FTDIBUS (v13.11.35.0) not the FTDIBUS (v2.12.28.0), does it matter for the problem?
How to see the the device is being detected by the USB? not from Zadig?
Best Regards
Xian Wang
Yes only UART comm ports should be recognized by device manager.
Can you confirm after aplying the Zadiag, you are seeing single comm port ?
Also, try to change the USB port and make sure RS232 driver is installed and you are able to see (Dual RS232 HS (interface 0)) and apply Zadiag on the comm port.
Thank you for the reply, I have tried to switch USB port, Dual RS232-HS (interface 0) and Dual RS232-HS(interface 1) can both see.
One more thing is, when I apply Zadig, the screen shows the same as the user guide shows (only FTDIBUS different version in the left), do I need to press replace driver or someting?
Best Regards
Xian Wang
Kindly try replacing the driver, after successfull installation, you should see single COMM port under device manager.
Hi,
I also experienced this.
Then I tried to launch command_prompt as Administrator, it's working.
Regards,
Naufal
Thank you for your help.
I tried your method, no difference.
GNU MCU Eclipse OpenOCD, 64-bitOpen On-Chip Debugger 0.10.0+dev-00593-g23ad80df4 (2019-04-22-20:25)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 5000 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description '*', serial '*' at bus location '*'
What did you see in Zadig?
Best Regards
Xian Wang
Thank you for the reply.
you mean replacing the driver is to replace the FTDIBUS driver into different version, or change FTDIBUS driver to some others in Zadig?
Best Regards
Xian Wang