• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 41 subscribers
  • Views 1025 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.

CC3100MOD: IRQ high output time from releasing reset becomes 350ms, not 1.35 sec

Hisao Uchikoshi
Genius 13560 points
Part Number: CC3100MOD
Other Parts Discussed in Thread: CC3100

Hello Experts,

 

We sometimes have an experience that IRQ signal outputed from CC3100MOD becomes high in 350ms after nRESET goes to high. We observed that this time is usually 1.35 sec. And not observed on all CC3100MODs.

 

Below is the picture that when IRQ becomes high soon after nRESET goes to high. nHIB is hold to high during reset and power is supplied. 

 

 

 

Since there is no information about the time that IRQ outputs high after reset, could you please investigate if this short time is matter or not.

 

Please note that this post is related to below post to narrow our issue.

 

e2e.ti.com/.../608101

 

Regards,

Uchikoshi

  • 0
    TI__Mastermind 28285 points
    Hisao,

    Is this causing problems in your system? or is this something you have noticed?

    The Radio calibration does not occur after every reset, so T3 time could be much smaller, thus results in IRQ Line going high quickly.

    Let me know if this helps,

    Vince Rodriguez
  • 0 in reply to Vincent Rodriguez
    TI__Genius 13560 points
    Hello Vince,

    Thank you for your answer.
    Actually, we are facing an issue. The following is the sequence after reset.

    1. Assert and dis-assert the reset of CC3100 from host CPU
    2. Host CPU is waiting IRQ becomes high.
    3. Once IRQ is high, host CPU calls sl_starts() that includes assert and dis-assert nHIB and wait IRQ signal becomes high.

    Usually, the time from dis-assert reset to IRQ signal high is around 1.35sec and works fine. For the case issue occurs, the time from dis-assert reset to IRQ signal high is 350ms. In this case, IRQ signal does not output high described in latter in above step 3 thus host program is continuously looping in the _SlDrvSyncObjWaitTimeout() in sl_start().

    This is the background of this question.

    If you notice anything, please let us know.

    Regards,
    Uchikoshi
  • 0 in reply to Hisao Uchikoshi
    TI__Mastermind 28285 points
    Hisao,

    Are you resetting because of an error?

    I would advise if you are resetting to recover from an error, than just assert and de-assert the nHIB pin. It will accomplish the same thing you are looking for.

    Regards,

    Vince Rodriguez
  • 0 in reply to Vincent Rodriguez
    TI__Genius 13560 points
    Vince,

    Reset is used when switching between STA and AP. I also understood that reset is not required for role switch and reset is required only for power-on(POR). As a result, we used reset for role switching and saw this behavior.

    Finally, we can recovery correctly by reset asserting duration longer than 30ms which is defined as 5ms in DS. When asserting reset longer than 30ms, the time from de-asserting reset to IRQ high becomes 1.35 sec and works fine.

    regards,
    Uchikoshi
  • 0 in reply to Hisao Uchikoshi
    TI__Mastermind 28285 points
    Hisao,

    I'm going to close this thread. Please open a new thread if you have any more questions.

    Regards,

    Vince Rodriguez
  • 0 in reply to Vincent Rodriguez
    TI__Genius 13560 points
    Vince,
    Sorry for no update so long time. Please close this thread.
    Regards,
    Uchikoshi