Hello everyone,
First time posting here, but not the first time on this forum. I am also french Canadian, I might make some horrible mistake, please don't judge.
I am not a expert in electronics, more of a advanced hobbyist.
As the title say, I burned 2 Teensy yesterday while working on a project.
For the first Teensy, I uploaded a big code I got to run leds via artnet using FastLED and a bunch of other libraries. The thing is, that it burned after several upload, during the day (and several other during the lifetime of this Teensy). The last thing I change was added a Serial.print somewhere, nothing major. Some people might ask for a link to the code but I am not able to share it because of a NDA, anyway I am 99% sure it is not the problem because the second Teensy 4.1 that I burned (fresh one out of the box) got the blink example from Arduino. For each TeensyI used a different cable, and a different USB port on my laptop. The "fresh out of the box" Teensy was running smoothly with the blink code that comes with it as is while powered by my laptop via the USB cable.
The "fresh out of the box" Teensy was naked, no header, no nothing solder on it, just the Teensy.
The picture here show the first burned Teensy 4.1 on a custom board I have, the only thing that look weird is the U2 chip, next to the Ethernet pin + USB connector. The U2 chip is the MKL02Z32VFG4. The chip have a rubbish ish look, like something that burned?
I got some other close up
Here is an other chip that have the same finish, but I am not sure if it is affected in anyway by the "burn". Its the U3 (W25Q64JVXGIM)
This Teensy is the "fresh out of the box" one.
Both Teensy now blink 9 times before "shutting down". The error on the website is (https://www.pjrc.com/store/ic_mkl02_t4.html):
9 Blinks = ARM JTAG DAP Init Error
The ARM JTAG DAP was detected (4 blinks) but could not be initialized. This error is rather unlikely!
My very mostly kind of wrong guest is that the boot loader have a weird problem.
I am running on Windows 11, Teensy Loader 1.57, I am also using PlatformIO for all of my projects 3.0.0
Also my laptop was plugged all the time with is power supply, its a ThinkPad P15v Gen 2 Intel
Any help or hint as of what happen and how I can never do it again will be appreciated.
A friendly french guy.
First time posting here, but not the first time on this forum. I am also french Canadian, I might make some horrible mistake, please don't judge.
I am not a expert in electronics, more of a advanced hobbyist.
As the title say, I burned 2 Teensy yesterday while working on a project.
For the first Teensy, I uploaded a big code I got to run leds via artnet using FastLED and a bunch of other libraries. The thing is, that it burned after several upload, during the day (and several other during the lifetime of this Teensy). The last thing I change was added a Serial.print somewhere, nothing major. Some people might ask for a link to the code but I am not able to share it because of a NDA, anyway I am 99% sure it is not the problem because the second Teensy 4.1 that I burned (fresh one out of the box) got the blink example from Arduino. For each TeensyI used a different cable, and a different USB port on my laptop. The "fresh out of the box" Teensy was running smoothly with the blink code that comes with it as is while powered by my laptop via the USB cable.
The "fresh out of the box" Teensy was naked, no header, no nothing solder on it, just the Teensy.
The picture here show the first burned Teensy 4.1 on a custom board I have, the only thing that look weird is the U2 chip, next to the Ethernet pin + USB connector. The U2 chip is the MKL02Z32VFG4. The chip have a rubbish ish look, like something that burned?
I got some other close up
Here is an other chip that have the same finish, but I am not sure if it is affected in anyway by the "burn". Its the U3 (W25Q64JVXGIM)
This Teensy is the "fresh out of the box" one.
Both Teensy now blink 9 times before "shutting down". The error on the website is (https://www.pjrc.com/store/ic_mkl02_t4.html):
9 Blinks = ARM JTAG DAP Init Error
The ARM JTAG DAP was detected (4 blinks) but could not be initialized. This error is rather unlikely!
My very mostly kind of wrong guest is that the boot loader have a weird problem.
I am running on Windows 11, Teensy Loader 1.57, I am also using PlatformIO for all of my projects 3.0.0
Also my laptop was plugged all the time with is power supply, its a ThinkPad P15v Gen 2 Intel
Any help or hint as of what happen and how I can never do it again will be appreciated.
A friendly french guy.
Last edited:
