PaulStoffregen

If you want me to investigate, please post another complete program to demonstrate the problem. Even if the change from the code you showed in msg #5 is trivial, I need you to understand I have a long history of wasting time not able to...

For the sake of testing, I'd try allocating many more blocks, like 100. Then if you see your usage is in the 90s, you'll know one or more of the queues is hogging memory.

Try using AudioMemoryUsage() to monitor how many of the 10 audio memory blocks are used up. Or use AudioMemoryUsageMax() to check whether you have at any point used up all the memory. My guess, admittedly from only a quick glace at your code, is...

To configure the input pins, you'll need to write to the mux registers and also the select input registers. IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_02 IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_03 IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_04...

One small gotcha... before you access any of the GPT2 registers, enable its clocks by setting the CCM_CCGR0_GPT2_BUS and CCM_CCGR0_GPT2_SERIAL bits in the CCM registers.

Some pin mapping info which might help: GPT2_CLK is on pin 14 (AD_B1_02 mux = ALT8) GPT2_CAPTURE1 is on pin 15 (AD_B1_03 mux = ALT8) GPT2_CAPTURE2 is on pin 40 (AD_B1_04 mux = ALT8) - Teensy 4.1 only

Quick answers I believe the GPT timers might able to do this. In the reference manual, see Figure 52-2 on page 3015, and section 52.3.1 on page 3016. The GPT timers are also 32 bits wide, which is much simpler than dealing with only 16 bits...

I don't see any connection in this diagram between Teensy and the dual motor driver. Assuming there is indeed a connection for Teensy to control the motors, check the GND wire. Perhaps GND is not properly connected between them? And maybe that...

Usually when that happens to me its the wiring. On quick review looks like you have RST got to 3,3v so either have RST set to 255 or hook it up to pin 3. Looks like you have pin 3 going to one of the touch pins? I would start by not hooking up...

Each open source library has license terms which allow you to the use the code. Usually this can be found in the comments at the beginning of the code. Some have a separate license file. I need to emphasize the official word is in those...

Basically, luck. As I tried to explain on that other thread, the U2 chip is never meant to be desoldered and used this way. The behavior is undefined. It might work, might fail, might partially work, might be unreliable.

Does "bootloader chip from a teensy 4.1 dev board" mean you desoldered and reused the chip from an actual Teensy 4.1 circuit board, or you purchased this T4 bootloader chip? Either way, 2 blinks means the JTAG connection is not working at all...

Would love to show this on the website. Any chance for a photo showing the hardware connection with MicroMod and with Teensy 4.1?

Article posted on the website https://www.pjrc.com/debugging-with-visual-micro/

Was this circuit board ever built? Do you have any photos, especially any photo or video of the LEDs in use?

Quick followup on this old project... is it still in development, or was it replaced with Microcosmos?

Thanks for measuring the high-res sine wave! I've often idly wondered this. Turns out the linear interpolation on table lookup is pretty good. Would be interesting to know if the excessive Taylor Series approach make a difference with a higher...

This sounds like a really awesome project. I want to help, but to give specific electronics troubleshooting advice requires seeing a lot more detail. Photos and schematics or clear diagrams are best. Small but complete test code also really...

Posted to the website today https://www.pjrc.com/fancy-pc-fan-controller/

Teensy 3.2 is discontinued. Some people still want them for old designs, where paying 3X or even 10X the original price might be less bad option than having to update or redesign. This is especially true for applications where the original...

I'm guessing you've already seen section "Power Up Sequence" on this page. https://www.pjrc.com/store/ic_mkl02_t4.html Difficult to guess what happened with your board. Perhaps pin 4 on the voltage regulator was the issue? Normally U4 is...

4 blinks usually means a problem with the crystal. Details here (scroll down to "Troubleshooting & Diagnostic Blink Codes") https://www.pjrc.com/store/ic_mkl02_t4.html

The red LED blinks in several ways. If you are seeing a slow steady blink (on time same as off time) repeating continuously (no pattern of blinks separated by a longer time with the LED off), this means your Teensy went into bootloader mode but...

I copied your code into Arduino IDE. But it does not compile for Teensy 3.6 or Teensy 4.1. Error is regarding use of Keypad library. Maybe you're using an old copy of Arduino IDE or Teensyduino? Or perhaps some other software?

Posted on the website today https://www.pjrc.com/software-defined-radio-transceiver/

Since a Teensy 4.x is so fast, I would add a delayMicroseconds(1); after the clockpin going low as well, like so: uint32_t SPIencoder::readRegister(void){ // Initiate variables uint8_t inputstream = 0; int outputVal = 0; uint8_t...

To troubleshoot, try adding delay at startup to give enough time for the USB enumeration to complete. Usually 1.5 seconds is enough for Linux. You might need 2.5 seconds or more for Windows. If the problem is happening inside a C++...

Programs which crash too early do this. Please try loading a simple "Hello World" program, without FreeRTOS and CAN libraries, just to confirm the upload process and serial monitor are still working. If not, please try testing with Arduino IDE.

10 inches is probably fine if you use shielded cable or twisted pair or even just 2 conductors held close together. What actually happens will really depend on whether your environment has something noisy which tends to couple to the wires...

As usual for blog articles, shout-out on 4 social networks https://bsky.app/profile/paulstoffregen.bsky.social/post/3kqe6a5mq432f https://mastodon.social/@PaulStoffregen/112288541665182235 https://www.facebook.com/groups/1470129233297275

Let's continue any conversation about BitByte on your other thread. https://forum.pjrc.com/index.php?threads/bitbyte-learn-create-play.74870/ I'm going to close this prior thread.

Article posted on the website today. https://www.pjrc.com/bitbyte-handheld-console/ Hopefully it helps your Kickstarter campaign! :) I see you have another older thread...

Article posted on the website today. https://www.pjrc.com/bitbyte-handheld-console/ Hopefully it helps your Kickstarter campaign! :)

I'm glad the FPU is working for you!

Any chance you might share the project or at least photos? Would probably be useful for others. And even if you're not looking to share the code and circuit details, just photos (or a cell phone video uploaded to youtube) and basic info could...

Which Teensy model are you using? I see you're doing float math as 64 bit double, even though you store the results into 32 bit float. Especially if using Teensy 3.2 which lacks FPU, use sinf() rather than sin().

Please check which version of Teensyduino you have installed. If using Arduino IDE 2.x.x, click Boards Manager and type "teensy" in search. If using Arduino IDE 1.8.x, click Help > About. Indeed this was needed with older versions. Before...

You could find the _reboot_Teensyduino_() function and delete its code. Finding the correct file on your hard drive can be a challenge. Pay attention to the folder name, as separate code is used for Teensy 3.x vs Teensy 4.x, and you might have...

You might consider this line when millis() grows to more than 23 bits (the size of float mantissa), which takes a little over 2 hours. float tempo = (float)millis()*0.003f; You'll gradually lose millis precision. Maybe that matters, or...

My guess is the sin() function. Its input is in radian units, so ideally you should be giving it numbers between 0 to 6.28 (or whatever Pi * 2 is). But after your program has run for only 4 seconds, even for the first LED (i == 0) the numbers...

That circuit should work fine for normal baud rates.

The behavior is undefined. U2 is never meant to be used this way.

The U2 chip that comes soldered to Teensy 4.0 or 4.1 is never meant to be used on a DIY circuit board. The T4 bootloader chip (IC_MKL02Z32_T4_QFN16) is meant for that DIY purpose. If you desolder U2 from Teensy 4.1 and attempt to use it on a...

Please do not create duplicate threads. Earlier thread: https://forum.pjrc.com/index.php?threads/problemes-with-diy-teensy-4-1.74851/

Yes, confirm

Captured the USB communication today. It's definitely something going wrong on the Teensy side. What exactly is still a mystery. I'm going to dig deeper soon...

This won't work. The U2 chip on a regular Teensy 4.1 is already pair with the U1 chip. It won't work with a different U1 chip.

Ah, found your other thread. https://forum.pjrc.com/index.php?threads/teensies-destroyed-by-buck-regulator-lm2596.74354/

Just to confirm, I'm running the code from msg #9 on a Teensy 4.1 and the PC side code on Ubuntu 22.04. It runs for about 20 seconds and the orange LED blinks, then it freezes. Is that what you're seeing?

Might be good to explain about the problem you're trying to protect. You said "external voltage regulator spikes", which seems strange as usually voltage regulators aim to give consistent voltage output, without spikes. But in general for...