How to connect via USB?

Hallo,
i want to connect via stm32f4-discovery by usb.  

First test:
USB OTG, device only and virtual com port.
error: physicaloid.open() failed.
I use for this an OTG Adapter + min usb cable.

So...before i start to try diffrent stuff, like:
build a new USB Cable (without OTG function) or  connect usb wires via Tx Rx  Usart pins, and also test some diffrent usb implementations on stm32....
please tell me how roboremo app handle the data trough smartphone's usb port.

Then i can adapt stm32 code;), i hope

ludaaakris

(@RoboRemo....could you maybe implement a function/button to switch quick between interfaces [menu->interface->select->0..7] )

Hi,
The stm32 must be set as usb device (not host), and CDC-ACM (virtual com port) is OK.
Try to connect the stm32 to a PC first and see if it works with a terminal (like CuteCom in Linux) (at the device you write /dev/ttyACM0 or /dev/ttyUSB0).
Also check the VID number of the USB device (you can use the comand lsusb in Linux, VID is the first 4-digit hex number after "ID").
To connect with RoboRemo, you may have to change the VID to one of the following:
ARDUINO (0x2341)
FTDI (0x0403)
MBED_LPC1768 (0x0d28)
MBED_LPC11U24 (0x0d28)
MBED_FRDM_KL25Z_OPENSDA_PORT (0x1357)
MBED_FRDM_KL25Z_KL25Z_PORT (0x15a2)
CP210X (0x10C4)

(App tries to connect only to these VIDs)
Please post here the original VID from stm32f4-discovery CDC example, so I will add it in the next version of the app.

Then when you first try to connect over USB in RoboRemo, a dialog appears and asks for permission. I still did not fin a solution to intercept when user presses OK on that dialog, so I made the app wait (about 1.5 sec) before trying to connect, so if you wait more then 1.5 sec before pressing OK, it will show
error: physicaloid.open() failed
and then you need to try again (now it should work, because the dialog appears only the first time).

Hope this helps,
Victor

Hey Victor,
more than a half year ago...

It was very easy to get it work.
VID of the STM32f4 is hex: 0x483
I use the MBED_LPC1768 (0x0d28) VID!

Thanks!!!

No problem!