Hi, everyone here. I met with a strange problem, when the random address lilfetime (using the following line: cmd->op.renew_dur = ;) is set to 60000, the external interrupt can not be recognized anymore, and when I change it to be smaller, for example, 15000, everything seems working well. But the doc AN-B-022_DA14580_Resolvable_private_address_guidelines says that it should be as large as 65535. So what's wrong with it ? Why dose it affect the external interrupt ? Thanks.
Device:
Any suggestions ? The result can be reproduced according to what I have posted here.
Hi summer20100514,
You 've noticed this behaviour acting as a peripheral and advertising? And while advertising the da didn't see any interrupts ?
Thanks
Yes, the advertising is normal, but no interrupts. Could your team please look into this ? Thanks.
Hi summer20100514,
I ve just reproduced the scenario with random resolvable address using the template from the sample128_After section 5.4 with no sleep. During advertising i ve issued interrupts from the push button and toggle the led. Seem to work fine. I 've also tried with sleep the same scenario waking up from external interrupt it seemed to be working fine as well with 60000 and with 15000 values in the op.renew_dur.
Thanks MT_dialog
Thanks for your tests. But did you do full modifications to implement the functionality described in doc AN-B-022_DA14580_Resolvable_private_address_guidelines ? Maybe changing the lifetime only won't cause any problem.
更重要的是,我使用一个背包在加速度计e the external interrupt signal. I reproduced the scenario just now, and everything remains to be the same.
Hi summer20100514,
I 've performed all the modifications the document describes acting as a peripheral and while advertising i 've issued interrupts. Can you try to issue some interrupts using a button ? or try to interrupt in lower rates ?
Thanks MT_dialog