[Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Question

Hi Nordic Guys,

hope you can help following issue (I think the issue is still mentioned in Ticket https://devzone.nordicsemi.com/f/nordic-q-a/87410/corrupt-matter-zcl-file-generation-matter-template-project, Case ID: 288305).

I try to extend the matter-template example from the nRF SDK. Out off the box the example compiles, build and links The application can be copied to the nRF5340DK board and works.

If I add a new endpoint, like it is described in https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_matter_gs_adding_clusters.html#ug-matter-creating-accessory and let the generator.py script do its work, the result is an unbuild-able application.

See the following build-output:

/Users/bennynestler/workspaces/matter/nRFConnect/matter-template/src/zap-generated/endpoint_config.h:570:3: error: conversion from '<brace-enclosed initializer list>' to 'EmberAfDefaultOrMinMaxAttributeValue' is ambiguous
  570 |   }
      |   ^
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-storage.cpp:102:71: note: in expansion of macro 'GENERATED_ATTRIBUTES'
  102 | constexpr const EmberAfAttributeMetadata generatedAttributes[]      = GENERATED_ATTRIBUTES;
      |                                                                       ^~~~~~~~~~~~~~~~~~~~
In file included from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/af-types.h:58,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/af.h:69,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/common.h:45,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-storage.cpp:42:
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:104:15: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(const EmberAfAttributeMinMaxValue*)'
  104 |     constexpr EmberAfDefaultOrMinMaxAttributeValue(const EmberAfAttributeMinMaxValue * ptr) : ptrToMinMaxValue(ptr) {}
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:103:15: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(uint16_t)'
  103 |     constexpr EmberAfDefaultOrMinMaxAttributeValue(uint16_t val) : defaultValue(val) {}
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:102:15: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(const uint8_t*)'
  102 |     constexpr EmberAfDefaultOrMinMaxAttributeValue(const uint8_t * ptr) : ptrToDefaultValue(ptr) {}
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:100:7: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(const EmberAfDefaultOrMinMaxAttributeValue&)'
  100 | union EmberAfDefaultOrMinMaxAttributeValue
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-metadata.h:100:7: note: candidate: 'constexpr EmberAfDefaultOrMinMaxAttributeValue::EmberAfDefaultOrMinMaxAttributeValue(EmberAfDefaultOrMinMaxAttributeValue&&)'
In file included from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/config.h:83,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/af.h:56,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/common.h:45,
                 from /opt/nordic/ncs/v2.0.2/modules/lib/matter/src/app/util/attribute-storage.cpp:42:

The error repeats several times as result of the inclusion of header files.

Benny Nestler · Accepted Answer

Hi Marte Myrvold 
 I removed my SDK v2.1.0 with the Toolchain Manager (and manually, because the Toolchain Manager times out ("Removing ... ") and moved some files to an new Directory "toBeDeleted"). 
 After the clearing I reinstall the SDK v2.1.0 and rebuild the zap tool with following tweaks: 
 - nvm v0.39.1 
 - node v18.11.0 
 - npm v8.19.2 
 1.) cd to /opt/nordic/ncs/v2.1.0/modules/lib/matter/ 
 2.) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh 
 --> Error occurs due to an openSSL issue 
 
 {
&#160; opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
&#160; library: 'digital envelope routines',
&#160; reason: 'unsupported',
&#160; code: 'ERR_OSSL_EVP_UNSUPPORTED'
} 
 2.1) Fix the error by setting an environment variable 
 export NODE_OPTIONS=--openssl-legacy-provider 
 2.2) (again) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh 
 --> zap tool will be compiled but cannot be started because of the openssl-legacy-provider option (set before in NODE_OPTIONS ) 
 ⇝ electron: --openssl-legacy-provider is not allowed in NODE_OPTIONS 
 2.3) export NODE_OPTIONS= 
 3.) (again) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh 
 --> zap tool is compiled and will be started and crashes because of an (arm64) sqlite3 issue 
 3.1) cd to / opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo 
 3.2) npm uninstall sqlite3 
 3.3) npm install sqlite3 --build-from-source --target_arch=arm64 --fallback-to-build 
 3.4) cd to /opt/nordic/ncs/v2.1.0/modules/lib/matter/ 
 4.) (again) bootstrap the zap tool with ./scripts/tools/zap/run_zaptool.sh 
 bennynestler@MacBook-Pro-von-Benjamin(arm64) /opt/nordic/ncs/v2.1.0/modules/lib/matter % ./scripts/tools/zap/run_zaptool.sh ~/workspaces/matter/nRFConnect/template/src/template.zap
ARGS: -i /Users/bennynestler/workspaces/matter/nRFConnect/template/src/template.zap
&#128640; Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
&#128269; Git commit: a94875d430d199ece002ab5bd971fdb78305fd4e from Fri Aug 12 2022 20:21:11 GMT+0200 (Mitteleurop&#228;ische Sommerzeit)
&#128269; Current src hash: h2euTBRFmUDzrR/ddxfwDvNx4Qk=
&#128269; Current src-shared hash: rF1YqWFjnJ5QZptyJBjTBuZ/z6M=
&#128269; Previous src hash: h2euTBRFmUDzrR/ddxfwDvNx4Qk=
&#128269; Previous src-shared hash: rF1YqWFjnJ5QZptyJBjTBuZ/z6M=
&#128077; There were no changes to front-end code, so we don't have to rebuild the SPA.
&#128640; Executing: npx tsc --build ./tsconfig.json
&#128640; Executing: npx copyfiles -V ./src-electron/**/*.sql ./dist/
unglobed path: ./src-electron/db/zap-schema.sql
copy from: ./src-electron/db/zap-schema.sql
copy to: dist/src-electron/db/zap-schema.sql
&#128640; Executing: npx electron /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/ui/main-ui.js --logToStdout --gen /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/app-templates.json --zcl /opt/nordic/ncs/v2.1.0/modules/lib/matter/src/app/zap-templates/zcl/zcl.json -i /Users/bennynestler/workspaces/matter/nRFConnect/template/src/template.zap
&#128295; Using state directory: ~/.zap
{"level":40,"time":1666253418767,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Check type contradiction in XML metadata for ColorControlOptions with type BITMAP8"}
{"level":40,"time":1666253418768,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Check type contradiction in XML metadata for LevelControlOptions with type BITMAP8"}
{"level":40,"time":1666253418768,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Check type contradiction in XML metadata for BarrierControlBarrierPosition with type INT8U"}
{"level":40,"time":1666253419054,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Attempting to insert cluster extension for a cluster which does not
 exist. Check clusterExtension meta data in xml file.
 Cluster Code: 0"}
{"level":50,"time":1666253419418,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Tray not created, icon does not exist: /opt/nordic/ncs/v2.1.0/modules/lib/matter/third_party/zap/repo/dist/src-electron/icons/zap_32x32.png"}
{"level":30,"time":1666253419610,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Init message received: WebSocket initialized handshake.. Responding."}
{"level":50,"time":1666253419635,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":{}}
{"level":30,"time":1666253420230,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Loading project(template.zap)"}
{"level":30,"time":1666253420274,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Loaded project(template.zap) into database. RESP: {\"sessionId\":1,\"sessionKey\":\"E6YW8pebXJV1ufBKAWS7GMldpwFG8hpa\"}"}
{"level":30,"time":1666253420319,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":"Init message received: WebSocket initialized handshake.. Responding."}
{"level":50,"time":1666253420330,"pid":41112,"hostname":"MacBook-Pro-von-Benjamin.fritz.box","name":"zap","msg":{}} 
 5.) Be happy about a working zap - tool

[Matter] Changing or adding Endpoints/Clusters to Matter-Template example with the zap tool leads to compiling errors

Top Replies