2018-01-29 03:02 AM
Hello!
Is it possible to send a UART break (0.3 seconds) over the Virtual COM Port.
It seems that UART break is connected with NRST.-Thomas
Solved! Go to Solution.
2018-01-29 08:08 AM
So, if you want the BREAK to reach the target STM32, you'll have to use a separate connection direct to the target's UART pins (and break the links to the ST-Link UART if you want to use those pins)
2018-01-29 03:28 AM
Is it possible to send a UART break (0.3 seconds) over the Virtual COM Port
In which direction?
2018-01-29 04:45 AM
PC --> STM32 (The STM32 resets.)
On the PC I generate the break with RealTerm or with pyserial. Both has the same effect.2018-01-29 06:12 AM
Now I'm confused.
So you're saying that you are sending a break, and that it causes your STM32 to reset?
But you don't want the STM32 to reset?
So why not use the debugger to see what happens when you send that break ... ?
2018-01-29 06:27 AM
Are you running a custom application on the STM32 or you are in the DFU mode (bootloader)?
2018-01-29 06:56 AM
I have tried it on the STM32F3DISCOVERY and NUCLEO-F302R8 boards. Both have the same behavior.
If I press ''Set Break'' in RealTerm'' then PIN T_NRST (PB0) of the ST-LINK MCU (U2) assert low and
the MCU (STM32F30X) resets.2018-01-29 07:05 AM
Ok. It means that the st-link captures the ctr-c and resets the target MCU.
STM32F3DISCOVERY does not emulates the VCOM because of st-link v2 so the VCOM should not be seen in the Device Manager, I guess
NUCLEO-F302R8has the VCOM (st-link v2-1).
It does not explain the behavior.
2018-01-29 07:14 AM
Note that a break is not the same as a Ctrl+C ...
2018-01-29 07:15 AM
Well, that's a whole load of information & context that was missing from the OP!
2018-01-29 07:54 AM
Right. Thanks.