That is an advantage I don't see many other devices having. Depending on how high a performance you need there's a number of 8-bit USB devices like the ATmega8U2 you could join with an AVR32 over SPI to give 2 USB ports. Or even using the FTDI chip with one of the precompiled firmwares. I've had the V2DAP running without issue, but obviously there's a fair performance hit compared to having two USB ports in the one device.
For non-mass production projects the extra couple of dollars to go to a fully fledged 32-bit processor with USB from one of the big names (like Microchip or Atmel etc.) is well worth it. I just got a 32bit AVR and loving it, guess I'll try and ebay off the FTDI devices or do a youtube clip of there distruction.
I bought a bunch of these chips to use in a prototype / Alpha test. To say this device/toolchain is "immature" is being far too kind. Some of the bugs are so glaringly obvious, for example on the devices I’ve got (32 pin variant) it requires pin 11 to be referred to as 199 for it to setup the IO correctly. And mind you this isn't actually stated anywhere; I just stumbled across it looking at the output from the IOMUX wizard (which seems to do some weird things in itself.)
After two nights spent playing with a device I built a dev board for, I'm tempted to cut my losses here and go for a different manufacturer.
Perhaps I should also note that I compiled their "hello world" example, downloaded it, plugged in a LEXAR 4GB usb flash disk that I had just been talking to over the pre-compiled V2DAP firmware, and it destroyed it. I honestly don't even know what it did, but windows or mac can no longer mount it as a USB device. Seriously this is their example code!
