ADVERTISE ISSUE IN DEBUG

RE: ADVERTISE ISSUE IN DEBUG

Karl Ylvisaker — Wed, 04 May 2022 13:35:38 GMT

Actually, could you also confirm if the new board ever has been able to communicate properly with another board / the sniffer?

Reading your initial comment again I get the understanding that the new board advertises properly when it is not in debug mode, is this correct?

Best regards,
Karl

RE: ADVERTISE ISSUE IN DEBUG

Karl Ylvisaker — Wed, 04 May 2022 13:33:38 GMT

Hello Brandon,

[quote user="Brandon_sbz"]Thank you for your reply![/quote]

No problem at all, I am happy to help!

[quote user="Brandon_sbz"]

My nRF52832 is advertising properly (I can see it with the nRF Connect mobile app or with a sniffer), but as soon as I enter in debug mode, I no longer see any advertisements.

I'm sure no reset was triggered because I'm logging a variable which is continuously incremented so my SW seems to be running correctly.

The new board has the internal LDO setup while the other boards have the DC/DC regulator setup. I also added an RF connector on the transmission line just before the matching network components. Those are the only changes I made.

[/quote]

Thank you for the clarifications here, it is very helpful.
We might need to take a look at the changes you made to the circuitry here, in which case you should open a separate private ticket so that you can share the schematics confidentially (unless you are fine with sharing them publicly in this ticket). Would this be fine with you?

I suspect that the change to the hardware has not been successful, so that the radio is no longer able to transmit as it is supposed to, because of it.

Best regards,
Karl

RE: ADVERTISE ISSUE IN DEBUG

Brandon_sbz — Wed, 04 May 2022 06:16:20 GMT

I want to correct myself, I can see advertisement packets with the sniffer in debug mode but the packets are malformed and the CRC is incorrect...

Hope this helps you understand this problem :-)

RE: ADVERTISE ISSUE IN DEBUG

Brandon_sbz — Wed, 04 May 2022 05:39:21 GMT

Hello Karl,

Thank you for your reply!

My nRF52832 is advertising properly (I can see it with the nRF Connect mobile app or with a sniffer), but as soon as I enter in debug mode, I no longer see any advertisements.

I'm sure no reset was triggered because I'm logging a variable which is continuously incremented so my SW seems to be running correctly.

Best regards,

Brandon

RE: ADVERTISE ISSUE IN DEBUG

Karl Ylvisaker — Tue, 03 May 2022 14:55:05 GMT

Hello,

Could you elaborate more on the issue? What behavior are you observing, and how does it differ from what you would have expected?
Does the device suddenly reset itself when advertising begins, or does it seem to be running but you are unable to find the advertisements?
What changes did you make from the last revision of the board until the new revision that does not work, what parts of the circuitry did you change?

Please be as specific as possible, so that we may better understand your issue and help you resolve it.

Best regards,
Karl

RE: ADVERTISE ISSUE IN DEBUG

Brandon_sbz — Mon, 02 May 2022 11:38:34 GMT

Hello all,

I have the same problem... Advertising works properly but when I am in debug mode, advertising stops (I don't use any breakpoints while debugging, just logging some data). This issue only occurs on my new custom board, on 2 other custom board I don't have this problem...

RE: ADVERTISE ISSUE IN DEBUG

Karl Ylvisaker — Mon, 10 Jan 2022 08:18:32 GMT

Hello,

[quote user=""]i am working on nRF52832. everything is working fine . only problem is advertise does not start in debug mode.[/quote]

Are you using breakpoints during your debug session?
Please note that the SoftDevice will assert immediately after a breakpoint has occurred, because it will have missed all its time-critical deadlines while the CPU was halted for the breakpoint. Using breakpoints in combination with the SoftDevice running is therefore not advisable, since you can not resume application execution after a breakpoint has been triggered.

If breakpoints are not what is causing your issue here, please elaborate on the behavior you are seeing, how it fails, and what you are doing to provoke the issue.

Best regards,
Karl