MPLAB Snap + Arduino Mega = Empty CMSIS-DAP response received #68

lrustand · 2023-01-13T10:41:55Z

lrustand
Jan 13, 2023

Hi, I am trying to use Bloom to debug an Arduino Mega 2560 using a MPLAB Snap, but I am not able to get it to work. I keep getting the following error:

2023-01-13 11:18:25 CET [MT] [1]: [INFO] Selected environment: "default"
2023-01-13 11:18:25 CET [TC] [2]: [INFO] Starting TargetController
2023-01-13 11:18:25 CET [TC] [3]: [INFO] Connecting to debug tool
2023-01-13 11:18:40 CET [TC] [4]: [ERROR] The TargetController encountered a fatal error. See below for errors:
2023-01-13 11:18:40 CET [TC] [5]: [ERROR] Empty CMSIS-DAP response received
2023-01-13 11:18:40 CET [TC] [6]: [INFO] Shutting down TargetController
2023-01-13 11:18:40 CET [MT] [7]: [ERROR] TargetController failed to start up
2023-01-13 11:18:40 CET [MT] [8]: [INFO] Shutting down Bloom
2023-01-13 11:18:40 CET [SH] [9]: [INFO] Shutting down SignalHandler

I have enabled the JTAG and OCD fuses on the Mega and have verified that the Snap is in AVR mode. I have the correct permissions to use the /dev/ttyACM0. What could be wrong?

EDIT: added below information:
Contents of bloom.yaml:

environments:
  default:
    debugTool:
      name: "snap"

    target:
      name: "atmega2560"
      physicalInterface: "jtag"

    debugServer:
      name: "avr-gdb-rsp"
      ipAddress: "127.0.0.1"
      port: 1442

Contents of fuses on Mega:

avrdude -p atmega2560 -c wiring -P /dev/ttyUSB0 -b 115200 -U lfuse:r:-:i -U hfuse:r:-:i -U efuse:r:-:i

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e9801 (probably m2560)
avrdude: reading lfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude: writing output file "<stdout>"
:01000000FF00
:00000001FF
avrdude: reading hfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude: writing output file "<stdout>"
:0100000018E7
:00000001FF
avrdude: reading efuse memory:

Reading | ################################################## | 100% 0.00s

avrdude: writing output file "<stdout>"
:01000000FD02
:00000001FF

avrdude done.  Thank you.

Output of lsusb | grep -e "Atmel" -e "Microchip":

Bus 003 Device 093: ID 03eb:2180 Atmel Corp. MPLAB Snap ICD CMSIS-DAP

navnavnav · 2023-01-13T18:06:45Z

navnavnav
Jan 13, 2023
Maintainer

Hi @lrustand,

Something really weird is happening here. It looks like the Snap isn't responding to Bloom, at all. When Bloom sends a command to the Snap, it waits 15 seconds for a response (which is more than enough - in most cases the Snap responds in <1 second). Looking at the timestamps in that log (11:18:25 -> 11:18:40), the 15 second difference suggests that the timeout is being reached, and we're not getting any response.

I suspect the Snap is in a weird state. Did you run any other program that would interface with the Snap (MPLAB IPE, AVRDUDE, etc) after connecting the Snap via USB but before running Bloom?

Can you please try the following:

Disconnect the Snap from USB and from any target.
Disconnect the Arduino from USB (if it was connected)
Enable debug logging in Bloom by setting debugLoggingEnabled to true in bloom.yaml:
```
debugLoggingEnabled: true

environments:
  ...
```
Ensure that you are not running any other program that can interface with the Snap (MPLAB IPE, AVRDUDE, MPLABX IDE, etc).
Connect the Snap via USB, but do not connect it to any target.
Run Bloom and post the output here.

Does it get a little further this time? Does it report [INFO] Debug tool connected and [INFO] Debug tool name: MPLAB Snap? If so, then it's likely that the Snap was somehow put into a bad state. You should be able to connect the Snap to the target, and run Bloom, without issue.

However, if it reports the same Empty CMSIS-DAP response received error, something is very wrong. Please follow the steps below to help me better understand what's going on:

Disconnect the Snap from USB.
Run lsusb (with the Snap disconnected) and post the output here.
Connect the Snap via USB and run lsusb -v -d 03eb:2180 and post the output here.

This will help me understand what's going on.

Additionaly, it would be good to know if MPLAB IPE can interface with the Snap, so please try the following:

With the Snap disconnected from any target, but connected via USB, open MPLAB IPE
Select the Snap debug tool and any AVR8 target
Click the 'Read' button
Paste MPLAB IPE's output here

If MPLAB IPE can interface with the Snap, it should complain about target voltage being too low, or not being able to find the selected target (because the Snap isn't connected to any target). Please post the MPLAB IPE output here, so I can see if it was able to interface with the Snap. If MPLAB IPE is not able to properly interface with the Snap, then that would suggest an issue with the Snap firmware.

Finally, are you doing anything with /dev/ttyACM0? That device file serves the Snap's USB CDC interface. Bloom doesn't make use of this interface, and any I/O on that device file shouldn't interfere with Bloom at all. However, to be safe, please ensure that you're not performing any I/O on /dev/ttyACM0 whilst following any of the steps listed above.

Thanks,

1 reply

lrustand Jan 13, 2023
Author

Thanks for the quick reply.

I suspect the Snap is in a weird state. Did you run any other program that would interface with the Snap (MPLAB IPE, AVRDUDE, etc) after connecting the Snap via USB but before running Bloom?

No, I do not even have MPLAB IPE installed, and do not run anything else that uses the Snap. I have plugged and re-plugged it several times as well.

Can you please try the following:
Disconnect the Snap from USB and from any target.

Disconnect the Arduino from USB (if it was connected)
Enable debug logging in Bloom by setting debugLoggingEnabled to true in bloom.yaml:
debugLoggingEnabled: true

environments:
  ...
Ensure that you are not running any other program that can interface with the Snap (MPLAB IPE, AVRDUDE, MPLABX IDE, etc).

Connect the Snap via USB, but do not connect it to any target.

Run Bloom and post the output here.

Okay, here it is.

2023-01-13 20:24:05 CET [MT] [1]: [DEBUG] Debug log printing has been enabled
2023-01-13 20:24:05 CET [MT] [2]: [DEBUG] Bloom version: 0.11.1
2023-01-13 20:24:05 CET [MT] [3]: [INFO] Selected environment: "default"
2023-01-13 20:24:05 CET [MT] [4]: [DEBUG] Number of environments extracted from config: 1
2023-01-13 20:24:05 CET [TC] [5]: [INFO] Starting TargetController
2023-01-13 20:24:05 CET [SH] [6]: [DEBUG] Starting SignalHandler
2023-01-13 20:24:05 CET [SH] [7]: [DEBUG] SignalHandler ready
2023-01-13 20:24:05 CET [TC] [8]: [INFO] Connecting to debug tool
2023-01-13 20:24:05 CET [TC] [9]: [DEBUG] HID device path: 3-1:1.0
2023-01-13 20:24:20 CET [TC] [10]: [ERROR] The TargetController encountered a fatal error. See below for errors:
2023-01-13 20:24:20 CET [TC] [11]: [ERROR] Empty CMSIS-DAP response received
2023-01-13 20:24:20 CET [TC] [12]: [INFO] Shutting down TargetController
2023-01-13 20:24:20 CET [TC] [13]: [DEBUG] Event "TargetControllerThreadStateChanged" (1) registered for listener ApplicationEventListener
2023-01-13 20:24:20 CET [MT] [14]: [ERROR] TargetController failed to start up
2023-01-13 20:24:20 CET [MT] [15]: [INFO] Shutting down Bloom
2023-01-13 20:24:20 CET [MT] [16]: [DEBUG] Joining TargetController thread
2023-01-13 20:24:20 CET [MT] [17]: [DEBUG] TargetController thread joined
2023-01-13 20:24:20 CET [MT] [18]: [DEBUG] Joining SignalHandler thread
2023-01-13 20:24:20 CET [SH] [19]: [DEBUG] SIGNAL 10 received
2023-01-13 20:24:20 CET [SH] [20]: [INFO] Shutting down SignalHandler
2023-01-13 20:24:20 CET [MT] [21]: [DEBUG] SignalHandler thread joined
2023-01-13 20:24:20 CET [MT] [22]: [DEBUG] Saving project settings to /home/lars/build/Bloom/build/.bloom/settings.json

Disconnect the Snap from USB.

Run lsusb (with the Snap disconnected) and post the output here.

I don't see the relevance of posting my other usb devices.

Connect the Snap via USB and run lsusb -v -d 03eb:2180 and post the output here.

Bus 003 Device 100: ID 03eb:2180 Atmel Corp. MPLAB Snap ICD CMSIS-DAP
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         2
  bDeviceProtocol         1 Interface Association
  bMaxPacketSize0        64
  idVendor           0x03eb Atmel Corp.
  idProduct          0x2180
  bcdDevice            1.00
  iManufacturer           1 Microchip Technology Incorporated
  iProduct                2 MPLAB Snap ICD CMSIS-DAP
  iSerial                 3 BUR190120466
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x008b
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      35
          Report Descriptor: (length is 35)
            Item(Global): Usage Page, data= [ 0x00 0xff ] 65280
                            (null)
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Collection, data= [ 0x01 ] 1
                            Application
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x40 0x00 ] 64
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Input, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Report Count, data= [ 0x40 0x00 ] 64
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Output, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Report Count, data= [ 0x04 ] 4
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Feature, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Main  ): End Collection, data=none
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      35
          Report Descriptor: (length is 35)
            Item(Global): Usage Page, data= [ 0x00 0xff ] 65280
                            (null)
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Collection, data= [ 0x01 ] 1
                            Application
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x40 0x00 ] 64
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Input, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Report Count, data= [ 0x40 0x00 ] 64
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Output, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Global): Report Count, data= [ 0x04 ] 4
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Feature, data= [ 0x02 ] 2
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Non_Volatile Bitfield
            Item(Main  ): End Collection, data=none
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         1
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       2 Abstract (modem)
      bFunctionProtocol       1 AT-commands (v.25ter)
      iFunction               5 Snap Virtual COM Port
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Union:
        bMasterInterface        1
        bSlaveInterface         2
      CDC Call Management:
        bmCapabilities       0x03
          call management
          use DataInterface
        bDataInterface          2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              16
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         2
  bDeviceProtocol         1 Interface Association
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

This will help me understand what's going on.

Additionaly, it would be good to know if MPLAB IPE can interface with the Snap, so please try the following:

With the Snap disconnected from any target, but connected via USB, open MPLAB IPE

Select the Snap debug tool and any AVR8 target

Click the 'Read' button

Paste MPLAB IPE's output here

I am sorry, I don't have MPLAB IPE and don't plan on installing it. The reason I am trying to use Bloom in the first place is because I am not comfortable with running proprietary closed source software, so installing MPLAB IPE is not an option for me.

Finally, are you doing anything with /dev/ttyACM0? That device file serves the Snap's USB CDC interface. Bloom doesn't make use of this interface, and any I/O on that device file shouldn't interfere with Bloom at all. However, to be safe, please ensure that you're not performing any I/O on /dev/ttyACM0 whilst following any of the steps listed above.

Nope, not doing anything with it, I just thought I would double check that I have the correct permissions to access the device's pseudo file. If Bloom does not use this file, which file does it use instead, /dev/bus/usb/xxx/xxx?

navnavnav · 2023-01-13T19:59:11Z

navnavnav
Jan 13, 2023
Maintainer

That log confirms my suspicion that Bloom isn't able to talk to the device at all.

I am sorry, I don't have MPLAB IPE and don't plan on installing it. The reason I am trying to use Bloom in the first place is because I am not comfortable with running proprietary closed source software, so installing MPLAB IPE is not an option for me.

Ok, what about AVRDUDE? Can you try reading fuses via AVRDUDE and the Snap? AVRDUDE 7.1, which was released a few days ago, supports Snap with the JTAG physical interface. You can download a Linux x86_64 binary of AVRDUDE from one of the automated builds (be sure to place the avrdude.conf file in /usr/local/etc/ before running 7.1).

Please post the output of AVRDUDE here. If it also fails, then there's likely something wrong with the Snap's firmware.

10 replies

navnavnav Jan 13, 2023
Maintainer

👍🏽

It's worth noting that, when upgrading, be sure to select a target in the AVR8 family (when configuring MPLAB IPE or MPLABX IDE), so that the tool remains in AVR mode.

navnavnav Jan 13, 2023
Maintainer

Just one more thing:

How did you install Bloom? Did you use a prebuilt binary package from the Download page? Or did you build from source?

If you built from source, could you please run ldd /absolute/path/to/bloom and paste the output here. This will give me an idea of what shared objects are being used by Bloom.

Finally, how did you install the libusb and libhidapi dependencies? What versions did you install?

I have a feeling that there's more to this error, so I'd like to look into it further.

lrustand Jan 13, 2023
Author

I built it from source.

Ouput from ldd:

        linux-vdso.so.1 (0x00007ffc773e4000)
        libusb-1.0.so.0 => /usr/lib/libusb-1.0.so.0 (0x00007fefa7277000)
        libhidapi-libusb.so.0 => /usr/lib/libhidapi-libusb.so.0 (0x00007fefa726c000)
        libprocps.so.8 => /usr/lib/libprocps.so.8 (0x00007fefa7233000)
        libyaml-cpp.so.0.7 => /usr/lib/libyaml-cpp.so.0.7 (0x00007fefa71b7000)
        libQt6UiTools.so.6 => /usr/lib/libQt6UiTools.so.6 (0x00007fefa7132000)
        libQt6Xml.so.6 => /usr/lib/libQt6Xml.so.6 (0x00007fefa710c000)
        libQt6SvgWidgets.so.6 => /usr/lib/libQt6SvgWidgets.so.6 (0x00007fefa7100000)
        libQt6Network.so.6 => /usr/lib/libQt6Network.so.6 (0x00007fefa6f72000)
        libQt6OpenGLWidgets.so.6 => /usr/lib/libQt6OpenGLWidgets.so.6 (0x00007fefa6f65000)
        libQt6OpenGL.so.6 => /usr/lib/libQt6OpenGL.so.6 (0x00007fefa6eca000)
        libQt6Svg.so.6 => /usr/lib/libQt6Svg.so.6 (0x00007fefa6e6f000)
        libQt6Widgets.so.6 => /usr/lib/libQt6Widgets.so.6 (0x00007fefa6600000)
        libQt6Gui.so.6 => /usr/lib/libQt6Gui.so.6 (0x00007fefa5e00000)
        libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007fefa6e3b000)
        libOpenGL.so.0 => /usr/lib/libOpenGL.so.0 (0x00007fefa6e10000)
        libQt6Core.so.6 => /usr/lib/libQt6Core.so.6 (0x00007fefa5800000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fefa5400000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007fefa5718000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fefa6dee000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007fefa5219000)
        libudev.so.1 => /usr/lib/libudev.so.1 (0x00007fefa6dbd000)
        libatomic.so.1 => /usr/lib/libatomic.so.1 (0x00007fefa6db3000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fefa77a5000)
        libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007fefa563c000)
        libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fefa6dac000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00007fefa6d58000)
        libbrotlidec.so.1 => /usr/lib/libbrotlidec.so.1 (0x00007fefa6d4a000)
        libzstd.so.1 => /usr/lib/libzstd.so.1 (0x00007fefa5170000)
        libz.so.1 => /usr/lib/libz.so.1 (0x00007fefa5de6000)
        libEGL.so.1 => /usr/lib/libEGL.so.1 (0x00007fefa6d36000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007fefa5d98000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0x00007fefa502d000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007fefa4eee000)
        libQt6DBus.so.6 => /usr/lib/libQt6DBus.so.6 (0x00007fefa4e3a000)
        libxkbcommon.so.0 => /usr/lib/libxkbcommon.so.0 (0x00007fefa4df3000)
        libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007fefa4dba000)
        libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007fefa4cd1000)
        libmd4c.so.0 => /usr/lib/libmd4c.so.0 (0x00007fefa4cbb000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007fefa4bec000)
        libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007fefa4b34000)
        libicui18n.so.72 => /usr/lib/libicui18n.so.72 (0x00007fefa4800000)
        libicuuc.so.72 => /usr/lib/libicuuc.so.72 (0x00007fefa4400000)
        libdouble-conversion.so.3 => /usr/lib/libdouble-conversion.so.3 (0x00007fefa47ea000)
        libb2.so.1 => /usr/lib/libb2.so.1 (0x00007fefa47cc000)
        libpcre2-16.so.0 => /usr/lib/libpcre2-16.so.0 (0x00007fefa473e000)
        libcap.so.2 => /usr/lib/libcap.so.2 (0x00007fefa65f0000)
        libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007fefa42b8000)
        liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007fefa470b000)
        liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007fefa46e9000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00007fefa4611000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00007fefa428a000)
        libcom_err.so.2 => /usr/lib/libcom_err.so.2 (0x00007fefa5d92000)
        libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00007fefa4603000)
        libkeyutils.so.1 => /usr/lib/libkeyutils.so.1 (0x00007fefa4283000)
        libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007fefa4271000)
        libbrotlicommon.so.1 => /usr/lib/libbrotlicommon.so.1 (0x00007fefa424e000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007fefa4223000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007fefa41f8000)
        libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007fefa415d000)
        libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007fefa410c000)
        libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007fefa40ea000)
        libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007fefa40d7000)
        libicudata.so.72 => /usr/lib/libicudata.so.72 (0x00007fefa2200000)
        libgomp.so.1 => /usr/lib/libgomp.so.1 (0x00007fefa408e000)
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007fefa4068000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0x00007fefa5637000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007fefa4060000)

And for the libusb and libhidapi I used the ones already present on my system, libusb 1.0.26-1 and hidapi 0.13.1-1.

Btw, I had to fix two tiny little things in order for Bloom to compile. A missing #include <optional> and a size_t that I had to change to std::size_t.

navnavnav Jan 13, 2023
Maintainer

Ok, some good news: I've been able to reproduce the issue. The problem is not the firmware on the Snap.

You're using a very recent version of hidapi (was released just 4 days ago). I built that from source, then built Bloom with it and can now reproduce the issue you were having.

I'm not yet sure if the issue lies in Bloom, which the new release of hidapi has exposed, or if this is a bug introduced in hidapi. Will post an update when I know more.

navnavnav Jan 14, 2023
Maintainer

I have found the cause for this. It was an issue within Bloom that became apparent with the new hidapi release.

I've pushed a fix to the develop branch and tested it against the new hidapi library, as well as some older versions - all works as expected now.

If you clear your previous build and rebuild from the develop branch, you should be able to use Bloom with the latest hidapi now. Be sure to pull down the changes from develop before building again. Oh, and you shouldn't have to worry about those #include <optional> changes - they were fixed in a previous commit on the develop branch some time ago, IIRC.

To clear your current build:

cd path/to/bloom/source;
rm -fr ./build/cmake-build-release/*;
rm -fr ./release;

lrustand · 2023-01-14T09:04:15Z

lrustand
Jan 14, 2023
Author

Seems like your latest fix worked like it should, now it recognises the Snap connects to the Mega, but it segfaults after starting the GDB server.

2023-01-14 09:50:57 CET [MT] [1]: [DEBUG] Debug log printing has been enabled
2023-01-14 09:50:57 CET [MT] [2]: [DEBUG] Bloom version: 0.11.1
2023-01-14 09:50:57 CET [MT] [3]: [INFO] Selected environment: "default"
2023-01-14 09:50:57 CET [MT] [4]: [DEBUG] Number of environments extracted from config: 1
2023-01-14 09:50:57 CET [TC] [5]: [INFO] Starting TargetController
2023-01-14 09:50:57 CET [SH] [6]: [DEBUG] Starting SignalHandler
2023-01-14 09:50:57 CET [SH] [7]: [DEBUG] SignalHandler ready
2023-01-14 09:50:57 CET [TC] [8]: [INFO] Connecting to debug tool
2023-01-14 09:50:57 CET [TC] [9]: [DEBUG] HID device path: 3-1:1.0
2023-01-14 09:50:57 CET [TC] [10]: [INFO] Debug tool connected
2023-01-14 09:50:57 CET [TC] [11]: [INFO] Debug tool name: MPLAB Snap
2023-01-14 09:50:57 CET [TC] [12]: [INFO] Debug tool serial:
2023-01-14 09:50:57 CET [TC] [13]: [DEBUG] Loading AVR8 target description file: /home/lars/build/Bloom/build/bin/../resources/TargetDescriptionFiles/AVR/AVR8/MEGA/ATMEGA2560.xml
2023-01-14 09:50:57 CET [TC] [14]: [DEBUG] Failed to extract pinout from target description element - Failed to convert position attribute value to integer on pin element 0
2023-01-14 09:50:57 CET [TC] [15]: [INFO] Activating target
2023-01-14 09:50:57 CET [TC] [16]: [DEBUG] Setting FLASH_PAGE_SIZE AVR8 device parameter
2023-01-14 09:50:57 CET [TC] [17]: [DEBUG] Setting FLASH_SIZE AVR8 device parameter
2023-01-14 09:50:57 CET [TC] [18]: [DEBUG] Setting FLASH_BASE AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [19]: [DEBUG] Setting SRAM_START AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [20]: [DEBUG] Setting EEPROM_SIZE AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [21]: [DEBUG] Setting EEPROM_PAGE_SIZE AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [22]: [DEBUG] Setting OCD_REVISION AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [23]: [DEBUG] Setting OCD_DATA_REGISTER AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [24]: [DEBUG] Setting SPMCR_REGISTER AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [25]: [DEBUG] Setting BOOT_START_ADDR AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [26]: [DEBUG] Setting OSCCAL_ADDR AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [27]: [DEBUG] Setting EEARL_ADDR AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [28]: [DEBUG] Setting EEARH_ADDR AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [29]: [DEBUG] Setting EECR_ADDR AVR8 device parameter
2023-01-14 09:50:58 CET [TC] [30]: [DEBUG] Setting EEDR_ADDR AVR8 device parameter
2023-01-14 09:50:59 CET [TC] [31]: [WARNING] Execution on AVR8 target could not be halted post attach - Failed to receive break event for AVR8 target
2023-01-14 09:51:00 CET [TC] [32]: [INFO] Target activated
2023-01-14 09:51:00 CET [TC] [33]: [INFO] AVR8 target promoted to megaAVR target
2023-01-14 09:51:00 CET [TC] [34]: [DEBUG] Setting FLASH_PAGE_SIZE AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [35]: [DEBUG] Setting FLASH_SIZE AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [36]: [DEBUG] Setting FLASH_BASE AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [37]: [DEBUG] Setting SRAM_START AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [38]: [DEBUG] Setting EEPROM_SIZE AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [39]: [DEBUG] Setting EEPROM_PAGE_SIZE AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [40]: [DEBUG] Setting OCD_REVISION AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [41]: [DEBUG] Setting OCD_DATA_REGISTER AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [42]: [DEBUG] Setting SPMCR_REGISTER AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [43]: [DEBUG] Setting BOOT_START_ADDR AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [44]: [DEBUG] Setting OSCCAL_ADDR AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [45]: [DEBUG] Setting EEARL_ADDR AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [46]: [DEBUG] Setting EEARH_ADDR AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [47]: [DEBUG] Setting EECR_ADDR AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [48]: [DEBUG] Setting EEDR_ADDR AVR8 device parameter
2023-01-14 09:51:00 CET [TC] [49]: [INFO] Target ID: 0x1e9801
2023-01-14 09:51:00 CET [TC] [50]: [INFO] Target name: ATmega2560
2023-01-14 09:51:00 CET [TC] [51]: [DEBUG] Event "TargetControllerThreadStateChanged" (2) registered for listener ApplicationEventListener
2023-01-14 09:51:00 CET [TC] [52]: [DEBUG] TargetController ready and waiting for events.
2023-01-14 09:51:00 CET [DS] [53]: [INFO] Starting DebugServer
2023-01-14 09:51:00 CET [DS] [54]: [INFO] Selected DebugServer: AVR GDB Remote Serial Protocol Debug Server
2023-01-14 09:51:00 CET [DS] [55]: [INFO] GDB RSP address: 127.0.0.1
2023-01-14 09:51:00 CET [DS] [56]: [INFO] GDB RSP port: 1442
2023-01-14 09:51:00 CET [DS] [57]: [DEBUG] Issuing GetTargetDescriptor command (ID: 1) to TargetController
2023-01-14 09:51:00 CET [DS] [58]: [DEBUG] Delivering response for GetTargetDescriptor command (ID: 1)
2023-01-14 09:51:00 CET [DS] [59]: [DEBUG] Event "DebugServerThreadStateChanged" (3) registered for listener ApplicationEventListener
2023-01-14 09:51:00 CET [DS] [60]: [INFO] DebugServer ready
2023-01-14 09:51:00 CET [DS] [61]: [INFO] Waiting for GDB RSP connection
[1]    353008 segmentation fault (core dumped)  bin/bloom

I have attached the core file. It seems to have crashed in something Qt related. I wish there was some way to build without insights, because I do not need it and it feels like a massive bloat. I saw that there was someone that opened an issue for this previously and that you closed it as wontfix, but I would like to add a strong +1 for this.
core.zip

5 replies

navnavnav Jan 14, 2023
Maintainer

Can you post a copy of the Bloom binary you've built?

navnavnav Jan 14, 2023
Maintainer

Also, what version of Qt did you install?

lrustand Jan 14, 2023
Author

Sure here you go. Built using Qt 6.4.2 on Arch Linux.
bloom.zip

lrustand Jan 14, 2023
Author

Okay, turns out it was enough to just disable insights in the config file in order to prevent the segfault. I seem to be able to debug now, at least I successfully connected gdb to the server.

navnavnav Jan 14, 2023
Maintainer

Ok, I've figured out the problem here. When building in release mode, the binary is configured to use the distributed plugins (as it should). Those plugins are built from Qt 6.2.4 LTS, but they appear to be incompatible with 6.4.2. This incompatibility is causing the seg fault.

I have no intention of upgrading Bloom's Qt support from an LTS to a non-LTS release, so I'm not going to update those distributed plugins any time soon. If you wish to use Insight, you have two options:

Build with the debug configuration. This will mean your local (system) Qt plugins will be used. If you do this, be sure to comment out line 58 of CMakeLists.txt (or point it to your local QT installation).
Use the prebuilt binary package hosted on the download page. This package includes prebuilt Qt 6.2.4 LTS shared objects, which have been the subject of countless hours of testing.

I wish there was some way to build without insights, because I do not need it and it feels like a massive bloat. I saw that there was someone that opened an issue for this previously and that you closed it as wontfix, but I would like to add a strong +1 for this.

There is already a ticket for this. But this won't entirely remove the Qt dependency. I'm not sure when I'll get to it, but it won't be any time soon.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MPLAB Snap + Arduino Mega = Empty CMSIS-DAP response received #68

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 16 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

MPLAB Snap + Arduino Mega = Empty CMSIS-DAP response received #68

lrustand Jan 13, 2023

Replies: 3 comments · 16 replies

navnavnav Jan 13, 2023 Maintainer

lrustand Jan 13, 2023 Author

navnavnav Jan 13, 2023 Maintainer

navnavnav Jan 13, 2023 Maintainer

navnavnav Jan 13, 2023 Maintainer

lrustand Jan 13, 2023 Author

navnavnav Jan 13, 2023 Maintainer

navnavnav Jan 14, 2023 Maintainer

lrustand Jan 14, 2023 Author

navnavnav Jan 14, 2023 Maintainer

navnavnav Jan 14, 2023 Maintainer

lrustand Jan 14, 2023 Author

lrustand Jan 14, 2023 Author

navnavnav Jan 14, 2023 Maintainer

lrustand
Jan 13, 2023

Replies: 3 comments 16 replies

navnavnav
Jan 13, 2023
Maintainer

lrustand Jan 13, 2023
Author

navnavnav
Jan 13, 2023
Maintainer

navnavnav Jan 13, 2023
Maintainer

navnavnav Jan 13, 2023
Maintainer

lrustand Jan 13, 2023
Author

navnavnav Jan 13, 2023
Maintainer

navnavnav Jan 14, 2023
Maintainer

lrustand
Jan 14, 2023
Author

navnavnav Jan 14, 2023
Maintainer

navnavnav Jan 14, 2023
Maintainer

lrustand Jan 14, 2023
Author

lrustand Jan 14, 2023
Author

navnavnav Jan 14, 2023
Maintainer