How to use X-CUBE-AVS 1.0.1 for 32F746GDISCOVERY (STM32F746NG MCU), which is has hex file for 32F769IDISCOVERY ?

[Nikhil Kate]

Posted on May 09, 2018 at 13:45

I have 32F746GDISCOVERY (STM32F746NG MCU) board and wanted to use Amazon voice service on it. But the X-CUBE-AVS  1.0.1  program present on STM website is for 32F769IDISCOVERY board. Also it contains the binaries and hex file for 32F769IDISCOVERY. I tried to compile the project using IAR Embedded workbench for  32F746GDISCOVERY  as target controller but the .out file i get after this can not be loaded on 32F746GDISCOVERY. Also i tried to load the existing hex file of 32F769IDISCOVERY  on 32F746GDISCOVERY , but failed.

I don't know much about embedded programming, so i was wondering if i have to convert the project or the output file from 769 to 746 to work.

Please share your feedback if someone has already tried and knows the solution..

Attaching the hex file of 769. Also present on STM web site.

Thanks in advance

#stm32f746ngh6 #32f746gdiscovery-3d-model-solid #32f746gdiscovery #32f769idiscovery #avs #stm32f746ng #x-cube-avs

[Tesla DeLorean]

Posted on May 09, 2018 at 15:39

There isn't a Harry Potter method of taking a F769I-DISCO binary and loading on an F746G-DISCO.

You have to manage the porting task at an earlier stage where you address the pin, peripheral, memory and screen differences. The BSP (Board Support Package) code should make the task easier, but it is non-trivial.

If you need embedded coders on your team, ST has a list of consultants/contractors.

[Imen.D]

Posted on May 28, 2018 at 09:24

Hello

only_nikhil

,

In order to run the example on a different board, you need to port it for that particular board.

In the IDE view, some changes are expected in the 'folder' application/src and in the Middlewares/ST/STAVS/Src/porting/stm32f7xx and potentially adapt the linker scatter file to adapt to the other mcu memory map.

With Regards,

Imen