cod.m Coordinator - Firmware not working

[UtechtDustin]

At first, thank you very much for your effort @Koenkk.

We randomly saw that your compiled firmware seems working with the cod.m Coordinator as written on the adapter page.

We tried to flash and use it, but we was not able to get it to work.
If we use the recommended webflasher, the XZG frontend shows as firmware revision 1.
We also tried to flash it using the CCTools of XZG, by modifying the manifest file.
Which don't work as the CCTools requires a bin (file size has to be a multiple of 4) instead of a hex file.
If we try to convert your hex files to bin using e.g. hex2bin we was able to flash the firmware using the CCTools, but got the same result with the firmware version 1 (sometimes version 2).

The Firmware itself also seems not working, if we try to use it using the open border router addon of home assistant (as written in your readme) we get timeouts.

s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[11:06:34] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[11:06:35] INFO: Setup OTBR firewall...
[11:06:35] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://end0
tiocmbic: Inappropriate ioctl for device
[NOTE]-ILS-----: Infra link selected: end0
50d.15:15:32.314 [W] P-SpinelDrive-: Wait for response timeout
50d.15:15:34.314 [W] P-SpinelDrive-: Wait for response timeout
50d.15:15:36.316 [W] P-SpinelDrive-: Wait for response timeout
50d.15:15:36.316 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
50d.15:15:38.319 [W] P-SpinelDrive-: Wait for response timeout
[11:06:43] WARNING: otbr-agent exited with code 1 (by signal 0).

Do you have an idea whats wrong ?
Or is the repository and the firmware still WIP ?

Thanks!

[UtechtDustin]

Okay we figured out that the XZG will cut off the firmware version.
Yesterday we compiled it with 2025.7.1 and we got the firmware version 1 in the frontend. Today we did the same with 2025.7.2 and got 2.
So it seems the firmware is flashed successfully but don't work because of the response timeouts.

[Koenkk]

I'm not sure why the firmware doesn't work on the CC2652P7 (I also did not test it myself on this device).

Can you check if the CC2652P2 firmware from https://github.com/Koenkk/OpenThread-TexasInstruments-firmware/releases/tag/2025.3.1 works?

(to give some context, this firmware was provided as a PoC to use with https://github.com/Nerivec/zigbee-on-host so not well tested/maintained atm)

[UtechtDustin]

There is no CC2652P2 Firmware, do you maybe mean CC1352P2_CC2652P_launchpad_ot_rcp_2025_3_1 or CC1352P2_CC2652P_other_ot_rcp_2025_3_1.zip ?
We tested the CC1352P7_ot_rcp_2025_3_1 and CC2652R7_ot_rcp_2025_3_1 firmware.

Is there a way to be sure that the firmware works or is correctly flashed ?
Right now we only see the firmware version and have no other point to check if it is flashed correctly.

[Koenkk]

yes one of those (try both), in the mail you send me you also mentioned you tested with a cc2652p2. Would be good to see if this is specific to the p7

[UtechtDustin]

I was able to flash both firmware to the CC2652P2 but i still the the timeout.
So it seems it's an issue of the firmware or the way we flash the firmware, but we are able to flash the XZG on the same way (J-Link or flashing using the Webinterface).

Any Ideas how we could debug that issue ?

[Koenkk]

That firmware definitely worked on my launchpad, @xyrzoe are any special changes required to make it work with the xzg firmware?

[UtechtDustin]

Is there an debug mode or something like that to check if the communication works as expected ?
How do you flashed the firmware to the launchpad ?

[Koenkk]

Is there an debug mode or something like that to check if the communication works as expected ?

I'm not sure, I just tested using the openthread addon and zigbee-on-host driver

How do you flashed the firmware to the launchpad ?

Using Uniflash, but I also tested it on a CC2652RB which I flashed through the smlight webflasher.

[UtechtDustin]

We tested some more stuff and got the CC1352P7_ot_rcp firmware to work on our pi module using Uniflash.
On the Coordinator the open border router addon also starts, but we get some errors.
We will check that, but thanks for the hint with Uniflash.

00:01:56.699 [W] P-HdlcIntface-: Error decoding hdlc frame: Parse
00:01:56.856 [W] P-HdlcIntface-: Error decoding hdlc frame: Parse
00:01:57.135 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:648, chksum:ad50, ecn:no, sec:yes, error:ReassemblyTimeout, prio:normal, rss:-45.0, radio:15.4
00:01:57.135 [N] MeshForwarder-:     src:[fda2:381:33b7:c510:e2b:1e92:960a:167a]:49159
00:01:57.135 [N] MeshForwarder-:     dst:[fda2:381:33b7:c510:69ca:494b:e97e:a25a]:53536
00:01:57.520 [N] RouterTable---: Allocate router id 33
00:01:59.140 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:648, chksum:ceee, ecn:no, sec:yes, error:ReassemblyTimeout, prio:normal, rss:-44.0, radio:15.4
00:01:59.140 [N] MeshForwarder-:     src:[fda2:381:33b7:c510:e2b:1e92:960a:167a]:49159
00:01:59.140 [N] MeshForwarder-:     dst:[fda2:381:33b7:c510:69ca:494b:e97e:a25a]:53536
00:02:00.258 [W] P-HdlcIntface-: Error decoding hdlc frame: Parse
00:02:03.144 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:648, chksum:542a, ecn:no, sec:yes, error:ReassemblyTimeout, prio:normal, rss:-44.125, radio:15.4
00:02:03.144 [N] MeshForwarder-:     src:[fda2:381:33b7:c510:e2b:1e92:960a:167a]:49159
00:02:03.144 [N] MeshForwarder-:     dst:[fda2:381:33b7:c510:69ca:494b:e97e:a25a]:53536
00:02:08.149 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:648, chksum:bd05, ecn:no, sec:yes, error:ReassemblyTimeout, prio:normal, rss:-44.125, radio:15.4
00:02:08.149 [N] MeshForwarder-:     src:[fda2:381:33b7:c510:e2b:1e92:960a:167a]:49159
00:02:08.149 [N] MeshForwarder-:     dst:[fda2:381:33b7:c510:69ca:494b:e97e:a25a]:53536
00:02:08.613 [W] P-HdlcIntface-: Error decoding hdlc frame: Parse
00:02:14.654 [W] P-HdlcIntface-: Error decoding hdlc frame: Parse
00:02:14.654 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:48, src:0x8400, dst:0x5400, sec:yes, tag:14880, offset:600, dglen:648
00:02:17.144 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:648, chksum:48db, ecn:no, sec:yes, error:ReassemblyTimeout, prio:normal, rss:-44.0, radio:15.4
00:02:17.144 [N] MeshForwarder-:     src:[fda2:381:33b7:c510:e2b:1e92:960a:167a]:49159
00:02:17.144 [N] MeshForwarder-:     dst:[fda2:381:33b7:c510:69ca:494b:e97e:a25a]:53536
00:02:33.142 [N] MeshForwarder-: Dropping (reassembly queue) IPv6 UDP msg, len:648, chksum:5093, ecn:no, sec:yes, error:ReassemblyTimeout, prio:normal, rss:-43.125, radio:15.4
00:02:33.142 [N] MeshForwarder-:     src:[fda2:381:33b7:c510:e2b:1e92:960a:167a]:49159
00:02:33.142 [N] MeshForwarder-:     dst:[fda2:381:33b7:c510:69ca:494b:e97e:a25a]:53536
00:02:34.434 [W] P-HdlcIntface-: Error decoding hdlc frame: Parse