STM32N6 Boot Pins

[Okeskin]

Hello, I have the STM32N6570-DK kit. I can compile, upload and debug by following the instructions on the kit. I designed my own board but I can't debug. I'm reviewing all the possibilities and I noticed some problems. I couldn't find any explanation.

https://community.st.com/t5/stm32-mcus/stm32n6-boot-rom-explained/ta-p/763648

@B.Montanari  's  article says H(High) VDDIO. However, in the DK schematics and pcb, the left side is vddio and the right side is gnd. Also, the Boot1 pin is pulled to the right to load software on the DK. So Boot0 becomes important. What's the problem? Are the documents wrong? Also, on the board I made, I can load software when boot1 is connected to vddio. But on the DK, it allows me to load software when boot1 is GND. What's the explanation?

[RomainR.]

Hi @Okeskin 

Pins BOOT0 and BOOT1 define the STM32N6 boot sequence.
This is what you shared with Table 32 in RM0486.

Note that BOOT1 has priority over BOOT0.

On your STM32N6570-DK, as explained in the article:

• When the BOOT1 switch is to the right, it forces pin BOOT1 = VDD = 3.3V.
  This is the DEV_BOOT mode, which allows you to load and debug your code in the internal RAM using SM32CubeIDE or program the external Flash memory and OTP with STM32CubeProgrammer.In DEV_Boot, PG10 (LED2 on the DK) is forced to 0V, and lights up LED2 to indicate that DEV_Boot is active.
• When the BOOT1 switch is to the left, pin BOOT1 = GND, then BOOT0 define the boot condition, to the left BOOT0 = GND is Flash Boot, and to the right, BOOT0=VDD, is Serial Boot.

There are no errors in the documentation or in the schematics. What are the error message whan you are trying to debug your application?

Share your board diagram or measure the voltage levels you have on BOOT0 and BOOT1 as I explain to confirm is you are applying the correct DEV_Boot conditions.
Best regards,

Romain,

[Andrew Neil]

---

@Okeskin wrote:

I designed my own board but I can't debug.

---

What do you mean by that?

What are you using to debug?

Where, exactly, does it fail?

If the problem is in the debugger connection to the board, see:

https://community.st.com/t5/stm32-mcus/how-to-solve-connection-errors-when-connecting-and-programming/tac-p/786977

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693