CC430F5133: frameInfo_t queue is getting full of frames and now stuck in FI_INUSE_TRANSITION

Omid (TI)

Part Number: CC430F5133
Other Parts Discussed in Thread: SIMPLICITI

Hi Team,

I have a customer with the following issue, can you please take a look and help out when you have a moment.

We are using the CC430 with the SimpliciTI stack. We're running into an issue where the frameInfo_t queue is getting full of frames stuck in FI_INUSE_TRANSITION, and hogging up the queue. We noticed that this only happens when there are two APs, and the second AP is acting as a range extender and repeating frames.

What exactly is the FI_INUSE_TRANSITION state used for in the queue? I couldn't find any solutions in the forum either.

Thanks in advance,
Omid D.

over 6 years ago

0 Andrew Dai28 over 6 years ago

Prodigy 50 points

Thanks Omid!

I've been debugging further, and I see fi_usage gets set to FI_INUSE_TRANSITION every time the nwk_retrieveFrame() grabs the frame via nwk_QfindOldest().

At the end of nwk_retrieveFrame(), fi_usage gets set back to FI_AVAILABLE.

However, I think I am running into an issue where, during the SMPL security check, frames are getting skipped if they are marked as "bogus" and the slot never gets set back to AVAILABLE:

else
{
/* Frame bogus. Check for another frame. */
done = 0;
continue;
}

0 Andrew Dai28 over 6 years ago in reply to Andrew Dai28

Prodigy 50 points

Ah, the issue I pointed out is actually addressed in the latest SimpliciTI stack. It seems like code composer support is only at version 1.1.1, but the IAR version is at 1.2.0. Does anyone know if there is a change log somewhere detailing all the bug fixes and other differences between 1.1.1 and 1.2.0?