STM32H747IIT6 CM4 not responding

[aradhyab]

I am working on STM32h747 series. I am debugging both CM4 and CM7. After a while, CM4 stops responding and the debug messages shows:

"Error in final launch sequence:

Failed to start GDB server

Failed to start GDB server

Error in initializing ST-LINK device.

Reason: (4) No device found on target."

If I run CM7 independently, it works but CM4 is not responding. I tried to erase the entire board but CM4 is still not responding and the same message is appearing.

[mƎALLEm]

Hello,

---

@aradhyab wrote:

I am using board STM32H747IIT6.

---

That's the chip not the board. Are you using a ST board: Eval board? discovery board? or a custom board?

---

@aradhyab wrote:

it turns out that when I assign LSE clock to RTC, CM4 does not boot, but when I assign LSE to LSI, it boots. . 

---

Sorry not clear. what do you mean assign LSE to LSI? do you mean if the RTC clock source is LSE CM4 doesn't boot while if the RTC clock source is LSI CM4 does?

And I've already requested to attach your project. I cannot help you with the elements you've provided.

[aradhyab]

I am using custom board.

Yes I mean that if the RTC clock source is LSE CM4 doesn't boot while if the RTC clock source is LSI CM4 does boot.

Attached the link to project below:

Project Link - CM4 not debugging 

[mƎALLEm]

---

@aradhyab wrote:

Yes I mean that if the RTC clock source is LSE CM4 doesn't boot while if the RTC clock source is LSI CM4 does boot.

---

That most probably means you have an issue with the crystal. Are you sure the LSE crystal is compatible with the MCU? please read this knowledge base article: How to select a compatible crystal and load capacitors for STM32 with layout guidelines

And with more detailed subject: AN2867 "Guidelines for oscillator design on STM8AF/AL/S and STM32 MCUs/MPUs"

PS: avoid using Google drive to share a project but attach your project compressed by using drag and drop:

[aradhyab]

I will check the crystal used and it's compatibility and get back to you on this next week, as the team is unavailable for a few days. 

I have also attached the project for your reference.