@Samuel Thanks for amazing works!! Many people asked me about CMSIS-DAP with gdb at Maker Faire Shenzhen. If I knew this, I could say "YES!!".

Why not supprting OS X? Is this because technical difficulties of HID handling on OS X?

@Samuel, thanks for your good product.

@ytsuboi, as you know, it's hard to support OSX because of technical issues around HID. I've not tried but probably it can support also OSX by preparing the another transport based on HIDAPI. I'll hack it on first of May if no one try.

Brilliant ! Thanks You very much for building this.

Are you planning on doing a video of the mbed with the DDD debugger ? If it works i think it could raise a lot of interest in the embedded community.

@Samuel: While I was trying out pyOCD, I found a bug in pywinusb_backend.py. If there are more than 1 usb device (apart from the mbed) connected to the host computer, then inside the function getAllConnectedInterface, not all the non-mbed usb devices will be removed from the all_devices list because when device is removed, the index of items change and the iteration skips the next device it wants to remove. Hence, this will not remove a non-mbed device:

  #keep devices with good vid/pid
  for d in all_devices:
      if (d.vendor_id != vid) or (d.product_id != pid):
          all_devices.remove(d) #this will cause the next item's index to decrement and gets skipped

I fixed this by using a temporary list temp_devices to remove the devices from it while iterating over all_devices, and then pointing all_devices to temp_devices after removal:

#keep devices with good vid/pid
        for d in all_devices:
            if (d.vendor_id != vid) or (d.product_id != pid):
                temp_devices.remove(d)
                
        if not all_devices:
            logging.debug("No Mbed device connected")
            return
        
        all_devices = list(temp_devices)

Other than that, pyOCD works great!

Cheers,
Timothy Teh

I've used the python PyOCD gdb proxy. After uploading a file the KL25Z didn't react any more. Nothing, not even the MBED drive appears. I've tried to reflash the mbed_if_v2.0_frdm_kl25z.s19 File from windows: still dead. Unfortunately that happened to two (!) KL25Z of mine. So how can I get it alive again?

I've got some very draft support for using pyOCD to target stm32 via the stlinkv2 transport at https://github.com/karlp/pyOCD/tree/stlinkv2

There's a few impedance mismatches between mbed and stm32, but pyOCD is a much nicer smaller codebase to work with for flashing and gdb service than openocd!

So, erm, the github repo link needs updating to https://github.com/mbedmicro/pyOCD, then? Or... ?

If you want to use pyOCD on a linux system you need to add udev rules to set the permissions to allow users to access the USB device.

On ubuntu 12.04 I did the following:

Created /etc/udev/rules.d/mbed.rules with the content

SUBSYSTEM=="usb", ATTR{idVendor}=="0d28", ATTR{idProduct}=="0204", MODE:="666"

Then I restarted udev

sudo udevadm trigger

I am pretty ignorant when it comes to python, but I get this error on Win7 32 bit. I have tried a few different CMSIS-DAP devices and it doesn't look like it is finding them.

INFO:root:Waiting for a USB device connected