Part Number: CC2541
Tool/software: TI C/C++ Compiler
Dear CC2541 related expert,
I'm developing Bracon module using CC2541F256 & CC2590 with some other parties.
I had downloaded BLE-CC254x-1.4.2.2 stack from TI web.
With mionor contents modifictaion in S/W in SimpleBLEBroadcaster part, it worked fine without problem.
But when we test with pre-produced 100set for 2 months, we found it suddenly stop bradcasting for approx (2hr55min-3hr) and
back to normal broadcating. Occurrence time is ramdom. once per week or once per 2 week and once per 1days etc.
But the dead time is always same 2hr 55-3hr. The failure rate is more than 50sets out of 100sets. But not sure the % exactly
since it was happen and back to normal automatically. And we can not watch the condition without sleeping.
Is it reated watchdog timer in S/W stack?
The schematic is as follows. I suspect the unconnected floating P0.1and P0.2 pins those are assigned to input port which can cause
I/O port interrupt. But not sure. If it's the case , why it's not happen more frequently.
Can you give me some advice which part of S/W module is related with 3hr stop broadcating and back to normal broadcating ?
When we measured the current when stop, current consumption was almost same 20mA. It means that it's not get into sleep mode.
Advertsing interval is 100msec.
-------------------in simpleBLEBroadcaster.c --------------------------------------
// For keyfob board set GPIO pins into a power-optimized state
// Note that there is still some leakage current from the buzzer,
// accelerometer, LEDs, and buttons on the PCB.
P0SEL = 0; // Configure Port 0 as GPIO
P1SEL = 0; // Configure Port 1 as GPIO
P2SEL = 0; // Configure Port 2 as GPIO
P0DIR = 0xFC; // Port 0 pins P0.0 and P0.1 as input (buttons),
// all others (P0.2-P0.7) as output
P1DIR = 0xFF; // All port 1 pins (P1.0-P1.7) as output
P2DIR = 0x1F; // All port 1 pins (P2.0-P2.4) as output
P0 = 0x03; // All pins on port 0 to low except for P0.0 and P0.1 (buttons)
P1 = 0; // All pins on port 1 to low
P2 = 0; // All pins on port 2 to low
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Woul you pls give me some idea regrading this issue ?
YS Kim
