stm32cubeprogrammer

[Conny Olander]

Posted on April 11, 2018 at 10:08

Fails to use stm32cubeprogrammer for stm32f765?

What can be wrong?

#stm32cubeprogrammer

[Amel NASRI]

Posted on April 11, 2018 at 11:21

Hi

conny

‌,

Why are you marking this question as 'Assumed answered'?

Did you already resolved the issue you have?

-Amel

[Conny Olander]

Posted on April 11, 2018 at 12:37

Hi!

It is not resolved.

How can I remove the marking 'Assumed answered'?

/Conny

[Conny Olander]

Posted on April 11, 2018 at 14:39

It works in stlink, see attached file. Same hex file, same address...

[Tesla DeLorean]

Posted on April 11, 2018 at 14:19

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.

[Amel NASRI]

Posted on April 11, 2018 at 14:36

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 .

-Amel

[Tesla DeLorean]

Posted on April 11, 2018 at 17:23

In the full editor you should be able to post images with the camera icon rather than as attachments.

[Conny Olander]

Posted on April 12, 2018 at 07:42

I have fixed the attachment now. Same hexfile worked with st-link program...

[Conny Olander]

Posted on April 12, 2018 at 13:43

I have not solved this problem, any ideas?

[Amel NASRI]

Posted on April 12, 2018 at 16:26

Hello,

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?

-Amel