Code works in another board, but not in my custom board.

[anuradha]

Original title: Facing a debug issue. the code works in another board and gets firmware update. but its not working in my current stm32f103zet6 customized board.

Shortened in accordance with Posting Guidelines .

---

[anuradha]

and i checked in st link utility ,the firmware is upgrading but in stm32cubeprogrammer its not even connecting when i try to upgrade it its started upgrading at the end its saying the st link connection is lost ..whyy??

[Andrew Neil]

Welcome to the forum.

Please see How to write your question to maximize your chances to find a solution  for best results.

---

@anuradha wrote:

 the code works in another board

---

Please give details of this board.

---

@anuradha wrote:

but its not working in my current stm32f103zet6 customized board.

---

And also details of this board - schematics, etc.

---

@anuradha wrote:

i checked in st link utility ,

---

Note that the ST-Link utility is long obsolete - STM32CubeProgrammer is the current tool.

---

@anuradha wrote:

in stm32cubeprogrammer its not even connecting when i try to upgrade it its started upgrading at the end its saying the st link connection is lost

---

Is this with the original board, or the "custom" board?

What CubeProgrammer version?

What ST-Link are you using? Is it a genuine ST-Link?

See: How to recognize a genuine ST-LINK/V2 versus a cloned one.

Please show the full log from CubeProgrammer; also a screenshot.

[anuradha]

It worked after erasing full chip. But i have a question In my stm32cube programmer whenever i connect my target board its showing the only message like "Ur connection mode is defined with HWrst reset mode .Iam using 2.20.0 stm32cube programmmer version

I put mode: under reset

reset mode: hardware reset 

and if i click option bytes option also its still sending the same message....

[Andrew Neil]

---

@anuradha wrote:

 message like "Ur connection mode is defined with HWrst reset mode....

---

Please show the actual message.

And a screenshot showing your settings.

You still haven't given any details of the boards you're using.

 How to write your question to maximize your chances to find a solution 

[anuradha]

I am using stm32f103zet6 board.

Not only this every board i connected its showing same message.

[Andrew Neil]

---

@anuradha wrote:

I am using stm32f103zet6 board.

---

That's just a chip part number - it tells us nothing about the board.

You need to post the schematic and/or a link to the manufacturer's page for the board.

---

@anuradha wrote:

Not only this every board i connected its showing same message.

---

You said in your original post that one board did work?

This is not a valid ST-Link serial number:

So your ST-Link is either fake or faulty - or both.

Again, see: How to recognize a genuine ST-LINK/V2 versus a cloned one.

In particular, see:

https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/tac-p/703663/highlight/true#M965

[anuradha]

Yeah it's worked another board means both have same serial chip number,same schematic ...okay I understood ,the launching debug issue is solved what my question is about st link v2 detection fail in cube programmer. i used another st link v2 its detecting but my stlink v2 debugger works in st link utility and gives result .so in there its works means why it's not work here? is it still debugger issue

[Andrew Neil]

You still haven't answered the question: is your ST-Link genuine, or a clone?

Again, here is how to check:  How to recognize a genuine ST-LINK/V2 versus a cloned one.

In particular, see:

https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/tac-p/703663/highlight/true#M965

[Tesla DeLorean]

Show picture of board and ST-LINK.

Show picture of STM32103ZET6 IC that's problematic, large, clear and in-focus if you can manage that.

Details so far suggest you are working with fake/counterfeit parts.