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.

CC2640R2F: CC2640R2FRGZ 32.768K clock abnormal output

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640

CC2640 problem description:

1. Chip model: CC2640R2FRGZ

2. Phenomenon:

Product 1: Bluetooth Beacon device, broadcast data at 220ms, directly powered by disposable lithium battery, full battery voltage 3.66V.

Problems: (1) When the equipment is power-on, the power cord needs to be welded. The back and forth contact between the welding pad and the power cord is bad, resulting in the chip not running. There is no output of 32.768K crystal oscillator in the test.(2) The Bluetooth beacon device has data detected before delivery, but a small part of it will crash after on-site installation. Some will crash after a few days, some after a few months, and there is still no output of 32.768K crystal oscillator back to the factory for testing.

Product 2: scanning beacon data equipment, rechargeable lithium battery through LP5912-3.3DRVT voltage stabilization to power the chip, lithium battery charging chip is BQ24040DSQR.2S turn on 260ms scan beacon to broadcast data.

Problem phenomenon: When 2 80 products were put into the temperature cycle chamber to do the temperature cycle experiment at -10~+55℃, 20 CC2640R2FRGZ were found to crash 48 hours later, and there was no output of 32.768K crystal oscillator in the test.

3. When the above two products crash, both can cut off the power supply, discharge the capacitor on the PCB and then restart the power supply.If the power supply is cut off without discharge operation, the restart is invalid.Doubts whether the chip dies under the low power consumption, hopes to assist the analysis, thanks!

  • Hello!

    I'm sorry your chips aren't working as expected. Perhaps you can share with us some more information about your board and the issues you're seeing. Any pictures of schematic/layout/boards would be helpful, and they can be shared offline if needed.

    When the equipment is power-on, the power cord needs to be welded. The back and forth contact between the welding pad and the power cord is bad, resulting in the chip not running. There is no output of 32.768K crystal oscillator in the test.

    Is the issue that there's a poor power connection to the CC device? Or that the device is frying your crystal?

    (2) The Bluetooth beacon device has data detected before delivery, but a small part of it will crash after on-site installation. Some will crash after a few days, some after a few months, and there is still no output of 32.768K crystal oscillator back to the factory for testing.

    Can you describe what you mean by "crash" in greater detail? Does the board simple not run the code as expected? Can it be re-flashed with the code and made to work after it crashes?

    When 2 80 products were put into the temperature cycle chamber to do the temperature cycle experiment at -10~+55℃, 20 CC2640R2FRGZ were found to crash 48 hours later, and there was no output of 32.768K crystal oscillator in the test.

    I see that the BQ24040DSQR device you're using has minimum recommended operating temperature of 0 C. If you can repeat this test only going down to 0 C we could try to isolate it to see if that's the issue, but I would understand if you don't want to re-run 280 more boards. I would again say we need more information about what you mean by "crash", and I'd also like to know what 32.768K crystal you're using. Perhaps both the scanning equipment and the beacon device are failing for the same reason, and you're simply accelerating that failure by stressing the devices in the temperature chamber.

    Best,

    Nate