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 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

[Conny Olander]

Posted on April 13, 2018 at 06:51

Hi!

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.

/Conny

[Conny Olander]

Posted on April 17, 2018 at 14:47

Not solved... Help!!!

[Cedric LECOUTRE]

Posted on April 17, 2018 at 15:59

Hi

Olander.Conny

‌, Hi

st.mcu

‌,

To share also with STCommunity the exchanges I have within ST online support (as supporter).

Setup of

Olander.Conny

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,

st.mcu

, why it is working for you on the STM32F769I-Discovery (since including aSTM32F769NIH6 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 .

Best regards,

Cedric

[Conny Olander]

Posted on May 18, 2018 at 06:32

When are the utdate available?

[Amel NASRI]

Hello,

Please note that the issue explained by Cedric was fixed in STM32CubeProg V1.1.0.

-Amel

[Conny Olander]

​Hi!

This still does not work, When comes the stmcubeprogrammer update that fixes this problem?

/Conny

[Conny Olander]

​Hi!

It still does not work...

I Have tried cubeprogrammer v2.50 today and the errors remains...

When can this be fixed?

/Conny

[Tesla DeLorean]

Fixing issues and basic functionality with these applications seems to be a problem for ST.

​

I've reported several issues with HEX and ELF parsing issues, including ones which break the external loaders, which don't seem to get addresses or tested throughly.​ ie issues with one file might be changed, but systemic issues with other files is not.

​

Needs independent code review and oversight.​

​

​