LWM2M Carrier Size Change

[esisk]

Hello, I have an application running on an nRF9160. The current app was built using NCS 1.7.0 with the L2M2M Carrier Library enabled. I'm upgrading the application to use NCS 2.4.2 and now my application's RAM usage is 8k larger than before. I haven't changed anything else about my app except for making the necessary migrations from 1.x.x to 2.x.x. Is it known that the new LWM2M Carrier library is larger than it used to be? Or is there some way I can configure down its size?

[dejans]

Hi,

Increase in the library size of LwM2M carrier library mainly depends on the application in has been integrated into. The size of the library has increased from this size in NCS v1.7.0 to this size in NCS v2.4.2. 

Best regards,
Dejan

[esisk]

Thanks for the references. Would it be ill-advised to reduce the size of CONFIG_LWM2M_CARRIER_WORKQ_STACK_SIZE from 4096 to 2048?

[dejans]

Hi,

Is there anything specific you want to achieve with this stack size reduction?

Best regards,
Dejan

[esisk]

My application already barely fits on the SoC, mainly because it's running the LWM2M carrier binary, the SUPL binary, the BLE Host Stack, and includes the Cryptography library. All of these are pretty sizable. So the motivation to reduce the workqueue stack is to make sure my application still fits in RAM

[dejans]

Hi,

esisk said:

Would it be ill-advised to reduce the size of CONFIG_LWM2M_CARRIER_WORKQ_STACK_SIZE from 4096 to 2048?

You could try to change stack size in your application. It is advisable that you test your application thoroughly after the change. Reducing stack sizes too much might lead to stack overflow errors. 

Best regards,
Dejan

[esisk]

Gotcha, I'll keep it lowered and test it out. I haven't noticed any problems with it yet. Thanks!