Other Parts Discussed in Thread: CC2640
The CC2640R2L enters low-power sleep with a normal current of 1.5ua, the same procedure and operation, batch TI 368, TI 388 power consumption of 100ua+
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
The CC2640R2L enters low-power sleep with a normal current of 1.5ua, the same procedure and operation, batch TI 368, TI 388 power consumption of 100ua+
Hello!
We have received your case and the investigation will take some time. Thank you for your patience.
1. Can you provide the lot trace code? I can check if the issue is related to a particular FAB.
2. If you install the failing part unto a launchpad and measure the low-power sleep using an empty example, do you see the same current draw? The purpose of this step is to rule out settings issue that can cause the chip to wake up when not explicitly defined.
3. If the issue still persist after step 2, initiate a return and ATE will provide a conclusive answer as their setup can bypass the stack.
Last check before initiating a return is to check if all the GPIOs are pulled up or down. 100uA is in that range.
The chips of the original TI 138 batch did not have the problem of high power consumption. For the same PCBA and programs, TI 138 was replaced with TI 368 and TI 388, and the problems changed along with the chips. The io part has also been checked before
Sorry about the delay. The reply was bugged and I could post my answer.
Start here: https://www.ti.com/support-quality/additional-information/customer-returns.html
Once the part is returned, it'll go through 3 tests.
1. Continuity which just checks for shorts
2. ATE which is validated test. This step will tell us if there's any truly wrong with the part.
3. Bench test which is where I install the bad part unto a launchpad and try to replicate the results you are seeing.
If the part passes all 3 steps, then the customer must do further troubleshooting on there end.