Hi ,
1.How do I port the NCS V1.8.0 asset_tracker example to NCS V1.9.0
2.The customer code was developed in asset_tracker and failed to port to NCS V1.9.0
Thank you for all your assistance.
Kind regards,
Peter.Min
Hi Kazi Afroza Sultana,
1. Copy the example asset_tracker from SDK NCS v1.8.0 to NCS v1.9.0: NCS \v1.9.0\ NRF \applications\asset_tracker
2. The following error occurs when ses is used to load files: log


error: line 97-161
3. The following error occurs when ses compilation is used: log


error line :266-293
Please provide a plan to migrate routine asset_tracker from NCS V1.8.0 to NCS V1.9.0
Thank you for all your assistance.
Kind regards,
Peter.Min
I had this same problem. I fixed it by merging the new SPM default prj.conf file in nrf/samples/spm/prj.conf with the one in nrf/applications/asset_tracker/child_image/spm/prj.conf.
It looks as though the following section was added, so this is what you need to add to your SPM .conf file in nrf/applications/asset_tracker/child_image/spm/prj.conf.
# RTC1 is configured as Non-Secure by default, hence it cannot be used as # the source for the system clock driver. Use the Cortex-M SYSTICK driver # instead. CONFIG_NRF_RTC_TIMER=n CONFIG_CORTEX_M_SYSTICK=y
I had this same problem. I fixed it by merging the new SPM default prj.conf file in nrf/samples/spm/prj.conf with the one in nrf/applications/asset_tracker/child_image/spm/prj.conf.
It looks as though the following section was added, so this is what you need to add to your SPM .conf file in nrf/applications/asset_tracker/child_image/spm/prj.conf.
# RTC1 is configured as Non-Secure by default, hence it cannot be used as # the source for the system clock driver. Use the Cortex-M SYSTICK driver # instead. CONFIG_NRF_RTC_TIMER=n CONFIG_CORTEX_M_SYSTICK=y