CC430F6137: Confusion about how to workaround RF1A5 errata

Jens Sierens

Part Number: CC430F6137

Hello,

I would like to intercept and possibly handle TX FIFO overflow conditions at the interrupt level. I found I could use the RF1AIFG6 radiocore interrupt for that purpose, but the errata noted in the respective erratasheet throws me off a bit at how to conclude whether this condition really occured.

I experienced the problem described, with sending data that was not supposed to trigger this interrupt, or at least not to my knowledge. Could someone explain how to workaround this issue when using this interrupt source.

I figured I could perhaps circumvent this particular interrupt flag all together by using the GDO signal on any of the first 3 interrupts

thanks and kind regards,
Sierens Jens

over 8 years ago

0 Caleb Overbay over 8 years ago

TI__Genius 15370 points

Hi Jens,

When you receive an interrupt you'll need to verify the corresponding RFINx input bit is what you would expect it to be. For example, in this E2E thread once in the interrupt, bowerymarc performs the following check to verify that the RFIFG9 is actually a valid interrupt:

if(RF1AIN & BIT9) // bail if not neg. edge - errata RF1A5
break;

Best regards,
Caleb Overbay

0 Jens Sierens over 8 years ago in reply to Caleb Overbay

Prodigy 50 points

Hello Caleb,

I got the interrupt installed with the way you suggested.

Kind regards

Sub-1 GHz

Sub-1 GHz forum

CC430F6137: Confusion about how to workaround RF1A5 errata