Unable to get Matter sample running on the Adafruit Feather nRF52840 Express

Hello.

I've recently been trying to get my Matter application to run on an Adafruit Feather nRF52840 Express. I'm having trouble getting the application to fully run as it seems to get part way through the initialization stage and then completely stops. These are the logs I'ms seeing:

I: Init CHIP stack
I: 217 [DL]BLE address: D6:54:7C:C3:98:7E
I: 224 [DL]OpenThread started: OK
I: 224 [DL]Setting OpenThread device type to MINIMAL END DEVICE
I: 224 [SVR]Subscription persistence not supported
I: 224 [SVR]Server initializing...
I: 225 [TS]Last Known Good Time: 2023-08-16T11:10:45
I: 226 [DMG]AccessControl: initializing
I: 226 [DMG]Examples::AccessControlDelegate::Init
I: 226 [DMG]AccessControl: setting
I: 226 [DMG]DefaultAclStorage: initializing
I: 227 [DMG]DefaultAclStorage: 0 entries loaded
D: 227 [IN]UDP::Init bind&listen port=5540
E: 227 [IN]SO_REUSEPORT failed: 109
D: 228 [IN]UDP::Init bound to port=5540
D: 228 [IN]BLEBase::Init - setting/overriding transport
D: 228 [IN]TransportMgr initialized
D: 231 [DL]Using Thread extended MAC for hostname.
I: 233 [ZCL]Using ZAP configuration...
I: 235 [DMG]AccessControlCluster: initializing
D: 235 [DL]Boot reason: 1
I: 236 [ZCL]Initiating Admin Commissioning cluster.
D: 237 [IN]SecureSession[0x20002b50I: 30255 [DL]CHIPoBLE advertising mode changed to slow
I: 30257 [DL]CHIPoBLE advertising started

My same code running on the nRF52840DK outputs this:

uart*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
:~$ I: Init CHIP stack
I: 216 [DL]BLE address: E9:F0:21:1F:69:D9
I: 226 [DL]OpenThread started: OK
I: 229 [DL]Setting OpenThread device type to MINIMAL END DEVICE
I: 235 [SVR]Subscription persistence not supported
I: 240 [SVR]Server initializing...
I: 243 [TS]Last Known Good Time: 2023-08-16T11:06:30
I: 248 [DMG]AccessControl: initializing
I: 252 [DMG]Examples::AccessControlDelegate::Init
I: 256 [DMG]AccessControl: setting
I: 260 [DMG]DefaultAclStorage: initializing
I: 264 [DMG]DefaultAclStorage: 0 entries loaded
D: 268 [IN]UDP::Init bind&listen port=5540
E: 272 [IN]SO_REUSEPORT failed: 109
D: 275 [IN]UDP::Init bound to port=5540
D: 279 [IN]BLEBase::Init - setting/overriding transport
D: 284 [IN]TransportMgr initialized
D: 290 [DL]Using Thread extended MAC for hostname.
I: 296 [ZCL]Using ZAP configuration...
I: 301 [DMG]AccessControlCluster: initializing
D: 306 [DL]Boot reason: 1
I: 308 [ZCL]Initiating Admin Commissioning cluster.
D: 314 [IN]SecureSession[0x20003388]: Allocated Type:1 LSID:8331
D: 320 [DL]CHIPoBLE advertising set to on
I: 324 [DIS]Updating services using commissioning mode 1
E: 329 [DIS]Failed to remove advertised services: 3
D: 334 [DL]Using Thread extended MAC for hostname.
I: 339 [DIS]Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1
E: 347 [DIS]Failed to advertise commissionable node: 3
E: 352 [DIS]Failed to finalize service update: 3
I: 357 [DIS]Updating services using commissioning mode 1
E: 362 [DIS]Failed to remove advertised services: 3
D: 367 [DL]Using Thread extended MAC for hostname.
I: 371 [DIS]Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=1
E: 380 [DIS]Failed to advertise commissionable node: 3
E: 385 [DIS]Failed to finalize service update: 3
I: 390 [DIS]Delaying proxy of operational discovery: missing delegate
I: 396 [IN]CASE Server enabling CASE session setups
D: 401 [IN]SecureSession[0x20003440]: Allocated Type:2 LSID:8332
I: 407 [SVR]Joining Multicast groups
I: 410 [SVR]Server Listening...
I: 413 [DL]Device Configuration:
I: 416 [DL]  Serial Number: 11223344556677889900
I: 421 [DL]  Vendor Id: 65521 (0xFFF1)
I: 424 [DL]  Product Id: 32768 (0x8000)
I: 428 [DL]  Product Name: not-specified
I: 432 [DL]  Hardware Version: 0
I: 435 [DL]  Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
I: 441 [DL]  Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
I: 447 [DL]  Manufacturing Date: (not set)
I: 451 [DL]  Device Type: 65535 (0xFFFF)
I: 455 [SVR]SetupQRCode: [MT:Y.K9042C00KA0648G00]
I: 460 [SVR]Copy/paste the below URL in a browser to see the QR Code:
I: 466 [SVR]https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3AY.K9042C00KA0648G00
I: 475 [SVR]Manual pairing code: [34970112332]
I: End init CHIP stack
I: [gpio_pin_configure_dt] completed with error code: 0
I: [gpio_pin_interrupt_configure_dt] completed with error code: 0
I: [gpio_init_callback] completed with error code: 0
I: Initialize temp sensor
I: 501 [DL]CHIP task running
I: 505 [DL]CHIPoBLE advertising started

Everything under "End init CHIP stack" is my application specific code making use of an i2c temperature sensor.

I experience similar results when using an unmodified sample. When using the Matter Lock sample I get the expected logs on my nRF52840DK, and I see this when flashing to the Adafruit Feather:

I: Init CHIP stack
I: 220 [DL]BLE address: C6:07:EF:5A:FD:7F
I: 224 [DL]OpenThread SED interval is 1000ms
I: 227 [DL]OpenThread started: OK
I: 227 [DL]Setting OpenThread device type to SLEEPY END DEVICE
I: 227 [SVR]Subscription persistence not supported
I: 228 [SVR]Server initializing...
I: 228 [TS]Last Known Good Time: 2023-08-21T13:25:16
I: 229 [DMG]AccessControl: initializing
I: 229 [DMG]Examples::AccessControlDelegate::Init
I: 230 [DMG]AccessControl: setting
I: 230 [DMG]DefaultAclStorage: initializing
I: 230 [DMG]DefaultAclStorage: 0 entries loaded
D: 230 [IN]UDP::Init bind&listen port=5540
E: 231 [IN]SO_REUSEPORT failed: 109
D: 231 [IN]UDP::Init bound to port=5540
D: 231 [IN]BLEBase::Init - setting/overriding transport
D: 232 [IN]TransportMgr initialized
D: 235 [DL]Using Thread extended MAC for hostname.
I: 237 [ZCL]Using ZAP configuration...
I: 239 [DMG]AccessControlCluster: initializing
D: 239 [DL]Boot reason: 1
I: 239 [ZCL]Initiating Admin Commissioning 

I'm using my DK as the programmer for the Feather, and I have RTT for logging on the feather instead of UART. I also disabled OTA capabilities on the Feather since it doesn't have an onboard flash. If I had to guess, I'd imagine it's a configuration issue, but I'm not sure where to go with my debugging.

Thanks for any suggestions.

Parents
  • Hi,

    I also disabled OTA capabilities on the Feather since it doesn't have an onboard flash.

    Did you do this by selecting prj_no_dfu.conf as configuration file, or did you do it in some other way?

    Does the Adafruit Feather nRF52840 Express have an external 32 KHz xtal? If not, please try adding the following to the project configuration:

    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y

    Can you test if you are able to run OpenThread and Bluetooth LE samples on the Feather?

    Best regards,
    Marte

  • Following up to see if you had any thoughts about what I could try next?

  • Hello,

    Okay, thank you for the suggestion. I am out of town this week, but I will try them and reply to this thread early next week!

    Best,
    Chris

  • Hello,

    Thank you for your patience. I was able to build, flash, and then follow the testing procedures outline in "Testing" in the readme for Bluetooth Peripheral LBS.

  • Hi,

    Thank you for testing. Then the issue is not with Bluetooth in general.

    When you run the Matter application, does the device advertise? You can use the nRF Connect app on your phone to check this. The device should show up as Matter<application>, for example MatterLock or MatterLight.

    If it advertises, you can try to commission it with the commissioner you are using. For the chip-tool, you can follow this guide: Using CHIP Tool for Matter device testing. As long as you have not made changes to the factory data, then the setup pin code and discriminator should be the default:

    Setup Pin Code: 20202021
    Setup Discriminator: 3840 (0xF00)

    If you are using commercial ecosystems (Google Home, Apple Home, etc.) and you need a QR code for commissioning, then you can find the QR code for the default factory data here: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A8IXS142C00KA0648G00.

    Best regards,
    Marte

  • I was able to see my application (based on the matter template example) advertise via the nRF Connect app. However, whenever I ran any of the other examples I didn't see them being advertised (on either the Feather or on the DK, which I thought was odd. In any case, I wasn't able to commission it with the chip-tool, but I was struggling to get that to work with the DK, so I suspect there's something unrelated afoot there. However, when I brought the kit home to attempt provisioning with my commercial ecosystem, it also failed. I've attached the RTT logs output from the Feather below. The "E: 65082 [BLE]ack recv timeout, closing ep 0x2000f3d0" is the culprit, I assume, but I haven't gotten anywhere with my investigation into that.

    I: Init CHIP stack
    I: 221 [DL]BLE address: F7:37:4B:6C:AC:81
    I: 231 [DL]OpenThread ifconfig up and thread start
    I: 233 [DL]OpenThread started: OK
    I: 233 [DL]Setting OpenThread device type to MINIMAL END DEVICE
    I: 234 [SVR]Subscription persistence not supported
    I: 234 [SVR]Server initializing...
    I: 235 [TS]Last Known Good Time: 2023-09-10T12:20:31
    I: 236 [DMG]AccessControl: initializing
    I: 236 [DMG]Examples::AccessControlDelegate::Init
    I: 236 [DMG]AccessControl: setting
    I: 237 [DMG]DefaultAclStorage: initializing
    I: 237 [DMG]DefaultAclStorage: 0 entries loaded
    D: 237 [IN]UDP::Init bind&listen port=5540
    E: 237 [IN]SO_REUSEPORT failed: 109
    D: 238 [IN]UDP::Init bound to port=5540
    D: 238 [IN]BLEBase::Init - setting/overriding transport
    D: 238 [IN]TransportMgr initialized
    D: 275 [DL]Using Thread extended MAC for hostname.
    I: 296 [ZCL]Using ZAP configuration...
    I: 297 [DMG]AccessControlCluster: initializing
    D: 298 [DL]Boot reason: 1
    I: 298 [ZCL]Initiating Admin CommissI: 30323 [DL]CHIPoBLE advertising mode changed to slow
    I: 30325 [DL]CHIPoBLE advertising started
    I: 42080 [DL]BLE connection established (ConnId: 0x00)
    I: 42080 [DL]Current number of connections: 1/1
    I: 42081 [DL]CHIPoBLE advertising stopped
    D: 43039 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 43039 [BLE]local and remote recv window sizes = 5
    I: 43039 [BLE]selected BTP version 4
    I: 43039 [BLE]using BTP fragment sizes rx 244 / tx 244.
    D: 43188 [DL]ConnId: 0x00, New CCCD value: 0x0002
    D: 43189 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
    D: 43189 [IN]BLE EndPoint 0x2000f3d0 Connection Complete
    I: 43190 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 247)
    D: 43249 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 43249 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 43250 [EM]>>> [E:3845r S:0 M:110455211] (U) Msg RX from 0:1125E77A4DA2C9FA [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
    I: 43252 [EM]<<< [E:3845r S:0 M:120801415] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
    I: 43252 [IN](U) Sending msg 120801415 to IP address 'BLE'
    D: 43253 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 140)
    D: 43308 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 43416 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 43417 [EM]>>> [E:3845r S:0 M:110455212] (U) Msg RX from 0:1125E77A4DA2C9FA [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
    I: 45115 [EM]<<< [E:3845r S:0 M:120801416] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
    I: 45115 [IN](U) Sending msg 120801416 to IP address 'BLE'
    D: 45116 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 132)
    E: 45117 [DL]Long dispatch time: 1700 ms, for event type 16388
    D: 45216 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 45217 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 45218 [EM]>>> [E:3845r S:0 M:110455213] (U) Msg RX from 0:1125E77A4DA2C9FA [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
    I: 45219 [EM]<<< [E:3845r S:0 M:120801417] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
    I: 45219 [IN](U) Sending msg 120801417 to IP address 'BLE'
    D: 45220 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 35)
    I: 45221 [SC]SecureSession[0x20002b50]: Moving from state 'kEstablishing' --> 'kActive'
    D: 45222 [IN]SecureSession[0x20002b50]: Activated - Type:1 LSID:34072
    D: 45222 [IN]New secure session activated for device <FFFFFFFB00000000, 0>, LSID:34072 PSID:22844!
    I: 45222 [SVR]Commissioning completed session establishment step
    I: 45223 [DIS]Updating services using commissioning mode 0
    E: 45223 [DIS]Failed to remove advertised services: 3
    D: 45224 [DL]Using Thread extended MAC for hostname.
    I: 45225 [DIS]Advertise commission parameter vendorID=65521 productID=32768 discriminator=3840/15 cm=0
    E: 45225 [DIS]Failed to advertise extended commissionable node: 3
    D: 45225 [DIS]Scheduling extended discovery timeout in 900s
    E: 45226 [DIS]Failed to finalize service update: 3
    D: 45226 [DL]CHIPoBLE advertising set to off
    I: 45226 [SVR]Device completed Rendezvous process
    D: 45336 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 45337 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 45338 [EM]>>> [E:3846r S:34072 M:160347114] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 45339 [IM]Received Read request
    I: 45341 [EM]<<< [E:3846r S:34072 M:171553345] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 45341 [IN](S) Sending msg 171553345 on secure session with LSID: 34072
    D: 45342 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 75)
    D: 45456 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 45457 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 45458 [EM]>>> [E:3847r S:34072 M:160347115] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 45459 [IM]Received Read request
    I: 45461 [EM]<<< [E:3847r S:34072 M:171553346] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 45461 [IN](S) Sending msg 171553346 on secure session with LSID: 34072
    D: 45462 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 97)
    D: 45576 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 45577 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 45578 [EM]>>> [E:3848r S:34072 M:160347116] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 45579 [IM]Received Read request
    I: 45581 [EM]<<< [E:3848r S:34072 M:171553347] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 45581 [IN](S) Sending msg 171553347 on secure session with LSID: 34072
    D: 45582 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 72)
    D: 45696 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 45697 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 45698 [EM]>>> [E:3849r S:34072 M:160347117] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 45699 [IM]Received Read request
    I: 45701 [EM]<<< [E:3849r S:34072 M:171553348] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 45701 [IN](S) Sending msg 171553348 on secure session with LSID: 34072
    D: 45702 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 75)
    D: 45816 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 45817 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 45818 [EM]>>> [E:3850r S:34072 M:160347118] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 45819 [IM]Received Read request
    I: 45821 [EM]<<< [E:3850r S:34072 M:171553349] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 45821 [IN](S) Sending msg 171553349 on secure session with LSID: 34072
    D: 45822 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 97)
    D: 45936 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 45937 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 45938 [EM]>>> [E:3851r S:34072 M:160347119] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 45939 [IM]Received Read request
    I: 45941 [EM]<<< [E:3851r S:34072 M:171553350] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 45941 [IN](S) Sending msg 171553350 on secure session with LSID: 34072
    D: 45942 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 86)
    D: 46056 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46057 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 46058 [EM]>>> [E:3852r S:34072 M:160347120] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 46059 [IM]Received Read request
    I: 46061 [EM]<<< [E:3852r S:34072 M:171553351] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 46061 [IN](S) Sending msg 171553351 on secure session with LSID: 34072
    D: 46062 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 72)
    D: 46176 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46177 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 46178 [EM]>>> [E:3853r S:34072 M:160347121] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
    D: 46179 [IM]Received Read request
    I: 46185 [EM]<<< [E:3853r S:34072 M:171553352] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
    I: 46186 [IN](S) Sending msg 171553352 on secure session with LSID: 34072
    D: 46186 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    D: 46296 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46296 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 21)
    D: 46416 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46417 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 46418 [EM]>>> [E:3854r S:34072 M:160347122] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 46419 [FS]GeneralCommissioning: Received ArmFailSafe (60s)
    I: 46421 [EM]<<< [E:3854r S:34072 M:171553353] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 46421 [IN](S) Sending msg 171553353 on secure session with LSID: 34072
    D: 46422 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
    D: 46536 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46537 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 46538 [EM]>>> [E:3855r S:34072 M:160347123] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 46541 [EM]<<< [E:3855r S:34072 M:171553354] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 46541 [IN](S) Sending msg 171553354 on secure session with LSID: 34072
    D: 46542 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
    D: 46656 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46657 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 46658 [EM]>>> [E:3856r S:34072 M:160347124] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 46659 [ZCL]OpCreds: Certificate Chain request received for PAI
    I: 46663 [EM]<<< [E:3856r S:34072 M:171553355] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 46663 [IN](S) Sending msg 171553355 on secure session with LSID: 34072
    D: 46664 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    D: 46776 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46776 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    D: 46896 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 46896 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 48)
    D: 47016 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 47017 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 47018 [EM]>>> [E:3857r S:34072 M:160347125] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 47019 [ZCL]OpCreds: Certificate Chain request received for DAC
    I: 47023 [EM]<<< [E:3857r S:34072 M:171553356] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 47023 [IN](S) Sending msg 171553356 on secure session with LSID: 34072
    D: 47024 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    D: 47136 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 47136 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    D: 47256 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 47256 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 78)
    D: 47376 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 47377 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 47378 [EM]>>> [E:3858r S:34072 M:160347126] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 47379 [ZCL]OpCreds: Received an AttestationRequest command
    I: 47413 [ZCL]OpCreds: AttestationRequest successful.
    I: 47418 [EM]<<< [E:3858r S:34072 M:171553357] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 47418 [IN](S) Sending msg 171553357 on secure session with LSID: 34072
    D: 47419 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    D: 47496 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 47496 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    D: 47616 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 47616 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 235)
    D: 47736 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 47737 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 47738 [EM]>>> [E:3859r S:34072 M:160347127] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 47739 [FS]GeneralCommissioning: Received ArmFailSafe (60s)
    I: 47741 [EM]<<< [E:3859r S:34072 M:171553358] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 47741 [IN](S) Sending msg 171553358 on secure session with LSID: 34072
    D: 47742 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
    D: 47856 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 49056 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 49058 [EM]>>> [E:3860r S:34072 M:160347128] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 49059 [ZCL]OpCreds: Received a CSRRequest command
    I: 49230 [ZCL]OpCreds: AllocatePendingOperationalKey succeeded
    I: 49265 [ZCL]OpCreds: CSRRequest successful.
    I: 49268 [EM]<<< [E:3860r S:34072 M:171553359] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 49268 [IN](S) Sending msg 171553359 on secure session with LSID: 34072
    D: 49269 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
    E: 49269 [DL]Long dispatch time: 213 ms, for event type 16388
    D: 49356 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 49356 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 138)
    D: 49476 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 49477 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    D: 49596 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 49599 [EM]>>> [E:3861r S:34072 M:160347129] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 49600 [ZCL]OpCreds: Received an AddTrustedRootCertificate command
    I: 49664 [ZCL]OpCreds: AddTrustedRootCertificate successful.
    I: 49666 [EM]<<< [E:3861r S:34072 M:171553360] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 49666 [IN](S) Sending msg 171553360 on secure session with LSID: 34072
    D: 49667 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 68)
    D: 49776 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 49777 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    D: 49897 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 49899 [EM]>>> [E:3862r S:34072 M:160347130] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 49900 [ZCL]OpCreds: Received an AddNOC command
    I: 49903 [FP]Validating NOC chain
    I: 49968 [FP]NOC chain validation successful
    I: 49969 [FP]Added new fabric at index: 0x1
    I: 49969 [FP]Assigned compressed fabric ID: 0x94AA7367DD8CF73F, node ID: 0x000000006D129BFA
    I: 49970 [TS]Last Known Good Time: 2023-09-10T12:20:31
    I: 49970 [TS]New proposed Last Known Good Time: 2023-09-10T17:43:52
    I: 49970 [TS]Updating pending Last Known Good Time to 2023-09-10T17:43:52
    I: 49976 [ZCL]OpCreds: ACL entry created for Fabric index 0x1 CASE Admin Subject 0x000000008E754C34
    D: 49977 [DL]Using Thread extended MAC for hostname.
    I: 49977 [DIS]Advertise operational node 94AA7367DD8CF73F-000000006D129BFA
    I: 49977 [ZCL]OpCreds: successfully created fabric index 0x1 via AddNOC
    I: 49979 [EM]<<< [E:3862r S:34072 M:171553361] (S) Msg TX to 1:FFFFFFFB00000000 [F73F] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 49979 [IN](S) Sending msg 171553361 on secure session with LSID: 34072
    D: 49980 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
    D: 50076 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
    D: 50077 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
    I: 50079 [EM]>>> [E:3863r S:34072 M:160347131] (S) Msg RX from 1:FFFFFFFB00000000 [F73F] --- Type 0001:08 (IM:InvokeCommandRequest)
    I: 50081 [EM]<<< [E:3863r S:34072 M:171553362] (S) Msg TX to 1:FFFFFFFB00000000 [F73F] --- Type 0001:09 (IM:InvokeCommandResponse)
    I: 50081 [IN](S) Sending msg 171553362 on secure session with LSID: 34072
    D: 50082 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 68)
    D: 50196 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x0e)
    I: 50196 [DL]BLE GAP connection terminated (reason 0x13)
    I: 50197 [DL]Current number of connections: 0/1
    E: 65082 [BLE]ack recv timeout, closing ep 0x2000f3d0
    D: 65082 [IN]Clearing BLE pending packets.
    I: 65082 [BLE]Releasing end point's BLE connection back to application.
    I: 65083 [DL]Closing BLE GATT connection (ConnId 00)
    

  • Hi,

    I recommend testing with chip-tool if possible, as then you are able to get logs from the controller as well. A good starting point would be to figure out why you are not able to commission the DK with the chip-tool and to get that working, so we know that the Matter controller works before trying to figure out the issue with the Feather.

    Can you share more about your setup for testing Matter? Are you running the controller and OTBR on different devices, or on the same device? You can find the guide for both here: Matter over Thread: Configuring Border Router and Linux/macOS controller on separate devices and Matter over Thread: Configuring Border Router and controller on one device.
    Are you using Linux or macOS for the chip-tool?

    Best regards,
    Marte

Reply Children
No Data
Related