Asset Tracker v2 SUPL Integration

[ibiglari]

Hi,

This might sound like a silly question, but is there a way to use SUPL library with Asset Tracker v2 with LwM2M integration without having to trade off logging? SUPL library is quite massive and linking against it requires AT client library and logging to be disabled. Even trying to enable LOG_MINIMAL seems not to be sufficient:

.
.
.
[30/30] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       40410 B        48 KB     82.21%
             RAM:       28024 B     211736 B     13.24%
        IDT_LIST:          0 GB         2 KB      0.00%
[425/447] Linking C executable zephyr\zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map 
cmd.exe /C "cd . && C:\ncs\toolchains\v2.2.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe  -gdwarf-4 @CMakeFiles\zephyr_pre0.rsp -o zephyr\zephyr_pre0.elf  && cmd.exe /C "cd /D C:\ncs\v2.2.0\nrf\applications\asset_tracker_v2\build\zephyr && C:\ncs\toolchains\v2.2.0\opt\bin\cmake.exe -E echo ""
c:/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
c:/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: region `FLASH' overflowed by 35440 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'c:\ncs\toolchains\v2.2.0\opt\bin\cmake.EXE' --build 'c:\ncs\v2.2.0\nrf\applications\asset_tracker_v2\build'

Kind Regards,
Iman

[Øyvind]

Hello,

Do you have "debug options" enabled in the board configuration settings?

Will have a look at your issue but will not have an answer before Monday. 

Kind regards,
Øyvind

[Øyvind]

My apologies for the late reply. Will get back to you today. 

Kind regards,
Øyvind

[Øyvind]

Iman, thank you for providing this information. Would if be possible to share your project instead?

Have you considered using nRF Cloud AGPS instead?

Do you have P-GPS enabled as well? This requires a good amount of flash.

Kind regards,
Øyvind

[ibiglari]

Hi,

Thanks for your reply.

I am not using P-GPS.

I thought about using nRF Cloud AGPS, but I'd rather use LwM2M location assistance mechanism if I could implement it in my LwM2M server (which is basically a Leshan server object). This would get rid of the massive SUPL library altogether.

Do you have any documentations (or better yet, a working sample) regarding how to respond to a LwM2M location assistant request?

Also, project folder here. asset_tracker_v2.7z

I have created a few logger macros to replace LOG_XXX so that I could have some sort of logging while using SUPL. You can perform a Find/Replace to revert back to normal logging.

Kind Regards,
Iman

[Øyvind]

Hi Iman, 

ibiglari said:

Do you have any documentations (or better yet, a working sample) regarding how to respond to a LwM2M location assistant request?

Yes, our nRF Cloud documentation shows how to communicate with the nRF Cloud Location services: https://docs.nrfcloud.com/LocationServices/LocationServicesOverview/

Have a look at the LwM2M location services which uses AVsystems.

Kind regards,

Øyvind

[ibiglari]

Hi,

Had a quick look. While it sounds promising, I'm afraid the costs are a setback. Specially since it seems that REST API does not have the same number of free calls per month as MQTT

I might end up implementing SUPL support on my server side instead of the client if SUPL library cannot be somehow shrunk. I opened another ticket for that, but not sure if that is going to be feasible.

In the meantime, were you able to reproduce the issue with the code I attached?

Kind Regards,
Iman

[Øyvind]

ibiglari said:

In the meantime, were you able to reproduce the issue with the code I attached?

No, I am not able to build it on my computer. Still working on it. 

ibiglari said:

Specially since it seems that REST API does not have the same number of free calls per month as MQTT

That sounds a little weird, could you please point to where you found that information? 

Could you provide information on what your needs are and I will discuss with the nRF Cloud team.

[ibiglari]

Hi,

Øyvind said:

That sounds a little weird, could you please point to where you found that information? 

Read that on "Location Services in a cloud-to-cloud setup" page. It says "You must have an nRF Cloud Pro or Enterprise plan."

What I want to achieve at the end of the day is for my hardware on the field to only need to communicate to one entity on the cloud, using one protocol only. That would mean no need for SUPL client library, but that is, at least for now, far from being realised as I am still trying to make heads or tails of Google's SUPL client.

The end-goal for me is to have a single LwM2M server that can reply to A-GPS or P-GPS requests by proxying it to either a SUPL service, or to an A-GPS cloud provider. This way the hardware in the field needs to only know about one server, one set of credentials, and one communication protocol (UDP in this case).

Kind Regards,
Iman

[Øyvind]

Hello Iman, 

Sorry for the late reply. I have forwarded the feedback to our cloud team, and I hope that they can provide some more information to you in regards to the nRF Cloud Location services with cloud-to-cloud. 

If you do want to get more information on this solution I think the best option is to directly contact your local RSM.

ibiglari said:

What I want to achieve at the end of the day is for my hardware on the field to only need to communicate to one entity on the cloud, using one protocol only.

Based on that, the cloud to cloud solution with nRF Cloud Location services sounds like the best solution especially to save flash on the device. 

 Kind regards,

Øyvind