STM32C071CB Flasher

Chan.Calvin · ‎2024-12-03

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

SofLit · ‎2024-12-03

Hello @Chan.Calvin ,

The problem is not clear. For example, what is the exact problem with CubeProgrammer? what error are you facing?

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

SofLit · ‎2024-12-03

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?

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

Chan.Calvin · ‎2024-12-03

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

SofLit · ‎2024-12-04

Hello @Chan.Calvin ,

For CubeProgrammer I didn't reproduce the behavior with a NUCLEO-C71RB. C71RB and C71CB are 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:

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

Andrew Neil · ‎2024-12-04

@Chan.Calvin wrote:

Your image is too low resolution to read.

Please select all the log text, and post here as text.

@Chan.Calvin wrote:
I am using stlink v2,

Is it a genuine ST model, or a clone?

https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/tac-p/703663/highlight/true#M965

What board are you using? If custom, please show the schematic:

https://community.st.com/t5/community-guidelines/how-to-write-your-question-to-maximize-your-chances-to-find-a/ta-p/575228

Chan.Calvin · ‎2024-12-04

Hi all

Attached is the cubeprog and stlink screenshot for your ref.

I believed it is the genuine stlink v2. And we are using custom board.

As mentioned before, with the C071CB on custom board, it is failed to flash.

Replacing the C071CB with C031C6, the board becomes alive, and I can do flashing and Keil debugging.

Another blank PCB, with just only another new C071CB put on, that also failed to flash.

That points to me that it is either the batch of faulty MCU, or missing update driver to handle xB - 128K parts.

Anyway, we are making some other different PCBA with the STM32C071GB from other supplier, so I think I need to wait for this batch to see if that goes well.

Rgds

Calvin

Chan.Calvin · ‎2024-12-04

Hi SofLit

Thank you for this info. I am also wondering about it. We are also getting some NUCLEO-C71RB, but the delivery time is relatively long. I would have though the flash algorithm should be identical to C031. It is just a matter of flash size problem that ST overlook that.

One point about that, is whether that particular NUCLEO-C71RB has it own updated stlink driver or the like that can handle the flashing. What I mean is latest embedded driver for that.

As my answer to the other helper, Andrew Neil. The replacement of C031C6 on the same board did get think going though.

Anyway, it would be beneficial to me and other users, if you have some other board, or not using nucleo onboard stlink, but using external stlink to check for flashing?

Rgds

Calvin

SofLit · ‎2024-12-04

@Chan.Calvin wrote:

Anyway, it would be beneficial to me and other users, if you have some other board, or not using nucleo onboard stlink, but using external stlink to check for flashing?

Not sure what do you mean by that but all available ST boards related to STM32C0 MCUs have an STLINK on board. If you need to use an external STLINK you need to check the board hardware and find if it's possible to connect an external probe.

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.

Chan.Calvin · ‎2024-12-04

Hi SofLit

Refer to UM3353, page 17, section 6.11 that the onboard stlink can be made disconnection to the main board.

JP2, JP4, and JP6 to JP8 default ON using onboard stlink-V2EC

By making JP2, JP4, and JP6 to JP8 OFF, STLINK-V2EC functions disabled and external debugger from the connector (CN4). Here you can help to connect an external stlink V2 to see if that also can be flashed.

Rgds

Calvin