OK, so it's putting queue_buffer in RAM2, not EXTRAM (aka EXTMEM). Looking at the source, this seems correct, so not entirely sure if I have your current (troublesome) code. Forcing it into EXTRAM still works, yes.
OK, switched back to the released version of cores, and this is what I get:
Memory Usage on Teensy 4.1:
FLASH: code:103648, data:160952, headers:8804 free for files:7853060
RAM1: variables:282912, code:98600, padding:32472 free for local...
Yes - if you could shave >=296 bytes off the code or variables then you’d have low padding and more stack space. Then again, 110,304 should be easily enough for any sane application!
If I recall correctly it was quite hard to nail down the point...
There were some startup issues fixed from 0.60.5 onwards which sound very much like this. They manifested as red LED blinks after flashing new code (8 could be the number…), but apparently minor changes could make them disappear … until they came...
I was commenting about the subassembly behind the glasses. The foreground wiring is still a mystery … four neat bundles but no clue as to their source or destination.
It would reduce emissions and pickup, but I’d be a bit surprised if it made a...
The existing driver can be made to work without the I2C multiplexer used to allow 4 devices on a TDM bus. You need to edit this line. And the associated examples should give you a starting point for a simple test, though obviously they’re aimed...
Is that your typical SD card wiring hidden behind your glasses? You might want to try putting series resistors in SCLK, MOSI and MISO. 100R is a good start, but somewhere in the range 47R to 220R ought to work. They’ll reduce ringing on the fast...
You might want to read through this thread. Lots of information there, and the final boards work well.
Your issue may well be the requirement for an inverted BCLK. @palmerr elected to take the hardware option, but it’s possible to flip a...