Thread Topology Monitor new version unavailable and old version incompatible with latestSDK

RE: Thread Topology Monitor new version unavailable and old version incompatible with latestSDK

Edvin — Wed, 06 May 2020 08:00:58 GMT

FYI:

The 0.13.0 version is available now, and the .hex file that you flash to use this tool is located in the hex folder inside the zip folder. So use this, and not the cli example from the SDK.

BR,

Edvin

RE: Thread Topology Monitor new version unavailable and old version incompatible with latestSDK

Edvin — Tue, 05 May 2020 15:00:14 GMT

Hello,

I have not been able to test the 0.13+4.1.0 yet, as the release of 0.13 is on an internal server, which I can't access from the home office. However, if 0.12 works, I would suggest that you just use this for now. I can't imagine that there are any significant changes in the TTM. I suspect that they only updated to 0.13 because of some changes in the example on the cli example.

RE: Thread Topology Monitor new version unavailable and old version incompatible with latestSDK

Eddyl — Tue, 05 May 2020 13:48:57 GMT

Ok so in terms of what works with what:
nrf_TTM v0.12 + SDK 4.0.0 Works

nrf_TTM v0.13 + SDK 4.1.0 can't test as no link download link yet

nrf_TTM v0.12 + SDK 4.1.0 didn't work for me - did you try that combination? If it works it would enable me to move to the later SD

Also re the programmer - I'm happy that it complains because a new serial number has popped up. What's more puzzling is whatever logic nRF Connect Programmer is using to colour-code the memory map into app vs bootloader vs mbr - doesn't spot an MBR section for the pre-supplied hex files. Whereas other examples like blink seem to be detected properly. Is this just a quirk of the programmer?

RE: Thread Topology Monitor new version unavailable and old version incompatible with latestSDK

Edvin — Tue, 05 May 2020 13:41:29 GMT

Hello,

a) The new release was recently published (together with the SDK), in the end of last week. I have reported that the public link is missing. It will probably come soon. However, in the meantime, the old version should work just fine (I downloaded it and tested now together with the .hex file from SDK4.0.0).

b) not valid

c) yes:

You will get the error when you program the dongle with nrf52840_xxaa_mbr_pca10059.hex using the nRF Connect -> Programmer app. The reason for this is because the USB device will get a new serial number, and appear as a new COM port. The error message in nRF Connect is only saying that the current COM port has stopped responding, which is true. But it doesn't detect that a new COM port has appeared.

This is an issue with nRF Connect, and not the dongle. It happens whenever you program either an example that doesn't use the USB peripheral at all, or if it will appear as a new COM port.

So, just program the dongle like you did. When the error message appears, just close the COM port that it was using. Then, open nRF_TTM-win32-x64\nRF_TTM.exe, and select the programmed device from the dropdown menu. If it doesn't appear, try to unplug an replug the dongle. If this doesn't work, please let me know.

BR,

Edvin

RE: Thread Topology Monitor new version unavailable and old version incompatible with latestSDK

Eddyl — Mon, 04 May 2020 15:42:23 GMT

Note: going back to 4.0 SDK the programmer still complains and still doesn't show the MBR in a different colour but the CLI hex file does seem to work with the monitor