Controller update help

GUYS MY CONTROLEER IS BRICKED!
Guys, I loaded the new firmware, to the controller. Restarted in update mode like the instructions on the configurator said, Removed the three files named Current.UF2 Index.HTM and Info_uf2.TXT.
Copied them to a backup folder and pasted the new firmware file atatched in the message above mine.
The controller rebooted successfully showing the 5.4V firmware. I unplugged the USB cable and plugged in the battery.

Then Nothing! Controller stays dark, doesn’t boot, ESC beeps continuously. HELP!
Tried to go back into the configurator to put it in update mode but it wont even detect the controler. Doesnt come on with USB cable attached so how can i put back the old firmware?
Help? Flying conditions are great all day today :frowning:

As a heads up, when updating you don’t need to remove any files from the controller, just copy and paste.

To reset you can just double tap the small reset button on the controller PCB. You’ll need to remove the plastic case. Once you plug it in to USB power and double tap that reset button you can drag and drop the update file onto the drive.

1 Like

Thank you Zack, I tried holding the reset button but I’m going to try the double tap now I’ve already got the controller taken apart.

Hmm, no Bueno.

I tried to plug the USB into the microcontroller and immediately double tapped the reset button. Still nothing. I tried another USB cable too with the same results. I also tried to plug in the USB cable and wait a little while then double tap the rest button.

It’s completely unresponsive, no light or leds are lit up on the board at all.

Seems like somehow, probably by removing the other two files, I’ve messed up the bootloader. Could that be possible?
Reading up on the issue i’ve encountered I’m leaning towards going this direction.

And ive put in an order for this device.
https://www.amazon.com/gp/product/B09KXSJ31D/ref=ppx_od_dt_b_asin_title_s00?ie=UTF8&th=1

Do you have any other ideas what I can do with my current controller? Am I barking up the wrong tree?

I was doing builds in the VS Code environment and using PlatformIO to upload my changes. Then I would plug into the battery and test. The same thing happened to me and I have tried holding reset and double tapping the reset and begging it to reset - but nothing. Hope we get a solution soon as it would be nice to be flying.

Do you have a jtag / swd debugger like I linked above? If so maybe try the fix described above?

How long ago did you brick your controller?

No, I do not have the device you linked. It happened on 4/24.

Bump? Anyone have some ideas or advice on a solution?

I was going to make the same query to you since there has been no response here or to my request for support - other than push the reset button. I researched your idea and think putting the bootloader back is the only hope at the moment but it appears tedious. There is a 10 pin header on the board but without a schematic I have no idea if it could be useful. I did check the 5V, 3.3V and 1.2V and confirmed the reset button to the processor but would really like to hear from Zach or Paul on this issue.

My Jtag/SWD programmer shows up tomorrow but beside the one forum post about it I have no idea what I’m doing with it. Likewise I need some help from Paul or Zach or I guess I we both just need to buy a new controler. Which I am also willing to do because I want to get back up flying.

I was out of town so apologies for the delay.

I’m not aware of any way to “delete the bootloader” by updating.
Can you upload a video to show how you are going though the steps to upload the update?

To update double press the reset button
(Pic below)

You’ll then see a USB drive show up and a red light on the board will pulse. If not check your cable and connection to your computer/Android

I have tried that over and over. I have used the same cable to load a Arduino Nano IOT controller. I have used another cable. Nothing works. The led does not come on, the USB drive never shows up.

Here is the video of what’s going on with my controller.

Thanks for the video!

Dm me and let’s set up a time to chat if you don’t mind and we can do some troubleshooting and try the flashing tool to fix the bootloader.
Once we get that figured out it may be worth adding a page so others know how to fix their broken boards in the future.

Per Paul, I shipped my controller back to Zach, so Zach should have a controller to check out in the next day or two,

Ok, so I have got the U-Link device and installed the 10 million drivers and software packs that it needs. I built a DIY J-Tag to SWD adapter using the instructions in the page above, without the pull down resistors because it looks like the OpenPPG controller already has them?

I thought I had bought J-Link but it turns out I didn’t, I honestly didnt really know the difference but the one I bought isnt compatible with SEGGER software so I have to use the U-Vision software instead.

Now I’m at this point and am totally confused. I have no idea what to do next except I know my objective is to load this .Bin file into the chip and restore the bootloader.

Anyone? Help please?

Ok, I didn’t get anywhere with the .Bin bootloader file, but I found this legit looking .Hex file that works with the U-vision program. But when I tried to flash it said it failed with this error. Anyone have any ideas? I would like some help please from someone who know litteraly anything? I have no idea what I’m doing.


Alright, troubleshooting update. I got as far as establishing communication to the AMD21 chip, but wasntb able to successfully burn the bootloader. It looks like that area of the chip is write protected by a" fuse" that I can’t seem to disable with the U link tool.

At this point I’m kinda stuck and think I either need to get a J link that can disable the fuse, or to give up on trying to reload the bootloader and focus on just loading the standard firmware back into the board.

Unfortunately I don’t exactly know how to do that without a U link project.

Can anyone help try and export the 5.3 sp140 firmware as a hex file and share it here? Or does anyone know how i can import or rebuild the project as a U vision compatible file?

Here is my debugger output.

Does this make sense to anyone?

UL2CM3.DLL - ULINK2/ME Driver Log

19:49:26:743 (08/05/2022) - WRITE DP  Access, Addr 0x00000008, Val 0x00000000, "SWD Write DP - Success" - ID 0
19:49:26:745 (08/05/2022) - WRITE DP  Access, Addr 0x00000004, Val 0x50000000, "SWD Write DP - Success" - ID 1
19:49:26:747 (08/05/2022) - READ  DP  Access, Addr 0x00000004, Val 0xF0000040, "SWD Read DP - Success" - ID 2
19:49:26:749 (08/05/2022) - WRITE DP  Access, Addr 0x00000004, Val 0x50000F00, "SWD Write DP - Success" - ID 3
19:49:26:751 (08/05/2022) - WRITE DP  Access, Addr 0x00000000, Val 0x0000001E, "SWD Write DP - Success" - ID 4
19:49:26:763 (08/05/2022) - READ  AP  Access, AP 0, Addr 0x000000FC, Val 0x04770031, "SWD Read AP - Success" - ID 5
19:49:26:763 (08/05/2022) - READ  AP  Access, AP 0, Addr 0x000000FC, Val 0x04770031, "SWD Read AP - Success" - ID 6
19:49:26:774 (08/05/2022) - WRITE AP  Access, AP 0, Addr 0x00000000, Val 0x23000052, "SWD Write AP - Success" - ID 7
19:49:26:778 (08/05/2022) - READ  AP  Access, AP 0, Addr 0x000000F8, Val 0x41003003, "SWD Read AP - Success" - ID 8
19:49:26:782 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0x41003FF0, End Addr 0x41003FFF, "SWD Read Memory Block - Success" - ID 9
  Item #0, AP 0, Addr 0x41003FF0, Value 0x0000000D
  Item #1, AP 0, Addr 0x41003FF4, Value 0x00000010
  Item #2, AP 0, Addr 0x41003FF8, Value 0x00000005
  Item #3, AP 0, Addr 0x41003FFC, Value 0x000000B1
19:49:26:784 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0x41003FD0, End Addr 0x41003FEF, "SWD Read Memory Block - Success" - ID 10
  Item #0, AP 0, Addr 0x41003FD0, Value 0x00000000
  Item #1, AP 0, Addr 0x41003FD4, Value 0x00000000
  Item #2, AP 0, Addr 0x41003FD8, Value 0x00000000
  Item #3, AP 0, Addr 0x41003FDC, Value 0x00000000
  Item #4, AP 0, Addr 0x41003FE0, Value 0x000000D0
  Item #5, AP 0, Addr 0x41003FE4, Value 0x000000FC
  Item #6, AP 0, Addr 0x41003FE8, Value 0x00000009
  Item #7, AP 0, Addr 0x41003FEC, Value 0x00000000
19:49:26:784 (08/05/2022) - ROM TABLE: Detected Unknown ROM Table at address 0x41003000 (PID 0x000000000009FCD0, CID 0xB105100D)
19:49:26:786 (08/05/2022) - READ  MEM Access, AP 0, Addr 0x41003000, Val 0x9F0FC003, "SWD Read Memory (32 bit) - Success" - ID 11
19:49:26:788 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE00FFFF0, End Addr 0xE00FFFFF, "SWD Read Memory Block - Success" - ID 12
  Item #0, AP 0, Addr 0xE00FFFF0, Value 0x0000000D
  Item #1, AP 0, Addr 0xE00FFFF4, Value 0x00000010
  Item #2, AP 0, Addr 0xE00FFFF8, Value 0x00000005
  Item #3, AP 0, Addr 0xE00FFFFC, Value 0x000000B1
19:49:26:790 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE00FFFD0, End Addr 0xE00FFFEF, "SWD Read Memory Block - Success" - ID 13
  Item #0, AP 0, Addr 0xE00FFFD0, Value 0x00000004
  Item #1, AP 0, Addr 0xE00FFFD4, Value 0x00000000
  Item #2, AP 0, Addr 0xE00FFFD8, Value 0x00000000
  Item #3, AP 0, Addr 0xE00FFFDC, Value 0x00000000
  Item #4, AP 0, Addr 0xE00FFFE0, Value 0x000000C0
  Item #5, AP 0, Addr 0xE00FFFE4, Value 0x000000B4
  Item #6, AP 0, Addr 0xE00FFFE8, Value 0x0000000B
  Item #7, AP 0, Addr 0xE00FFFEC, Value 0x00000000
19:49:26:790 (08/05/2022) - ROM TABLE: Detected ROM Table (Cortex-M0+) at address 0xE00FF000 (PID 0x00000004000BB4C0, CID 0xB105100D)
19:49:26:792 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE00FF000, Val 0xFFF0F003, "SWD Read Memory (32 bit) - Success" - ID 14
19:49:26:794 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE000EFF0, End Addr 0xE000EFFF, "SWD Read Memory Block - Success" - ID 15
  Item #0, AP 0, Addr 0xE000EFF0, Value 0x0000000D
  Item #1, AP 0, Addr 0xE000EFF4, Value 0x000000E0
  Item #2, AP 0, Addr 0xE000EFF8, Value 0x00000005
  Item #3, AP 0, Addr 0xE000EFFC, Value 0x000000B1
19:49:26:796 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE000EFD0, End Addr 0xE000EFEF, "SWD Read Memory Block - Success" - ID 16
  Item #0, AP 0, Addr 0xE000EFD0, Value 0x00000004
  Item #1, AP 0, Addr 0xE000EFD4, Value 0x00000000
  Item #2, AP 0, Addr 0xE000EFD8, Value 0x00000000
  Item #3, AP 0, Addr 0xE000EFDC, Value 0x00000000
  Item #4, AP 0, Addr 0xE000EFE0, Value 0x00000008
  Item #5, AP 0, Addr 0xE000EFE4, Value 0x000000B0
  Item #6, AP 0, Addr 0xE000EFE8, Value 0x0000000B
  Item #7, AP 0, Addr 0xE000EFEC, Value 0x00000000
19:49:26:796 (08/05/2022) - ROM TABLE: Detected SCS (ARMv6-M) at address 0xE000E000 (PID 0x00000004000BB008, CID 0xB105E00D)
19:49:26:798 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE000EDFC, Val 0x01000000, "SWD Write Memory (32 bit) - Success" - ID 17
19:49:26:800 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE00FF004, Val 0xFFF02003, "SWD Read Memory (32 bit) - Success" - ID 18
19:49:26:802 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE0001FF0, End Addr 0xE0001FFF, "SWD Read Memory Block - Success" - ID 19
  Item #0, AP 0, Addr 0xE0001FF0, Value 0x0000000D
  Item #1, AP 0, Addr 0xE0001FF4, Value 0x000000E0
  Item #2, AP 0, Addr 0xE0001FF8, Value 0x00000005
  Item #3, AP 0, Addr 0xE0001FFC, Value 0x000000B1
19:49:26:804 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE0001FD0, End Addr 0xE0001FEF, "SWD Read Memory Block - Success" - ID 20
  Item #0, AP 0, Addr 0xE0001FD0, Value 0x00000004
  Item #1, AP 0, Addr 0xE0001FD4, Value 0x00000000
  Item #2, AP 0, Addr 0xE0001FD8, Value 0x00000000
  Item #3, AP 0, Addr 0xE0001FDC, Value 0x00000000
  Item #4, AP 0, Addr 0xE0001FE0, Value 0x0000000A
  Item #5, AP 0, Addr 0xE0001FE4, Value 0x000000B0
  Item #6, AP 0, Addr 0xE0001FE8, Value 0x0000000B
  Item #7, AP 0, Addr 0xE0001FEC, Value 0x00000000
19:49:26:804 (08/05/2022) - ROM TABLE: Detected DWT (ARMv6-M) at address 0xE0001000 (PID 0x00000004000BB00A, CID 0xB105E00D)
19:49:26:806 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE00FF008, Val 0xFFF03003, "SWD Read Memory (32 bit) - Success" - ID 21
19:49:26:808 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE0002FF0, End Addr 0xE0002FFF, "SWD Read Memory Block - Success" - ID 22
  Item #0, AP 0, Addr 0xE0002FF0, Value 0x0000000D
  Item #1, AP 0, Addr 0xE0002FF4, Value 0x000000E0
  Item #2, AP 0, Addr 0xE0002FF8, Value 0x00000005
  Item #3, AP 0, Addr 0xE0002FFC, Value 0x000000B1
19:49:26:810 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0xE0002FD0, End Addr 0xE0002FEF, "SWD Read Memory Block - Success" - ID 23
  Item #0, AP 0, Addr 0xE0002FD0, Value 0x00000004
  Item #1, AP 0, Addr 0xE0002FD4, Value 0x00000000
  Item #2, AP 0, Addr 0xE0002FD8, Value 0x00000000
  Item #3, AP 0, Addr 0xE0002FDC, Value 0x00000000
  Item #4, AP 0, Addr 0xE0002FE0, Value 0x0000000B
  Item #5, AP 0, Addr 0xE0002FE4, Value 0x000000B0
  Item #6, AP 0, Addr 0xE0002FE8, Value 0x0000000B
  Item #7, AP 0, Addr 0xE0002FEC, Value 0x00000000
19:49:26:810 (08/05/2022) - ROM TABLE: Detected BPU (ARMv6-M) at address 0xE0002000 (PID 0x00000004000BB00B, CID 0xB105E00D)
19:49:26:812 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE00FF00C, Val 0x00000000, "SWD Read Memory (32 bit) - Success" - ID 24
19:49:26:814 (08/05/2022) - READ  MEM Access, AP 0, Addr 0x41003004, Val 0x00003003, "SWD Read Memory (32 bit) - Success" - ID 25
19:49:26:816 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0x41006FF0, End Addr 0x41006FFF, "SWD Read Memory Block - Success" - ID 26
  Item #0, AP 0, Addr 0x41006FF0, Value 0x0000000D
  Item #1, AP 0, Addr 0x41006FF4, Value 0x00000090
  Item #2, AP 0, Addr 0x41006FF8, Value 0x00000005
  Item #3, AP 0, Addr 0x41006FFC, Value 0x000000B1
19:49:26:818 (08/05/2022) - READ  MEM BLOCK Access, AP 0, Start Addr 0x41006FD0, End Addr 0x41006FEF, "SWD Read Memory Block - Success" - ID 27
  Item #0, AP 0, Addr 0x41006FD0, Value 0x00000004
  Item #1, AP 0, Addr 0x41006FD4, Value 0x00000000
  Item #2, AP 0, Addr 0x41006FD8, Value 0x00000000
  Item #3, AP 0, Addr 0x41006FDC, Value 0x00000000
  Item #4, AP 0, Addr 0x41006FE0, Value 0x00000032
  Item #5, AP 0, Addr 0x41006FE4, Value 0x000000B9
  Item #6, AP 0, Addr 0x41006FE8, Value 0x0000001B
  Item #7, AP 0, Addr 0x41006FEC, Value 0x00000000
19:49:26:818 (08/05/2022) - ROM TABLE: Detected MTB-M0+ (Cortex-M0+) at address 0x41006000 (PID 0x00000004001BB932, CID 0xB105900D)
19:49:26:820 (08/05/2022) - READ  MEM Access, AP 0, Addr 0x41003008, Val 0x00000000, "SWD Read Memory (32 bit) - Success" - ID 28
19:49:26:822 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000ED00, Val 0x410CC601, "SWD Read Memory (32 bit) - Success" - ID 29
19:49:26:824 (08/05/2022) - READ  DP  Access, Addr 0x00000004, Val 0xF0000040, "SWD Read DP - Success" - ID 30
19:49:26:826 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE000EDFC, Val 0x00000001, "SWD Write Memory (32 bit) - Success" - ID 31
19:49:26:828 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE000EDF0, Val 0xA05F0003, "SWD Write Memory (32 bit) - Success" - ID 32
19:49:26:830 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE000EDFC, Val 0x01000000, "SWD Write Memory (32 bit) - Success" - ID 33
19:49:26:832 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE0002000, Val 0x00000040, "SWD Read Memory (32 bit) - Success" - ID 34
19:49:26:834 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE0001000, Val 0x20000000, "SWD Read Memory (32 bit) - Success" - ID 35
19:49:26:836 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001024, Val 0x0000001F, "SWD Write Memory (32 bit) - Success" - ID 36
19:49:26:838 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE0001024, Val 0x0000001F, "SWD Read Memory (32 bit) - Success" - ID 37
19:49:26:840 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001024, Val 0x00000000, "SWD Write Memory (32 bit) - Success" - ID 38
19:49:26:842 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001028, Val 0x00000100, "SWD Write Memory (32 bit) - Success" - ID 39
19:49:26:844 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE0001028, Val 0x00000000, "SWD Read Memory (32 bit) - Success" - ID 40
19:49:26:846 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001028, Val 0x00000080, "SWD Write Memory (32 bit) - Success" - ID 41
19:49:26:848 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE0001028, Val 0x00000000, "SWD Read Memory (32 bit) - Success" - ID 42
19:49:26:850 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001028, Val 0x00000000, "SWD Write Memory (32 bit) - Success" - ID 43
19:49:26:852 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001038, Val 0x00000100, "SWD Write Memory (32 bit) - Success" - ID 44
19:49:26:854 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE0001038, Val 0x00000000, "SWD Read Memory (32 bit) - Success" - ID 45
19:49:26:856 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001038, Val 0x00000080, "SWD Write Memory (32 bit) - Success" - ID 46
19:49:26:858 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE0001038, Val 0x00000000, "SWD Read Memory (32 bit) - Success" - ID 47
19:49:26:860 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001038, Val 0x00000000, "SWD Write Memory (32 bit) - Success" - ID 48
19:49:26:862 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0002000, Val 0x00000002, "SWD Write Memory (32 bit) - Success" - ID 49
19:49:26:864 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001028, Val 0x00000000, "SWD Write Memory (32 bit) - Success" - ID 50
19:49:26:866 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE0001038, Val 0x00000000, "SWD Write Memory (32 bit) - Success" - ID 51
19:49:26:868 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE000EDFC, Val 0x00000001, "SWD Write Memory (32 bit) - Success" - ID 52
19:49:26:870 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 53
19:49:26:872 (08/05/2022) - WRITE MEM Access, AP 0, Addr 0xE000ED0C, Val 0x05FA0004, "SWD Write Memory (32 bit) - Success" - ID 54
19:49:26:874 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x03030003, "SWD Read Memory (32 bit) - Success" - ID 55
19:49:26:876 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 56
19:49:26:878 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 57
19:49:26:880 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 58
19:49:26:886 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 59
19:49:27:196 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 60
19:49:27:447 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 61
19:49:27:700 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 62
19:49:27:951 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 63
19:49:28:204 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 64
19:49:28:457 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 65
19:49:28:708 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 66
19:49:28:961 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 67
19:49:29:213 (08/05/2022) - READ  MEM Access, AP 0, Addr 0xE000EDF0, Val 0x00030003, "SWD Read Memory (32 bit) - Success" - ID 68
19:49:29:288 (08/05/2022) - WRITE MEM BLOCK Access, AP 0, Start Addr 0xE0002000, End Addr 0xE0002017, "SWD Write Memory Block - Success" - ID 69
  Item #0, AP 0, Addr 0xE0002000, Value 0x00000002
  Item #1, AP 0, Addr 0xE0002004, Value 0x00000000
  Item #2, AP 0, Addr 0xE0002008, Value 0x00000000
  Item #3, AP 0, Addr 0xE000200C, Value 0x00000000
  Item #4, AP 0, Addr 0xE0002010, Value 0x00000000
  Item #5, AP 0, Addr 0xE0002014, Value 0x00000000
19:49:29:290 (08/05/2022) - WRITE DP  Access, Addr 0x00000004, Val 0x00000000, "SWD Write DP - Success" - ID 70