We have a CC2533 that is running off of a battery. Every 20 seconds, the CC2533 wakes up, sends a short message, and then goes back to sleep (PM2 power mode). What we have found is that as soon as the supply voltage for the CC2533 hits 2.0 volts (we tested this with a digital power supply), the CC2533 will wake up transmit the message, and then hang on the line of code that should return the part to the PM2 power mode. While it is hanging current draw is about 2 mA (which is normal for active mode) instead of the typical 0.7 uA. At this point the micro will hang indefinitely, no watchdog or brown out reset.
With the CC2533 in this state, with a power supply, if you increase the voltage up to 2.2V, it will do one of two things:
Is this a known issue? Is there a workaround for this issue? Are there any settings that we might not have configured correctly?
We suffering similiar problem on CC2530 on which we run HA profile of Zigbee Pro. Hope TI guys can help on this issue.
Hi Jimmy,
This seems like a strange problem, and nothing we have seen before. What kind of hardware are you using, SmartRF05EB+CC2533EM, custom board or other? Would you be willing to send me your code (through email)?
Regards,
Fredrik
--PS. If I answered your question, please hit Verify Answer !
Fredrik,
Thank you for taking the time to respond. I would like to email you. What is your address?
Thanks,
Jimmy
I have heard of an issue with using the radio near to the brown-out voltage level - the Vdd is not low enough to trigger a brown-out, but then using the radio cause Vdd to sag and then SOC execution is hung as observed. Therefore, s/w must be added that will disallow code execution (or at least radio useage) near to the brown-out level.
Downlaod the RemoTI stack for the CC2533 and take a look at how the BATMON battery monitor peripheral is used to enforce this "pre-brown-out" halt in s/w.