tag:blogger.com,1999:blog-8909459762367220480.post8426176242255716155..comments2024-02-14T03:40:47.584-08:00Comments on Stuff and Nonsense: FTDI's Vinculo Development Board: A Reviewhotchk155http://www.blogger.com/profile/13452320361660792114noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-8909459762367220480.post-4570628605206209272012-07-20T06:08:35.364-07:002012-07-20T06:08:35.364-07:00Hi Phil
I have some difficulties to find where to...Hi Phil<br /><br />I have some difficulties to find where to add your code in the HelloWorld example.<br /><br />Could you please publish the sources ?<br /><br />Thanks in advance<br /><br />JulienAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-24099964435415748222012-07-03T00:41:45.149-07:002012-07-03T00:41:45.149-07:00I was wondering if someone know a forum where peop...I was wondering if someone know a forum where people share their thought regarding Vinculo 2 ?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-80596189491080048442012-07-03T00:35:02.151-07:002012-07-03T00:35:02.151-07:00I am 100% agree with you. They technical support s...I am 100% agree with you. They technical support sucks big time. I sent multiple emails regarding the update of the program loader and no replay. Than is just ridiculous. I work for one of the largest chipset makers and FTDI really sucks. HW without the appropriate SW support is just useless.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-57925792299481148312012-02-26T09:41:55.414-08:002012-02-26T09:41:55.414-08:00Hey Phil, just realised I never thanked you for th...Hey Phil, just realised I never thanked you for the info above. I've just returned to working with the VNC2 as a USB host and this information was invaluable. Cheers, Jasonhotchk155https://www.blogger.com/profile/13452320361660792114noreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-62727511357299853862011-08-27T07:17:36.553-07:002011-08-27T07:17:36.553-07:00Finally got this to work. It seems the "know...Finally got this to work. It seems the "known-good" ROM file I got from FTDI was broken!<br /><br />Here is what you need to do to get this to work:<br /><br />1. Power jumper set to PSU, not VBUS. If you trace through the schematic you'll see why this is.<br />2. You need to set up GPIO to bring pin 40 & 41 low. Pin 41 must be low to power the USB host port. Pin 40 controls the LED next to the port.<br />3. Power the board with a wall wart or just get a 9V battery and plug it into Vin and GND on the Vinco board.<br /><br />Here is some code I got from FTDI. Using this code I was able to modify the regular (not Vinco) HelloWorld example from 1.4.2.<br /><br /><br />////////////////////////////////////////////////////////////////////////<br />// Vinculo....Reassign pins for USB port LED and Power Control (port E used)<br />// Pin 40 is connected to LED and Pin 41 is Power Enable on Vinculo<br /><br />//vos_iomux_define_input(40,IOMUX_IN_UART_RXD); // Vinculo - commented out UART Rx<br /> vos_iomux_define_output(40,IOMUX_OUT_GPIO_PORT_E_5); // Vinculo - USB port 2 LED<br /><br />//vos_iomux_define_output(41,IOMUX_OUT_UART_RTS_N); // Vinculo - commented out UART RTS#<br /> vos_iomux_define_output(41,IOMUX_OUT_GPIO_PORT_E_6); // Vinculo - Power control<br /><br />// Note that LED0..LED3 which are used in the code below are not present<br />// on the Vinculo board<br />////////////////////////////////////////////////////////////////////////<br /><br /><br /><br />////////////////////////////////////////////////////////////////////////<br />// Vinculo....Initialise Port E to control power transistor and LED<br /> gpioCtx.port_identifier = GPIO_PORT_E; // Vinculo<br /> gpio_init(VOS_DEV_GPIO_E,&gpioCtx); // Vinculo<br />////////////////////////////////////////////////////////////////////////<br /><br />////////////////////////////////////////////////////////////////////////<br /> // Vinculo....Set port E bits<br /> // LED is on E5 and Power Enable is on E6 so 8 port bits are as follows<br /> // Bit 7 Not used<br /> // Bit 6 Power Enable (active low)<br /> // Bit 5 LED (active low)<br /> // Bit 4 Not used<br /> // Bit 3 Not used<br /> // Bit 2 Not used<br /> // Bit 1 Not used<br /> // Bit 0 Not used<br /><br /> hGpioE = vos_dev_open(VOS_DEV_GPIO_E); // Vinculo - Handle = port E<br /><br /> gpio_iocb.ioctl_code = VOS_IOCTL_GPIO_SET_MASK; // Vinculo<br /> gpio_iocb.value = 0x60; // Vinculo - 01100000 set bits 6 and 5 as output<br /> vos_dev_ioctl(hGpioE, &gpio_iocb); // Vinculo<br /><br /> leds = 0x00; // Vinculo<br /> vos_dev_write(hGpioE,&leds,1,NULL); // Vinculo - Write data of 00000000 to port<br /> ////////////////////////////////////////////////////////////////////////<br /><br /><br />I hope this helps!<br /><br />PhilDr. Phil Polstrahttps://www.blogger.com/profile/05371953714583667430noreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-90152149956267326132011-08-26T20:02:39.086-07:002011-08-26T20:02:39.086-07:00After some back and forth with FTDI I seemed to ha...After some back and forth with FTDI I seemed to have a bad board. I had them send me a known-good ROM file for the HelloWorld app that writes to a flash drive and that too didn't work. I ordered a new Vinco board which arrived today. It does the exact same thing as the other one. I have to wonder if anyone outside of FTDI has gotten one of these to enumerate a USB device.<br /><br />I was provided some code to enable a GPIO port and send toggle a couple bits in order to light the LED and power the host port, but that still doesn't fix the problem.<br /><br />I'm about to give up on this whole platform. If I have an app that needs a USB B port, I'm going to use one of the development boards and solder the port on there myself.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-83335631838918244912011-08-19T16:05:00.002-07:002011-08-19T16:05:00.002-07:00Although I recommended to request FTDI to
supply ...Although I recommended to request FTDI to <br />supply "HC_defs.h"in the previous comment,<br />it seems it is not necessary. <br />As I wrote, my system installed a month ago <br />does include "HC_defs.h" but the recent <br />installer does NOT include it. <br />I inquired FTDI the reason and they answered<br />as follows.<br />1. The installer in the early time for several<br />days accidentally included "HC_defs.h" <br />and later it was removed since it is not<br />needed to compile the sample program.<br />2. Removing the control line <br />#include "HC_defs.h"<br />in the file "vinco_USBH.h" is a solution to<br />prevent errors.<br />I followed the above and confirmed no error <br />happens and generates a workable ROM file.<br />Please try.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-34370921070095293742011-08-18T22:51:33.884-07:002011-08-18T22:51:33.884-07:00It is true that "HC_defs.h" is not inclu...It is true that "HC_defs.h" is not included <br />by the IDE installed by the latest copy from<br />FTDI. I experienced it today with a new PC.<br />I wonder why but my IDE installed a month <br />ago includes "HC_defs.h" and no such an error<br />happens as the person posted a report on<br />August 5th.<br />Please note the version numbers for my latest<br />system and a month old system are both 1.4.2. <br />And it seems the main body =the execution<br />files ="VinIDE.exe" for the systems are<br />completely same.<br />Maybe FTDI changed something about the<br />configuration of the installation set and <br />missed to include "HC_defs.h". <br />Since it seems even my latest system works<br />normally by copying "HC_defs.h" from a month<br />old system, I strongly recommend the person<br />posted a report on August 5th to request FTDI<br />would provide "HC_defs.h".Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-24808849181599844792011-08-10T21:01:30.170-07:002011-08-10T21:01:30.170-07:00I have been beating my head against the wall for a...I have been beating my head against the wall for a couple months working on a Vinco project that needs to use both the host and slave ports. I have finally come to realize the board is crap. I had to resolder the mini-B connector to get that to work and the host port doesn't seem to work at all. I have tried examples and moving over code that worked great on the development boards to no avail.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-22494441128425540582011-08-05T17:58:47.973-07:002011-08-05T17:58:47.973-07:00Unfortunately, I'm running into the same issue...Unfortunately, I'm running into the same issues. I bought five Vinco (Vinculo) development boards to prototype up a few examples of a product that's under development. I carefully walked through the "Getting Started" steps, but the application generated by their app wizard wouldn't compile, nor would the example program. <br /><br />I bought the board to be used in "USB Host Mode" but apparently there's a missing HC_defs.h file being referenced from their core libs, so none of the host mode apps will build.<br /><br />This is very sloppy and smacks of bad QA, I'm already regretting buying five development modules and two debugger modules. I should have just stuck with the AVR, but I was looking for a cheap and fast way to get a USB host working.<br /><br />Live and learn, I guess.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8909459762367220480.post-70835048620790677502011-07-12T10:56:43.019-07:002011-07-12T10:56:43.019-07:00Thanks for the write up. My experiences with FTDI ...Thanks for the write up. My experiences with FTDI have been much the same. They're very sloppy with the details, and frankly, they don't seem to care that much. <br /><br />It seems many silicon companies put just enough time into their software toolchains to be able to carefully demo them at trade shows, conferences, and sales calls. Those running the demos follow a specific script that won't make the IDE crash, etc. Once they get that far, they largely stop however many other bugs remain unless some large potential customer screams loudly and threatens to buy someone else's product. It's sad.<br /><br />Companies like FTDI don't seem to care that, for lower volume products, it's just not worth it for any of us to spend an extra 20 - 200 hours fighting development tools, working around bugs, waiting for responses from their support people, etc. <br /><br />It's cheaper, quicker, and vastly easier, to just use parts, boards, and toolchains that work as promised. In this case, I think most just spend another few dollars and glue an FTDI or Silabs USB-to-whatever chip onto an MCU with a proper stable toolchain rather than fight the Vinculum's uncharted, buggy and poorly documented waters.Anonymousnoreply@blogger.com