pico 2040 multi segment second data pin

[4rkhaon]

I can't find an option in cmakelists, where can i choose a pin for the second segment?

[awawa-dev]

it's LED output + 1

[4rkhaon]

Thanks that is exactly what I needed to finish setup. Hugely appreciative of your work!

[ender]

So, I’m using the ItsyBitsy, GPIO14 is the default, but that’s because that’s the one with 5V output, unless i’m misunderstood? Before I start, I just wanted to ask if pin 15 is still suitable for multi segment control with HyperSPI on the RP2040 ItsyBitsy

[awawa-dev]

I dont consider RP2040 ItsyBitsy as capable of multi-segment because of the single 5v data output. Pin 15 or GPIO 15? GPIO 15 should be fine unless it's not connected to the pin header or it's used for other purposes - you must consult the product specification.

[poundlane]

Hi, Im trying to add second segment on an rp2040 scorpio, Im sorry im new to this, I just dont understand your answer - where do I define pin for segment in cmakelists, all I can see is the index setting. ? thanks!

[awawa-dev]

on your fork in this file: https://github.com/awawa-dev/HyperSPI/blob/master/rp2040/CMakeLists.txt

[poundlane]

Hi, Thankyou very much for your reply. I have looked and read everything I can find on how to configure 2nd segment on RP2040. Perhaps Im not able to do what I am attempting. In summary I have configured an initial segment on NEOPIXEL0 GPIO16 no problem, works great. I want to configure a 2nd segment, and I think I understood your answer to be that if I connect the LED Data pin to NEOPIXEL1 GPIO17, that would do the trick. I have not defined that GPIO in CMakelists.txt, It only seems to have definitions for Default on 16 and the Index. Would appreciate any pointers you can give me, happy to look at some documentation, but cant seem to find any details for this setup on rp2040, though there is detail on this for the ESP boards, updating platformio. Thanks again, and sorry if these are basic questions, Im learning as I go. Regards...

[awawa-dev]

Hi
This isn't explained in the documentation, but in this thread, which you also found. In the case of the rp2040, after activating the second segment (SECOND_SEGMENT_INDEX), its output for the second segment is always 1 higher than the GPIO of the first segment (OUTPUT_DATA_PIN). You don't need to define anything else.

[poundlane]

Thankyou for confirming, it seems I have the software configuration right as far as I can tell. I'm not getting a response from the 2nd output pin - I'll recheck all the wiring etc again. Thanks again!

[awawa-dev]

You must have correct LED geometry set in HyperHDR and proper compiled firmware to make it work with SECOND_SEGMENT_INDEX dividing LEDs you configured in HyperHDR LED geometry into two equal sub-segments. You can also test it using HyperSerialPico (https://github.com/awawa-dev/HyperSerialPico?tab=readme-ov-file#default-pinout)

[poundlane]

Hi again, Ive checked all that and can report I found my error, I had everything configured ok, BUT, I picked the wrong compiled artifact, pico instead of feather/scorpio! Sorry!. So the second pin with second strip now works fine. However not in parallel, around the whole TV twice in same direction. Ive come across another thread/question which seems to advise a bit on this so I'll explore this and try my best to figure out how to configure the two strips for this use case - I'm thinking from reading its more to do with HyerHDR LED config of multiple strips?, than the index/direction on the pico feather code?. Just need to experiment with where the index of strip 2 needs to start, 1 or strip1length+1 then configure manually in HYPERHDR ....Thankyou so much, Im appreciative of your work, and kind support.

Other discussion thread here!: https://github.com/awawa-dev/HyperHDR/discussions/668