• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 57 subscribers
  • Views 1254 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Startup time required by CC2530ZNP

Daniel Kageff
Prodigy 80 points
Other Parts Discussed in Thread: CC2530EM, CC2531

I am using a CC2530EM loaded with the ZNP executable CC2530ZNP-Pro.hex from ZAP-MSP430-2.5.0 in my product.  The application processor, which is a Renesas V850 MCU, is communicating with it via SPI.  I can successfully communicate with the ZNP, But noticed that after a hardware reset, I have to delay quite a while in order to get a valid SYS_RESET_IND message.  The SRDY signal looks correct relative to the other interface signals.  For the ZNP interface software on the application processor, I ported the code from the ZNP Minikit.

My question is, how long does it take for the CC2530ZNP to respond with a valid SYS_RESET_IND message after a hardware reset?

Thanks

  • 0
    TI__Mastermind 19350 points

    400-600 msec after powerup - most of the time is spent initializing the 12-KB of non-volatile memory. Wakeup from sleep modes is obviously in the hundreds of usecs.

  • 0 in reply to Dirty Harry
    Expert 1240 points

    I am now using CC2531ZNP-Pro-Secure_LinkKeyJoin.hex

    I need to wait for about 1 minute to get Reset Indication and get any response from serial port commands.

    What can I do to reduce that time?

  • 0 in reply to Kyle Zhou
    Guru 735515 points

    CC2531 goes through USB interface and I guess the response time depends on how fast your driver does.

  • 0 in reply to YiKai Chen
    Expert 1240 points

    I don't think it's the driver. I used CC2531 in multiple projects which have the same driver and no delay issues at all.

    It must be the ZNP. I read some older post regarding the serial boot loader and sending the magic '0x07' byte, but it does not work for me.

    Need to dig further.

  • 0 in reply to Kyle Zhou
    Expert 1240 points

    I found the solution.

    The serial boot loader is waiting for 60 seconds before jumping to the ZNP application image, as documented in Serial Boot Loader document.

    Sending a magic byte 0xef can force the sbl to skip the waiting.

    However, the version in Home-1.2.1 changed the magic byte from 0x10 to 0xef, and the document did not update this.

    That's why I could not get it work before.

    Also the response to the magic byte has been changed from 0x00 to SYS_RESET_IND. again no document update.