Fails to use stm32cubeprogrammer for stm32f765?
What can be wrong?
Hi Conny Olander, Hi Amel N,
To share also with STCommunity the exchanges I have within ST online support (as supporter).
Setup of Conny Olander is using an STM32F765ZG, i.e. with the 1MB Flash configuration. This was not supported by default out of the box from the STM32FlashLoader V2.9.0RC8, but I was able to provide previously an associated .STmap configuration file to make it work.
If I look at the STM32CubeProgrammer database (in C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\Data_Base file STM32_Prog_DB.xml), I am only seeing the 2MB single and dual banks flash configuration for the STM32F76x/STM32F77x (with Device ID 0x451).
This explains, Amel N, why it is working for you on the STM32F769I-Discovery (since including a STM32F769NIH6 microcontroller featuring 2 Mbytes of Flash)
So for me, we have the same issue as for the STM32FlashLoader, we need to add inside STM32CubeProgrammer a 1MB Flash configuration to STM32F76x/STM32F77x Device ID 0x451 covering STM32F765xG products .
Hi Conny Olander,
Why are you marking this question as "Assumed answered"?
Did you already resolved the issue you have?
It is not resolved.
How can I remove the marking "Assumed answered"?
I think that's Jive's heuristics at work, the OP didn't mark anything correct.
Looks like the Cube Programmer doesn't understand the 0x00200000 mapping of the FLASH. There is perhaps a linker script setting to map it better so as to avoid the error.
I don't think it is a Jive's issue; the OP may mark his question as assumed answered clicking on:
Unfortunately, there is no way even for moderators to unmark it. So we have to look for the answer now .
It works in stlink, see attached file. Same hex file, same address...
In the full editor you should be able to post images with the camera icon rather than as attachments.
I have fixed the attachment now. Same hexfile worked with st-link program...
I have not solved this problem, any ideas?
I have an STM32F769I-Discovery and I generated a .hex from one example available in the CubeF7 package (GPIO_EXTI), then I was able to load it successfully with STM32CubeProgrammer.
Could you please retry again from your side with another .hex?
If the issue is related to your initial .hex file, may it be possible for you to share it (even in PM) for farther check from our side?
I have attached a hexfile. It did not work with stmcubeprogrammer.
This is a the new file.
The old and the new file work with older st-link utility program.
They also work with the CAN bootloader.
Hex files were created with IAR.
Not solved... Help!!!
When are the utdate available?
Why can you not just fix this?
Retrieving data ...