Wrong documentation for stm32n6 nucleo board, programming is not working following that documentation

[cornway]

Describe the bug

I refer to article
https://docs.zephyrproject.org/latest/boards/st/nucleo_n657x0_q/doc/index.html

Issue #1 :
Seems that BOOT switch positions are twisted, board says that development mode is enabled :

But article says opposite; I may be wrong here, but considered it worth noticing

Issue #2 :
Application programming following this tutorial into external flash is not working, I didn't manage to start application from external flash
WA: none
UPD
Having STM32_SigningTool_CLI in path is sufficient, booting from flash requires signed image

Issue #3
Application programming following SB procedure (Serial Bootloader) is not working
WA :
There are couple of steps :

• export PATH=$PATH:<path_to_home>/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin
  As STM32_SigningTool_CLI must be available through the PATH, otherwise binary is not signed

• west build -b nucleo_n657x0_q//sb samples/basic/blinky -d build-sb
  Original command is missing -d build-sb, otherwise it won't sign the binary

• west flash is not working, adding -d build-sb doesn't help
  Only way around - is to program it manually:
  STM32_Programmer_CLI --connect port=/dev/ttyACM0 --download build-sb/zephyr/zephyr.signed.bin 0x1 --start noack
  Otherwise west flash tries to flash .hex file which is not accepted :
  Error: The download command you trying to perform (--download) is missing the filePath to be loaded or it has a wrong extension, please note that the supported extension are .bin, .hex, .srec, .s19, .elf, stm32, .ext2, .ext3, .ext4, .vfat, .ubi, .jffs2, .img and .tsv files.

• In boards/st/nucleo_n657x0_q/board.cmake port is pointing to a wrong endpoint :
  board_runner_args(stm32cubeprogrammer "--port=usb1"); I may be misusing it, but anyways worth noticing

I'll keep working on find and fix these issues on my own, but I presume article created (by ST vendor ?) Is slightly off the truth

Regression

• This is a regression.

Steps to reproduce

Follow the article and try to flash the board

https://docs.zephyrproject.org/latest/boards/st/nucleo_n657x0_q/doc/index.html

Relevant log output

Impact

Not sure

Environment

Not relevant

Additional Context

No response

[etienne-lms]

Hello @cornway,

I've tested a nucleo_n657x0_q based in current Zephyr documentation.

I confirm your initial Issue-1: the doc is wrong.

• to program the flash through STLink, we need to set BOOT0=1, BOOT1=0
• to run the programmed flash: BOOT1=1

Issue-2/Issue-3:
As you said, you need to sign your image so that it is executed.
The documentation already includes a note about STM32_SigningTool_CLI installation (with stm32cubeprogramer + addition in PATH).

You don't need to specify to west build the build directory with -d. The default build dir, if -d <DIR> is not set, is ./build/.
Same for west flash.
Note that if want to build in a specific directory (e.g. west build -d some_directory ..., then you'll need to give the west flash the same directory path (here: west flash -d some_directory).

I've checked building and programming the flash with the serial-boot variant (nucleo_n657x0_q//sb). Building, signing, programming work fine, assuming you set BOOT0:0/BOOT1:1, contrary to the doc directive.

I'll create a P-R to propose some documentation fixes and maybe clarification. I'll keep you informed.

[etienne-lms]

See #96476.

[etienne-lms]

I confirm your initial Issue-1: the doc is wrong.

to program the flash through STLink, we need to set BOOT0=1, BOOT1=0
to run the programmed flash: BOOT1=1

My mistake. Documentation is right (BOOT0=0/BOOT1=1 to program the flash, BOOT0=0/BOOT1=0 to run the flashed program)
I think the prints on nucleo_n657x0_q are confusing: there "1" jumper position printed near jumpers, but they relate to position "0" of the related BOOTx, while the un-printed "2" jumper position relates to position "1" of the related BOOTx. See #96476, I hope it clarifies the expected configuration.