PaulStoffregen's latest activity

I know software and accessories aren't as exciting as new Teensy hardware, but my hope is to really focus more on those in this first half of 2026. After a 1.60 release, I'm imagining another gcc toolchain update. We'll need a newer toolchain...

We decided to skip RT1170 and wait for NXP's next generation RT chip. PJRC signed a NDA with NXP, so if I knew anything about NXP's future plans I wouldn't be able to discuss details that aren't yet on their public website.

You didn't divide the timer load value by the prescaler, you're trying to load it with 2.5e6 instead of 39061.

Sorry, I can't dig into this quadtimer code right now. But I can offer you known-good code that definitely does use quadtimer to create 30 Hz. If you want to dig into the quadtimer details, the implementation is in the core library pwm.c. void...

Indeed this thread is quite outrageous in terms of etiquette. For now PJRC is allowing this forum conversation to continue. For comparison, Adafruit's own forum allows only discussion of Adafruit products purchased directly from Adafruit or...

Quick followup, it was indeed a mistake "some codes applied in the background that shouldn’t have" at Mouser. They've fixed the problem.

You didn't mention which program you're using. Please test with something simple, like File > Examples > 01.Basics > Blink. Teensy has native USB, which is awesome because it's so fast and can become many types of USB devices. But it means the...

Might work with Teensy 4.1, where the bottom side pads are the USB device D+ and D-. But on Teensy 4.0 the bottom side D+ and D- are USB host, not USB device. Space is extremely limited on Teensy 4.0 and a lot of signals are made available...

Windows backwards compatibility is pretty easy. I personally don't use Windows and I'm no fan of Microsoft, but they do deserve credit for providing the very best backwards compatibility of any mainstream operating system. In that regard...

There has been drama between Adafruit and SparkFun. I'm not prepared to comment on any of this drama. I have also mixed feelings about whether to allow this forum conversation to continue, partly due to the fact this is heated drama which most...

So you've come here on the Teensy forum to advertise your new products meant to compete with Teensy?

Isn't this required by the constructor? How would it work with usbMIDI where we create a static instance by default?

First the easy part. With the audio shield you need to use AudioInputI2S. The best way to get started with the audio shield is this 31 page tutorial. https://www.pjrc.com/store/audio_tutorial_kit.html That page also has a 45 minute full...

Any chance the pink wire accidentally touched the red 12 volt wire? Looks like they connect to adjacent pins on a terminal block.

I think I figured it out. Hardware issues. The I2C and I2S pins are right next to each other and my messy breadboard construction seems to generate some crosstalk. I can make it worse if I bring the wires close together.

No. I'm not going to begin an investigation if I have to substitute something else which isn't confirmed to reproduce the problem. I've gone down that path many times before. It almost always turns out to be fruitless wasted effort. Even if a...

Confirm, I'm able to compile code from msg #6 in Arduino IDE. Now 1 step closer, but still need quite a bit of info to be able to reproduce the problem here.... Just to be realistic, to have any hope of getting to the bottom of what's really...

Even if I can compile the code and run it here on a Teensy 4.0 or Teensy 4.1, what else do I need to connect? Some sort of display is needed on the SDA and SCL pins, right? Is this an off-the-shelf item I can buy? Or is it something special...

How would I use this code to reproduce the problem? First, I tried copying into Arduino IDE. It doesn't compile. I get this error: sketch_jan03a:83: error: variable or field 'sendToDisplay' declared void 83 | void sendToDisplay(Packet...

I'm watching this conversation and struggling to form an opinion of how serious this matter really is. Please remember I'm not a musician. I'm depending on your feedback. I am much more interested in practical effects and compatibility with...

To specifically answer whether it is related to the audio library, I would need to know what "it" is. But I have pretty much no idea. All I know is the words you gave, "skip floating point arithmetic for a personal project and representing pure...

I decided to try out your setup, on a MAC that I just got some of the zephyr working on... Would have been easier with my windows setup, but thought this would be a good test Your app partially works. It is showing results on the three I2C...

Maybe the click sound is due to ground current flowing between Teensy and whatever other hardware you have connected to Teensy? It's easy to think of the 3.3V power fluctuating, and that can indeed be the problem. But since adding a capacitor...

Please understand I can only answer with guesswork. This new description helps, but I still know relatively little about the design of your CNC controller. If the problem consistently happens after the motor drives a mechanism to reach a limit...

Maybe you're experiencing a limit of USB power? But usually CNC machine controllers have a source of external power. Difficult to know if that applies here, since we have no specs or info about your specific CNC controller. Usually the first...

I've committed code to enable the glitch filter for I2C slave mode. https://github.com/PaulStoffregen/Wire/commit/1a69812fd6d6343134391074a200847ad47c82e2 Previously we were only using it for master mode. I did quite a bit more testing...

The SPI hardware can indeed do 24 bit frame size. Of course you have to use direct access to the hardware registers, since this isn't supported by the SPI library which aims for Arduino compatibility. Frame size is controlled by the FRAMESZ...

This is an Arduino IDE bug. Teensyduino 1.59 can't do anything about it, because it's in the software from Arduino and not any part Teensyduino provides.

HFW8R-1STE1H1LF Plenty are in stock at Digikey, Mouser, probably other places. For more detail, check out the parts list and other info on this page. https://www.pjrc.com/breakout-board-for-teensy-4-0/

This type of microprone has omnidirectional sensitivity. Pointing it in a different direction will give little to no useful effect.

I sent a message to SparkFun. Many of their people are on vacation this week. Mouser probably has a similar situation. We might not hear much until next week. The audio shield definitely is still being made and sold. It's not end of life...

This code can't harm your Teensy board. But wiring 3.3V power directly to a TRS connector is asking for trouble! This can go horribly wrong in a few different ways, some of which will just cause Teensy to reboot but others could result in...

Can you tell show us what actually happens? I'm really not getting a clear picture from only words "Led 1 works but not 2,3 and 4.." Maybe a quick cell phone video uploaded to youtube would help? You can set a youtube video to "unlisted" which...

You haven't said how long your wires will be, or what type of wiring you intend to use, but since you're wanting to connect 4 microphones my guess is you will want them spread apart by some distance so you're not just receiving 4 virtually...

Before I try to answer, please understand the only if I have is the photo you shared. I can't even know which MEMS mic is actually on that circuit board. If this answer isn't enough, please try giving a link to the product or a datasheet or...

Any chance you could make a test case that shows this LittleFS slowness? Or if not a complete program, at least describe the usage which led to this terrible result? I've recently had a few conversations with people who were surprised to hear...

Looking at this again... early Christmas morning before family time. Still a mystery why it sometimes works, but often fails with Linux "jstest /dev/input/js2". One thing is really becoming clear though. Linux does not transmit IN tokens to...

Indeed happy Christmas to everyone!

Yes, it really should work.

Thanks for trying. :) Deep diving into FlexSPI LUTs requires strong will and a brave heart!

In anticipation of the next question, when the referenced variable is local to the calling function, its memory will be temporarily allocated on the stack. That's why you see exactly the same number for RAM used for variables. A reference does...

I'm testing this now, and indeed it seems something weird is happening with Linux. To read the joystick, I'm running "jstest /dev/input/js2" in a terminal. Also watching with Arduino Serial Monitor using a modified copy of the Buttons example...

The memory test program tells you the configured clock speed. Until recently, we've used a pretty conservative default, about 88 MHz. 1.60-beta increases the speed to slightly over 100 MHz, but still well below 120 or 133 MHz.

Use #define MB ModbusRTUClient Then you can use MB.whatever

Normally the first way is used. It makes a copy of "toWait" which is used inside that function. The second function is indeed a reference, so it's actually using the "toWait" variable from the calling code. Usually this isn't done unless there...

Looks like slave mode handling of repeated start might also be broken on Teensy 3.2 and Teensy LC (the two I tested just now) and perhaps other older boards. Not planning to dive into those right now, just leaving this message to document this...

I've committed the fix on github. https://github.com/PaulStoffregen/Wire/commit/d0c447c63a6f1a6b6920b0d259778527761a7ebe Here's an updated copy of my test program that tries to emulate a 24C02 EEPROM chip with Wire and EEPROM libraries...

Just want to confirm I'm looking into this problem. I am able to reproduce it. Also looks like the onRequest handler doesn't have any way to detect when the master size replies NAK to end the transfer. As usual, no solution yet. Just...

Simplest way to check is measure the voltage on the Program signal which connects to your pushbutton. The bootloader turns on a built in pullup resistor to 3.3V. Measuring approx 3.3V (or whatever your power supply happens to be) is a sure sign...

My guess is this may be a link location problem (linking the wrong SD library even after compiling the right one) rather than a link order problem (correct library but given in different order on the linker command line). Any chance you could...