I'm trying to use imx_usb on a Mac. I observe the following output when I invoke "sudo ./imx_usb":
config file <.//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
vid=0x1fc9 pid=0x0134 file_name=mx8mm_usb_work.conf
vid=0x1fc9 pid=0x013e file_name=mx8mn_usb_work.conf
vid=0x3016 pid=0x1001 file_name=mx8m_usb_sdp_spl.conf
config file <.//mx6_usb_work.conf>
parse .//mx6_usb_work.conf
Trying to open device vid=0x15a2 pid=0x0061
claim interface failed
The last line (highlighted in bold) above is the subject of my question. Does anyone know how to correct this "claim interface failed" problem on a Mac with High Sierra (10.13.6)?
Thank you for the response, Weidong. I don't actually know how to determine which kernel extension got associated with the iMX usb client. So, I don't know if the problem I am encountering matches your description or not.
I worked around it by installing an ubuntu VM on my Mac, which works fine.
Thank you for your help.
-Brian
That's great!
Anyway it finally works fine!
Have a nice day!
Weidong
Hello Brian,
See below, please!
---------------------
Could you check if Mac OS can drive i.MX6 board to be a HID Compliance Device ?
if Mac OS can, the reason why caused the issue you encountered should be for comflicts between HID devices. For example, mouse and keyboard are both HID device, it there are 2 or more HID devices on one USB BUS, the conflict will most likely occurs.
Search the related messages from internet, some people also encontered the same situation as yours.
---------------------
Hope above infromation is helpful for you!
Have a nice day!
B.R,
Weidong