I can see that the Devkit supports SWD access to Ruuvi tags, but I cannot see any other option for programming and debugging Ruuvi tags using SWD. We have extensive experience using Nordic and Segger Dev tools and developing firmware for nRF52x solutions. We would like to develop firmware to support the Ruuvi tags and getting SWD access to do this is critical. OTA firmware updating won’t support the debugging required.
Is there any way to get a Devkit (in the next few weeks) or is there any other way to get SWD access without a dev kit?
You can use linked TagConnect cable https://lab.ruuvi.com/pinout/ + nRF52 DK on RuuviTag B6 and upwards. All RuuviTags shipped since summer are B6 to my best knowledge.
Thanks for the reply. We have an nRF52 DK. So, we use host to DK connection via a standard USB connection and then DK to Ruuvi Tag via “Tag-Connect” cable. Which Tag-Connect cable, the version with legs: http://www.tag-connect.com/TC2030-IDC
Ok, my tag-connect cables and Ruuvi tags have arrived. The tag-connect cable (NL) mates with the Ruuvi tag properly and the clip secures it well. The other end of this cable, however, is an RJ11 connection and will not connect to an nRF52 Dev Kit. How can I adapt the RJ11 to communicate via USB?
The RJ-11 connector sounds like you’d received a wrong part number?
Also the link at lab.ruuvi.com/pinout seems to lead at wrong part number with 6-pin head, and correct one would be http://www.tag-connect.com/TC2030-CTX-NL which has 10-pin connector (@lauri please confirm?)
If the Tag-Connect has delivered wrong part, I’d ask them to change it.
Once when I was on a tight schedule I just cut off a connector of a cable and soldered wires it to the 2.54 mm programming header P20 on DK, with “GND Detect” replaced by GND pin. It has worked well for past 6 months or so.
Yes. I ordered the wrong part, I ordered the TC2030-MCP-NL. I was looking for the TC2030-IDC-NL (from the incorrect web link), so I would have been stuck there as well. Not sure how I selected the wrong item at Mouser :{