Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

zpm1066 — Wed, 20 Mar 2024 12:09:26 GMT

Hi Sigurd,

I wasn’t aware that sysbuild feature is incomplete.

What currently works from the command line is impressive. It’ll be a great feature to look forward to,

I think we can close this ticket on non-secure builds for Thingy:53.

Thank you so much for your assistance. it’s much appreciated.

Regards,
Ravi

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

Sigurd Hellesvik — Wed, 20 Mar 2024 07:59:14 GMT

[quote user="zpm1066"]However, in NCS VSCode’s build configuration, after enabling sysbuild, I got build errors. Is there something additional that needs to be configured NCS VSCode for sysbuild?[/quote]

I would not recommend that you use sysbuild yet, as it is not finished.
We are working on getting a warning saying so somewhere.

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

zpm1066 — Tue, 19 Mar 2024 17:41:35 GMT

Hi Sigurd,

Thanks for the Kconfig suggestions.

Success! I'm able to build and run successfully thingy53_cpuapp_ns target.

I reviewed the BME68X_IAQ Kconfig dependencies in the nRF Config GUI and fixed SETTINGS & SETTINGS_NONE configuration.

However, I haven’t been able to get rid of the LOG_DEFAULT_LEVEL, MCUBOOT_LOG_LEVEL_INF, and LOG_MODE_MINMAL warnings. These appear to be overridden in MCUBoot.

I noticed that the sample peripheral_lbs throws up the same warnings.

I also tried a sysbuild from within NCS VSCode and from the terminal. After running “west build.sysbuild True”, I was able to successfully build and run sysbuild targets.

However, in NCS VSCode’s build configuration, after enabling sysbuild, I got build errors. Is there something additional that needs to be configured NCS VSCode for sysbuild?

Thank you,
Ravi

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

Sigurd Hellesvik — Tue, 19 Mar 2024 08:30:11 GMT

Good job on the porting. It is indeed good news that you are getting further here!

I see you got some Override Kconfig warnings in the _ns build. This often cause the "missing dts" error type that you see.

I like to use "west build -t menuconfig" or the Kconfig action in the VS Code extension to debug this. Then you can browse configurations and more importantly: The values of their dependencies.

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

zpm1066 — Mon, 18 Mar 2024 16:46:02 GMT

Hi Siguard,

I've updated most of my Thingy53 apps to NCS 2.6.0.

I did have a few minor issues with LVGL, Zephyr 3.5.x eliminated CONFIG_LV_Z_MEM_POOL_NUMBER_BLOCKS and replaced it by CONFIG_LV_Z_MEM_POOL_SIZE.

Otherwise, Thingy53 sensor hub thingy53_nrf5340_cpuapp target runs fine once I installed the Bosch BME68X IAQ driver (BSEC2) for NCS 2.6.0.

NCS 2.6.0 build for the thingy53_nrf5340_cpuapp_ns target is still an issue.

On the plus side, thingy53_nrf5340_cpuapp_ns build for the sample peripheral_lbs works now.

It looks like I'm getting much closer to a successful build for the sensor hub for thingy53_nrf5340_cpuapp_ns build. I'm getting a linker error.

Here's the error for thingy53_nrf5340_cpuapp_ns, also output for the successful thingy53_nrf5340_cpuapp build, and the main.c for sensor hub.

There's a Linker error in main.c (line 337) but I don't see anything wrong.

Do you mind taking a quick look?

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

Sigurd Hellesvik — Fri, 15 Mar 2024 12:09:49 GMT

I just answered the other ticket and I do have cause to beleive that this is fixed in v2.6.0

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

zpm1066 — Fri, 15 Mar 2024 12:01:58 GMT

Hello Sigurd,

Thank you for the ongoing investigation.

I’ll review the nRF5340 TF-M and MCUboot issue that you’ve linked, although it’s for the nRF5340DK. It may well be the same issue as the Thingy:53.

NCS 2.6.0 got released today, so will check it out later to see if any fix in it resolved Thingy:53 TF-M issues.

have a great weekend!

Regards,
Ravi

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

Sigurd Hellesvik — Fri, 15 Mar 2024 08:45:31 GMT

[quote user="zpm1066"]fyi - I've opened an issue for @nordic-tiago on his sensor hub GitHub.[/quote]

Good to know, thanks!

[quote user="zpm1066"]btw - Thank you for yesterday's DFU/FOTA Webinar. [/quote]

Hope it was helpful!

[quote user="zpm1066"]With the j-link connected, I don't get any output at all. It was the same when I first reported the issues over 4 months ago.[/quote]

I have another issue with TF-M and MCUboot for the nRF5340 simultaneous multi-image update now, which I guess would be the same as this issue.

I will continue to work on this over at nRF5340 DFU both cores with external flash , so keep an eye on that one.

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

zpm1066 — Thu, 14 Mar 2024 15:42:12 GMT

HI Siguard,

fyi - I've opened an issue for @nordic-tiago on his sensor hub GitHub.

btw - Thank you for yesterday's DFU/FOTA Webinar.

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

zpm1066 — Wed, 13 Mar 2024 13:20:15 GMT

Hi Sigurd,

Thank you.

With the j-link connected, I don't get any output at all. It was the same when I first reported the issues over 4 months ago.

Please see my support ticket https://devzone.nordicsemi.com/f/nordic-q-a/105483/thingy53-flashed-nrf-connect-sdk-for-vs-code-applications-don-t-execute-successfully.

Susheel mentioned that there is an internal ticket number NCSDK-24834 for this bug.

I haven't been able to successfully run any nrf5340dk_nrf5340_cpuapp_ns targets since NCS 2.3.

I hope we'll see a resolution soon.

Regards,
Ravi

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

Sigurd Hellesvik — Wed, 13 Mar 2024 12:33:54 GMT

Which build error do you get?

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

zpm1066 — Tue, 12 Mar 2024 18:15:21 GMT

Hi Sigurd,

I wasn't able to build and run successfully the Thingy52 sensor hub for NCS 2.4.0 but after a minor change I got to build thingy53_nrf5340_cpuapp and run it successfully.

However, using NCS 2.5.2, thingy53_nrf5340_cpuapp_ns builds fine but fails to run successfully.

It's only with NCS 2.3.0 that I'm able to build & run a thingy53_nrf5340_cpuapp_ns successfully. It appears that thingy53_nrf5340_cpuapp_ns builds are "broken" since NCS 2.3.0.

I'd appreciate if you could review and suggest what I may be missing to get the thingy53_nrf5340_cpuapp_ns build to run successfully with NCS 2.5.2?

Thank you.

RE: Thingy:53 sensor data using Bluetooth LE doesn't run successfully for thingy53_nrf5340_cpuapp_ns with NCS 2.5.2

Sigurd Hellesvik — Mon, 11 Mar 2024 15:31:54 GMT

Hi,

That blog is updated for v2.4.0, but has not yet been updated for v2.5.2.

Thanks for reporting the issue.

Do I understand correctly that you have been able to resolve this on your end?

Regards,
Sigurd Hellesvik