awawa-dev / hyperserialpico Goto Github PK

Sorry, resolved.
Wrong GPIO connected.

Hello,
Since the “Adafruit ItsyBitsy RP2040” is mentioned as a one lane output, would “HyperSerialPico_Spi.uf2” work on “Adafruit ItsyBitsy RP2040”, with the DATA on GPIO 3 and CLOCK on GPIO 2 with the SPI WS2801 LEDs? Or should I compile differently?
Adafruit ItsyBitsy RP2040 pinout.pdf

WebOS 4.5 - v5.30.40
HyperHDR installed onto tv directly

Log from HyperHDR:

dmesg log on TV:

[  278.271523] usb 7-1: USB disconnect, device number 2
[  281.040496] usb 7-1: new full-speed USB device number 3 using ohci-platform
[  281.269488] usb 7-1: New USB device found, idVendor=2e8a, idProduct=000a
[  281.269503] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  281.269509] usb 7-1: Product: Pico
[  281.269514] usb 7-1: Manufacturer: Raspberry Pi
[  281.269520] usb 7-1: SerialNumber: E6614C311B4FC726
[  281.273810] cdc_acm 7-1:1.0: ttyACM0: USB ACM device

lsusb:

Bus 005 Device 002: ID 043e:3109
Bus 007 Device 003: ID 2e8a:000a
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0002
Bus 005 Device 001: ID 1d6b:0002
Bus 006 Device 001: ID 1d6b:0001
Bus 007 Device 001: ID 1d6b:0001
Bus 008 Device 001: ID 1d6b:0001

Tried two different RP2040s with no change (one is an RP2040W original, the other is a Pimoroni Plasma 2040W).
Using the latest HyperHDR v20beta and HyperSerialPico

HyperHDR set with rp2040 handshake, and to ttyACM0.

The only thing I can see is that ttyACM0 is linked to cdc_acm 7-1:1.0. But based on lsusb, it should be 7-1:1.2?

hey,

just flashed the "HyperSerialPico_sk6812Cold.uf2" onto a Raspberry Pi Pico,

a "Reset" Device appeared after the Flash in the Device Manager under "other"

Device itself gets Recognized in HyperHDR v20beta

2023-05-09T13:08:18.388Z [LEDDEVICE_ADALIGHT] Opening UART: COM9 2023-05-09T13:08:18.388Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:216) _rs232Port.open(QIODevice::ReadWrite): COM9, Baud rate [2000000]bps 2023-05-09T13:08:18.390Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:221) portName: COM9 2023-05-09T13:08:18.390Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:222) systemLocation: \\.\COM9 2023-05-09T13:08:18.390Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:223) description: Serielles USB-Ger�t 2023-05-09T13:08:18.390Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:224) manufacturer: Microsoft 2023-05-09T13:08:18.390Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:225) productIdentifier: 0xa 2023-05-09T13:08:18.390Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:226) vendorIdentifier: 0x2e8a 2023-05-09T13:08:18.390Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:227) serialNumber: E66138935F287729 2023-05-09T13:08:18.415Z [LEDDEVICE_ADALIGHT] Detected Rp2040 type board. HyperHDR skips the reset. State: 0, 0 2023-05-09T13:08:18.496Z [LEDDEVICE_ADALIGHT] ESP sent: 'HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem1: 0, mem2: 206, heap: 124256' 2023-05-09T13:08:18.496Z [LEDDEVICE_ADALIGHT] ESP sent: 'RGBW => Gain: 255/255, red: 160, green: 160, blue: 160' 2023-05-09T13:08:18.496Z [LEDDEVICE_ADALIGHT] DETECTED DEVICE USING HYPERSERIALESP8266/HYPERSERIALESP32 FIRMWARE (Welcome! Awa driver 9.) at 1 msec

Hi,

is the max. baud rate 2Mbit/s oder can you go higher with these picos?
I switched from my ESP8266 and I did not change this value, but I am wondering if I should...

I am using the 2040 with level shift :-)

Mayby you could add that information in the readme.md as well :-)

Trying this out on Windows.
Followed instructions for flashing and configuration.
Does not seem to detect the device via the COM Port.

2023-06-16T20:39:15.310Z [LEDDEVICE_ADALIGHT] Opening UART: COM4
2023-06-16T20:39:15.310Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:216) _rs232Port.open(QIODevice::ReadWrite): COM4, Baud rate [200000]bps
2023-06-16T20:39:15.311Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:221) portName:          COM4
2023-06-16T20:39:15.311Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:222) systemLocation:    \\.\COM4
2023-06-16T20:39:15.311Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:223) description:       USB Serial Device
2023-06-16T20:39:15.311Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:224) manufacturer:      Microsoft
2023-06-16T20:39:15.311Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:225) productIdentifier: 0xa
2023-06-16T20:39:15.311Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:226) vendorIdentifier:  0x2e8a
2023-06-16T20:39:15.311Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:227) serialNumber:      E6616408432Fxxxx
2023-06-16T20:39:16.630Z [LEDDEVICE_ADALIGHT] Could not detect HyperSerialEsp8266/HyperSerialESP32 device
2023-06-16T20:39:16.630Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:333) Switch on
2023-06-16T20:39:16.630Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:409) Power On
2023-06-16T20:39:16.631Z [COMPONENTREG0] LED device: enabled
2023-06-16T20:39:17.633Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:300) Timeout after 1000ms: 0 frames already dropped
2023-06-16T20:39:18.634Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:300) Timeout after 1000ms: 1 frames already dropped