Building edbg for windows has some dependencies (while none are indicated in README.txt)
dbg_win.c includes the followinf ddk files :

#include <ddk/hidsdi.h>
#include <ddk/hidpi.h>

Consequently, building fails with :

$ make
gcc -W -Wall -Wextra -O2 -std=gnu11 dap.c edbg.c target.c target_atmel_cm0p.c target_atmel_cm3.c target_atmel_cm4.c target_atmel_cm7.c target_atmel_cm4v2.c  dbg_win.c -lhid -lsetupapi -o edbg.exe
dbg_win.c:34:10: fatal error: ddk/hidsdi.h: No such file or directory
 #include <ddk/hidsdi.h>
          ^~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:45: edbg.exe] Error 1

Any chance to for you to add them in your git rather than pull the whole ddk ?

Thanks.

The check() function causes a recursive call to itself if function dap_led() fails.

Hi
I am using samd21G18A chip, with atmel ice I am trying to burn bootloader to it. I am getting the following response when using the command.
./edbg -t atmel_cm0p
Error: invalid response while writing the register 0x00 (count = 0, value = 7)

what can be the cause for the error.

Hi,

I'm trying to connect to an ATSAMD51J20A using an atmel-ice debugger. command:

> sudo ./edbg-b56-LINUX_GCC-4f5d490 -t atmel_cm4v2 -rb -c 2000

Debugger: ATMEL Atmel-ICE CMSIS-DAP J41800048174 01.27.0082 (SJ)
Clock frequency: 2.0 MHz
Error: invalid response while writing the register 0x00 (count = 0, value = 0)

sudo is necessary because of permission issues.
All the light flash on the debugger so I think that it is connecting properly. Whenever I disconnect the MCU I get (count = 0, value = 7), so something is going on.

Do you know how to solve this issue?

Hi, I have followed your instructions for Windows. I inserted the command make all, in the cmd.exe but the following message appears (see message in my Atmel community post - http://community.atmel.com/forum/erase-memory-saml21-whilst-sleep-mode#comment-1825186).

How would I get around this? Thanks

I would like to ask that you include the required dependencies in the README.md file. It does not state it, but the libudev-dev package is required to successfully compile.

After cloning, when I try to make it throws error :

git clone git://github.com/signal11/hidapi.git
Cloning into 'hidapi'...
fatal: unable to connect to github.com:
github.com[0: 192.30.253.113]: errno=Operation timed out
github.com[1: 192.30.253.112]: errno=Operation timed out

Any ideas why? I even tried it as a super user, same issues.

For a fresh compile on MacOS Big Sur, I found that I needed to add

LIBS += -framework Cocoa

to the Makefile to get it to link.

Awesome work so far! Very happy to see some options opening up for development outside of AVR Studio...

Anyways, more of a feature request than an issue...I have an ATSAMB11 development kit and I'm getting the following error when trying to program:

Debugger: ATMEL EDBG CMSIS-DAP ATML2534030200001457 03.0C.0191 (S) Error: unknown target device (CHIP_ID = 0x00000000)

I've tried with all of the target options (no success)...Any ideas?

Hi ataradov,

working perfectly with your tool. Faced a new part that is not currently supported.
ATSAMD20G18A
Debugger: ATMEL EDBG CMSIS-DAP ATML1873060200016987 01.1A.00FB (S)
Error: unknown target device (DSU_DID = 0x10001405)

I believe an added line to .h in cm0p will do the job as stated in the datasheet.

{ 0x10001405, "SAM D20G18A", 0, 256*1024, 64, 4096, 256 },

Good job!

Testing with LPC845 Breakout:
(gdb) r -b -t stm32g0 -r
Starting program: /devel/edbg/edbg -b -t stm32g0 -r
Missing separate debuginfos, use: zypper install glibc-debuginfo-2.26-lp151.18.7.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Debugger: NXP Semiconductors LPC11U3x CMSIS-DAP v1.0.7 0F040028 1.10 (S)
Clock frequency: 16.0 MHz
(gdb) bt
#0 0x00007ffff78e3c61 in read () from /lib64/libc.so.6
#1 0x00000000004073b0 in dbg_dap_cmd ()
#2 0x0000000000402539 in dap_reset_link ()
#3 0x0000000000402bd7 in reconnect_debugger ()
#4 0x00000000004015d6 in main ()
Running a second time hangs even earlier:
Debugger: NXP Semiconductors LPC11U3x CMSIS-DAP v1.0.7 0F040028 1.10 (S)
Clock frequency: 16.0 MHz
(gdb) bt
#0 0x00007ffff78e3c61 in read () from /lib64/libc.so.6
#1 0x00000000004073b0 in dbg_dap_cmd ()
#2 0x0000000000401b99 in dap_get_debugger_info ()
#3 0x0000000000401598 in main ()

After hang "pyocd gdb" does not see the device.
After un/replug, "pyocd gdb" sees the device.

After running "pyocd gdb" successfull, "edbg -b -t stm32g0 -r" suceeds as far as it is expected for an unknown device.:
(gdb) r -b -t stm32g0 -r
Starting program: /devel/edbg/edbg -b -t stm32g0 -r
Missing separate debuginfos, use: zypper install glibc-debuginfo-2.26-lp151.18.7.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Debugger: NXP Semiconductors LPC11U3x CMSIS-DAP v1.0.7 0F040028 1.10 (S)
Clock frequency: 16.0 MHz
Error: unknown target device (DBG_IDCODE = 0x00000000)

inside dbg_mac.c I got an error on compile the variable report_size was not declared.

  char cmd = data[0];
  int res;

  memset(hid_buffer, 0xff, report_size + 1);

  hid_buffer[0] = 0x00; // Report ID

I added the line of code:

  char cmd = data[0];
  int res;
  int report_size = dbg_get_report_size();

  memset(hid_buffer, 0xff, report_size + 1);

  hid_buffer[0] = 0x00; // Report ID

This may or may not be right but it compiled and I am going to make sure it works now.

Hello,
I tried to flash an SAM E70 on the Atmel SAME7 Xplained Dev Board.
I compiled edbg from scratch. libudev-dev was need, so I installed this via apt-get.
The build had no problems.

When I tried to flash the binary, I got this error:

~/workspace-Qdev/SAME70-Blinky $ edbg -bpv -t atmel_cm7 -f bin/SAME70-Template.bin 
Debugger: ATMEL EDBG CMSIS-DAP ATML2637010000000000 02.09.0169 (S)
Target: SAM E70Q21
Programming........,....................................... done.
Verification...................................
at address 0x404000 expected 0x86, read 0x00
Error: verification failed

I seems that the MCU is not programmed. I am not sure, where I have to look
to find the problem.

Regards,
Andre

I have a new Catalina install, XCode and developer tools installed. But I get the following

ENG-1510:edbg travisg$ make all
git clone git://github.com/signal11/hidapi.git
Cloning into 'hidapi'...
remote: Enumerating objects: 2006, done.
remote: Total 2006 (delta 0), reused 0 (delta 0), pack-reused 2006
Receiving objects: 100% (2006/2006), 2.73 MiB | 2.37 MiB/s, done.
Resolving deltas: 100% (1172/1172), done.
cd hidapi && ./bootstrap
+ autoreconf --install --verbose --force
./bootstrap: line 2: autoreconf: command not found
make: *** [hidapi/mac/.libs/libhidapi.a] Error 127

bintray

If you are logged into bintray, you should see a list of repositories on the left named Owned Repositories. There you can Add New Repository.

Please create a public repository named edbg of type Generic. Inside the repository you need to add a package named travis-ci. You can of cause change the names to whatever you like, I will change my pull request accordingly.

Now with the repository and package being created, we need to extract your bintray API key. It's available in the bintray web GUI at Edit Your Profile / API Key

Please do not share your API key here directly, but encrypt it using Travis CI first. The rest of this document assumes your API key is super_secret. In reallity it should look like a long hexdecimal character sequence.

Travis CI

Encrypt your bintray credentials for usage in Travis CI

travis encrypt -r ataradov/edbg BINTRAY_DEPLOYMENT_API_KEY=super_secret

You might need to install the travis gem, I recommend doing so inside an ephemeral container:

$ docker run -it --rm ubuntu:16.04
# apt-get -y update && apt-get -y install build-essential ruby ruby-dev
# gem install travis
# travis encrypt -r ataradov/edbg BINTRAY_DEPLOYMENT_API_KEY=super_secret

In my opinion, encrypting secrets for usage inside Travis CI is the most annoying part. Travis CI should offer a GUI on their website for this task ☹

You should see an output similar to

  secure: "mMXpe5Vhl6vgvT/D9HwfPgamDJsuk4q9cKRidIqp3Xe2TmOr5PZ3KMxXaJhNBzRPiI/kH2pYImK3EG2pbAhFUj2D3YKyyB6B1FrE7YQB72MzTFn86MY1L+igywap/3dm7ZRDT0pGLSQCjVN9QOpbKzpcCFlLu0oLMFT23FNOj6BFN/+fHJrIW9b4x44vd3P2MPk2E4CYMr43seedPzUHmio4mrqXJKAa3sHH9BvS/E6tpeYiWNJ1+RO2e/p5AqrS1d157+hnH8upsC2BIwlkRbUEkZdrjsJjc+CNVS2IBPjXbfeD+nGIJdiKP33+s3i1lnyMUAmy8hmZ80X2sKTFElow0cxXVhEI8uwLmylSmMR50VpmLHM2VZJV16dNJ2HvadDm4ztm82fPL4Ob7sybDK34+of8BYXoSWDBJ6Fx0ABISQ1z7riargPxdGI09a0+z6ZbJwARWWPD0K0av/W/PpCMTSnV4zmcWilTkw5t9JhIRLXral5Z/ghS7u1qVBvS6SgSf46e41oSAgRJyfnPl21R4D8uU6/b2MqvslQ0re+JKMdcrSROCYIc/455SwTol1Q0YAm5d7kCFSKVVS+dfV3BdtcxvgO57VcbSRsppTSC+PzZPh0EGgf2KUyb2Rj+ZltaqJYiWgpUyVdizrfE0/kqEkE17G7lj+wh3TpoAk4="

Please paste this string here. While your bintray API key is secret and must not be shared with anybody, the encrypted string is not. It's encrypted with your public Travis CI key, thus only Travis CI will be able to decrypt the string and inject additional secret environment variables into your build environment.

Hello and first of all thanks a lot for the great work!

I'm currently evaluating programming options for an atsamd21 and am benchmarking programming speeds for different tools and different programmers. At the moment, I'm noticing a massive difference between Atmel Studio and tools on linux (see below).
I would be therefore curious to know if you have done in the past some similar benchmarks?

My current results:

Atmel Studio for different SWD clocks, 142652 bytes firmware, program and verify:
Atmel-ICE:

• 8MHz (not recommended): 12s
• 4MHz: 13s17
• 2MHz: 14s49
• 1MHz: 17s40
• 500kHz: 22s31

JLink:

• 8MHz (not recommended): 7s5
• 4MHz: 8s
• 2MHz: 8s61
• 1MHz: 9s93
• 500kHz: 13s

Edbg on Ubuntu on Virtualbox, same firmware, erase, program and verify:
command line: sudo ./edbg-b77-LINUX_GCC-04b7508 -b -epv -t samd21 -f mini_ble.bin -c 8000
Atmel-ICE:

• 16MHz (not recommended): 1m01
• 8MHz (not recommended): 1m01
• 4MHz: 1m04
• 2MHz: 1m04

JLink: doesn't have CMSIS-DAP

OpenOCD on Ubuntu on Virtualbox, same firmware, erase, program & verify:
command line for jlink: sudo openocd -f samd21_jlink.cfg -c "init; targets; program mini_ble.bin verify reset; shutdown"
command line atmel ice: sudo openocd -f samd21_ice.cfg -c "init; targets; program mini_ble.bin verify reset; shutdown"

Atmel-ICE:

• 2MHz: 1m04
• 1MHz: 1m00
• 400kHz: 1m02

JLink:

• 8MHz: FAIL
• 4MHz: FAIL
• 2MHz: FAIL
• 1MHz: 1m27
• 500kHz: 1m27

samd21_ice.cfg file contents:
source [find interface/cmsis-dap.cfg]
set CHIPNAME at91samd21g18
set ENDIAN little
set telnet_port 0
source [find target/at91samdXX.cfg]
adapter_khz 2000

samd21_jlink.cfg file contents:
interface jlink
transport select swd
set CHIPNAME at91samd21e18
set ENDIAN little
set telnet_port 0
source [find target/at91samdXX.cfg]
adapter_khz 2000

@ataradov This ought to speed up the program/test cycle for small programs. Right now it takes more than 8 seconds to erase same70q21 (2MB.) My program is actually smaller than one erase block.

Thanks, Mark

After manually adding its entry, programming an ATSAMD21G16L with an Atmel-iCE and a hex file (~34kb) appears to work fine, including erasing and verifying.

However, the code on the chip does not run afterwards.

If I program the same device, with an Atmel-iCE, using Atmel Studio 7, with the same hex file, it runs just fine.

Dumping the memory from the device, after either program, reveals that the data is identical up until offset 0x00008420 (around where I expect the end of the hex file data to be).

After that though, the portion of the empty memory is different:

Dump after EDBG programming

Dump after Atmel Studio 7 programming

Is there some other option/configuration step I'm missing?

Hi,

I have a samr21/30 target board. I want to get the target voltage to check if my target is correctly powered before flashing?
How could I add an arg to read target voltage only?

Thanks,

I have been testing this with an Atmel SAMD21 Xplained Pro board I have. When I plug the board into the debug USB port (this is what the Atmel FAEs specified was the correct way to interface to the device for programming and debugging) with the "./edbg -l" command I get, "Attached debuggers:
ATML2130021800014950 - Atmel Corp. EDBG CMSIS-DAP", but if I attempt to read the contents of the chip with the "./edbg -r" command I get, "Error: unknown target device (DSU_DID = 0x10010300)". I should point out that this board is less than a day old an I have not loaded any code onto it yet. I just wanted to test if this would be able to communicate to the device.

Hi,
I'm trying to use edbg on MinGW. I used a SAMD20-Xplained board to program a custom board based on SAML21.
When I used edbg on linux or linux vm, everything runs fine.
But on MinGW, edbg said there are several debuggers attached (which is not the case)
here the output of edbg --list
Attached debuggers: ATML1873040200013344 - Atmel Corp. EDBG CMSIS-DAP EDBG CMSIS-DAP - EDBG CMSIS-DAP EDBG CMSIS-DAP EDBG CMSIS-DAP - EDBG CMSIS-DAP EDBG CMSIS-DAP
If I specify edbg -s ATML1873040200013344, it works as expected.
This is no a main issue but this is a bit annoying.
Any ideas ?

Could you consider to add support of last Microchip core Cortex M23, SAML11 family ?

https://www.microchip.com/promo/sam-l10-and-l11-microcontroller-family

Hi @ataradov, some Atmel AVR boards (XMINI) embed an EDBG, well an mEDBG but with similar commands.
Do you think it would be easy for you to add their support?

Thanks,
T.

More of a question than an issue... but didn't know where else to ask.

Description

This change (b65dc24#diff-00259a9e325566089cd936bcc3e75e50R564) caused targets to be reset twice. This is relevant when one just wants to reset (using, e.g., edbg -t atmel_cm0p)

The first reset:

Why is it relevant

In the RIOT OS test suite we reset the boards at the beginning of each test. The test script waits for a known string to start the test. With the current edbg behaviour the test starts and shortly afterwards the board is reset, causing it to fail. Since this is happening only with atmel boards using edbg, I'd like to avoid having to add a specific kludge to handle it in the test infrastructure if I can avoid it.

Steps to reproduce

Load an program that does something immediately after boot, for example output a string over the UART. In my case I'm running the RIOT OS test suite, and listening on the serial connection.

Reset the board with edbg -t <target type> (in my case atmel_cm0p.)

Expected result

Board is reset once thus the message is sent once.

Actual result

Board is reset twice in a short span thus the message is sent twice.

Hi,

as discussed in pull request #56, I have set up a proof of concept of how to automatically deploy edbg binaries to bintray using Travis CI.

The current setup will result in an URL looking something like

https://dl.bintray.com/ataradov/edbg/master/

where master is the branch being build. This directory contains a list of all revisions build by Travis CI. The binaries inside a build are currently named like this:

edbg-b36-LINUX_CLANG-1657458
edbg-b36-LINUX_GCC-1657458
edbg-b36-OSX_CLANG-1657458
edbg-b36-OSX_GCC-1657458
edbg-b36-WINDOWS-1657458.exe

• 36 is the Travis CI build number
• LINUX_CLANG is the target's name
• 1657458 are the first eight digits of the git revision build by travis, in this case 165745819852853cf625db28878d240be2aa09ea

I personally dislike the mixing of SNAKE_CASE and kebab-case, so maybe we should change the target names. What do you think?

Hello, your program run very good for flash a "same70q21". But i have a question, with this program can i make a proxydebug for debugging my firmware?

Thank

Hi, Alex!

I'm linux user and edbg is great thing for CLI project flow!

Which one file format supported by your tool?
bin/hex/elf???

I think edbg need simlpe check for file-extension for preventing brick the uC-device.

WBR,
Dmitry

Hi.
You have not stated any licensing for this project so is this GPL ?

Hi,

I'm using edbg to program an Atmel CM7. I'm compiling edbg on Windows and OS X. Initially both are not working as i'm always getting this:

Debugger: ATMEL Atmel-ICE CMSIS-DAP J41800088582 01.27.0082 (SJ)
Error: invalid response while writing the register 0x00 (count = 0, value = 7)

A hardware guy told me that the SWD clock ratio was too high compared with the CPU clock. So I went into Atmel Studio under Tools -> Device Programming and in interface settings I set the SWD clock to 128 kHz (was 2 MHz). When I hit save and go back to edbg I can now program my file on this specific machine only.

How can I do the same on OS X or Linux where Atmel Studio doesn't run?

Any help would be appreciated.

Thanks

I'm trying to use edbg to program, and later debug, a SAM4LXplained pro board.

I had modified target.c to add the uC part number( ATSAM4LC4CA) but I'm not being able to execute any comand.
I've tried:

edbg -be -t atmel_cm4

And had the following error:

Debugger: ATMEL EDBG CMSIS-DAP ATML1783020200003186 03.19.01A3 (S)
Error: invalid response while writing the register 0x0d (count = 1, value = 4)

With gdb I found that the problem occur when the dap command to AIRCR for reset is being written.

I think that is possibly not a problem with edbg, but I want some help to figure out a solution, and to add it to edbg

I noticed a couple of Travis CI builds look like they failed. The reason is that a restarted build gets the same build number and bintray does not allow overwriting of build artifacts by default.

Depolyment to Bintray failed with response {"message":"Unable to upload files: An artifact with the path 'master/19/edbg-b19-OSX_GCC-72ab2d2' already exists"}

I created this issue as a reminder for myself. I'll try to find a solution, at least I will check if the file exists before trying to upload it so the build will not be marked as failed in Travis CI.

Downloads/edbg-master$ make all
gcc -W -Wall -O2 -std=gnu99 dap.c edbg.c target.c target_atmel_cm0p.c target_atmel_cm3.c target_atmel_cm4.c target_atmel_cm7.c dbg_lin.c -ludev -o edbg
aswin@aswin-fourthfrontier:~/Downloads/edbg-master$ ./edbg -bev -t atmel_cm4
Error: unable to find parent usb device

After commit 800e209 I get verification errors anytime I attempt to program my samd21j18 board:

edbg -t atmel_cm0p -bpv -f boot.bin
Debugger: ATMEL Atmel-ICE CMSIS-DAP J41800049111 01.26.0081 (SJ)
Clock frequency: 16.0 MHz
Target: SAM D21J18A (Rev D)
Programming........................... done.
Verification...
at address 0x0 expected 0x38, read 0xff
Error: verification failed
make: *** [flash] Error 1

I played around in target_atmel_cm0p.c and I could get occasional success by tweaking some of the changes (like converting dap_write_half and dap_write_byte back to dap_write_word) but no one line fix.

Writing a wrong clock config locks up my samd21g18, and makes me unable to program with edbg.

I solved this by adding dap_reset_target() after dap_connect(), but this seems to introduce another problem with the chip not running after programming, until I press reset. I don't know enough about CMSIS-DAP for a proper solution yet, but I'm looking into it.

Hi,

Would it be possible to just create a release tag like 1.0? I made an homebrew formula for OS X but they require a tag/release.

Thanks

I have several samr21xpro devices each attached to several machines running Debian Jessie. Edbg has been flawlessly loading binaries to all of these devices for some time.

The latest code that was loaded for debugging onto the devices seems to have caused many (perhaps 2/3) of the samr21xpro to no longer work with edbg. All edbg operations now fail with the following:
"Error: invalid response while writing the register 0x00 (count = 1, value = 2)"

Looking through dap.c, count=1 seems to be the expected output, but value=2 seems to correspond to the DAP_TRANSFER_WAIT return code.

My understanding is that similar issues can arise when the security bit is set (I don't think I've accidentally done this), but that a chip erase will undo even the worst goof-ups. However, in this case even the erase operation fails in the above manner.

Hello,

Board was working fine for some time, but now that my program has grown in size, I am having trouble programming it. It uploads the larger program just fine but does not work after that. It responds in Microchip/Atmel Studio just fine, and if I erase the board from there then I can program it with this tool. This is using the onboard programmer; there is only a USB cable involved.

OpenOCD seems to be affected by the same issue (I know this is a different project but could be relevant if they work in similar ways).

Debugger: Atmel mEDBG CMSIS-DAP ATML2378032700000781  (SJ)
Clock frequency: 16.0 MHz
Error: invalid response during transfer (count = 0/1, status = 7)

If the GPIO use for SWCLK or SWDIO is reconfigured (MUX GPIO) just after boot on the target, edbg does not success to erase/flash/read the target

It is a timing problem

I inverted some commands on edbg.c to not loose time after board reset:

  dbg_open(&debuggers[debugger]);

----------------------------------------
  dap_get_debugger_info();

  print_clock_freq(g_clock);
----------------------------------------
// above and below has been inverted here to show success code
----------------------------------------
  dap_reset_target_hw(1);

  reconnect_debugger();
----------------------------------------
  target->ops->select(&g_target_options);

And it works great
I have no time yet to make this short pull request, so I'll will do later if nobody did it before

Unfortunately travis-ci.org will shut down in December. While Travis CI encourages moving to travis-ci.com, I do not recommend this move, since the open source build minutes are severely limited.

I therefore propose to migrate the CI to GitHub Actions. There are other alternatives like Circle CI, however I am most familiar with GitHub Actions.

Would moving to GitHub Actions be ok for you? I would propose a pull request.

Hello,

I am trying to get the Blackmagic Debugger running with CMSIS_Dap adapters. I found your edbg a good start. As the DAP_PORT_JTAG may bot be implemented, is is needed outside of dap.c to know of "J" is in the return of ID_DAP_INFO/DAP_INFO_CAPABILITIES.

What would you propose to export these values?

I've added what I believe is the correct entry to target_atmel_cm0p.c for programming an ATSAMD21G16L device:

{ 0x10011557, "samd21", "SAM D21G16L", 64*1024 }

However, when I try and program the device I get the following error:

Debugger: ATMEL Atmel-ICE CMSIS-DAP J42700001914 01.27.0082 (SJ)
Clock frequency: 16.0 MHz
Error: unknown target device (DSU_DID = 0x10011557)

Hi,
What's the effort to add a debug functionality in your implementation so we can use it with gdb?
Or is it already possible? Please explain me how?

Hi @ataradov, do you think you could provide binary releases for all supported OS, please?

I'm integrating this tool into my Arduino SAM port (https://github.com/aethaniel/ExperimentalCore-sam) and I'm able to compile only win64 and linux64 binaries.

Usual OS targets are:

• Win32
• Win64
• Lin32
• Lin64
• OS X

This isn't a strong request but more a nice to have. No stress ;-)

If you have a solution to remote build the project similar to the Travis-CI I'm using at the moment, I could investigate myself and provide you the binaries to bring here for a Release.

Thanks,

T.

Hi,

first of all, thank you very much for this great project! I have a question regarding Windows dependencies. The readme states that no dependencies on windows are required.

However dbg_win.c seems to need the Windows Driver Kit? I'm asking because I'm currently trying to cross compile edbg for Windows and I'm missing the ddk include directory.

Maybe the README should extended by stating the Windows Driver Kit is required, but that's normally bundled with Visual Studio?

-- ooxi

Hello,

a MIMXRT1060-EVK return no values for DAP_INFO_VENDOR, DAP_INFO_PRODUCT an info DAP_INFO_SER_NUM.

As https://arm-software.github.io/CMSIS_5/DAP/html/group__DAP__Info.html states, this is allowed and the descriptor values should be used in that case.

Running on the MIMRXT1060, some register access fails fatal:
Debugger: 1.10 (S)
Clock frequency: 16.0 MHz

Breakpoint 1, dap_write_reg (reg=reg@entry=5 '\005', data=data@entry=1073829888) at dap.c:413
413 error_exit("invalid response while writing the register 0x%02x (count = %d, value = %d)",
(gdb) bt
#0 dap_write_reg (reg=reg@entry=5 '\005', data=data@entry=1073829888) at dap.c:413
#1 0x0000000000401a83 in dap_read_word (addr=addr@entry=1073829888) at dap.c:470
#2 0x0000000000405fe0 in target_select (options=0x60e180 <g_target_options>) at target_st_stm32g0.c:182
#3 0x00000000004028d1 in main (argc=, argv=) at edbg.c:496
(gdb) n
Error: invalid response while writing the register 0x05 (count = 0, value = 7)

In my BMP setup using dbg_xxx.c and dap.c, accesses to 0x400xyyyy also fail fatal. These accesses happen when the probe tests for the STM32F0. STM32L0 and LPC43 Idcode registers. I have not found a way to recover after that failure. Do you have any idea?

So glad to have found this, I've been dreading building my own edbg programmer. There's no LICENSE file or stated license terms, can you clarify those in the repository?

I have a Microchip PG164140 programmer coming and intend to use it for the ATSAMC21G17A.
Will the edbg software be able to program it using that programmer and MCU?

If not can you recommend another software. I use Linux command line.

Is it feasible for me to add support for the microbit? It uses a cm0 nrf51822. I looked at the cm0p support and I’m not sure what would need to be changed. Thanks, Mark.