cancel
Showing results for 
Search instead for 
Did you mean: 

Debugging NUCLEO-H533RE using STM32CubeIDE

BrucePB
Associate II

I am new to STM32CubeIDE  2.0.0 environment and I cannot debug my first project. See failure message in attachment.  What do I need to do to debug in this environment?  Is there instructions hidden somewhere that I need to follow?

 

1 ACCEPTED SOLUTION

Accepted Solutions
Andrew Neil
Super User

How to solve connection errors when connecting and programming the STM32 target board.

How to solve debugger connection issues

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

View solution in original post

5 REPLIES 5
MGogr.1
Senior

There may be problem with your hardware connection or debugger or usb cable. 

Please try again after checking everything.

Andrew Neil
Super User

How to solve connection errors when connecting and programming the STM32 target board.

How to solve debugger connection issues

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Thanks Andrew,

I can use this is information to do more testing. My cable may be too long (6') but it is heavy duty.  The NUCLEO is right out of the box and not connected to any other hardware..

Is it possible that I have to program my code into the NUCLEO before the IDE can debug it?  I thought the IDE programmed it before starting the debugger.

Bruce

Hi Andrew,

Using the programmer gave me more information why it failed.  I am designing for a H573 but the NUCLEO has a H533. The memory is much smaller and my program exceeded the H533 memory.

My design is no longer blocked. Thanks,

Bruce


@BrucePB wrote:

My cable may be too long (6')  ...


Six feet ?!!

Yes, that's waaaaaaaaaaaaaaaaaaaaaaaaaaaaaaay too long!

 


@BrucePB wrote:

 

...  but it is heavy duty.


What do you mean by that?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.