2018-09-02 02:57 PM
Usually with STM32 development boards I am able to see a virtual com port/serial port when I hook the board up to a computer via USB. This board, the F0308-DISCO, seems to have the TX/RX pair for UART communication between the target MCU and the ST-LINK MCU, but no such port is visible on the computer. I am using macOS and have updated the debug probe to it's newest firmware version using the STM32CubeProgrammer tool. Is there a special driver needed for this board (seems unlikely as the boards seem to have a common implementation of the ST-LINK probe), or some other reason why the VCP will not show up? I have come to rely on this functionality quite a bit in my development process, as the semihosting print capability is extremely slow. Thanks in advance.
Solved! Go to Solution.
2018-09-02 03:21 PM
The older DISCO boards had a smaller F103 part for the ST-LINK that doesn't support mbed MSC or VCP functionality. ie V2 vs V2-1
You can't update the firmware to get the functionality.
In the case of the CM0 you don't have the SWV/SWO connectivity either. Keil had a method for using the EVT (Event Recorder)
https://www.keil.com/pack/doc/compiler/RetargetIO/html/_retarget__examples_er.html
https://www.keil.com/pack/doc/compiler/EventRecorder/html/er_use.html
2018-09-02 03:21 PM
The older DISCO boards had a smaller F103 part for the ST-LINK that doesn't support mbed MSC or VCP functionality. ie V2 vs V2-1
You can't update the firmware to get the functionality.
In the case of the CM0 you don't have the SWV/SWO connectivity either. Keil had a method for using the EVT (Event Recorder)
https://www.keil.com/pack/doc/compiler/RetargetIO/html/_retarget__examples_er.html
https://www.keil.com/pack/doc/compiler/EventRecorder/html/er_use.html