Code is running well on STM32H755ZIQ board but not on a custom board

[kavyamm]

Post moved from this thread.

@ STTwo-32

I am using the same STM32H755ZIQ board and facing the same issue where the target is not detected by ST-Link after uploading the program.
This is the code link: https://github.com/kavyammengineer/stm32debug/tree/main/led_on_off
The code works correctly on the Nucleo-H755ZIQ board, but when I upload it to my customized board, the target gets stuck and is no longer detected by ST-Link.


this is my sysclk 64Mhz 

[mƎALLEm]

Hello,

---

@kavyamm wrote:

Post moved from this thread.

The code works correctly on the Nucleo-H755ZIQ board, but when I upload it to my customized board, the target gets stuck and is no longer detected by ST-Link.

---

Need to ensure you have the same hardware configuration as of Nucleo-H755ZIQ on your custom board. So the first question comes here: what is the power configuration you have on your custom board? Direct SMPS? LDO? 

Nucleo-H755ZIQ board is Direct SMPS configuration by default. So if your board is not in direct SMPS by hardware, you've locked your MCU and you need to unlock it.

Please read: How can I recover my STM32H7/STM32H7RS board after facing a power configuration deadlock?

[kavyamm]

@mƎALLEm 
I am using a direct SMPS power supply on the custom board. I have a doubt — is there any chance that the startup code is different between the custom board and the development board?NO RIGHT
 If you have time, could you please take a quick look at the code once of the CM7 core ?

[kavyamm]

@mƎALLEm 
Is there any condition that requires using a 400 Hz clock when using a direct SMPS supply? Or is it okay to use the internal HSE clock?

[mƎALLEm]

---

@kavyamm wrote:

@mƎALLEm 
Is there any condition that requires using a 400 Hz clock when using a direct SMPS supply? Or is it okay to use the internal HSE clock?

---

You can go up to 400MHz with SMPS configuration, no more.. using PLL and HSI.

[Pavani]

Hi,

As an initial step, I would recommend creating a fresh project in STM32CubeIDE and implementing a very simple application, such as toggling an LED.

If this basic code is flashed successfully on the custom board without any ST-Link target detection errors, it would help confirm that there is no fundamental issue in the Hardware of the STM32H755ZIQ board.

One possible cause of the issue could be a difference in the linker script configuration. I suggest comparing the linker scripts used for the evaluation (Nucleo) board and the custom board. If there are differences, especially in the memory definitions, it could lead to target detection or execution issues.

Please verify that the FLASH and RAM memory regions (FLASH.ld and RAM.ld entries) are correctly defined according to the custom board’s memory layout and update them if required.

Best regards,
Pavani