Hello,
I designed a module with a CC2540, and launched a pilot run. I found around half of the modules are ok (programming with CC Debugger ok, working ok, BLE peripheral communication ok,... everything ok).
Other 50% have hardware troubles. Programming fails randomly (at verifying). However, when the programming is sucessful (sometimes), the chip seems stuck, the software doesn't start. Sometimes, it starts if I don't disconnect the CC debugger right after the programming. I can see the two Crystals at work (32k and 32M). After reseting the board several time (either by disconnecting the power supply or by playing the reset pin), the chip doesn't start (Crystals offwork). Resetting over and over has no effect. I can restart the board, by programming again (but, it very difficult because I need to try many many times before getting sucessful verify).
There is a TX pin of UART connected to an external FDTI adapter to USB for logs. After the chip start the Crytals (when it can), the logs are partial, or messed, very random.
When the Crystals are started, I have measured the frequencies, they are both ok.
Knowing that 50% of the boards are ok, and others are working randomly, I stuck...
Anyone has a clue on that issue?
