Add script reading bootloader flags

diff --git a/Bootloaders/DFU/README.md b/Bootloaders/DFU/README.md
index b25591a..3953f43 100644 (file)
--- a/Bootloaders/DFU/README.md
+++ b/Bootloaders/DFU/README.md
@@ -75,3 +75,10 @@ always starting the application over the bootloader:
     avrdude -c usbasp -p m32u4 -B100 -U efuse:w:0xc6:m -U hfuse:w:0x18:m -U lfuse:w:0xff:m
 
 
+Test DFU flags
+--------------
+The DFU bootloader flags of the programmed Pro-Micro can be read by a script:
+    read-dfu-bootld-flags.sh
+
+This script runs naturally also be used for other boards, but might output different
+results other than expected.

diff --git a/Bootloaders/DFU/read-dfu-bootld-flags.sh b/Bootloaders/DFU/read-dfu-bootld-flags.sh
new file mode 100755 (executable)
index 0000000..429be09
--- /dev/null
+++ b/Bootloaders/DFU/read-dfu-bootld-flags.sh
@@ -0,0 +1,17 @@
+#!/bin/bash
+# Reading some bootloader flags of the ProMicro
+echo "Reading Bootloader flags of Sparkfun ProMicro"
+dfu-programmer atmega32u4 get bootloader-version
+echo "Bootloader Version: 0x20 (32)  expected"
+dfu-programmer atmega32u4 get ID1
+echo "Device boot ID 1: 0xdc (220)  expected"
+dfu-programmer atmega32u4 get ID2
+echo "Device boot ID 2: 0xfb (251)  expected"
+dfu-programmer atmega32u4 get manufacturer
+echo "Manufacturer Code: 0x58 (88)  expected not 0x1e (30)"
+dfu-programmer atmega32u4 get family
+echo "Family Code: 0x1e (30)  expected not 0x95 (149)"
+dfu-programmer atmega32u4 get product-name
+echo "Product Name: 0x95 (149)  expected not 0x01 (1)"
+dfu-programmer atmega32u4 get product-revision
+echo "Product Revision: 0x87 (135)  expected not 0x01 (1)"