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.

CC2530: CC2530 Cannot response to the interrupt

Part Number: CC2530
Other Parts Discussed in Thread: Z-STACK

Hi Champs,

My customer is developing based on CC2530, here is the description of his question, could pls help look at it?

He is not using ZIGBEE, and program the project with register.

In the boot loader, code is received via a BIN file, it always called IAP.

After the bootloader skip to APP, in the APP, the key, timer interrupt and other functions are working normally. But the UART interrupt is not working. Could you kindly give your suggestion and what information is needed for debugging?

Regards,

Brian

  • Does your CC2530 enter sleeping mode? The UART interrupt of CC2530 cannot work when device is in sleeping mode.

  • Hi Brian,

    I agree with YK's idea.  Furthermore, is the customer able to send/receive UART bytes outside of the interrupt?  Does the application work as expected without having the bootloader alongside it?  Have they tried using a USART separate from the one needed for the boot loader, or confirmed that the bootload app uninitializes the UART before jumping to the main application?  It would be best to ensure that all USART and pin registers are as expected both before and after the boot loader is used.

    Regards,
    Ryan

  • Customer provided an update offline: Now the question is from bootloader to application,the application's program,like main{} can work normally,but the interrupt still stay in bootloader,Interrupt vector table cannot jump to the application. I just don't know why.I don't use the zigbee. 

    Even if not using Z-Stack, the customer should be referecing Serial Boot Loader for CC2530.pdf and the Z-Stack 3.0.2\Projects\zstack\Utilities\BootLoad\CC2530 project (can be standalone from Zigbee) to best understand intended flash bootloader operation.  Keep in mind that the application project must use a linker command file (*.xcl) with SBL-compatible mapping, as well as invoking specific post-processing tools (follow Section 10 of the PDF).

    Regards,
    Ryan