I am attempting to run the Thread topology monitor as per
https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v4.1.0%2Fthread_topology_monitor.html
1) First problem is the above refers to nRF_TTM-win32-x64_v0.13.0 and this is not available on the linked https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Thread-topology-monitor/Download which only wants to offer https://www.nordicsemi.com/-/media/Software-and-other-downloads/Desktop-software/nRF-Thread-topology-monitor/nRFTTMwin32x6401201alpha.zip i.e. 0.12 alpha.
2) Second problem is that attempting to flash
nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\cli\ftd\usb\hex\nrf52840_xxaa_mbr_pca10059.hex
onto a PCA10059 Dongle using nRF Connect / Programmer fails:
2020-05-04T15:01:25.872Z INFO Performing DFU. This may take a few seconds
2020-05-04T15:01:25.891Z INFO DFU procedure starts. This may take a few seconds.
2020-05-04T15:01:43.880Z INFO DFU for Application completed successfully!
2020-05-04T15:01:43.880Z INFO 0 dfu package(s) left.
2020-05-04T15:01:43.880Z INFO Waiting for device
2020-05-04T15:01:48.882Z ERROR Reopen device failed: Timeout while waiting for device F338462931F7 to be attached and enumerated
2020-05-04T15:01:48.882Z INFO Nordic DFU Trigger Interface was not found.Please physically reset device.
2020-05-04T15:01:48.884Z ERROR Device not found due to failure during DFU
Now it does seem to program things despite complaining. If I program the blinky example the LED makes exciting colours. If I put the CLI back you can open the serial port and talk to it. I note that unlike the blinky example the CLI firmware does NOT show a mbr coloured block in the programmer - it shows a solid green application section over both regions.
3)Assuming it's programmed correctly and attempting to use topology monitor 0.12 fails with a timeout:
4)If I find an old dongle that has the CLI programmed from last year all is well - but I've no idea what firmware that is.
Questions:
a)Can you provide a link to the 0.13 topology manager?
b)Is there a problem with the PCA10059 CLI hex file that causes it not to show a bootloader in the programmer?
c)Any other suggestions to make the topology monitor work?