doctea

Well, there is one other longshot... The crash report that gets written when a program faults is located right at the end of RAM2. So in theory, if nothing else touches that memory in between (and the device stays powered), you could upload a new...

Ooh, I hadn't thought of that, thanks. Are there any neat tricks I could use to find likely suspects in my code/libraries? Almost everything I do in my own code is created with new during setup, so this will be a bit of a needle-haystack...

If you use C++ it may be crashing somewhere in a constructor for a static object. Besides commenting them out, you can use the builtin LED to see which ones are completing successfully.

I've been attempting to update from Teensy 4.17 to any later version, but somehow the resulting firmware crashes the Teensy before reaching setup() and without ever appearing as a USB device on the host, so I'm at a loss how to start...

I meant you might be able to send the SPI signals further than SDIO, but maybe not that far. Hopefully more hardware-savvy folks will comment, but for T4,0, for example, what I remember seeing is usually a piggyback board, so the signal distances...

SD using SDIO protocol on the built in SD socket uses 50 MHz clock. SD over SPI defaults to 16 MHz, but you can configure slower or faster speed. Slower clock is (probably) more forgiving of lengthy wiring. Adding series resistors on the...

If I were to use an external SPI SD controller, then I guess the best thing to do would be to send the SPI over the IDC from Teensy, have the controller and the socket at the end of the IDC, rather than sending all the SD pins over the IDC...

Just this at the Teensy end. The other end connects to a header on PCB that connects all the pins up to a PJS008U-3000 socket

Hi! I made a simple SD card extender board+cable in order to give easy access to the SD card when the T4.1 is mounted behind a Eurorack panel,. I've not done anything nearly as clever as stg reports, simply routing all the pins over uh-ohan...