facing issue in programming stm32h7a3zi-q

Thank you so much for your reply,

I am using the nucleo board, nucleo h7a3ziq, with on board ST-Link debugger. I have properly used all the jumpers as per the datasheet. 

Target is getting powered up, and when i tried to upgrade the st link its detecting the STlink V3 also. But while loading/ debugging its showing target not found. 

Initially it was working perfectly, when the IDE asked for GDB server update i have done that, after that only this started happening. 

please find the attached images for your reference

Thanking you again, and it will be really great if you can support

Thank you so much for your reply,

I am using the nucleo board, nucleo h7a3ziq, with on board ST-Link debugger. I have properly used all the jumpers as per the datasheet. 

Target is getting powered up, and when i tried to upgrade the st link its detecting the STlink V3 also. But while loading/ debugging its showing target not found. 

Initially it was working perfectly, when the IDE asked for GDB server update i have done that, after that only this started happening. 

please find the attached images for your reference

Thanking you again, and it will be really great if you can support

You've posted in the Keil forum:

but you're not using Keil!

That's from ST's CubeIDE:

You need to go to ST for support with their IDE!

https://community.st.com/s/topic/0TO0X000000y2j7WAA/stm32cubeide

Sorry for the inconvenience,

i tried with both keil v5 and stm ide while attaching i made mistake .

These are some picture for reference.

The second photo clearly shows you that uVision cannot see the ST-Link at all.

So:

• Is it actually connected?
• Is it properly installed?
• Are you sure that CubeIDE isn't using it?

Rakshitha said:

i tried with both keil v5 and stm ide

That, surely, tells you that the problem is with the ST-Link and/or the target - nothing to do with the IDE ?

Rakshitha said:

that's detecting the board's ST link debugger

What do you mean by that?

Sorry, I see - the Keil screenshot is, indeed, showing that it sees the ST-Link but not the Target.

But, again, if you get the same with CubeIDE then it can't be anything to do with the IDE - there must be a problem in your Target and/or in your connections from the Target to the ST-Link.

Are you sure that the Target hasn't disabled the debug pins, or had readout protection applied, etc ?

As these are ST-Specific things, you'd be better pursuing these on the ST forum:

https://community.st.com/s/topic/0TO0X000000BSqSWAW/stm32-mcus

(if you do cross, be sure to give links in all threads).

Sure thanks for the support