STM32H723ZG Board losing communication

[PGM.2]

Hi all,

Nucleo-144 Stm32h723zg board while debugging suddenly loses communication and shows target not found, unable to read register values. This does not happen always but during debugging this issue is coming up,any solution or any problem with the board can someone help me out.

Thank You.

[mƎALLEm]

Hello,

It could be an issue with your USB port: connection issue or couldn't deliver enough current to the board.

It could be due to the USB cable, so try to change the cable.

[PGM.2]

Hi, I have tried using other USB port and USB cable but still I am facing the same issue.

[mƎALLEm]

Is there something plugged to the board, I mean another shield, daughter board, device? that get power from the USB? or it's only the Nucleo powered by the USB?

Do you have another Nucleo board to do the same test?

[PGM.2]

Yes I am using a wireless mouse but I have 2 boards actually one board works fine but the other one is facing this issue

[mƎALLEm]

"I am using a wireless mouse" --> is it connected to the Nucleo over USB-OTG?

[PGM.2]

No it is connected to the laptop using a different USB port

[mƎALLEm]

Did you try to debug a simple example from CubeH7, for example \Projects\NUCLEO-H723ZG\Examples\GPIO and without modification?

Do you have the same issue?

[PGM.2]

Yes but i did not face any issue while debugging the example code

[mƎALLEm]

There are two hypothesis:

1- I suspect an issue with your application, may be a power configuration issue

2- watchdog resetting your micro.

Could you please use CubeProgrammer and provide a screenshot of "User Configuration" in Option bytes menu (OB)?

[mƎALLEm]

If there is no issue with GPIO example: normally no watchdog is activated.

So there are two hypothesis:

• An issue with a power configuration in your application.
• An issue in your board (may be the power section).

[PGM.2]

The same application and program I can debug using an other board without facing any issue but while using this board I face the issue

[mƎALLEm]

ok but the "working" board could be working at the limit of the spec. Note that not all chips are same. So if you are not using the chip in the recommended configs, some chips "work" as you expect, others not. if you know what I mean ..

Note that "power issue" was just an hypothesis.. So it could be a board issue ..