cancel
Showing results for 
Search instead for 
Did you mean: 

Riverdi_101 STM32H7: ST-Link can't connect to board

richi
Associate III

For more than 3 days I am trying to solve a problem of connecting to Riverdi board using external ST-link from a discovery board. I flashed apps without problem and now I can't do anything. I remember last time I was flashing an app it asked that firmware of St-link has to be updated before continuing so I proceeded. I successfully flashed the app but now I am unable to flash it again. 
 

13:07:23 : STM32CubeProgrammer API v2.18.0 | Windows-64Bits
13:07:27 : UR connection mode is defined with the HWrst reset mode
13:07:27 : ST-LINK SN : 0670FF3332584B3043153854
13:07:27 : ST-LINK FW : V2J45M31
13:07:27 : Board : STM32F4DISCOVERY
13:07:27 : Voltage : 2.91V
13:07:27 : Error: Unable to get core ID
13:07:27 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

If I try to connect to other boards It is connected without problem.
Please help,

Regards

 

8 REPLIES 8
SofLit
ST Employee

Hello,

Which board? in the title you said: "STM32H7 cant connect to board"

but the log said: Board : STM32F4DISCOVERY

Could you please clarify? do you have a F4 discovery board connected via USB to your PC?

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
PS:
1 - This is NOT an online support (https://ols.st.com) but a collaborative space.
2 - Please be polite in your reply. Otherwise, it will be reported as inappropriate and you will be permanently blacklisted from my help/support.

That is the weird thing , this is the ST-link from F4 discovery board, I removed the jumpers to use only ST-link. I performed connect under Reset and performed full chip erase. However, flashing is still not possible. 


@richi wrote:

That is the weird thing , this is the ST-link from F4 discovery board,


Not clear. Are you using a STLINK module from F4 discovery to connect to that Riverdi board? If yes that was an important information you should provided in the first post.

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
PS:
1 - This is NOT an online support (https://ols.st.com) but a collaborative space.
2 - Please be polite in your reply. Otherwise, it will be reported as inappropriate and you will be permanently blacklisted from my help/support.

@richi wrote:

 this is the ST-link from F4 discovery board. 


That'll be why it shows up as "F4Discovery"

 


@richi wrote:

I removed the jumpers to use only ST-link.


Show your schematic of how you connected between the Discovery board and the Riverdi board.

Did you remember to connect GND and Reset?

 

Riverdi board only offers block diagram:
mcu.png

 

 

On the stm32f4 side I just removed jumpers and connected pins 2,3,4,5,6 , VCC is given from an external power supply on through a power connector. 

swd.png

 

I was reading on internet that MCU could be bricked if I accidentally re-configured SWD pins for some other alternate function, what is the procedure if that is the case?

None of that shows us the actual connections that you have made between your disco & riverdi boards.

 


@richi wrote:

I was reading on internet that MCU could be bricked if I accidentally re-configured SWD pins for some other alternate function


Not really "bricked" - but inaccessible to SWD.

 


@richi wrote:

what is the procedure if that is the case?


  1. Connect under hardware reset.
    That's why I asked if you'd included reset in your connections.
     
  2. Use the System Bootloader (requires manipulation of BOOTx pins)

Can you please tell me how can I flash a program from STMCubeProgrammer but with 2 hex files. One is for internal flash starting at 0x08000000 and one for external flash 0x090000000, earlier I would just click on flash in TouchGFX and everything would be done automatically. 

That's a separate question - you need to be able to connect to the board first!

Have you now got the connection working?