Search results

This is awesome! Added myself to the tindie.com waitlist, so I hope you'll consider stocking more :D I've been looking at options to upgrade my light show from a Teensy 3.2 to a Teensy 4.0 or 4.1. This would give me a ton of room to expand and has the horsepower to run my show at 60fps (or higher).

Epic! Amazing work and craftsmanship!!

So glad I was able to help out! Have fun :)

Oh! If the Teensy 4.x buffers have a different data format, that might be the issue. Try this variation of the loop() code. It uses the setPixel function so that the OctoWS2811 library can populate the buffer correctly. void loop() { // Quickly check if next bytes are the header if...

Glad you found the code helpful! You've posted a good amount of info. Below is a stream of thoughts about what to take a look at: The first thing that jumped out to me was your table of channel addresses. I put your config into my spreadsheet and got some different channel numbers: For the...

I think you're right that it isn't the same issue since memory use is low and nothing seems to cross the boundary. In the case I had, the memcpy could be unaligned depending on the data coming from USB and would cause a hard fault in some cases, other times would lead to corruption that was...

I'm not sure it is what you're running into, but I ran into USB corruption with lots of data for WS2811 LEDs due to having a large array sitting across the SRAM_L and SRAM_U boundary at the 0x20000000 address. Check the memory placement in the symbol file to see if something is crossing over the...

Wow! That's quite the impressive build. Thanks for sharing!! I've been looking for examples of how much power the Teensy 4's have for WS2811s. I've been using a Teensy 3.2 to run ~2400 WS2811/2813s @ 58fps and this looks like a way to really push that up!

We're on CBS News!! https://www.cbsnews.com/live/video/20201029175350-how-to-safely-celebrate-halloween-in-the-era-of-coronavirus/

This looks very interesting and am looking forward to the details! BTW, the video you included is unavailable as it is private.

This might be a long shot, but it sounds like you might be using enough memory that you could have a variable (a large array) crossing the SRAM_L and SRAM_U boundary, which under some access conditions can cause a hard fault. Check the memory placement in the symbol file to see if something is...

I've been using a Teensy 3.2 with the OctoWS2811 board and library for the past few years to run much of my Halloween and Christmas light shows. This year, I reworked the code on the Teensy 3.2 to improve the frame rate of the show from 25ms / 40fps to 17ms / ~60fps for 3000 leds. I've shared...

I found that adding "__attribute__((aligned(2048)))" to the megaBuffer declaration did a good enough job of coercing the linker to keeping from placing it across the SRAM_L / SRAM_U boundary. With that fixed and some optimizations based on the movie2serial.pde code, I've been successfully...

I think I've been able to confirm the issue is related to the SRAM_L / SRAM_U boundary. In the sym file, it showed the megaBuffer was being placed just before the boundary and it's length would go beyond it. Adding a 5k dummy array cause the megaBuffer to move past the SRAM_U boundary at...

I've been able to pull my hardware (RPi4 & Teensy 3.2) onto my bench and setup hardware serial out to get some insight of what is going on when trying to do a large serial.readBytes. The short version is that, after much debugging, I think I'm running into a SRAM_L to SRAM_U boundary fault. I'm...

Can you post the code you're running on the Teensy 3? Your video looks similar to an issue I'm seeing with my ws2811 setup.

defragster, I did some testing using your code. The only modification I made was to setup() where I commented out Serial lines after qBlink and just set rCnt to 12408. I also switch to n = Serial.readBytes(megaBuffer + curItem, cntN ); in the loop. In one SSH window, I sent a single...

Thanks for the reply defragster! I gave your suggestion a try and still encountered more or less the same result, but it did get me to find a simpler repo and it might have provided, what I think is, a clue. While trying this out, I would typically see values of 1, 64, 65, or 128 being...

I'm using a Teensy 3.2 with the OctoWS2811 Adaptor, connected via USB Serial to a Raspberry Pi 4 running Falcon Player v3.3 (Raspbian based) to control 2378 WS2813 LEDs being updated at 25ms intervals. The Teensy & OctoWS2811 library are configured to run the longest string of 517 LEDs, so it is...