Help with setup LED WS2812 + Adafruit rp2040 scorpio + raspberry pi 5

[freestaila]

Hello. Please help me with my setup. I tried with everything. I have raspberry pi 5 with pi OS. SPI enabled, Adafruit RP2040 Scorpio, WS2812 led strip.

I connected A0, A2, A3 port from rp2040 to pi. LED strip data is connected via GPIO16. I forked repo to build uf2 with that port.
It looks like scoprio is detected by hyperhdr but led strip displays all the time same led colors and only few first without any symptoms of being controled over scorpio.
Scorpio is connected via USB to pi. Common ground between scorpio and led is also connected. LED is powered by power supply 12v 60w and Im using stepdown to set 5v output.
All devices are new. I verified that led have power all over strip and I was able to use python program to turn on full strip directly connected to pi.

Please give me a tip what else I can check. I really dont have any idea.
logs.txt

[awawa-dev]

Hi
Please do not upload the logs directly but use pastebin service: otherwise it creates a mess here. You dont need to compile a firmware for a standard single segment setup: there is a dedicated firmware for scorprio in the release section. SPI communication is stale-less so you wont see any error. The only available diagnostic path is serial connection as described on the main page.

More picture how my cable connector looks like are on the main page, so my red cable is going to SCKL pin on Rpi.

[awawa-dev]

If you want to dig deeper then you must acknowledge that Scorpio has different pin-out that is described on the main page. And you need to change more than GPIO for LED output but also select proper GPIO for SPI. And what you select on the first screen GPIO14 is for itsybitsy: I though that / separator in the column label is clear and why I would release a firmware for Scorpio with not functioning GPIO14 but well...

and the rest of your SPI settings points nowhere on Scorpio but they were described in that table clearly both for Scorpio and ItsyBitshy:

That why it didn't have any chance for work. Just take the release firmware and perform test exactly as it's described. It should work or at least have a communication in the 'screen'.

[freestaila]

Yes, it's clear now with the GPIOS. My mistake. I connected all like you on image. I verified using screen however screen is blank. Device is discovered.

[awawa-dev]

The output is only available when you perform the test exactly as described: it needs the LED device to be disabled & enabled again. Try it few times.

[freestaila]

I installed fresh soft for Scorpio and fresh hyperhdr. Performed tests as on main page however still screen not showing anything. Is my schema showing correct connections? Please let me know what more I could do.

[awawa-dev]

Which exactly firmware did you upload? What are your current LED driver settings in HyperHDR?

[freestaila]

HyperHDR 21 version
HyperSPI - https://github.com/awawa-dev/HyperSPI/releases/download/v9.0.0.0/Adafruit_Feather_RP2040_Scorpio.zip

My steps:

1. Enable LED device
2. Remote control -> colors/effect -> choose efect
3. Wait until on Overview page in section Performance I can see that Pico device is visible
4. Disable LED device
5. use test command " screen /dev/ttyACM0 115200

My LED hardware setup:

[awawa-dev]

Could you take 2 pictures each of how the cables are connected to RPi and Scorpio? This one picture doesn't look clear enough for me to verify it.

in section Performance I can see that Pico device is visible

This is irrelevant for HyperSPI, as it use serial port only for debug log. And did you enable continues output when you tested it? without it there will be no continues output, just one frame.

[freestaila]

Continuous output is enabled

[awawa-dev]

Thank you. The connection looks OK. I've just tested the firmware ws2812 from this release package with new cables and Rpi5 and Scorpio rp2040 and it started immediately to work under screen /dev/ttyACM0 115200 and HyperHDR v21 (BTW tested also v22beta and it also works fine):

So what's left? One of your cables is not making contact, or you have cold solder joints on some pins on one or both boards. Worst-case scenario: a fried GPIO on the RPI5. Unfortunately, you can't diagnose this without an oscilloscope, so at least make sure you have continuity between the GPIOs on the other side of the boards using, for example, a multimeter in continuity mode.