Search results

This is what I am leaning towards, that we are getting essentially a ground loop through the processor. We have checked several failed teensies and the two we checked had IO pins which also were failed (eg 4 ohms VS the 38-40K ohms we see on "good" pins). Note this is for the teensy...

- The 24V base power supply is AC connected, with earth ground - We have had these failures when the board is not connected to any external ports (we control motors, collect signals, etc) but they translators on both inputs and outputs.

Attached please find the power subsystem, as well as the main processor block. The overall board is fed by a 24V power supply (high quality) which is then broken down into 12, 5 and 3.3V. I will check the 5V startup, but in the past its pretty clean. And again on normal (non USB cable...

Hi Bill, thanks for the thoughtful reply. - Our 4.1 design is a full 3.3V compliant design, with 5V translators where appropriate. - On the diode issue, there was a post in these forums somewhere around backfeed from the 3.3V internal supply into an already turned off 5V rail causing unexpected...

We have experienced ongoing failures of Teensy 4.1 modules in our system over the last 18 months. These failures appear random and arbitrary except: 1) Never fails during normal operation. In other words once up and running fine during that power cycle. 2) The symptom of the failure is that...

Awesome, this is perfect

Is there any way to have the running Teensy code (on 4.1) update its own code. in other words looking for a fielded unit to get new firmware from the network, then store that and run the new downloaded code on a reboot. EG remote update? I am guessing no, but curios if anyone has ideas on how...

Had a weird issue loading code then having my Teensy 4.1 lockup and serial port dissapear Can recreate using simple blink code. Code loads but then never blinks and the Teensy dissapears from the serial port list. it will load again when the reset button is pressed but same behavior. Briefly...

We are looking at a US contract (non defense) but they want NDAA compliance which has requirements around computing sources. Key questions are around the overall PCB build, and as well as the two processors on the Teensy 4.1

I am having an issue with correct interrupt behaviour on a Teensy 4.1. I have boiled it down to a small piece of code. Basically I am attaching an interrupt to a RISING edge of a pin. Using a function generator I send a block of 10 pulses to the pin. I have confirmed with an oscilloscope that...

Ahh, great thanks. That may help explain an anomaly we have seen on our boards.

I have a board with various IO's connected to a Teensy 4.1. In addition I have a CR2032 battery connected to the VBAT pin. The RTC works just fine. All system functions are powered independent of the teensy. So for example I have a separate 3.3V regulator which provides power to the 3.3...

Why did this work Paul, turning the input off seems counter-intuitive when I am trying to do a read. Why is this necessary and why does it work?