search

pico-coder / sigrok-pico

Use a raspberry pi pico (rp2040) as a logic analyzer and oscilloscope with sigrok
814 stars 92 forks source link

RP2350 Rev A Deadlock #55

Open spit4520 opened 1 day ago

spit4520 commented 1 day ago

Hi Everyone,

I have tried making some tweaks to force the Pulldowns to be disabled on all of the GPIO pins for the Pico 2, but to no avail. I haven't been able to read any data in from my Pico 2, the system will dead lock with the following:

./sigrok-cli-NIGHTLY-x86_64-debug.AppImage -d raspberrypi-pico:conn=/dev/ttyACM0 -C D2,D3,D4 --samples 100 -c samplerate=50000 -O ascii:width=80:charset='_"\/' sr: serial-libsp: Error setting serial port parameters (110): Connection timed out. sr: srpico: 1st serial open fail No devices found.

When I run the same modified code on the original Pico, I am able to successfully take a trace:

/sigrok-cli-NIGHTLY-x86_64-debug.AppImage -d raspberrypi-pico:conn=/dev/ttyACM0 -C D2,D3,D4 --samples 100 -c samplerate=50000 -O ascii:width=80:charset='_"\/' sr: srpico: Drain reads sr: srpico: Drain reads done libsigrok 0.6.0-git-f06f788 Acquisition with 3/24 channels at 50 kHz D2:________________________________________________________________________________ D3:"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" D4:________________________________________________________________________________ T:^ 0 D2:____________________ D3:"""""""""""""""""""" D4:____________________

I don't really know how else to patch this out, perhaps there are other underlying issues with the new Pico 2 chip?

TimoNotThy commented 18 hours ago

How did you get the pico 2 to connect? I've tried on fedora but it wouldnt work for me. Did you install any seperate drivers?

pico-coder commented 12 hours ago

I haven't bothered to buy a PICO 2 because the changes weren't all that compelling (still 12Mbps USB). and having latched up GPIOs doesn't help the case either. But a few things that come to mind: 1) Make sure the device shows up via lsusb when you plug it in. 2) Sometimes putty or terraterm etc. do a better job creating a serial connection. You can send an "i" to the device and see if it responds. 3) When you rebuilt the uf2, did you specify the build for the 2350? (I could be wrong, and haven't bothered to look, but it's reasonable to assume that some kind of device specific code of the rp2040 doesn't match the 2350.?)

pico-coder commented 12 hours ago

Also, gusmanb (https://github.com/gusmanb/logicanalyzer ) under the "born dead" section seems to imply that the pull up situation makes a PICO 2 useless as a logic analyzer. I can't confirm or deny the analysis, but I'd at least recommended reading the Errata from raspberry PI and seeing if you agree before trying further.

pico-coder commented 12 hours ago

See also https://forums.raspberrypi.com/viewtopic.php?t=375954 from Dr. Gusman

spit4520 commented 12 hours ago

Hi Pico-Coder/Sigrok-Pico,

I built the firmware for the PICO2, the interest in using it would be to port and embed the firmware in a signed encrypted flash embedded in our product to take PCAP files in the field or raw trace files to diagnose issues. The 2354A is a co-processor to our main application, and in the debug mode it will act as a debug probe. I can see a lot of use for an application like this in early IoT applications until the first generation or two have worked out a lot of the kinks.

I checked Errata 9 and we have A2 revision parts, I may have misread the documentation but I thought we could get around the issue by disabling the internal pull ups and pull downs?

Grateful for any feedback,

Scott

On Tue, Dec 3, 2024 at 12:53 pico-coder @.***> wrote:

See also https://forums.raspberrypi.com/viewtopic.php?t=375954 from Dr. Gusman

— Reply to this email directly, view it on GitHub https://github.com/pico-coder/sigrok-pico/issues/55#issuecomment-2515229344, or unsubscribe https://github.com/notifications/unsubscribe-auth/AESOJ7PWLPPK7KE5PKTQ4CL2DXVYJAVCNFSM6AAAAABS42OHCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJVGIZDSMZUGQ . You are receiving this because you authored the thread.Message ID: @.***>

pico-coder commented 8 hours ago

Again, I can't confirm or deny the Errata issue, but assuming that isn't a problem, the next step is to ensure the device does show on an "lsusb" and that you can establish a serial connection to it -either with putty/terraterm etc or just a sigrok-cli scan.