• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 17 subscribers
  • Views 1341 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.

TRF7963A: How to solve collision error?

Janet Shen
Expert 7795 points
Part Number: TRF7963A
Other Parts Discussed in Thread: TRF7970A, TRF7960A

Dear Champs,

When customer use TRF7963A running below example but met collision error on IRQ Status Register. (But it's OK on TRF7970A)

Here is error message

Do you have any reminder or suggestion?

Please feel free to let me know if you have any idea.

Thanks a lot.

  • 0
    TI__Guru*** 128115 points

    Hello Janet,

    Did they enable the TRF7960A software modifications via the #define in the trf79xxa.h file? This can be done by changing TRF79xxA_VERSION to be defined at 60 instead of 70.

    I don't see the dummy write after the IRQ status is read to ensure it cleared properly. That seems to be the issue.

    If the #define is set properly, this should be handled as seen in the bold line of this function:

    uint8_t TRF79xxA_readIrqStatus(void)
{
	uint8_t pui8Value[2];

	pui8Value[0] = TRF79XXA_IRQ_STATUS;
#if (TRF79xxA_VERSION == 70)
	SPI_readSingle(pui8Value);
#elif (TRF79xxA_VERSION == 60)
	SPI_readCont(pui8Value,2);		// Dummy read to properly clear IRQ Status for TRF796xA devices (except 64A)
#endif

	return pui8Value[0];
}

  • 0 in reply to Ralph Jacobi
    Intellectual 330 points

    Hi Ralph J.

    We modified the dummy dta  issue but anoother issue as following:

    How to solve this error?

  • 0 in reply to Huang Hong Chun
    TI__Guru*** 128115 points

    Hello Huang,

    My first suspicion is that perhaps the SPI line isn't being handled as outlined in the example firmware.

    See this PowerPoint which describes extra/duplicate bytes occurring: 4807.6355.TRF7960A Extra Bytes on RX.pptx

    Slide 5 describes how the SPI lines should be handled to avoid this issue.

    Please let me know if this is already being accounted for, but if not I suspect that is the root cause.

  • 0 in reply to Ralph Jacobi
    TI__Expert 7795 points
    Dear Ralph,

    Thanks for your help, we have solved this issue and transplant the code successfully from TRF7970A to TRF7963A.
    If it still have other problem, please kindly give us any suggestion.
    Thanks a lot.

    Best regards,
    Janet