Thanks Rene!
It's funny that I was kind of thinking about an approach similar to
what you suggested but I wasn't clued in enough to sort out exactly
how to execute it :).
Anyways, I tried what you suggested and had trouble getting it to
work. If I was more experienced with this stuff, I probably would have
been able to debug what was wrong.
I'm definitely closer though. Below is what I did. I think it's mostly
what you suggested in "()" at the end of your mail.
-Built the generic pulseview
-Ran new_driver in the libsigrok/build directory as you suggested
-Applied the patch created by this new_driver script as instructed in
the README created:
'cd /some/path/libsigrok'
'git am /some/place/0001-raspberrypi-pico-Initial-driver-skeleton.patch'
Of course, I used the actual paths for my environment :).
After this, I did have source files for the raspberry pi pico in the
"hardware" directory (in a directory called raspberrypi-pico)
-Edited the original build script to remove the rm of the $BUILDDIR
and the git clones. I also removed all the build directories under
each of the modules (e.g
sigrok-util/cross-compile/macosx/build/libsigrok/build). I know this
is a bit brute force :). I originally tried just running 'make clean'
but that didn't resolve the issue, so I decided to get a bigger hammer
:). It didn't help, obviously.
-Ran the modified script
Here's an example of a section of the script that makes libserialport:
# libserialport
#$GIT_CLONE $REPO_BASE/libserialport
cd libserialport
./autogen.sh
rm -rf build
mkdir build
cd build
../configure $C
$SB make $PARALLEL $V
make install $V
cd ../..
The rest of the sections are similar.
So, pulseview does now build and it also runs (yay :)). I can start it
up, get a GUI, and monkey with it. The issue is that when I try to
"connect to device", then try to select the driver (from the GUI), the
new driver doesn't show up in the list. I see a bunch of other
drivers, but not the raspberrypi pico one. However, I do see it listed
as an "Enabled hardware driver" in that section of the build script
output. Perhaps I'm missing a step to allow my new driver to be
selected in the GUI?
Note that do get this error at the end of the build:
----
Running tests...
Test project /Users/dan/sigrok-util/cross-compile/macosx/build/pulseview/build
Start 1: test
1/1 Test #1: test .............................***Failed 16.15 sec
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 16.16 sec
The following tests FAILED:
1 - test (Failed)
Errors while running CTest
Output from these tests are in:
/Users/dan/sigrok-util/cross-compile/macosx/build/pulseview/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
make: *** [test] Error 8
-----
I was getting this before I tried to install the new driver. I decided
to ignore it for now. But, I would also like to fix this too.
Thanks,
Dan
----
On Mon, Jun 13, 2022 at 9:13 AM Rene Kita <m...@rkta.de> wrote:
>
> On Sun, Jun 12, 2022 at 11:52:42AM -0700, Dan Crocker wrote:
> > Hi All,
>
> Hi Dan!
>
> > Forewarning...
> Forewarning, the following is untested.
>
> > I'm a novice at all this. I am an engineer, but a hardware/system one.
> > I have very little experience with software and related tools.
> >
> > I'm attempting to add a driver for the Pico to Pulseview on OSX (12.4,
> > Monterey). I've managed to get the latest release of Pulseview to
> > build using the sigrok-native-macosx script (the homebrew approach
> > described here:
> > https://sigrok.org/wiki/Mac_OS_X
> >
> > I'm now attempting to follow these instructions:
> > https://github.com/pico-coder/sigrok-pico/blob/main/SigrokBuildNotes.md
>
> Skip steps 1 and 2. Do step 3 in the 'build' directory created by the
> sigrok-native-macosx script. Do step 4 and 5, skip the rest.
>
> - 'cd libsigrok/build && make'
> - 'PYPATH=$PREFIX/lib/python2.7/site-packages make install'
>
> Go into the sigrok-cli and PulseView build directories and use 'make;
> make install' (maybe a 'make clean' before).
>
> Done (I hope)!
>
> If this doesn't get you going, report back.
>
> Caveat: If you run the sigrok-native-macosx script again you have to add
> the driver again as this scripts removes the repo and clones it again.
> (You can make a version without this behaviour by removing lines 67-70,
> removing the 'git clone' and mkdir stuff.)
>
> > Dan
> Rene
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
