Search results

Glad to be of help. I can't believe I looked at that statement so many times and missed that the color ordering field was missing. Ahh well, Glad I could be of help. Great to see pictures of projects others are working on! Cheers! and HAPPY THANKSGIVING! Regards, Karl Litterer AKA LitterBug

I tried to complile it on mine, but I am missing the library for the #include<input.h> . Do you know what library that you installed for that? EDIT: You need to add the LED color order to the initialization command. the "BGR" is currently missing. (or what ever order works correctly for...

Can you please provide everything in the error box? There can be other clues that we are not seeing.

Please paste your code between code wrappers. It is very difficult to help debug code otherwise. See picture:

If you are using the WS2812SERIAL library, you need to swap the FastLED.addLeds command with LEDS.addLeds // FastLED.addLeds<WS2812B, ledDataPin>(leds, numLeds); LEDS.addLeds<WS2812SERIAL, ledDataPin>(leds, numLeds); LB

When you paste code to the forum, it makes it easier to work with if you have it wrapped in code tags (use the # button above the text box) so we can make sure that we are not grabbing more than just the code, or that emoticons don't change the context of the code. There are two key places...

I modified the DemoReel100 to use the same initialization that is used in the Teensy WS2812SERIAL demo, and it works.

I get similar results. Works fine with one of my APA102 strips on the T4.1 Probably a timing issue with the standard FastLED WS2812 library running on the Teensy 4.x. Have you checked on the FastLED support forum? EDIT: I tested with the Teensy FastLED_Cylon demo, and that demo works...

Sorry if I was a little thick headed, but I have seen the light. :)

I think I see the error in my ways after a lot more digging. I think there is an easy workaround whether or not the vselect signal is output on the intended pin or not. There is nothing stopping someone from using a different pin for VSELECT in the SDIO/SDFat routines. The Teensy 4.0 does not...

Which is an internal signal handled by the IOMUX.

The IOMUX is an internal component of the CPU. it is NOT exposed. VSELECT gets set by writing to CMD6. The IOMUX does the the voltage change internally. For SDIO cards, the high speed mode/DDR50/SDR50/SDR104 are enabled by writing the EHS bit in the CCCR register after the SHS bit is...

Those are internal pins on the IOMUXC. Not exposed pins. The voltage selection and change happens inside the CPU via a configuration register.

The NXP reference board has the SD VDD wired the same to 3.3v, and pretty much the rest of the SD slot for that matter. No level shifter between the CPU and SDcard. The SDCARD SDIO reference says the supply voltage should be 2.7-3.6V The "signaling voltage" needs to switch to 1.8V for the...

It is handled internal to the CPU. no external hardware is necissary.

Just a quick update on my uSDHC / UHS-I / SDR104 findings. People over on the NXP forums have in fact run these iMXRT106x chips successfully at full UHS-1 specifications. There is a register that needs to be flipped that handles the voltage change from 3.3V to 1.8V. Some of my chicken...

OOoooo nice! I've been wanting to clean up my installs. Amazing how fast I get them polluted with excess stuff. Will throw it down on Ubuntu and W10.

From what I'm reading in the CPU specs and manual, That can be done using the SD/SDIO interfaces. Data sheets are here https://www.pjrc.com/teensy/datasheets.html High level DataSheet: https://www.pjrc.com/teensy/IMXRT1060CEC_rev0_1.pdf Deep dive Manual...

These numbers suggest we are using High Speed Mode (25 MB/s) 50mhz-4bit clocking and not UHS clocking. Wonder if the hardware can handle at least the slower 100Mhz UHS clock and 50MB/s. I won't beg for the 208MHz rate of 104MB/s... LB The CPU Spec sheet looks promising for even the higher...

I don't have any of the EVO Selects, but I have been doing my own playing and bench testing of cards on a 4.1, 1-54B4, with the Built in reader and FIFO_SDIO. All of these cards have worked. I can even read two "bricked" cards that nothing else seems to want to. (marked with X in bottom of...

@mwpaus I am like you just starting down the Teensy 4.1 path after picking one up the other day. I'm looking for the best SD performance I can get for various data logging, data replay, etc. So far it looks like the best write performance is around 20MB/s for a small handfull of cards I have...

Downloaded and installed 1.54 beta4, which fixed the compile errors on the SD test code above. Quick test on an older Samsung Evo 32GB Thanks for the tip! ... 230 MBytes 240 MBytes 250 MBytes Writing 256MBytes took 13.16 seconds For an average rate of 19.454 Mbytes/second Reading 10240...

Good to know. Where are the beta releases stored? EDIT: NVM Found them

Hi @mborgerson, I am new to the Teensy world after picking up a 4.1 recently but have been around Ardu, linux, unix, etc. for a long time. I am interested in running the SD bench you listed, but am having some issues getting it to comple it with AurduinoIDE. Curious if that version is for a...