MCUXpresso SDKのトピックRe: Matter application (from Project-CHIP) on NXP K32W061

Matter application (from Project-CHIP) on NXP K32W061

kenshin_891991 — Fri, 01 Apr 2022 07:31:10 GMT

Dear NXP TechSupport,

Let me say thank you for your times to get my request for now.

We are creating big project following Matter open source (project-chip/connectedhomeip ) base on Hardware NXP K32W061.

The first of all, we are try to build and run lighting app example on NXP K32W development kit but have been stuck.

Please help to get summarize content as below:

Lighting app demo (BLE - Thread):

a. Topology:

- NXP K32W061 development kit (Lighting app example)

- Raspberry Pi4 (open thread border router)

- USB dongle OM15080 K32W (RCP mode)

- Ubuntu’s PC (Matter controller)

b. Run example

a. Step 1: Commission process:

1. On Matter controller (Ubuntu's PC), runs:

# ./chip-tool pairing ble-thread [NODE-ID] hex:[RAW-DATASET] [setup-pin- code] [discriminator]

In there:
- NODE-ID: you can assign any node id
- RAW-DATASET: you can get from ot-ctl
- setup-pin-code and discriminator: you could look in the Preparing accessory device section

2. On K32W development kit:

- Already plugin expansion board: OM15082

- Push the USERINTERFACE button on the K32W board. This will start the BLE advertising process;

3. Output result

a. Commission process alway show output log on K32W development kit:

....

[4743775][P][DL]BLE is disconnected with device: 0.
[4786235][E][SVR]Commissioning failed with error 32
[4786240][E][SVR]Commissioning failed (attempt 1): Error CHIP:0x00000032
[4786247][D][SC]Assigned local session key ID 2
[4786251][D][SC]Waiting for PBKDF param request
[4786256][D][DIS]DNS-SD StartServer modeHasValue=1 modeValue=1

...

b. But

- K32W has IPv6 address, then verify connection by using IPv6 success (ping command), reduce log are:

...

[60532][E][DL]Long dispatch time: 160 ms, for event type 3
[61993][P][DL]SRP Client was started, detected server: fd85:cce7:fdf5:3fe6:baa0:0524:746d:c313
[62003][D][DL]OpenThread State Changed (Flags: 0x200002a4)
[62008][D][DL] Device Role: CHILD
[62012][D][DL] Partition Id: 0x4FAEEA68
[62016][D][DL]OpenThread State Changed (Flags: 0x00000001)
[62021][D][DL] Thread Unicast Addresses:
[62025][D][DL] FD11:22::CAAA:CB07:C1B4:91EF/64 valid preferred
[62032][D][DL] FD7A:7499:500F:982A:0:FF:FE00:E001/64 valid rloc
[62039][D][DL] FD7A:7499:500F:982A:9664:731C:E28D:47FC/64 valid
[62045][D][DL] FE80::6836:5CA1:8126:C2A0/64 valid preferred
[62052][D][DL]LwIP Thread interface addresses updated
[62057][D][DL] FE80::6836:5CA1:8126:C2A0 IPv6 link-local address, preferred)
[62064][D][DL] FD7A:7499:500F:982A:9664:731C:E28D:47FC Thread mesh-local address)
[62072][D][DL] FD11:22::CAAA:CB07:C1B4:91EF IPv6 unique local address, preferred)

....

- Verify adding node via Openthread web UI and it is created.

b. Step 2: Remote Matter accessory, control on/off demo

1. On Matter controller (Ubuntu's PC), run command:

# $ ./chip-tool onoff on [NODE-ID] 1

in there:

- NODE-ID: is assigned before.

- '1' : endpoint ID

2. Phenomenon:

- On Matter controller: has been time out while sending out request messages.

- On K32W: Did not received any message

- Have you have any experience to bring-up Matter on NXP K32W and knowledge issue, if yes, please share with me ?

I am looking forward to hearing from you soon.

Regards,
Phuong

Re: Matter application (from Project-CHIP) on NXP K32W061

stephanie_m — Wed, 06 Apr 2022 04:10:46 GMT

Hello,

Could you please help us confirm you are already using the latest release available and also you have checked the different guides available in the matter repository ?

Regards

Re: Matter application (from Project-CHIP) on NXP K32W061

kenshin_891991 — Wed, 06 Apr 2022 09:00:56 GMT

Hi estephania_mart,

I would like to confirm that I am using example from https://github.com/project-chip/connectedhomeip

To build the example, I referred from examples_lighting-app_nxp_k32w

The reported result was based on commit number as below (from master branch):

commit 843643c5f0884dcb20dad0b5946cbeccab32dc66 (HEAD -> master) Author: Kamil Kasperczyk <66371704+kkasperczyk-no@users.noreply.github.com> Date: Wed Feb 23 17:38:32 2022 +0100

With latest commit version, I face a building issue:

a. Commit information:

commit d39df2bb3392c042d4c37367ff01585d085045b7 (HEAD -> master, origin/master, origin/HEAD) Author: Yufeng Wang <yufengwang@google.com> Date: Tue Apr 5 23:08:58 2022 -0700

b. Log issue while compiling:

root@0aa642002585:/var/chip/examples/lighting-app/nxp/k32w/k32w0# ninja -C out/debug/ ninja: Entering directory `out/debug/' [896/901] ld ./chip-k32w061-light-example FAILED: chip-k32w061-light-example chip-k32w061-light-example.map arm-none-eabi-g++ -T../../third_party/connectedhomeip/examples/platform/nxp/k32w/k32w0/app/ldscripts/chip-k32w061-linker.ld -Wl,--defsym -Wl,__app_load_address__=0x4000 -Wl,--defsym -Wl,__app_stated_size__=0x99A00 -march=armv7e-m -mcpu=cortex-m4 -mfloat-abi=soft -mthumb -Wl,-O2 -Wl,--gc-sections -Os --specs=nosys.specs --specs=nano.specs -Werror -Wl,--fatal-warnings -fdiagnostics-color -Wl,--wrap=malloc -Wl,--wrap=free -Wl,--wrap=realloc -Wl,--wrap=calloc -Wl,--wrap=MemoryAlloc -Wl,--wrap=_malloc_r -Wl,--wrap=_realloc_r -Wl,--wrap=_free_r -Wl,--wrap=_calloc_r -Wl,-Map,./chip-k32w061-light-example.map -Wl,--gc-sections @./chip-k32w061-light-example.rsp -o ./chip-k32w061-light-example /var/chip/.environment/cipd/packages/arm/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/bin/ld: ./chip-k32w061-light-example section `.text' will not fit in region `Flash640' /var/chip/.environment/cipd/packages/arm/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/bin/ld: region `Flash640' overflowed by 32432 bytes collect2: error: ld returned 1 exit status

Besides the latest commit and above reported commit, with other commit versions, I got a runtime issue on NXP K32W development kit, for example:

a. Commit information:

commit fae3888d4baadd8d3b598e13e6c01b06c0180e97 Author: Song GUO <songguo@google.com> Date: Tue Apr 5 19:41:22 2022 +0800

b. Log on K32W development kit:

[0][OT]Welcome to NXP Lighting Demo App Device_MAC_ID = 0:60:37:ac:81:c7 [521][P][DL]OpenThread started: OK [525][P][DL]Setting OpenThread device type to MINIMAL END DEVICE [532][D][DL]Thread task running [536][D][DL]CHIP task running [539][D][DL]OpenThread State Changed (Flags: 0x00038200) [544][D][DL] Network Name: OpenThread [548][D][DL] PAN Id: 0xFFFF [551][D][DL] Extended PAN Id: 0xDEAD00BEEF00CAFE [556][D][DL] Channel: 11 [558][D][DL] Mesh Prefix: FDDE:AD00:BEEF::/64 [563][P][ZCL]Using ZAP configuration... [567][E][DL]Chip stack locking error at '../../third_party/connectedhomeip/src/app/util/attribute-storage.cpp:551'. Code is unsafe/racy [579][E][-]chipDie chipDie chipDie

Have you implied that K32W development kit is able to run the example from Matter_lighting_example_k32w successfully ?

If yes, could you please share with me commit version and instruction that could help K32W (as a Matter accessory) working well ?

Regards,
Phuong

Re: Matter application (from Project-CHIP) on NXP K32W061

hwkim — Thu, 07 Apr 2022 05:18:07 GMT

We're having the same problem with the latest git connectedhomeip sources(with SDK_2_6_4_K32W061DK6). please help us.