Static Provisioner - ACCESS_STATUS_INSUFFICIENT_RESOURCES

[MSEE]

Hi, 

I have a problem with the BLE mesh light example using the static provisioner. I have modified the example to have multiple Generic OnOff servers. Client and Servers are working using nRF mesh to provision and set up publish/subscribe.

I have modified the configuration steps in the provision code to be able to setup all generic OnOff as i wanted. It have been working to subscribe to the client but when i added a publish configuration step i get an error. I have tried to limit the steps and changed to only publishing from the servers to the client and that is also working.

I'm getting opcode error 5. 

<t:    2212109>, node_setup.c,  289, opcode status field: 5 

Which is

ACCESS_STATUS_INSUFFICIENT_RESOURCES             = 0x05, /**< The node cannot store provided information due to insufficient resources on node. */

I'm having a hard time to debug this i dont understand what the insufficient resources on the node actually means and how to fix it whether it is on the Provision device or Server node?

Thanks,
Michael

[Simonr]

Hi Michael

It seems like the node is out of space (probably in flash). Are you able to find out how much space is left on the node before adding these functions, and compare it to how much flash is on your nodes. You can for example use the nRFConnect for desktop "programmer" app to see how much flash storage is left.

This post describes a "last resort" fix for applications that are "out of" flash storage where you can erase some of the UICR register to free up more of the flash storage, although I wouldn't recommend it if there is anything in your application you can live without.

Best regards,

Simon

[MSEE]

Hi Simon,

Thank you for the fast reply.

I testing with only having added one more Generic OnOff server per server node. The difference between the example and modified example are approximately 728 bytes. There should be around 45 % flash back to play with. 

Tested with the "programmer" app and checked with the Memory Usage from SES. Seems to be correct.

Best regards,
Michael