Regarding to RAKDAP1

Dear RAK Support Team,

We are currently working with RAK11720 and RAK3172 LoRa modules in our project. During development, we encountered firmware-related issues where the modules are no longer responding correctly (AT mode and custom firmware upload are not functioning as expected).The error message is attached below.

To recover the modules, we are planning to use the RAKDAP1 debugger and would like to clarify the following points before proceeding:

  1. Is the RAKDAP1 debugger suitable for both RAK11720 and RAK3172 modules for firmware recovery and reprogramming via SWD?
  2. Does this SWD-based recovery method provide a 100% reliable solution to restore modules that are unresponsive due to incorrect or corrupted firmware?

Welcome to the forum @Haridhar

First to clarify:

You are talking about RAKDAP1 but your screenshot shows the JFlash application.
What are you planning to use?

Personal experience, RAKDAP1 with pyOCD works (most of the time), however, I had some strange and not reproducible problems where it didn’t work and could not connect.

I always use a full JLink adapter with JFlash and use it for flashing of our devices (with exception of the ESP32 boards).

Only problem I usually have is

  • bad connection
  • bad connection
  • bad connection
  • device is dead

I repeated the first one, because a bad connection is 75% of flashing problems I have.

we are going to use RAKDAP1 only, not with JFlash, whether it is suitable? Also in that picture it shown JLink because we used that but it doesn’t work.So we are planning to use RAKDP1

As I wrote before
JLink is more reliable than any DAPLink adapter including the RAKDAP1.
If you get connection errors, it is

  • bad connection (wire/adapter problem)
  • wrong connection (wrong signal connection)