Problem in Teensy 4.1

Zeann

New member
I have a problem with the teensy 4.1 module, almost all of our damaged modules have problems with the u2 and q1 ICs when the thermal part is hot and when connected to the laptop the port is not read and there is no power input even though the boot button is pressed there is no response indicating the module can turn on. There are already about 5 damaged modules there, we are having difficulty finding components in our country, Indonesia. Can you recommend the components and complete specifications? We really hope to get a reply. Then what is the function of the q1 IC? I initially felt it was a regulator but it seems it was a p channel for switching. And what is the u2 IC serial IC for reading ports?
 
Do you see these problems with bare Teensy 4.1's or are they connected to other electronic circuits?
A Teensy does not have a Boot button, only a Program button.
A fresh Teensy from the factory contains the Blinking program (flashing the onboard LED).
Q1 is acting a an "ideal diode". U2 is the Bootloader chip, nothing to do with serial IC for reading ports.
I suggest to study the Teensy 4.1 page and the Bootloader page thoroughly - it may answer your questions and help to debug the problems you see.

Regards,
Paul
 
I have a problem with the teensy 4.1 module, almost all of our damaged modules have problems with the u2 and q1 ICs when the thermal part is hot and when connected to the laptop the port is not read and there is no power input even though the boot button is pressed there is no response indicating the module can turn on. There are already about 5 damaged modules there, we are having difficulty finding components in our country, Indonesia. Can you recommend the components and complete specifications? We really hope to get a reply. Then what is the function of the q1 IC? I initially felt it was a regulator but it seems it was a p channel for switching. And what is the u2 IC serial IC for reading ports?
If you are experiencing USB power issues on Teensy 4.1 and Teensy 4.0, use an external +5V power supply connected to the Teensy Vin pin. However, be careful: the USB Vin wire must then be cut with a utility knife (see image). Do not overload the Teensy 3.3V connection with any other circuit. The maximum current is 250mA.

For development on the Teensy, I always use a USB2.0 isolator—for example, this one here : ISO-U20
This protects the Teensy from overvoltage
Screenshot 2026-05-12 174949.png


Screenshot 2026-05-12 175201.png


Screenshot 2026-05-02 122625.png

Screenshot 2026-05-12 173706.png
 
Last edited:
Some time ago, I put on the forum another question wich did not received any answer. If the board is powered by an external 3v3 source, with the above connexion opened, what happens when the power is off while a computer is connected to the USB port, there maybe some voltage on the two USB input with no power on the chip ... Is that dangerous ? And if the connexion is not cut, then the poor 3V3 regulator TLV75733 will power my whole system and get down on his knees because current will be too high. But I suppose that USB standard is such than anything not powerd may stay connected to a computer : such is the case for a printer ...
 
Last edited:
My advice and experience: One +5V power supply for the Teensy (or Teensys) is the better solution. Use the 3.3V pin on the Teensy only in an emergency.
 
My advice and experience: One +5V power supply for the Teensy (or Teensys) is the better solution. Use the 3.3V pin on the Teensy only in an emergency.
But I do not want to have two power supplies ; one 5 V for teensy, and one 3V3 for peripherals which do not withstand 5 V... It is far simpler if my whole logic system is powered with only one supply ! I have yet an unregulated +18V from a lithium battery to a step motor, then a first step down switching regulator to provide +12 V to a DC motor, and then another to +3V3 to logic circuity.
By the way, with a +5V power supply connected to Vin, and an opened jumper between Vin and USB power, the problem is exactly the same ! When this +5V is switched off, does the IMXRT chip withstands USB signals from the USB connector ? What happens if you cut +5V power supply during an USB transaction ? Normal CMOS input pins doesnot withstand voltage above power supply (zero !) excepted if current is limited in the internal protection diodes of the chip. What can source the computer USB data signal if they are shorted to groud in thes protection diodes ?
 
Last edited:
But I do not want to have two power supplies ; one 5 V for teensy, and one 3V3 for peripherals which do not withstand 5 V... It is far simpler if my whole logic system is powered with only one supply !
Teensy is simply not intended to be powered from 3.3V alone, there are some pins (on the MCU, not the PCB) which expect 5V.
 
Teensy is simply not intended to be powered from 3.3V alone, there are some pins (on the MCU, not the PCB) which expect 5V.
Yes indeed, without 5V the internal USB drivers won't work. But the data sheet (not reference manual) says that the VBUS pins can be left not connected when not used. So the chip can be powered with 3V3 and other lower voltages derived from 3V3, and +5V supplied by USB connector only when in use (aforementioned jumper not open). Then the only problem is that Teensy's 3V3 regulator will be in parallel with external 3V3.
1780303986530.png
 
But USB power is also used to power SNVS, which should be active before 3.3V power is connected. This doesn't happen if you directly connect a 3.3V supply (unless you have a battery connected to VBAT).
 
But USB power is also used to power SNVS, which should be active before 3.3V power is connected. This doesn't happen if you directly connect a 3.3V supply (unless you have a battery connected to VBAT).
Do I need SNVS ? I am not concerned with Real Time Clock, protections, keys, security ... And diode D2 routes +3V3 to VDD_SNVS_IN.
 
Last edited:
From @Paul. Although it quotes Teensy 4.0, I believe the sequence/requirements are the same for Teensy 4.1.
Teensy 4.0 was not designed to be powered this way. It can be made to work, but you should be aware of the startup sequencing requirements (which currently are not yet well documented).

The main issue is Teensy 4.x needs power on its SNVS input before or simultaneously with the other power inputs, except USBx_VBUS. If you apply power to the NVCC_xxx pins or VDD_HIGH_IN or VCC_ADC before SNVS, or if you externally drive any I/O pins while SNVS is off which bleeds power through the ESD protection diodes to the chip's internal power rails, the chip may fail to start up because SNVS wasn't powered first or at least simultaneously.

To be more specific, this means applying power to the VDD_SNVS_IN pin and allowing enough time for the capacitor connected to VDD_SNVS_CAP to charge up. If power gets applied to the other pins before that SNVS capacitor reaches about 1.0 volt, the chip may not start up.

Normally when you apply power to VUSB or VIN, the 3.3V regulator is kept off by a 100K resistor connected to its enable pin. The incoming power does go to USB1_VBUS and USB2_VBUS. The USB VBUS regulator is an exception to the "SNVS first" rule, as it's fully independent of the rest of the chip's startup sequence.

With USB power applied to those 2 pins, the capacitors on VDD_USB_CAP start to charge, reaching about 2.5 volts.

VDD_SNVS_IN starts to get power as VDD_USB_CAP charges up, because it's connected by a BAT54C diode. Keep in mind VDD_SNVS_IN will be "behind" VDD_USB_CAP due to the forward voltage drop of the diode. The diode's forward voltage drop causing effectively a delay is an important point to keep in mind if you power Teensy 4.x in alternate ways where the power rises slowly.

In the normal startup sequence, once VDD_SNVS_CAP is charged, the chip's internal power management and security hardware boots up. Within several milliseconds, it drives PMIC_ON_REQ high. Keep in mind logic high on that pin is about 1.1V at this early stage. The 3.3V regulator we use on Teensy 4.x is rated to work with 1V enable. Regulators needing a higher logic voltage won't work.

As the 3.3V power come up, the DCDC buck converter remains off due to a 100K resistor connected to DCDC_PSWITCH. The VDD_HIGH_CAP and NVCC_PLL capacitors start to charge up.

The MKL02 chip boots up and configures its brown-out detection for approx 2.9V. It then waits several milliseconds for the 3.3V power to be stable and then drives DCDC_PSWITCH high, which causes the buck converter to start creating the 1.15V power the main CPU needs to start. NXP's documentation gives a wrong impression that DCDC_PSWITCH may be level sensitive. It is not. A rising edge after 3.3V is stable is required to make the DCDC buck convert start.

The MKL02 also drives POR_B high after another short delay, which lets the main IMXRT chip boot.


If you try to power Teensy 4.0 with only 3.3V power, you'll be skipping the first half of this power up sequence. Remember, the voltage at VDD_SNVS_IN is slightly "behind" due to the BAT54C forward voltage drop. If your 3.3V power rises very quickly to at least 1.5V, you may be able to get power to VDD_SNVS_IN and VDD_SNVS_CAP fast enough for the chip to start up. But if your 3.3V power is created by a power supply with "soft start" or a linear power supply with large capacitors, it will probably rise too slowly.

There are a couple possible workarounds. As you can see on the Teensy 4.x schematic, the cathode of all those diodes which connect to VDD_SNVS_IN come to a test point. If you short that test point to 3.3V power, then VDD_SNVS_IN will no longer be "behind" or delayed from the 3.3V rise.

The other alternative is to arrange for VBAT to have power before you apply the main 3.3V power. Maybe a resistor and zener diode or LED to create a low power 2-3V input to VBAT would be used from your unregulated power. Only a fraction of a milliamp is needed.
 
From @Paul. Although it quotes Teensy 4.0, I believe the sequence/requirements are the same for Teensy 4.1.
Many thanks for these enlightening explanations. I saw in IMXRT manual that power up sequence was somewhat complicated, and thought that there was adequate things on the board, I did not try to analyse things further as you do there. Maybe the connexion of some VBAT supply is the simplest solution, but I don't like any connexion outside of a regular 28 pins DIL socket (I am using Teensy 4.0). So, now, I am defeated :mad: , I will change my schematic to provide a +5V supply, but this complicates the routing on my PC board (gerber files were ready to send to JLCPCB) ... Perhaps it will be interesting (at least for me :) ) to put a new Teensy 4.2 on the market, working with a +3.3V supply ...
 
Last edited:
Hopefully you are planning on using a different name before you go to market
This is a major issue for small batch custom electronics. Why must the world of EE insist on shipping something different than used in development haha. I love the idea of a teensy 4.2 @Denis Bélières , especially if it pins out the USB connector so I can stop cutting a usb cable and soldering the wires to my carrier board blah, and just including the "optional" diode so you don't have to worry about using 5V Vin and USB at the same time would be great too. Little things like that make for major quality of life improvements, for me at least :)
 
Maybe consider using MicroMod or Lockable MicroMod. It is designed for 3.3V power input.

To explain the tech side, NXP's chip has complicated power startup requirements. It's documented on the T4 bootloader chip page. Scroll down to "Power Up Sequence".

The requirement for higher than 3.3V versus direct 3.3V comes at step #6. On Teensy 4.0 and Teensy 4.1, a LDO voltage regulator receives the PMIC_ON_REQ signal at its enable pin. So the minimum input voltage is determined by that voltage regulator's low (but not zero) dropout voltage.

MicroMod has a pair of mosfet transistors rather than a voltage regulator. When PMIC_ON_REQ asserts, the 3.3V power is passed directly by a P-channel mosfet with low on resistance. Look on the upper left part of the schematic for details.

NXP also documents all this stuff in their datasheet, a hardware design guide, and some app notes. Life would have been easier had they designed their chip to just take 1 power input and it would do all the rest automatically. But that's not the silicon they made. The chip implements a large number of features, including a number of security features. The chip designers chose this approach because they needed a way to meet all those requirements. They too were probably under some constraints, as adding analog circuitry in a new generation of chip costs more design time and higher risk compared with purely digital circuitry. Unfortunately, choices NXP's engineers made do mean the chip has this complicated startup process. In the design of Teensy, I tried to make it as simple as possible, but only so much could be done (at a reasonable cost and fitting in the small form factor).
 
Last edited:
Back
Top