CC2530: the usage of CC2530 system reset API

Part Number: CC2530

Hi ALL：

   how can I kown the system reset source when the cc2530 restarts,for example the normal power on reset or the watch dog timeout reset and so on.

  

Hi Chen:
Thank you for your timely reply!

Which Z-Stack version do you use?

HA1.2.1

I have project based on HA 1.2.1 and use SystemResetSoft which works fine. How do you judge SystemResetSoft doesn't work?

I use the SystemReset API and it can cause the system reset,can you tell me the difference between SystemReset and SystemResetSoft !

Hi Chen:
I am sorry!
I have forgotten I modified the code which is HAL_BOARD_INIT in the hal_board_cfg.h beacause I want to use CC2530 P2.3,P2.4 as general purpose IO
the modified HAL_BOARD_INIT is :
#define HAL_BOARD_INIT() \
{ \
uint16 i; \
SLEEPCMD &= ~OSC_PD; \
while (!(SLEEPSTA & XOSC_STB)); /* wait for 32MHz XOSC stable */\
asm("NOP"); /* chip bug workaround */ \
for (i=0; i<504; i++) asm("NOP"); \
CLKCONCMD = (OSC_32KHZ | OSC); \
CLKCONCMD &= ~OSC; \
while (CLKCONSTA & OSC); \
SLEEPCMD |= OSC_PD; \
/* Turn on cache prefetch mode */ \
PREFETCH_ENABLE(); \
}

however when I modify the HAL_BOARD_INIT as above and then the P2.3,P2.4 can be used as normal but SystemResetSoft API can't cause the system reset,I don't know why is this?

SystemResetSoft just does LJMP to start of program and SystemReset use WATCHDOG to force HW to do reset itself. I don't see your modification to use CC2530 P2.3/P2.4 as GPIO in HAL_BOARD_INIT and I don't think that will make SystemResetSoft doesn't work. Anyway, if you use SystemReset instead of SystemResetSoft, does it work?

Hi chen：
I find out the bit3 and bit4 of SLEEPSTA register that indicate the system reset source can only be read .it may cause a question that the last watchdog timeout reset will cause the next normal power-on operation if only by reading the the bit3 and bit4 of SLEEPSTA register!

Yes, SLEEPSTA is read only register but I couldn’t understand why it has problem when you use it.

Hi darren,

Do you have any updates to provide or is this matter resolved?

Regards,
Ryan