DAPLINK LPC1768/88 crashes.

Hi there, how is it doing? I hope you all are having great days!

So;
On 2020, I have struggled a lot on DAPlink using interface LPC11U35 for lpc1768/88.
The project that I have taken as base is the C027_if, and I'm using Keil V5.1 for development.

The issue is:
Until lasts of 2020, the processors had the codes:
LPC1768FBD100,551 and LPC1788FBD208,551.
So, the cores was changed for:
LPC1768FBD100K and LPC1788FBD208K

For some reason, using the drag and drop function, some boards crashes the code!
Those boards have absolutely the same hardware, same software, etc and so on.

But, some crashes after energizing, another ones after some time, another ones after hours!

If I get the board and uses the Segger J-LINK, or Keil Ulink for writing the code, nothing wrong happens, it works as it has to do!

Perhaps, someone had that information about LPC1768/88 incident?
Getting information from the net, I have got that link as below, and it has me done crazy and messy!
https://www-editcode-net.translate.goog/archiver/tid-701613.html?_x_tr_sl=zh-CN&_x_tr_tl=pt&_x_tr_hl=pt-BR&_x_tr_pto=op,sc (Chinese one, just take into a translator)

Someone could give me some advice and directions for figuring out what is happening?

Thanks in advance!

Fabio!

No source files or tests are named. Start by reproducing the drag-and-drop failure on the LPC1768/1788 boards with the changed part markings, then compare it with programming through Segger J-LINK or Keil Ulink. Done means identifying a reproducible cause and documenting or fixing the DAPLink-specific crash.

Written by the indexing model from the issue text.