cancel
Showing results for 
Search instead for 
Did you mean: 

Q : STM32N6570-DK for gesture recognition control applications related

Tom87
Associate

 

01.jpgFSBL.png

 

 

Hello, I would like to ask about a question regarding “STM32N6570-DK for gesture recognition control applications.”

I have downloaded the official example x-cube-n6-ai-hand-landmarks-main and reviewed the DataBrief of the development board. Since the board itself does not contain internal Flash, the file _htmresc/FSBL.PNG in the example clearly indicates two possible solutions:

  1. User APP programmed into SRAM (address: 0x3400 0400 ~ 0x3418 0000)
  2. User APP programmed into external Flash (address: 0x7008 0000 ~ 0x7FFF FFFF)

Following the instructions in README.md, I executed the following steps:

~make -j8~

 

Program the Firmware in the External Flash

After building the application, it is necessary to add a signature to the binary file:

~STM32_SigningTool_CLI -bin build/Project.bin -nk -t ssbl -hv 2.3 -o build/Project_sign.bin~

 

After obtaining the signed binary file, I manually programmed it to address 0x70100000.
(The files ai_fsbl.hex, hand_landmark_data.hex, and palm_detector_data.hex had already been pre-programmed on the development board.)

However, after programming Project_sign.bin to address 0x70100000, the development board did not operate as expected according to the official example.

I do not understand where the mistake occurred in the process. The only modification I made was deleting the option “-fcyclomatic-complexity” from lines 128 and 129 of the Makefile:

  • ASFLAGS = …………… -fcyclomatic-complexity
  • CFLAGS = …………… -fcyclomatic-complexity

This was done to allow the command make -j8 to run successfully in Bash.

I am seriously considering whether the issue might be related to the STM32N657xx.ld file. The binary files generated by the Build process in the Bash terminal seem to be located at address 0x34000000, while the official example application file (x-cube-n6-ai-hand-landmarks-dk.hex) located at address 0x70100000 as it be generated as hex file.

Therefore, I would like to ask whether it is necessary to modify the .ld file. If my problem is indeed caused by an incorrectly configured address in the linker script, I hope to receive some guidance and instructions so that I can continue and complete my subsequent research a

I have been struggling with this issue and have spent a great deal of time researching it… I sincerely hope to receive some help !

Thank U so much !!

 

0 REPLIES 0