TC321x Secure Debug: how to re-enable SWS with the debug key (datasheet 18.4.2)?

TL_SUNPENG

<div class="quote"><blockquote><font size="2"><a href="https://community.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102979&ptid=98922" target="_blank"><font color="#999999">Alex Kafando 发表于 2026-9-28 23:37</font></a></font>  Okay, here is my wirin ...</blockquote></div> The wiring is correct. Could you share your firmware so I can try to reproduce the issue on a development board? That way, the only difference left between our setups would be the DUT hardware. Besides that, does your firmware have any sleep in it? If yes, about how long after starting does it go to sleep? Provided that the SWS pin on the DUT is not shared with any other function and the chip has not entered sleep mode, you may use the programmer below to flash the custom firmware. After the update is finished, perform a power cycle and then click the "Re-enable" button. The procedure for updating the programmer is as follows: click **Help → Upgrade**; click **Load** and select the provided firmware image; then click **Upgrade** to begin the upgrade.   [ProrammerFW202609291043.7z](https://forum.telink-semi.cn/forum.php?mod=attachment&aid=MjQxNHxlYjdiMWVlZHwxNzkwNjUwMzIzfDY2fDA%3D) <i class="pstatus"> 本帖最后由 TL_SUNPENG 于 2026-9-29 10:55 编辑 </i><br /> <br />

Alex Kafando

Thank you. I will try the programmer firmware. Is it compatible with Programmer V1-V3 (pid\_8266)? According to our hardware config, PA3 is reserved for SWS on our board and not shared. Our firmware has a deep sleep state, but I have not measured the delay. The test code busy-waits 30 s after each power-up. Our product firmware is confidential, so I can send a minimal firmware that only writes the two eFuse values, if that helps. <i class="pstatus"> 本帖最后由 Alex Kafando 于 2026-9-29 15:50 编辑 </i><br /> <br />

Alex Kafando

[EFuseReproDemo.zip](https://forum.telink-semi.cn/forum.php?mod=attachment&aid=MjQyNnxiNjk5MjkxZXwxNzkwNjY4NDc3fDE1Mjd8MA%3D%3D) <div class="quote"><blockquote><font size="2"><a href="https://community.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102983&ptid=98922" target="_blank"><font color="#999999">TL_SUNPENG 发表于 2026-9-29 09:49</font></a></font> The wiring is correct. Could you share your firmware so I can try to reproduce the issue on a deve ...</blockquote></div> Here is a minimal non-confidential firmware reproducing the issue, built on your OTP\_Demo structure. README.md explains the two-step procedure. Programmer firmware compatible with Programmer V1-V3 (pid\_8266)?

TL_SUNPENG

The firmware is compatible. If the chip enters sleep later than expected, you can update the programmer firmware first and use that to verify. <div class="quote"><blockquote><font size="2"><a href="https://community.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102990&ptid=98922" target="_blank"><font color="#999999">Alex Kafando 发表于 2026-9-29 15:48</font></a></font><br /> Thank you. I will try the programmer firmware. Is it compatible with Programmer V1-V3 (pid\_8266)? A ...</blockquote></div><br />

Alex Kafando

Update: Re-enable Debug-interface now returns 'ok' consistently - the issue was a bad physical connection (pogo pins not properly seated on the board). However, right after a successful Re-enable, Activate still fails with Error<0x1002> on the same board, same session, no power cycle. Is this expected? Does Re-enable require a power cycle of the DUT afterward before Activate works, or should Activate work immediately?  <div class="quote"><blockquote><font size="2"><a href="https://community.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102983&ptid=98922" target="_blank"><font color="#999999">TL_SUNPENG 发表于 2026-9-29 09:49</font></a></font><br /> The wiring is correct. Could you share your firmware so I can try to reproduce the issue on a deve ...</blockquote></div><br />

TL_SUNPENG

Once Re-enable succeeds, you can go ahead and download the program again — no need to run Activate. Activate will power-cycle the chip. <div class="quote"><blockquote><font size="2"><a href="https://community.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102993&ptid=98922" target="_blank"><font color="#999999">Alex Kafando 发表于 2026-9-29 16:28</font></a></font><br /> Update: Re-enable Debug-interface now returns 'ok' consistently - the issue was a bad physical con ...</blockquote></div><br />

Alex Kafando

Thank you so much for your help throughout this thread! I can confirm the issue is fully resolved. The key was: after Re-enable Debug-interface returns "ok", do NOT click Activate right after — Activate power-cycles the chip and closes the re-enable window. Going directly to Download (or another flash operation) instead works perfectly. I successfully re-enabled SWS access on our locked TC3215F board and confirmed full flash access (Flash Info, full flash read-back). This solves a blocking issue on our project. Really appreciate your patience and the detailed troubleshooting (programmer firmware update, wiring check, endianness tip on the debug key). Thanks again! <div class="quote"><blockquote><font size="2"><a href="https://community.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102995&ptid=98922" target="_blank"><font color="#999999">TL_SUNPENG 发表于 2026-9-29 16:52</font></a></font><br /> Once Re-enable succeeds, you can go ahead and download the program again — no need to run Activat ...</blockquote></div><br />

TL_SUNPENG

You're welcome! Glad it helped. <div class="quote"><blockquote><font size="2"><a href="https://community.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102996&ptid=98922" target="_blank"><font color="#999999">Alex Kafando 发表于 2026-9-29 18:10</font></a></font><br /> Thank you so much for your help throughout this thread! I can confirm the issue is fully resolved. ...</blockquote></div><br />