WB55: Leaving the chip in the brick after loading the stack. Very important for everyone.
2 years ago it happened that the controller turned to brick. I corresponded with technical support for a long time and I was offered to send the controller to the factory or representative. But since the case was a single one, I did not take advantage of this case and forgot about it.
Now there is a situation that, probably, everyone who uses this chip has, namely, that for unknown reasons it turns into a brick.
I re-read all my messages in the STM community, but to my surprise, the post in which I described the transformation into brick disappeared.
Today I have about 70 controllers with which I cannot do anything because they are not programmable.
I decided to understand the reason and found it.
The reason is well described in the post:
https://community.st.com/s/feed/0D53W000010si7oSAA?t=1676280731376
But for all this time, not a single STM employee has given a clear explanation of why this is happening.
The question is simple: why sometimes, after loading the stack, the chip register SFSA = 0?
After all, because of this, the chip turns into a brick.
I lost some money to buy the chips, but I lost a lot more because I couldn't sell my final product.
How long will STM keep silent about this problem?
None of the ERRATAs describe this case.
It turns out that STM does not give a damn about its consumers?
If the official representatives do not answer this question, I will raise a storm on the Internet about the quality of the chips and the sabotage of employees in front of consumers.
Vyacheslav : Bluetooth SIG Id is "LVI Cо."