• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 405 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2640 NPI timings required

PhilM5
Intellectual 1680 points
Other Parts Discussed in Thread: CC2640

Hi,

with regards to NPI usage on CC2640 :  http://processors.wiki.ti.com/index.php/Unified_Network_Processor_Interface 

We need :

 Master initiates what are values for :  Delta t3,  Delta t4,  Delta t1,  Delta t2

 Slave initiates what are values for :  Delta t8, Delta t9, Delta t6 Delta t7

Thanks in advance.

Best Regards

  • 0
    TI__Guru 56215 points
    You can use logic analyzer or oscilloscope while running our project to check the time.
  • 0
    TI__Guru 56215 points
    The most important point is that the NPI does not depend on these values.

    MRDY and SRDY are regular GPIOs. On CC26xx it's a function of when the API is called, and the numbers in the data sheet. Our API maps to direct register access via RTOS driver and DriverLib. As it executes from an RTOS task context it is subject to preemption from higher priority tasks, SWI and HWI.

    On any other host it depends on that device' characteristics and API. For example, controlling a GPIO in a Linux system can differ a lot based on how it's implemented. It can range from direct register access to a file handle in user space, with the additional context switch overhead.

    In any case, the point is the protocol does not depend on this. It is regretful that these symbols are there in the diagrams.