Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

PSoC™ Creator & Designer Forum Discussions

DaPi_1514011
Level 3
Level 3
First like received

Hi

We've been using CyBle_AesCcmEncrypt and CyBle_AesCcmDecrypt and were getting some random NOMEM global interrupt hangups.

It turns out that you have to check the BLE stack state before calling this function, however the documentation doesn't say this.

So some feedback for users who find themselves in a stack trace containing things like llh_load_encryption_key, wondering how a strh r0,[r1, #0] is causing a memory issue when all parameters are correct and there is sufficient stack and heap available, might find that they need to do something like this:

        while((CyBle_GetBleSsState() != CYBLE_BLESS_STATE_EVENT_CLOSE));

       

        eret = CyBle_AesCcmEncrypt(edActiveKey, edActiveNonce, data, chunksize, out, intmic);

At least, this works for me.

Perhaps Cypress can comment on the recommended way of calling the function or checks to do before executing?

Thanks, Dave

0 Likes
1 Solution
himam_31
Employee
Employee
50 likes received 25 likes received 10 likes received

Hello,

Thank you for your observation and feedback. It is recommended.

Thanks,

Hima

View solution in original post

0 Likes
1 Reply
himam_31
Employee
Employee
50 likes received 25 likes received 10 likes received

Hello,

Thank you for your observation and feedback. It is recommended.

Thanks,

Hima

0 Likes