2024-12-03 09:02 AM - last edited on 2024-12-03 09:21 AM by SofLit
Hi all
Is it correct that the flashing of STM32C071CB is not quite readily available? I am using the newest stm32cubeprog, version 2.18.0, or Keil MDK version 5.41.
In both cases, I have tried to make a connection to the captioned MCU but I got failure in connection.
In particular, in MDK 5.41, I get this screen shot:
That the flashing driver of STM32C0x_64 is not the appropriate driver to being used for the 128K part. I did look into the corresponding file folder, and I did locate STM32C0x_128.FLM file but some how I cannot get this in the file list for the selection.
Anyone out there experienced similar issue, and any remedy to the problem.
By the way, I did tried to use 3 different PCBA boards in no vain, but replacing the MCU with stm32c031c6 on one of the PCBA did get connection done seamlessly though.
Rgds
Calvin Chan
2024-12-03 09:14 AM - edited 2024-12-03 09:17 AM
Hello @Chan.Calvin ,
The problem is not clear. For example, what is the exact problem with CubeProgrammer? what error are you facing?
2024-12-03 09:20 AM
For KEIL do you mean as you are using STM32C071CB: B means Flash size of 128KB and there is no corresponding flasher for KEIL for this size but just only 64KB?
2024-12-03 06:34 PM
Hi SofLit
Regarding stm32cubeprog v2.18.0, the connection could not established.
For Keil 5.41, even though I selected the correct part of STM32C071CB, the 128K flash part, Keil just give me the flashing driver of STM32C0x_64, which is not the appropriate driver to being used for the 128K part. I did look into the corresponding file folder, and I did locate STM32C0x_128.FLM file but some how I cannot get this in the file list for the selection.
If you look into the initial screen capture of Keil flash download page, you can see the ROM address space did give 128K flash selection (08000000H - 0801FFFFH) though.
Having said that, I cannot get Keil into debug mode, and is experiencing the same failure to make connection issue.
Of course, there is also a chance of getting unlucky batch of faulty MCUs though.
I am using stlink v2, its details was shown in the stm32cubeprog screenshot.
Rgds
Calvin Chan
2024-12-04 12:47 AM
Hello @Chan.Calvin ,
For CubeProgrammer I didn't reproduce the behaviors with a NUCLEO-C71RB. C71RB and C71CB are the same from Flash point of view. So you need to check your HW.
This is a screen shot of my connection with CubeProgrammer to an STM32C71RB. I've written 0xA5 to the last location of 128KB: