bmp enhancements; swo support about cortex-debug HOT 10 OPEN

I have been working on this, but currently I'm running into an issue with the libusb library for node where I'm either getting lost data and/or significantly delayed data. Once I can get past that issue it should be fairly quick to complete. Going to try to have another look at this in the next couple of weeks.

from cortex-debug.

This is on my radar. From the description on the BMP wiki it doesn't sound too difficult for the basic logic (although I haven't looked into the actual code of it, either for Orbuculum or the example linked on the wiki, because of the licensing issues; although I have been reading your blog with great interest). Unfortunately it is a bit more difficult than it would appear because of the Visual Studio Code environment.

The need to do raw access to the USB device, via libusb, presents some difficulty. The JavaScript environment for extensions causes issues as it doesn't naturally expose direct access to USB devices (like it does for Network sockets or file access, used for J-Link and OpenOCD respectively). While I can in theory add binary modules for extending the capabilities (as I have done for the serial port mode) - I haven't yet been able to build a libusb module that is compatible with the VS Code environment. Once I have that roadblock sorted out, then I will likely work on adding native support for SWO from BMP (at least on platforms where I am able to get the module built).

from cortex-debug.

from cortex-debug.

I did make some progress on this item - but isn't ready for release yet.

Was able to get the binary module I need for VS Code compiling (at least on Linux and OS X; haven't figured it out for Windows).

Still running into some issues with getting the data off the device reliably. Not sure if it is an issue with the library, or a mistake in how I'm trying to use it (haven't done much with USB programming on either host or device side, so need to look into it more).

If for example - I try to read 64 bytes off of the end point with a timeout of 100 milliseconds (particular values don't actually matter) - if at least 64 bytes were available then they get read off the device and processed properly. If the full 64 bytes weren't available then whatever data should have been collected seems to disappear completely and will never be received.

Since I can't predict the exact speed that data will be available I run into problems (if I try to read faster than it is available it seems to disappear, but can't go slower than it is available as obviously buffers will fill up).

Don't know if you encountered anything like that in your work?

from cortex-debug.

Hi, the SWO support is now officially in the BMP, and having access to this would be really good!
Instructions for the SWO: https://github.com/blacksphere/blackmagic/blob/master/UsingSWO

I have hardware and can test if there are additions that need testing.

from cortex-debug.

Looking forward to SWO support for the BMP, this could be useful both in our research projects and in education (where we promote vscode + cortex debug). Overall impressions from the students are good, BMP might be another step forward.

from cortex-debug.

from cortex-debug.

Hi,
Any progress/updates ?

from cortex-debug.

Hi,
has anyone made it work (native or alternative way)?
I get a "SWO support is not available from the probe when using the BMP GDB server. Disabling SWO." error message.

from cortex-debug.

Take a look at orbuculum, it'll do what you want. @Marus the code has nowadays be librified so would hopefully be easier to incorporate, and I'd be very happy to see it in there. Opencd and pyocd both have native orbuculum support now (see instructions in the orbuculum readme). bmp always did have.

from cortex-debug.