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.

CC2538 end device wake up time too long for the end device join the coordinator's network

Other Parts Discussed in Thread: TIMAC

Hi Support,

Now we used TIMAC, two board smartRF06 EB and CC2538EM, we used no beacon and direct message for the communication, because for the end device, we require the sleep mode for the system to reduce power consuming, and we hope the end device wake up time should less than 20ms in 100ms period time.

but when I used the two board to do the testing using TIMAC, one is coordinator and the other is end device.

I found the time is 600ms when end device join the coordinator's network.

I will explain where the 600ms from.

Below is the packet captured from sniffer software when end device request association with coordinator, and the coordinator assign an short address for the end device.

From frame 2, end device send out deacon request, the time is 2402639us, and the last get an short address the end device send out ack the time is 3041823us.

The gap time about 640ms.

My question is that can the CPU go into sleep mode when do the association request like upper?

When in this stage (end device setup network with coordinator), I check the source code find that MAC_PwrOffReq(MAC_PWR_SLEEP_DEEP) = MAC_SUCCESS  and this due to the sleep condition is not ok in function halsleep() in hal_sleep.c.

 

 

Please help me to check this quesiton, any informaiton is appreciated.

 

BR,