Error in initializing ST-LINK device. Reason: No device found on target. F103RB

[BadEngineer]

I am using a nucleo-F103RB. This device was functional in the past. 

I am getting an error 

 

Error in final launch sequence:

 

Failed to execute MI command:

target remote localhost:61239

 

Error message from debugger back end:

localhost:61239: Connection timed out.

Failed to execute MI command:

target remote localhost:61239

 

Error message from debugger back end:

localhost:61239: Connection timed out.

localhost:61239: Connection timed out.

 I have tried different cables to ensure it isn't the issue. I have also changed the port number. 

This is my debugger information: 

I am able to upgrade my stlink chip via cube ide as shown in the image below (it detects it)

I have tried to use the stm32cubeprogrammer application too but that doesn't seem to work. 

I get the below error. 

However i know it is working on COM7 because the last thing i did was create a program to output some information through the USART, which it is still doing (image below). 

 

I have also attached images of my board. 

 

 

 

 

[AScha.3]

Maybe you did something, to block the swd , not defined degub in Cube, use swd pins for something else...

to get access :

set debug to hardware reset;

try. If not connect in IDE :

or in cubeProgrammer : set st-link, hardware reset, connect under reset.

Then full erase , to get away the "problem" program.

[BadEngineer]

Is this what you mean?

 

I have changed the option to this and i still get the same error 

[AScha.3]

ok,

so check: boot0 lo ?

And try - as i wrote -

in CubeProgrammer : set st-link, hardware reset, connect under reset.

Then full erase , to get away the "problem" program.

show, what cubeprog telling:

 

 

 

 

If no connection with CubeProg or IDE possible, last chance:

set boot0 hi , reset or power cycle, and connect to bootloader .

+

If connection not working at all:

- some connection (wire) not there, check jumpers for swd/swc , connect st-link to cpu  really ?

- you damaged cpu, need a new board, or replace cpu.

[BadEngineer]

I have connected boot0 to high and and then tried to use stmcube to try and see if i can detect it. However i am getting the same issue (image below)

below is an image of boot0 being high. 

 

[AScha.3]

You cannot connect to bootloader this way !

+

still missing info:

>after i had connected pin 5 and pin 6 jumper.

Leave this jumper away ! It cannot work with connected pin 5 and pin 6 .

+ -> show, what cubeprog telling ...now.

[BadEngineer]

That is how you get into boot loader mode. You can see from the circuit diagram pin 7  on the CN7 connector, the boot pin and i am pulling it high to 3.3V. 

 

 

[zizic]

how did you solve this problem?

I have the same problem, and I've tried everything, but nothing works.

Please help me....