ram_report results seem to be inaccurate

RE: ram_report results seem to be inaccurate

SwRa — Thu, 03 Oct 2024 11:06:37 GMT

HI Neal,

Really sorry for the delay.. Is this issue still persistent when using the new nRF Connect SDK v2.7.0 as well.?

Regards,

Swathy

Neal Riedel — Thu, 14 Mar 2024 16:13:14 GMT

Hi Swathy,

I am using v2.4.0 of the nrfConnect library, so the example is in a slightly different place: https://github.com/nrfconnect/sdk-nrf/tree/v2.4-branch/samples/nrf9160/location

I think the sample project is the same, the path to the library was just changed from samples/nrf9160/location to samples/cellular/location.

I built the sample without any overlays:

west build -p -b nrf9160dk_nrf9160_ns

SwRa — Thu, 14 Mar 2024 10:48:39 GMT

Hi Neal,

Could you confirm if this is the sample that you used: https://github.com/nrfconnect/sdk-nrf/tree/main/samples/cellular/location ? How did you build the sample since there are a few overlays in it.?

Regards,

Swathy

Neal Riedel — Fri, 08 Mar 2024 15:39:28 GMT

Hi Swathy,

The sample I used is the 9160 location sample (nrf/samples/nrf9160/location).

Thanks!

Neal

SwRa — Fri, 08 Mar 2024 13:10:19 GMT

Hi Neal,

Could you state which sample you tried here.?

Regards,

Swathy

SwRa — Fri, 08 Mar 2024 12:30:44 GMT

Hi Neal,

Sorry for the delay. This has been reported internally and will be looked at by the R&D.

Regards,

Swathy

Neal Riedel — Tue, 23 Jan 2024 15:24:57 GMT

Hi Swathy,

We have observed this problem on both the nRF9160 and nRF9161. As you noted, for the example I used the nRF9160.

Thanks,

Neal

SwRa — Tue, 23 Jan 2024 11:59:50 GMT

Hi Neal,

This issue is only for the nRF9160 right (quite evident from the build, but just confirming because of the tag for nRF9161).?

Regards,

Swathy