Skip to main content
Visitor II
January 19, 2024
Question

STM32F103VFT6 99CBK 93 A MYS 99 322

  • January 19, 2024
  • 6 replies
  • 5120 views

Hi 

 

Since almost 10 years I'm working with STM32F103VF microcontroller with KEIL IDE, and I don't have any problem. But yesterday I received the last batch from my PCB manufacturer, and it installs that reference STM32F103VFT6 as always, but I can't debug with KEIL. And I don't understand why. 

 

I erased all sectors, and with ST-link Utility I can program my device successfully, but I can't debug with KEIL. 

 

Is anything to take into account to debug it? 

If I check the completely name writted in the microcontroller I can see: STM32F103VFT6 99CBK 93 A MYS 99 322

Is this batch the problem?

 

Regards, 

    This topic has been closed for replies.

    6 replies

    Technical Moderator
    January 20, 2024

    Dear @FLast.14 ,

     

    Can you provide a picture of top marking ? Also using ST-link utility to have the UniqueID in that device .

    how many parts are impacted ? And finally what means You can not debug ? If possible to provide more details with MDK Keil ?  Most probably it is not a genuine ST product and please check with you PCB manufacturer on their sources .

     

    Cheers,

    STOne-32

    January 22, 2024

    Dear @STOne-32 

    The picture of uC is:

    Image (2).jfif

     

    I do the follow steps:

    1) Open the keil and compile. Press "Start Debug Session"

    2) The following messages appear:

    FLast14_0-1705905918272.png

    FLast14_1-1705905925114.png

     

    3) then I open St-link Utillity, and connect the target. The go to Target menu > Option bytes, I DON'T change anything, only "apply" the current options:

    FLast14_2-1705906005844.png

    4) Then go to Keil again, and press "Start Debug" and it

    FLast14_3-1705906136830.png

    5) But the cursor do not is in "main" function. 

    FLast14_4-1705906371011.png

    6) If I burn this part of the project with the St-link utility, there is no problem and the code progresses and the device works fine. So, I can't debug. 

     

    My project has three parts: Bootloader, a Module, and application part.  From bootloader the code jumps to application part, and it when is working the device does some queries to Module part and it answers. 

    FLast14_5-1705906956540.png

     

    About Keil + St-link:

    FLast14_6-1705907046056.png

    What do you think can be happening?

    Thanks

     

    January 22, 2024

    When I do the same with old board:

    FLast14_7-1705907778883.jpeg

    There is no problem, I can debug:

    FLast14_8-1705907801700.png

    FLast14_9-1705907823254.png

     

     

    Technical Moderator
    January 22, 2024

    Hi @FLast.14 ,

     

    The marking of the device shows it is not an ST genuine Part as we never split the STM32F103VFT and then 6 on new line .

    as shown in the working MCU .

     

    please contact your manufacturer/supplier 

    Ciao ,

    STOne-32

     

    January 22, 2024

    FLast14_0-1705913099819.jpeg

     

    Thank you, I will contact with my manufacturer.... 

     

    January 23, 2024

    Hi

    I've contacted with my components supplier, this is an official distributor from ST in Spain, and they say:

     

    FLast14_1-1706007633709.png

    @STOne-32 do you have any other answer?

    Regards, 

    Technical Moderator
    January 23, 2024

    Hi @FLast.14 ,

    Yes, now the right path is to Open an official Ticket on our Online support, you will be in touch first with our regional team : Technical and Quality for follow-up of this unusual strange case indeed .

    Cheers,

    STOne-32.

    Graduate II
    January 23, 2024

    What version of the Keil tools and ST DLLs are you using here?

    They might need update.

     

    Graduate II
    January 23, 2024

    Not addressing your specific issue, but here are Keil's most recent versions

    https://developer.arm.com/documentation/ka005381/latest/

    Notionally living in C:\Keil\ARM\STLink depending on your install.

    You could also install a current version of the MDK and move files, but just be aware the MDK 5.3x doesn't ship with the version 5 compiler, but only version 6, and that might take some rework of code/projects if they are old.

     

    The newer / alternate mask sets should be very similar, but would check the errata, and whatever @STOne-32 can offer in regards to deltas and differences, and differences in System Loader placed in the devices.

    February 15, 2024

    Now, I'm doing test with STM32CubeIDE with the same microcontroller and I cann't debug either. When I start debug, after 1-2seconds the program stops debugging and I can't jump to any breakpoint, and no errors are appearing.
    If I test with other ST microcontroller batch, all is working fine.

    Technical Moderator
    February 15, 2024

    Hi @FLast.14 ,

    can you provide the UniqueID dump registers and also the package top marking , we need first to know if it is a genuine STM32F1.

    Cheers,

    STOne-32

    February 15, 2024

    The UniqueID is: 

    FLast14_0-1707999300387.png

     

    The top marking of the pill is:

    FLast14_1-1707999469266.png

    The top marking of the package I don't have know here because I sent to my PCB manufacturer. I bought these microcontrollers in Official ST Distributor.