BLE Stack 2.0.2 is it possible that it doesn't run on older CC2640 running fine on 1.4 ?

Hi Rachel,

I am using CC2640 since 2014 under NDA and have some designs already in mass production.
All the simpler things I have done with stack 2.0 and 2.1 don't work with 2.2
I have weird results as well as some other here in E2E.
I have to get running this project until this weekend, and I tell you that the stack 2.2 is not useable at all.

This will be my last project using TI. I will switch over to Nordic for sure. My request about these bunch of problems I have are unanswered since 6 weeks as well as the one from other engineers.

I did learn programming using Texas Instrumenst TI 9900 cpu's back in 1982 and have always been a TI fan. But what I see now with stack 2.2 is the proof that TI lost connection.

However, I can not believe that it ends like this. I have setup TWO computers the past weekend one WIN 10 other WIN 7 to check out if it is related to operating system. But on both computers the same.

With stack 2.2 debugging is not possible, as soon as you use the pragma to switch off optimization for one single function, the whole code does not run at all. I am used to that general optimization off does not work, but in 2.1 I could at least use the pragma to control optimization for parts of the code.

If you use advertising strings longer then 21byte, nothing works
if you change the length of the scan response string it works sometimes, sometimes not ( depends if you change lenght even or uneven bytes).

The new issue I am despair on is the following:

I delivered two of my board to my customer, these boards ran fine here with stack 2.1 code and held one board back for remote developing.

My hardware design I am using is the same running fine in a mass production product.

I am using the SPB sample project (stack 2.2) as base. The original SBP runs with no issues on all three boards.

If I add some files and make the simple_peripheral.c, and references, local in workspace, the same code runs fine on one board but does not run on the others.

not only this, if I run a code verification after the boards were powered for >20min the boards which don't run fail in code verification.
So either the chip flash 'forgets' programming or the stack 2.2 makes changes to the flash. Reprogramming the chip passes verification, but code does not run.
Reprogramming the unchanged SBP project runs fine for hours and days. But any code changed just a little bit does not and flash content alters after a while.
And not only this, on one of the boards I got the code running once, BUT the chip send a wrong BLE address over air. It was not the same you read out with FP2, the last byte was supposed to be an B2 but sent was A2. Reading with FP the address remains ending with B2.

So Stack 2.2 seems really sick to me. I am not a newcomer with the CC2640 and I do want to know the reason.
I have been posting a view issues in the past 6 weeks like others and none of the experienced TI'ers responded. This is to me a sign that there is something serious wrong.

So either find somebody who has the balls to say 'stay away from 2.2 for the moment' or tell us what is wrong.

From my view and situation, there is one last issue as a possible explanation. The CC2640 I am using I did buy in 2015. they are PG2 for sure but not sure about .1

So question remains, is it possible that these chips are too old for stack 2.2 ?

Ah ja I forgot, going back to stack 2.1 works fine on all boards ....

Good luck