2011-01-18 01:30 AM
ST-Link and STM CDC/VCP drivers interference?
2011-05-17 05:21 AM
I believe the VID/PID of ST-LINK doesn't overlap to those of the ST CDC example (STM32_USB-FS-Device_Lib_um0424 V3.2.1), though I don't have ST-LINK, yet.
ST CDC example VID/PID = 0x0483 / 0x5740 ST-LINK VID/PID = 0x0483 / 0x3744 (found on web) Is your board enumerated without ST-LINK connection, after ST-LINK burns its firmware? If it runs without ST-LINK, the problem lies in the setting of ST-LINK. For ULINK2 and KEIL uVision, I've met similar problem (don't enumerate on debug) without these settings. - On the board, connect JTAG reset pin to MCU reset - Enable ''Use Reset at Startup'' option - Disable ''Run to main()'' option ST-LINK and EWARM pair should have similar setting, too. Tsuneo2011-05-17 05:21 AM
I believe the VID/PID of ST-LINK doesn't overlap to those of the ST CDC example (STM32_USB-FS-Device_Lib_um0424 V3.2.1), though I don't have ST-LINK, yet.
ST CDC example VID/PID = 0x0483 / 0x5740
ST-LINK VID/PID = 0x0483 / 0x3744 (found on web)
Yes, such interference would be strange.Is your board enumerated without ST-LINK connection, after ST-LINK burns its firmware? Yes, but I had once to reboot PC as my board connection seemed to be blocked further after previous ST-Link connection.If it runs without ST-LINK, the problem lies in the setting of ST-LINK. Thank you for advise.- On the board, connect JTAG reset pin to MCU reset
- Enable ''Use Reset at Startup'' option
- Disable ''Run to main()'' option
O.K., I can try this settings. However, I have DFU bootloader from 0x08000000 and the application from 0x08003000. Of course, the bootloader normally skips to 0x08003000 but perhaps it will not work with your settings? Ivan
2011-05-17 05:21 AM
- On the board, connect JTAG reset pin to MCU reset
Yes.- Enable ''Use Reset at Startup'' option
There is no options for ST-Link in EWARM 6.1 except JTAG/SWD switching.
- Disable ''Run to main()'' option
Yes.
Ivan