No crapware needed. In my case, id be happy with a stream of ASCII hex of each RGB (maybe RGBW) value if the data fit the time slice. Even throwing away every other pixel or some such subsample would still be huge for those developing led software that don’t want to test with miles of lights. The pio would have to keep count as there isn’t a “start bit” per byte. Once the drummer starts,. It’s one bit per N clocks. (Corrupting one bit is what turns these strings into a flickering mess.)
This is perhaps getting OT, but stuffing something approximately like
Into the project could be awesome. (Of course, seeing that project, I see it could also be done without BP but integrating it into sigrok and pairing it with a scriptable output would be big for this (tiny) market of devs. I just don’t really have a concept of how much headroom 2040 has while slurping an unforgiving 800Khz sample rate. Drift . 5% on a 10px strand is not big deal, but by the end of a. 1000px strand, you’re sampling the wrong sub-frame. The pio thing could probably bit bang (is the receiver version “bit slurp” or something? Since the strings can be long and the protocol is rarely able to be decoded and dmaed straight into ram.
Someone needs to do this (implement Neopixel receive) and I think it’s within my reach. I think I just talked myself into a project and will add one of these to my wish list. I’d thought about doing this with 'v003, but 2040 is such a better xhoice.
Oh, and of course, Bus Pirate needs HUB75 bus decoders. Later. I need that less. Unit testing Neopixel (et al) against known reference streams or renderinfg them into a web view for documentation would be lovely.
So I’m interested in helping with a ws2812 decoder, which I’m pretty sure we can pull off for at least a short strand and see where it goes from there.
(and the other message that was eaten by the mail response handler)
Re: hex dump and file editing.
Do we have curses? I’ve done tiny hex editors and vim clones in the past. I guess if you just nail the requirement to vt100 80x25, even building a “raw mode” curses (no FMLI) insnt THAT hard… Do the files all fit in RAM/mappings or do they need to be demand-paged?
If you’re willing to coach the design a little (e.g. “we don’t care about your VT-52 or ADM-3a”, " here’s how to do live monitoring without destroying the bus", “we officially don’t car about libe reload”, " file locking is critical ", etc.) I’m willing to do the carpentry on some features like that.
Sounds like we should indeed be friends.
I’d like to build a ws281x receiver.
I have relevant experience building file viewers and implementing “enough” of vi keystrokes in places where it “should not go” like kernel debuggers. Id help build either or both., esp if you have designs and/or UX mocks . (“Hexdump -C. Done”. Works for me…)
Show quoted text