2021-09-10 02:54 AM
2021-09-10 03:00 AM
Nobody here knows what chips you're talking about.
Try specifying full part numbers, and perhaps have large clear pictures of the parts and markings you're talking about.
2021-09-10 03:08 AM
Sorry,Chip is STM32F103.
2021-09-10 03:20 AM
Ok, but still not clear on 2.3.x marking you talk about. Sounds like a code load added to a part by distributor, customer or custom manufacturer.
Most marks are lasered, not silk screened.
Take a photo, large resolution, clear and in focus.
2021-09-10 04:26 AM
2021-09-10 04:26 AM
2021-09-10 04:55 AM
Ok, that should reflect the chip revision / die stepping
It should be readable via an DBGMCU register
The features and issues of give versions should be covered in the Errata documents.
2021-09-10 05:04 AM
Thank you for your reply. You are my lucky star.Now I am going to find the answer in the documentation.
2021-09-10 05:07 AM
How this impacts your design and software will depend on the peripheral usages, and coincidence with the errors/bugs in each of the respective IC design changes.
Generally ST has been very good at keeping these to a minimum, or hiding the impact in the SPL/HAL library implementations.
You'll need to go through the list, determine what might be impactful, and test/evaluate in your implementation.
This is likely to be a particular issue currently as anyone with old or surplus stock of parts is likely to be selling those via brokers, etc, leading to a random mix, rather than the freshest version of the part straight out of the fab.
2021-09-10 05:27 AM
Thanks again for your reply to my question.