Loading...
 
Skip to main content

System Workbench for STM32


After update openocd is incomplete

Hi Laurent,

I'm currently setting up my SW4STM32 environnement with one of those bluepills board, I encounter somme erratic behaviours.
I use a STLINK V2 USB adapter (a clone one), it works fine since STLink utility run fines and that I'm able to (after 2 trials) to upload a code into the uC with SW4STM324's debug command, even with some errors messages.

Do you say in yout post that the reset output of the STLINKV2 should alaways be connected to the reset pin of the uC ? or do you say that physical reset has to be applied only if SWD lines are not free for STLINK OR uc operate in Low Power ?

This may be an answer to the issues I met. Currently the connection with the board use the 4 wires of the connector (Vdd, Gnd and 2 wires SWD), my test app is the code generated by CubeMX compeleted by 2 line handling PC13 led blink and the SWD lines are properly dedicated for this in CubeMX. After two trials, code is uploaded and a manuel reser make the board start excuting the code : blinking led. On first trial I've mainly an 'unable to write flash error', on second the process doesn't generate error but doesnt restart the Uc, so manual reset is required.

I think that I may have a reset issue because OpenOCD's highlight errors linked to 'CPU not halted' status or 'unable to reset'. It looks like STLINKV2 with the 2 wire SWD within SW4STM32 environnement can't reset the cpu. Please not that STLINK utility give succefully full control on the cpu : halt, reset, connect, disonnect, uploaed, read,...etc.

Thanks
Chris