STM32F3DISCOVERY USB CDC (Virtual COM port) Example

[harshad]

Posted on April 30, 2013 at 14:30

Hi,

I was looking for USB CDC (Virtual COM) Example code for STM32F3DISCOVERY Kit.I can't see it in Example code downloaded from ST.Regards, #usb-(cdc) #stm32f3-discovery-usb-cdc-web #amazing-google-skills

[Tesla DeLorean]

Posted on April 30, 2013 at 15:31

Probably targets the EVAL board, but should be easy enough to port.

STM32_USB-FS-Device_Lib_V4.0.0\Projects\Virtual_COM_Port

[harshad]

Posted on April 30, 2013 at 16:10

Will you please give me link for this example.

[Tesla DeLorean]

Posted on April 30, 2013 at 17:14

http://www.st.com/web/catalog/tools/FM147/CL1794/SC961/SS1743/PF257917

[oyakovlev]

Posted on January 20, 2014 at 19:28

Hi All

Unfortunately this URL invalid now. I've tried download examples from https://my.st.com/st-extranet-web-active/active/en/catalog/tools/PF258224 but unsuccessfully also. Could you please help me with those examples? Thanks in advance

[Tesla DeLorean]

Posted on January 20, 2014 at 21:42

http://www.st.com/web/en/catalog/tools/PF258157

[oyakovlev]

Posted on January 21, 2014 at 00:40

I've got it! Thanks a lot!

I'm sorry for stupid questions but I'm newbie in STM32 programming. But may be do you know why the target clock has been set up on 8 MHz in all demo? Could I change it to standard 72 MHz? Thanks in advance

[Tesla DeLorean]

Posted on January 21, 2014 at 01:00

Depends on what you mean, the 8 MHz in the Keil target dialog means very little. The HSI (high speed internal) in the F3 is 8 MHz, the crystals used in the Discovery series boards is usually 8 MHz, and many of the Eval boards have a 25 MHz crystal.

The PLL setting, which you should find in system_stm32f3xx.c should get you to 72 MHz for the processor, and a 1.5 divider should get 48 MHz for the USB peripheral.

[oyakovlev]

Posted on January 21, 2014 at 14:23

Thanks a lot! This is excellent forum!

[oyakovlev]

Posted on January 22, 2014 at 10:31

Hi Clive,

I've ported the VCP to F3DISCOVERY board but the one problem has been raised - application has broken SWD. As fact reprogramming (from Keil) and debug is impossible. I'm getting error ''Cannot access target. Shutdown debug session'' when I'm trying start the application in debug mode. And I'm getting ''Internal communication error'' for any other attempts. After it any other deals with board via ST-LINK are impossible due to following error: Target DLL has been cancelled. Debugger aborted ! But the application is working properly and board can be reprogrammed via ST-LINK utility.

On the other hand

ST-STUDIO doesn't wok also. How I can fix it? I have suspicion that application is using the wrong USB but I don't know how it can be checked. Thanks in advance