SES debug errno_val

[Minseo]

Hi.

I'm debugging using SES right now.

It appears like this on SES, but I don't know what it means.

Help me.

Thank you.

[Karl Ylvisaker]

Hello,

Help me.

I will gladly help you resolve your issue, but you need to provide a whole lot more information about the issue and the behavior you are seeing for me to be able to help you.
Remember that we do not know anything about your project. If you make it easier for us to understand the issue and help you, we will together resolve your issue faster.

Please elaborate on what you are debugging currently. Is your application not behaving as expected? If so, what is it doing, and how does it diverge from your expectations? Which device are you working with, is it a Development kit, or a custom board?
Which SDK version are you working with? Are you working out from an example provided in the SDK, or out of project code provided elsewhere?
Is any of your function calls failing, is any error messages being printed to the logger?

Please make sure to have DEBUG defined in your preprocessor defines, to make the logger print a detailed error message whenever a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.
It should look like the included image:


Please do this, and let me know if any errors are written to your logger.
If no errors are written to your logger, please elaborate thoroughly on the issue you are facing.

Best regards,
Karl

[Minseo]

Thank you for reply

Currently, it is being developed using BLE + LCD + Timer + GPIOTE.

Implement screen touch and slide using GPIOTE & Timer

nRF5_SDK_17.0.0 is used

I think BLE Advertising and IRQ are colliding.

Thank you.

[Karl Ylvisaker]

Minseo said:

Thank you for reply

No problem at all, I am happy to help!

Minseo said:

Currently, it is being developed using BLE + LCD + Timer + GPIOTE.

Implement screen touch and slide using GPIOTE & Timer

nRF5_SDK_17.0.0 is used

Thank you for elaborating, thought I still do not have a clear picture of the issue you are facing / behavior you are seeing. Is the device resetting during operation, or is some of the functionality just not working at all?
If so, which functionality is it that is not working? 

Minseo said:

I think BLE Advertising and IRQ are colliding.

Please be advised that the SoftDevice uses the top two interrupt priority levels in order to meet the timing-critical deadlines of the BLE protocol. This means that the SoftDevice will wrest control of the CPU from your application every time a BLE event is upcoming.
Which IRQ priority levels are you using for your peripherals?
And, why do you suspect that they are colliding? What behavior are you seeing?

I notice that you seem to not make any use of the peripheral drivers provided in the SDK, but rather do every operation yourself at register level. If I could ask, why have you chosen this?

Best regards,
Karl