MPU FAULT occurs when discovering attributes of client

RE: MPU FAULT occurs when discovering attributes of client

Vishnu Vijayan — Wed, 10 Aug 2022 11:25:35 GMT

[quote userid="7377" url="~/f/nordic-q-a/90853/mpu-fault-occurs-when-discovering-attributes-of-client/380990"]Ah, good, I looked at the screenshot to quickly. In that case, try to add CONFIG_BT_RX_STACK_SIZE=2048 (or even higher if needed) to your prj.conf.[/quote]

Ya this Works. Thank you for your immediate response

RE: MPU FAULT occurs when discovering attributes of client

Einar Thorsrud — Wed, 10 Aug 2022 11:16:53 GMT

Hi,

[quote user="Vishnu Vijayan"]before adding the CONFIG_THREAD_NAME=y in prj.conf , the thread name is available in the error code (Current thread:0x20001ae0 (BT RX)) But how can I found out the location of this thread?[/quote]

Ah, good, I looked at the screenshot to quickly. In that case, try to add CONFIG_BT_RX_STACK_SIZE=2048 (or even higher if needed) to your prj.conf.

[quote user="Vishnu Vijayan"]I created a .c file and .h file inside a new folder in the src. I have added all the ble part to this c file and declare functions in .h file.[/quote]

Knowing exactly which changes you made could be relevant, so if the above does not solve it please explain that in detail all the changes/additions you made (for instance by sharing the full project or a diff).

RE: MPU FAULT occurs when discovering attributes of client

Vishnu Vijayan — Wed, 10 Aug 2022 11:06:56 GMT

Hi,

I created a .c file and .h file inside a new folder in the src. I have added all the ble part to this c file and declare functions in .h file.

I created the code based on this reference:https://www.youtube.com/watch?v=ufjv2NaLfN8&t=1638s

before adding the CONFIG_THREAD_NAME=y in prj.conf , the thread name is available in the error code (Current thread:0x20001ae0 (BT RX)) But how can I found out the location of this thread?

RE: MPU FAULT occurs when discovering attributes of client

Einar Thorsrud — Wed, 10 Aug 2022 10:31:38 GMT

Hi,

What changed did you do other than copying out the sample? In any case, MPU fault is typically what you get when there is a stack overflow. I suggest that you set CONFIG_THREAD_NAME=y in your prj.conf as described in this post and test again. What does the full log output say then? Then try increasing the stack size of that thread.