Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLCapture 'capture' mode returns all zeros. All 3 UF2s, Windows and RasPiOS workstations, usb-serial and network connections. #138

Open
gusmanb opened this issue Sep 9, 2024 Discussed in #137 · 0 comments
Labels
bug Something isn't working

Comments

@gusmanb
Copy link
Owner

gusmanb commented Sep 9, 2024

Discussed in #137

Originally posted by DeeJay September 9, 2024
I can see that CLCapture has been available for over 2 years, so I may be misunderstanding how to use it.

Whatever I try, I get a .csv where all rows and all columns (other than the first row of channel names) contain Zero.

Testing with current V5.1 released code.

Tried with basic Pico and the appropriate UF2. Also with a PicoW and both variants of UF2 firmware.

Tried with CLCapture on both RasPiOS (Debian arm64) and Windows10 workstations.

The Pico running the LA firmware is being fed a serial UART message on its Physical pin #15 - LA Channel #14. Running the graphical LA app correctly acquires the input signal. The arguments supplied to CLCcapture are intended to be those that are used to configure the acquisition in ./LogicAnalyzer.

If I disable the serial signal generator so there is no test signal the LA does not start the capture until I enable to generator source, so I am confident that the Trigger data is being applied to the correct pin (Pin 15, Channel 14) on the Pico.

Where supported by the PicoW firmware I have tried both usb-serial and tcp/ip network connections from the workstation to the Pico.

A typical invocation of CLCapture looks like this -

C:\Users\David\Downloads\ClCapture-5.1.0.0-win-x64\win-x64>CLCapture capture COM4 500000  10,11,12,13:Null,14:Serial,15,16,17 512 8192 0 TriggerType:edge,Channel:14,Value:1 capture.csv
Opening logic analyzer in COM4...
Conneced to device LOGIC_ANALYZER_PICO_V5_1 in port/address COM4
Starting edge triggered capture...
Capture running...
Capture complete, writting output file...
Done.

(This isn't urgent for me. I don't HAVE to be able to generate a .csv of the data. This is largely curiosity to compare LogicAnalyzer with the two other Sigrok-based Pico LA solutions I am aware of.)

{edit: added later... }

It seems to be a regression failure. The capture works as expected with the Pico .UF2 and Win10 CLCapture.exe at Release v2.1.1.0 Jan 2023.)

@gusmanb gusmanb added the bug Something isn't working label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant