<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Now that we finally have a working MXE build that includes the FTDI</p><p class=MsoNormal>user space code, I’m sad to report that this doesn’t quite work, yet.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Here are the relevant messages in the error log:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>INFO: in ftdi_open<o:p></o:p></p><p class=MsoNormal>INFO: serial_ftdi_open called<o:p></o:p></p><p class=MsoNormal>INFO: setting up ftdi_ctx<o:p></o:p></p><p class=MsoNormal>INFO: initialize ftdi_ctx<o:p></o:p></p><p class=MsoNormal>INFO: call serial_ftdi_open_device<o:p></o:p></p><p class=MsoNormal>INFO: serial_ftdi_open_device called<o:p></o:p></p><p class=MsoNormal>INFO: FTDI tried VID 0403 pid 6001 ret -4<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>ERROR: usb_open() failed<o:p></o:p></p><p class=MsoNormal>INFO: serial_ftdi_open() failed<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>And according to the libftdi1 sources, -4 is the very insightful<o:p></o:p></p><p class=MsoNormal>“unable to open device” error… and poking at the source this simply<o:p></o:p></p><p class=MsoNormal>means that libusb_open on the device as found by VID/PID returned<o:p></o:p></p><p class=MsoNormal>a negative number.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So the question is… why? And how do I figure that out with my utter<o:p></o:p></p><p class=MsoNormal>lack of Windows knowledge…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>/D<o:p></o:p></p></div></body></html>