2024-01-19 05:52 AM - edited 2024-01-21 10:41 PM
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,
2024-01-20 12:10 AM - edited 2024-01-20 01:57 AM
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
2024-01-21 11:05 PM
Dear @STOne-32
The picture of uC is:
I do the follow steps:
1) Open the keil and compile. Press "Start Debug Session"
2) The following messages appear:
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:
4) Then go to Keil again, and press "Start Debug" and it
5) But the cursor do not is in "main" function.
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.
About Keil + St-link:
What do you think can be happening?
Thanks
2024-01-21 11:17 PM
When I do the same with old board:
There is no problem, I can debug:
2024-01-21 11:40 PM
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
2024-01-22 12:45 AM
Thank you, I will contact with my manufacturer....
2024-01-23 03:01 AM
Hi
I've contacted with my components supplier, this is an official distributor from ST in Spain, and they say:
@STOne-32 do you have any other answer?
Regards,
2024-01-23 05:21 AM
What version of the Keil tools and ST DLLs are you using here?
They might need update.
2024-01-23 08:51 AM
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.
2024-01-23 09:26 AM
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.