Hi Dev team,
I was trying to build the mqtt_simple sample in the new NCS v1.5.0 and I am getting a build error.
I tried to build other samples as well but was faced with the same error. I think its related to the FLASH memory partition.
Can you help me out in running the samples of NCS v1.5.0
Regards,
Adeel.
Hi Hakon,
I managed to fix it by using this thread : https://devzone.nordicsemi.com/f/nordic-q-a/72569/sdk-v1-5-0-sample-application-cloud_client-to-large-for-flash
Now the samples are building.
I had 1 more query with respect to migrating the code from NCS v1.3.0 to NCS v1.5.0 :
I had a config in my prj.conf of my code in NCS v1.3.0 : CONFIG_LEGACY_TIMEOUT_API=y
When I migrate my code to NCS v1.5.0, it gives a KConfig error due to this (CONFIG_LEGACY_TIMEOUT_API=y).
I had referred to the below thread as I had faced the same issue as in the below thread.
https://devzone.nordicsemi.com/f/nordic-q-a/66410/nrf9160-date-time-example/271721#271721
CONFIG_LEGACY_TIMEOUT_API=y solved my issue in v1.3.0 but I am unable to use this config in NCS v1.5.0 due to which I get the error :
Is there any alternative that has come up to resolve this issue ?
Regards,
Adeel.
Hi Hakon,
The MQTT sample builds fine. I was trying to build my own sample wherein I encountered this error.
I am using the kernel timers in that along with the date_time library.
This error was generally solved using CONFIG_LEGACY_TIMEOUT_API. Can you let me know what changes can I make in the sys_clock.h file to solve this error .
The Zephyr issue for "CONFIG_LEGACY_TIMEOUT_API" states that : "All kernel timeout usage must use the new-style k_timeout_t type and not the legacy/deprecated millisecond counts." What does this mean ?
Regards,
Adeel.
Hi Hakon,
No worries. I was able to figure it out myself. Thanks for the help 
Regards,
Adeel.
Hi Hakon,
No worries. I was able to figure it out myself. Thanks for the help
Regards,
Adeel.
