STM32L151RDT6 (SMD marked as rev V) but ST-Link utility displays "Unknown" revision ID and wrong flash size(256 isntead of 384KB) (ID_CODE = 0x10f86427) . Where I can find full list of silicon revisions of this particular MCU ?

[OrestHWeng]

..

[OrestHWeng]

In addition to that. Debug session allways start with the HardFault_Handler().

What I have noticed that for the particular MCU there is A, Z, Y, X, 1 revision (according to errata sheet) and no one has 10f8 ID CODE.

Looks like i got a clone.

[Tesla DeLorean]

Pull current materials

https://www.st.com/en/microcontrollers-microprocessors/stm32l151rd.html#documentation

[OrestHWeng]

[Tesla DeLorean]

Pull current tools, tools which are old are not future-proof, and will not be aware of any new die, mask sets, fabs or steppings

https://www.st.com/en/development-tools/stm32cubeprog.html

[Tesla DeLorean]

Don't use the ST-LINK Utilities, it has been deprecated for several years at this point. Use STM32 Cube Programmer.

The Reference Manual and the Errata?

The RM should have details of the Chip, Stepping/Revision, and also the address in OTP to read the tested flash size from.

https://www.st.com/resource/en/reference_manual/rm0038-stm32l100xx-stm32l151xx-stm32l152xx-and-stm32l162xx-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

https://www.st.com/resource/en/errata_sheet/es0240-stm32l15xxc-stm32l15xxd-stm32l15xxca-stm32l162xc-stm32l162xd-device-errata-stmicroelectronics.pdf

STM32L15xxC STM32L162xC Rev 0x10F8 

Should be marked as "1" or "V", please attach a large, clear, in focus image of the part in question.

[OrestHWeng]

[OrestHWeng]

Cube Programmer also can not recognize the REV ID:

19:16:00 : Board    : --

 19:16:00 : Voltage   : 3.25V

 19:16:00 : SWD freq  : 4000 KHz

 19:16:00 : Connect mode: Normal

 19:16:00 : Reset mode : Software reset

 19:16:01 : Device ID  : 0x427

 19:16:01 : Revision ID : --

 19:16:01 : UPLOADING OPTION BYTES DATA ...

 19:16:01 :  Bank     : 0x00

 19:16:01 :  Address    : 0x40023c1c

 19:16:01 :  Size     : 136 Bytes

 19:16:01 :  Bank     : 0x01

 19:16:01 :  Address    : 0x1ff80000

 19:16:01 :  Size     : 136 Bytes

 19:16:01 : UPLOADING ...

 19:16:01 :  Size     : 1024 Bytes

 19:16:01 :  Address    : 0x8000000

[Tesla DeLorean]

@Peter BENSCH​ @Nawres GHARBI​ @Sara BEN HADJ YAHYA​ 

Can you please review this situation with the consistency of the tools, docs, and markings. Thanks.

[OrestHWeng]

And the screenshot of document is page of ERRATA to L15xx family of devices

[Tesla DeLorean]

Looks to be a die out of Crolles, so not a clone. Could well be something that was waived out to a specific custom, and thus not a retail part. Assuming you picked these up from the secondary market.

For Cat 3 devices the FLASH size is reported in a 16-bit word at 0x1FF800CC

If you touch beyond the usable memory on-die it will Hard Fault, suggest having the Hard Fault routine unpack the observed state/registers.

[OrestHWeng]

According to document from Product page on Mouser (Where actually I bought those MCUs) https://www.mouser.com/PCN/STMicroelectronics_10548.pdf

Change is visible through assembly traceability plant, in the marking:

- “GQ�? and "GH" for Stats ChipPAC China

and it is not from Crolles!

[Tesla DeLorean]

I said the die is out of Crolles, looks to be packaged/assembled in China.

Work with your FAE out of Mouser, and have them work their ST contacts. If it's from Mouser they should be able to establish provenance and traceability.

@Imen DAHMEN​  @Amel NASRI​ can you please assign this for review, thanks.

[OrestHWeng]

Also I dont know what to beleive to. To REV ID? DEVICE ID? or SMD Marking?

That is kind of weird. I need confirmation from somebody from ST that my MCU are Clone (and i should not use it ) or not, and point me to the documents where I can get valid info about changes in case of their presence.

[Tesla DeLorean]

Well I think there's significantly fewer die than there are product SKUs

Enough boxes are checked here that it's likely a legitimate part, and whatever production side has done seems to have repercussions that the documentation and tools side hasn't fully caught up with, at least publicly. The documentation likely exists, and I'm trying to shake the part of the tree I have hold of to get some answers/attention.

ST has a history with odd orphan / step-child parts, where delivery has been made using equivalent, or better, die to meet demand of specific parts and foot-prints.

[Billy OWEN]

Hello Orest,

This forum thread was marked by the moderator as needing a little more investigation, so a Support case was created in your name.

I wanted to first say that you should feel confident using any devices purchased in the authorized distribution channel, such as Mouser that you mentioned. There may some other variables going on here, so we will be in contact in just a bit to look into this further from the Support case that was made.

Lastly, should anyone have any similar questions like this, such as authenticity or device markings, please feel free to open a Support case directly at your myST portal, here: https://st.com/ols

Thank you for your interest in ST products.

Regards,

Billy

[Tesla DeLorean]

I think perhaps the deeper concern here is the systemic failure of the documentation and the tools to support a part that's shipped for 2+ years.