In order to use the USB port in the mini breakout board as an OTG port you need to connect to it a USB cable type A, and in order to use as "device mode" you need an USB cable type B.
1. Are you able to see something in your PC?
2. Which OS are you using?
3. Are you able to see something in the Device Manager(if you are on Windows)?
4. Did you install the needed drivers?
You can try by using different cables or another USB port on your PC.
in order to use as "device mode" you need an USB cable type B
Based on my description, would you say that I am using the correct cable? I also have some USB OTG adapters, am able to leverage USB NICs, storage, hubs, etc... when using those cables.
Are you able to see something in your PC?
I see the system initialization stuff on the FTDI console (this is the other cable)
Which OS are you using?
OSX and Linux
Did you install the needed drivers?
I'm expecting the device to appear as a USB mass storage device. I believe that every modern OS already has drivers for this built right in. Are you saying that there's a driver needed to accomplish the same thing that the Arduino board's SW1 appears to do? One that enables the storage feature, perhaps? Would you please elaborate?
During boot-up, the mini-breakout board presents 3 devices to the host PC:
Shortly after power-up, USB 0x8086/0xe005 appear. It vanishes at "*** Ready to receive application ***"
Then, at "GADGET DRIVER: usb_dnl_dfu", I find USB 0x8087/0x0a99. This vanishes at "Starting kernel..."
Finally, USB 0x0525/0xa4a2 appears. This one is probably related to a network-over-usb function, and unrelated to my problem.
BTW, it's really neat that Intel's USB vendor id is 8086. Ha!
Yes, you are using the correct cable, type B.
Have you tried to use another cable and another USB port in your PC? If you can, try with a 2.0 USB port
If you only want to flash the image and have it with a clean/factory image you can run the flashall.sh script.
If the problem is not solved by changing the cables and ports it could be related to a software issue and running the flashall script should fix it too.