Skip to main content
Visitor II
November 18, 2025
Solved

STM32F303CCT6 vs STM32F303CBT6

  • November 18, 2025
  • 8 replies
  • 531 views

I recently purchased some STMF303 boards for implementing a free pre-compiled HEX file.
I received the boards with the STM32F303CCT6 chip, but the pre-compiled file was for the STM32F303CBT6 chip. The HEX loads but does not run on any 303CCT6.
Are there significant compatibility differences between the CCT6 and CBT6 chips that would justify this?
Could I have lost the purchased boards?
Thank you.

    This topic has been closed for replies.
    Best answer by mƎALLEm

    @ValterMatos wrote:

     therefore we lack sufficient knowledge to debug a complex HEX file.


    Debugging is something related to the source code not to the HEX file.

    "Debugging" HEX file is something to do with experts.

    8 replies

    Graduate II
    November 18, 2025

    Hi,

     

    the STM32F303CCT6 has 256kB Flash, while STM32F303CBT6 has only 128kB.

    So a binary for STM32F303CBT6 should fit

    I see no other differences. The problem should be somewhere else.

     

    P.S.: ... and 40kB SRAM instead of 32, but should be no harm as well.

    Technical Moderator
    November 18, 2025

    Hello @ValterMatos and welcome to the ST community,

    This information is provided in the product datasheet / Section 8 Ordering information:

    mALLEm_1-1763483972215.png

    and in Table 2. STM32F303xB/STM32F303xC:

    mALLEm_2-1763484103542.png

    The difference is in the Flash and RAM size . I don't see other differences. So if you have a hex file working fine on CBT6 that should work on CCT6.

    Are you sure the boards are OK? boot pin? power? etc ..

     

     

    Super User
    November 18, 2025

    @ValterMatos wrote:

    I recently purchased some STMF303 boards for implementing a free pre-compiled HEX file.


    Are you sure those boards are actually suitable for that hex file?

    Are you sure that they work at all ?

    Please share details of this mystery Hex file?

    Have you discussed this with the  author/provider of the Hex file?

    Visitor II
    November 18, 2025

    The files were shared at:
    https://disk.yandex.ru/d/QJmF7P2byAYma
    https://disk.yandex.ru/d/zgN9puZg3NKG8m
    The idea was to train a group of students in electronics to make an oscilloscope STM as a work tool. As we don't have enough experience in STM programming, we decided to select a shared project.
    I spoke with the author who reported having no problems at the time when using the 303CBT6.
    Maybe we'll try another project.
    Thank you.

    Technical Moderator
    November 19, 2025

    Hello,

    Unfortunately we cannot progress based on the information you shared with us. If you have the same board with CBT6 and confirm the hex file is working fine. 

    Visitor II
    November 19, 2025

    Unfortunately, the author does not share the source code. At the time, he used the 303CBT6. All the boards we received were 303CCT6, which is apparently compatible and even better. We followed all the resources requested by the shared electronic circuit and used STLink to program the HEX.
    We programmed other files on the boards for testing and they are good. I believe that the shared HEX, shown in the previous message, may be corrupted.
    We will try to switch to another project with available source code that uses the 303CCT6 boards we have.
    It is a study project for students with limited resources.
    Thank you very much for your help.

    Thank you

    Super User
    November 19, 2025

    @ValterMatos wrote:

    We will try to switch to another project with available source code that uses the 303CCT6 boards we have.


    That sounds like a good idea.

    The learning value of blindly loading an unknown hex file seems rather limited?

     


    @ValterMatos wrote:

    It is a study project for students with limited resources.


    In such cases, the Nucleo boards are ideal: they are cheap, come complete with built-in ST-Link, and are well-supported with ready-to-run examples...

     

    If your issue is now resolved, please mark the solution.
     

    Visitor II
    November 19, 2025

    We are still in the early stages of developing STM microcontroller programming, therefore we lack sufficient knowledge to debug a complex HEX file.
    Thank you all for your help and understanding.

    mƎALLEmAnswer
    Technical Moderator
    November 19, 2025

    @ValterMatos wrote:

     therefore we lack sufficient knowledge to debug a complex HEX file.


    Debugging is something related to the source code not to the HEX file.

    "Debugging" HEX file is something to do with experts.

    Visitor II
    November 19, 2025

    Debugging HEX. It's almost impossible, for sure.
    We don't have the knowledge for that. Therefore, we have to move on to a project with the source code because we don't have the time to develop one like the one we tried to do.

    We will continue to focus on STM microcontrollers.

    Technical Moderator
    November 19, 2025

    You can try to run a very simple project. If you have LEDs on the board, try to blink them at least to check the board is working well. Use tools STM32CubeMx to help you to configure the GPIO and STM32CubeIDE to upload your program and to debug it. To me this is the first step you need to do.

    If you can share the schematic of the board I can help you for this task.

    Visitor II
    November 25, 2025

    Good morning.

    I'm still trying to develop in STM code.

    I have an open-source code developed for the STM32L476.

    Questions:

    If I generate a compiled HEX for the STM32L476, will it run on the 411?

    Are they compatible?

    Is it possible to migrate to an STMF303 or an STM32F411?
    These are the ones I have to continue developing my studies.

    I still don't have enough knowledge.

    I've been trying to adapt it to the various available STM controllers.

    Thank you.

    Valter Matos

    Technical Moderator
    November 25, 2025

    Hello @ValterMatos ,

    This is a new question, please create a new post for it.

    Thank you for your understanding.

    Super User
    November 25, 2025

    The New thread is here: STM32L476vsSTM32F411vsSTM32F303.