stm32f4discovery usb-cdc problem

ChibiOS public support forum for topics related to the STMicroelectronics STM32 family of micro-controllers.

Moderator: RoccoMarco

Post Reply
deadlyboy
Posts: 27
Joined: Wed Nov 26, 2014 9:27 am

stm32f4discovery usb-cdc problem

Post by deadlyboy »

hi every body ,
i want to send and receive data over usb cdc, the example for stm32f4 implemented in olimex board, and in usb-otg2 and in discovery board the usb board is connected to otg1(USBD1)

the only different i saw in other opensource project was in

Code: Select all

static const SerialUSBConfig serusbcfg = {
  &USBD1,
  USBD2_DATA_REQUEST_EP,
  USBD2_DATA_AVAILABLE_EP,
  USBD2_INTERRUPT_REQUEST_EP
};


i chnged USBD2 to USBD1 , but it's not recognized by my system(win7).
i already installed stm32 usb cdc drivers .

is there any other configuration to make this work for stm32f4discovery(usb-otg1)??

----
thanks in advance
MA
User avatar
Giovanni
Site Admin
Posts: 14892
Joined: Wed May 27, 2009 8:48 am
Has thanked: 1202 times
Been thanked: 996 times

Re: stm32f4discovery usb-cdc problem

Post by Giovanni »

Hi,

In the main() function there is the USB initialization, you have to change that too.

Giovanni
deadlyboy
Posts: 27
Joined: Wed Nov 26, 2014 9:27 am

Re: stm32f4discovery usb-cdc problem

Post by deadlyboy »

i don't know what is going wrong.
windows can't recognize my com port.

in STM32 demos :i suppose ARMCM4-STM32F407-DISCOVERY-MEMS using otg1 (PA9,PA10,PA11,PA12).
i build this demo and program micro with that,

and windows exactly can recognize com port, but when i open the Serialport terminal(like tera term) it shows nothing ??
what is it's Baud rate??

is there any possibility that my virtual com port driver has problem or ...
any idea would be great .

-----
thanks in advance
MA
User avatar
Giovanni
Site Admin
Posts: 14892
Joined: Wed May 27, 2009 8:48 am
Has thanked: 1202 times
Been thanked: 996 times

Re: stm32f4discovery usb-cdc problem

Post by Giovanni »

Hi,

The baud rate is not important, that demo should just work.

Check silly things like selecting the right com port in the terminal, cables, hubs etc.

Giovanni
Post Reply