Sigrok folks, Since. Y first email to this group, I’ve come a long way with better understanding how to create a new driver for libsigrok. I just issued a pull request for the TinyLogicFriend driver, to be able interface sigrok/PulseView with a widely available microcontroller development boards that can act as logic analyzers. https://github.com/sigrokproject/libsigrok/pull/137
The key novelty of this driver is that rather than defining the capabilities in the driver code, the driver instead scans the board to get its capabilities. I have selected a SCPI command set that communicates over USBTMC to get the capabilities from the device (pin names, trigger types, sample rates, etc). I hope that this TinyLogicFriend libsigrok driver is sufficiently generic to allow for interfacing with a wide array of affordable microcontroller boards. I have demonstrated the basic functionality by decoding I2C signals using Adafruit’s Arm Cortex M4 development boards. I have created .UF2 files of the logic analyzer firmware that can be copied to boards. https://github.com/kmatch98/tinylogicfriend The code is organized to be able to expand to other boards and chipsets. If anyone has feedback or suggestions, please feel free to email me directly (ksmato...@gmail.com) or respond to the pull request on GitHub. These email archives and all the hardware drivers were a great help to me to learn about using and developing for sigrok. I hope that this driver can give a little back and allow for broader use of the capabilities of sigrok and PulseView. Best regards, Kevin (kmatch) > On Mar 30, 2021, at 6:27 PM, Kevin Matocha <kmato...@ieee.org> wrote: > > Sigrok community, > > I’m brand new here, taking on a new challenge to extend my hardware/software > skills and work to enable using an array of Adafruit boards as logic > analyzers. I’m taking a look at further developing the concept of the > “TinyLogicFriend” that was proposed started here: > https://www.youtube.com/watch?v=qetJHmfNA_g. The concept is to create a > sigrok driver that can interface with a wide array of boards (collect meta > data with pin names, etc), and then create the firmware for each board that > can be easily downloaded that will allow it to talk to sigrok. > > I’m in the process of configuring to build the drivers on my local machine. > > I’ve read through the wiki but have struggled to build all the components on > my Mac (running Big Sur MacOS 11.2.3). I was able to build libsigrok but with > warnings about missing C++ bindings. The sigrok-cli also builds, but > PulseView will not build. > > Before I deal with the specific build issues, my main focus is to develop the > hardware drivers (defined in libsigrok). If I can build libsigrok, can I > interface my compiled libsigrok to the pre-built nightly image build of > PulseView? If so, what are the steps to get PulseView and sigrok-cli to > interface with my new build of libsigrok? > > Any insights will be helpful. If I do have to build PulseView to nororate mew > drivers, I hope you will not be bothered if I request pointers and guidance > on how to get it to build on my Mac machine. > > Kind regards, Kevin (kmatch) >
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
