LWM2M Carrier Size Change

RE: LWM2M Carrier Size Change

esisk — Wed, 26 Mar 2025 12:59:40 GMT

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

RE: LWM2M Carrier Size Change

dejans — Wed, 26 Mar 2025 09:53:48 GMT

Hi,

[quote user="esisk"]Would it be ill-advised to reduce the size of CONFIG_LWM2M_CARRIER_WORKQ_STACK_SIZE from 4096 to 2048?[/quote]

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

RE: LWM2M Carrier Size Change

esisk — Tue, 25 Mar 2025 12:10:30 GMT

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

RE: LWM2M Carrier Size Change

dejans — Tue, 25 Mar 2025 08:22:42 GMT

Hi,

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

Best regards,
Dejan

RE: LWM2M Carrier Size Change

esisk — Mon, 24 Mar 2025 12:32:27 GMT

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

RE: LWM2M Carrier Size Change

dejans — Mon, 24 Mar 2025 12:06:33 GMT

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