Thngy53 matter weather station app, build error.

RE: Thngy53 matter weather station app, build error.

Maria Gilje — Tue, 01 Nov 2022 14:52:09 GMT

Hello,

[quote user="brando14"]I am trying to use the chip tool via android, the documentation tells me that for this app the nrf tag is used as a way to commission the device,[/quote]

Yes, commissioning with NFC is the default setting, and is active when starting the application. Pressing the central button (SW3) will turn on the Bluetooth LE advertising. This is documented in the User Interface section of the application documentation. The wording is as follows:

If pressed for less than 3 seconds, it starts the NFC tag emulation, enables Bluetooth LE advertising for the predefined period of time (15 minutes by default), and makes the device discoverable over Bluetooth LE.

Did you touch your phone to the NFC tag before or after enabling the Bluetooth LE advertising?
Also make sure that your mobile device is connected to a WiFi access point which is connected to the Thread border router.

Unfortunately, I do not have all of the required hardware to be able to test the application myself. I hope some of this is helpful.

Kind Regards,
Maria

RE: Thngy53 matter weather station app, build error.

brando14 — Fri, 28 Oct 2022 12:42:28 GMT

ok, maria thanks for the help

RE: Thngy53 matter weather station app, build error.

Maria Gilje — Thu, 27 Oct 2022 12:47:55 GMT

Hello,

I am still looking into this. Thank you for your patience.

Kind Regards,
Maria

RE: Thngy53 matter weather station app, build error.

brando14 — Mon, 24 Oct 2022 14:17:36 GMT

i receive this logs via serial:

1:01:39.198,028] <dbg> chip: [DMG]Endpoint 2, Cluster 0x0000_0405 update versi on to 8b35a2fb
[01:01:39.199,981] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update versi on to 73a7196a
[01:01:39.200,164] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update versi on to 73a7196b
[01:01:39.200,347] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update versi on to 73a7196c
[01:01:39.200,531] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update versi on to 73a7196d
[01:01:39.200,683] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update versi on to 73a7196e
[01:01:39.200,866] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update versi on to 73a7196f
[01:01:39.201,049] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update versi on to 73a71970
[01:01:42.197,662] <dbg> chip: [DMG]Endpoint 1, Cluster 0x0000_0402 update version to 137d3293
[01:01:42.197,814] <dbg> chip: [DMG]Endpoint 3, Cluster 0x0000_0403 update version to d1200e80
[01:01:42.198,028] <dbg> chip: [DMG]Endpoint 2, Cluster 0x0000_0405 update version to 8b35a2fc
[01:01:42.200,012] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71971
[01:01:42.200,195] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71972
[01:01:42.200,347] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71973
[01:01:42.200,531] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71974
[01:01:42.200,714] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71975
[01:01:42.200,897] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71976
[01:01:42.201,080] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71977
[01:01:45.197,662] <dbg> chip: [DMG]Endpoint 1, Cluster 0x0000_0402 update version to 137d3294
[01:01:45.197,814] <dbg> chip: [DMG]Endpoint 3, Cluster 0x0000_0403 update version to d1200e81
[01:01:45.198,028] <dbg> chip: [DMG]Endpoint 2, Cluster 0x0000_0405 update version to 8b35a2fd
[01:01:45.200,012] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71978
[01:01:45.200,195] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a71979
[01:01:45.200,347] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a7197a
[01:01:45.200,531] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a7197b
[01:01:45.200,714] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a7197c
[01:01:45.200,866] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a7197d
[01:01:45.201,080] <dbg> chip: [DMG]Endpoint 0, Cluster 0x0000_002F update version to 73a7197e

RE: Thngy53 matter weather station app, build error.

brando14 — Mon, 24 Oct 2022 14:13:26 GMT

hanks for the help maria, try to pass the app to the thingy and the flash was done correctly, now I am currently facing the following problem:

I am trying to use the chip tool via android, the documentation tells me that for this app the nrf tag is used as a way to commission the device, I saw a video of the nordic webinar, where they show how to make that connection that is just bringing the phone to the antenna of the thingy and wait for the pairing to start.

However, I can't get that process to start, according to the documentation, when the app is transferred to the nordic it activates the viable provisioning for 15 min, so in that period of time it should be able to do it.

when i use the nrf tool i am able to see the device so the ble is active, i can also see it via bluetooth. What can this be due to?

RE: Thngy53 matter weather station app, build error.

Maria Gilje — Thu, 20 Oct 2022 11:39:32 GMT

Hello,

Great that you were able to build the application.

The application can be flashed to and run on your Thingy:53. You just won't be able to debug the application with debugging software. Logging is still available if you have it enabled in the prj.conf of the application.

My suspicion in my previous reply has been confirmed. The application was too big for the Thingy:53 when the debug options were enabled. The Matter applications and samples are in general quite large, needing most of the available flash on the device. If you want to make your application smaller you can take a look at the Memory footprint optimization for Matter.

Building the application with prj_release.conf instead of prj.conf will also make it possible to build with debug options enabled. So depending on your preferences you may consider that option if you want to debug with debugging software. Note that the Thingy:53 does not have an onboard debugger, and you would need an external debug probe to debug the flashed application with for example an nRF5340 DK.

Kind Regards,
Maria

RE: Thngy53 matter weather station app, build error.

brando14 — Wed, 19 Oct 2022 14:53:48 GMT

ok, thanks for the reply, I tried to do the built without debug option and works. should i try to pass the code to thingy or it's better wait for your reply?

RE: Thngy53 matter weather station app, build error.

Maria Gilje — Mon, 17 Oct 2022 12:22:42 GMT

Hello,

[quote user="brando14"] When I begin to build the app, I use this configuration:[/quote]

I was able to reproduce your error with this configuration. When I built the application earlier, I did not enable the debug options. I have not confirmed the source of the error, but I am working on it

<ncs-installation>/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr\zephyr_pre0.elf section `text' will not fit in region `FLASH'
<ncs-installation>/toolchains/v2.1.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: region `FLASH' overflowed by 18048 bytes

Take note that two of the errors are referencing that the FLASH region is to small to contain 'text' and that it results in an overflow. On my setup, this does not happen when I build with debug options disabled. The application should be able to build successfully when you disable the debug options. You can still use the debug configuration file: prj.conf.

My suspicion is that the application is too big with debug options enabled, but I need more time to confirm or refute this.

Kind Regards,

Maria

RE: Thngy53 matter weather station app, build error.

brando14 — Fri, 14 Oct 2022 13:16:34 GMT

Hello, When I begin to build the app, I use this configuration:

When the code finish the build process this messages is appears:

I

RE: Thngy53 matter weather station app, build error.

Maria Gilje — Fri, 14 Oct 2022 07:47:17 GMT

Hello Brando,

The warnings listed in the Problems tab should not stop the application from building.

What is printed to the terminal when you build the application now?

Kind Regards,

Maria

RE: Thngy53 matter weather station app, build error.

brando14 — Thu, 13 Oct 2022 15:41:46 GMT

ok thanks for the help, I tried next:

First:

1) I Removed de NCS v2.1.0 fromo Tool Chain Manager
2) I Deleted all data from ncs folder and reinstall the ncs again. but It doesn't work I still recive the follow errors:

Second:

1) I changed the directory for the install in the Toolchain Manager to a different location. but I receive the same errors.

RE: Thngy53 matter weather station app, build error.

Maria Gilje — Wed, 12 Oct 2022 11:16:51 GMT

Hello again Brando,

I have tried to reproduce your error on my end. I was not able to identically reproduce it, but I did get another error related to CMakeLists when building the Matter Weather Station application from my existing install of nRF Connect SDK (NCS) v2.1.0.

I did some tests on different setups, which resulted in a few configurations where the application was able to build successfully. These configurations were:

installing NCS v2.1.0 on a computer where NCS v2.1.0 had not been installed before
changing the directory for the install in the Toolchain Manager to a different location on my work computer (where I have installed NCS v2.1.0 before)
removing and deleting my installed NCS v2.1.0 in the default location (C:\ncs) and then installing it again with the Toolchain Manager.

I have not come to a conclusion on why the application is not able to build on my install that was not new. I suspect that installing the GN tool manually breaks the automatic install, and I will examine this further.

You are free to test any of the solutions listed above. Follow the detailed description below if you want to use workaround 3.

Take backup of any local changes you have made within NCS and want to keep.
Close any instances of NCS v2.1.0 that are open.
Remove NCS v2.1.0 by selecting "Remove" from the dropdown menu in the Toolchain Manager.
Delete the v2.1.0 folder from C:/ncs/
Delete the v2.1.0 folder from C:/ncs/toolchains/
Install NCS again from the Toolchain Manager.

Let me know if your building problems are still not solved.

Kind Regards,

Maria

RE: Thngy53 matter weather station app, build error.

brando14 — Tue, 11 Oct 2022 13:55:33 GMT

thanks maría I'll be waiting, i try to use with two versions of sdk, the 2.0 and 2.1, so i find this new errors, in addition to the aforementioned.

RE: Thngy53 matter weather station app, build error.

Maria Gilje — Tue, 11 Oct 2022 13:47:30 GMT

Hello Brando,

I am looking into this and will get back to you shortly. Thank you for your patience.

Kind Regards,

Maria