Teensy 4.1 NXP ROM in open mode

[Dr.What]

Greetings,

I did buy a 2. Teensy now after over a year of being amazed by my first.
The first initially had some problems after i soldered the headers on but it was resolved by rinsing it and then heating it to dry.

The second now shows issues too that sadly are not resolved in such easy way. Iam quite curious how its possible to ? damage? that thing with only carefully soldering headers onto it.
Anyway, here are the logs.

First is when only connecting it second is when pressing down the button and then plugging it in followed by releasing the button.
The Teensy tool for Arduino is in Automode, it starts to try to erase it but as in any case the Teensy seems to be shutting down after almost a second.
So the recovery function doesnt seem to work as the Teensy will shut down.
I wen through the forum and did check the voltages.
I do have 5V at Vin, 3.3 V at 3.3V but...well yeah, see for yourself.


1. LOG:

14:32:36.896 (ports 5): Begin, version=1.57, high-res time
14:32:36.896 (ports 5): LoadLibrary cfgmgr32 ok
14:32:36.896 (ports 5): LoadLibrary ntdll ok
14:32:36.898 (ports 5): callback 0024
14:32:36.898 (ports 5): callback 0081
14:32:36.899 (ports 5): callback 0083
14:32:36.899 (ports 5): hWnd = 263822
14:32:36.900 (ports 5): nothing new, skipping HID & Ports enum
14:32:43.465 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:32:43.465 (ports 5): nothing new, skipping HID & Ports enum
14:32:43.468 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
14:32:43.469 (ports 5): nothing new, skipping HID & Ports enum
14:32:43.515 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:32:43.515 (ports 5): nothing new, skipping HID & Ports enum
14:32:48.192 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
14:32:48.192 (ports 5): nothing new, skipping HID & Ports enum
14:32:48.195 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:32:48.195 (ports 5): nothing new, skipping HID & Ports enum
14:33:19.529 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:33:19.530 (loader): remote connection 1528 opened
14:33:19.531 (ports 5): nothing new, skipping HID & Ports enum
14:33:19.532 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
14:33:19.532 (ports 5): nothing new, skipping HID & Ports enum
14:33:19.557 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:33:19.557 (ports 5): nothing new, skipping HID & Ports enum
14:33:19.708 (loader): handle 578
14:33:19.710 (loader): Device came online, code_size = 100
14:33:19.712 (loader): Board is: NXP IMXRT1062 ROM
14:33:19.714 (loader): begin operation
14:33:19.722 (loader): File "C:\Users\birkm\AppData\Local\Temp\arduino_build_9 91357\1-Simple_Differential.ino.hex", 25600 bytes
14:33:19.726 (loader): File "1-Simple_Differential.ino.hex". 25600 bytes
14:33:19.730 (loader): set background IMG_ONLINE
14:33:19.736 (loader): nxp_write: success
14:33:19.739 (loader): nxp_write: success
14:33:19.742 (loader): HAB open mode, bootcfg=8B018
14:33:19.744 (loader): Opps, NXP ROM in open mode, but we do not yet have code for this case
14:33:19.747 (loader): start ignoring usb:80001/4/0/1/1
14:33:19.749 (loader): end operation, total time = 0.033 seconds
14:33:19.753 (loader): redraw timer set, image 79 to show for 3000 ms
14:33:22.762 (loader): redraw, image 9
14:33:24.260 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
14:33:24.261 (ports 5): nothing new, skipping HID & Ports enum
14:33:24.263 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:33:24.264 (ports 5): nothing new, skipping HID & Ports enum
14:33:24.331 (loader): stop ignoring usb:80001/4/0/1/1



2. LOG:

14:45:48.387 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
14:45:48.388 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
14:45:48.388 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
14:45:48.388 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
14:45:48.388 (ports 5): found_usb_device, devinst=00000007
14:45:48.388 (ports 5): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
14:45:48.388 (ports 5): hiddev_from_devinst_list: iface=0
14:45:48.388 (ports 5): found_usb_device complete
14:45:48.389 (ports 5): hid, found devinst=0000000C
14:45:48.389 (ports 5): hid, path=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000#{4 d1e55b2-f16f-11cf-88cb-001111000030}
14:45:48.389 (ports 5): hid, opened handle
14:45:48.389 (ports 5): devinst=0000000C, location=usb:80001/4/0/1/1
14:45:48.389 (ports 5): vid=16C0, pid=0478, ver=0108, usepage=FF9C, use=0025
14:45:48.389 (ports 5): devpath=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000 #{4d1e55b2-f16f-11cf-88cb-001111000030}
14:45:48.389 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader
14:45:48.413 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:45:48.413 (ports 5): nothing new, skipping HID & Ports enum
14:45:48.579 (loader): secure mode can not be locked: this is Standard Teensy
14:45:48.581 (loader): encryption is possible on this Teensy, but not yet configured
14:45:48.582 (loader): but without secure mode locked, encryption will NOT be secure!
14:45:48.584 (loader): Device came online, code_size = 8126464
14:45:48.585 (loader): Board is: Teensy 4.1 (IMXRT1062), version 1.08
14:45:48.592 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
14:45:48.594 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
14:45:48.617 (loader): set background IMG_ONLINE
14:45:48.624 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
14:45:48.626 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
14:45:48.679 (loader): elf appears to be for Teensy 4.1 (IMXRT1062) (8126464 bytes)
14:45:48.682 (loader): elf binary data matches hex file
14:45:48.684 (loader): elf file is for Teensy 4.1 (IMXRT1062)
14:45:48.686 (loader): using hex file
14:45:48.709 (loader): begin operation
14:45:48.739 (loader): flash, block=0, bs=1024, auto=1
14:45:48.742 (loader): flash, block=1, bs=1024, auto=1
14:45:48.745 (loader): flash, block=2, bs=1024, auto=1

// THIS IS WHERE TEENSY FREEZES.

14:45:52.858 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
14:45:52.859 (ports 5): remove: loc=usb:80001/4/0/1/1
14:45:52.859 (ports 5): usb_remove: usb:80001/4/0/1/1
14:45:52.859 (ports 5): nothing new, skipping HID & Ports enum
14:45:54.484 (ports 5): purge, name=hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader, loc=usb:80001/4/0/1/1, age=1.625 sec
14:45:57.877 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
14:45:57.878 (ports 5): nothing new, skipping HID & Ports enum
14:46:18.767 (loader): program: write error
14:46:18.769 (loader): HID/win32: HidD_GetPreparsedData failed, device assumed disconnected
14:46:18.772 (loader): end operation, total time = 30.061 seconds
14:46:18.775 (loader): set background IMG_DOWNLOAD_ERROR
14:46:18.778 (loader): redraw timer set, image 11 to show for 4000 ms
14:46:18.796 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
14:46:18.799 (loader): HID/win32: vid:0001 pid:0001 ver:0001
14:46:18.803 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
14:46:18.810 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
14:46:18.817 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
14:46:18.821 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
14:46:18.824 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
14:46:22.771 (loader): redraw, image 9



Tested it under Windows 11 and Windows 7 with Arduino 1.8.19
Please advise.

[PaulStoffregen]

This is very likely caused by damage to the flash memory chip, or connection between the flash chip and IMXRT processor.

On Teensy 4.1 the flash chip is very close to I/O pins 24 and 26. Any chance stray solder from those pins shorted over to the flash memory?

[Dr.What]

non that i can see.
The .65 ( replacement for the two diodes?) looks though as if there would be an air gap between its contacts and the PCB. at least when i look at it under 10x with my microscope.
I used 0.5 mm solder and a soldering needle at low temps so iam not sure how i could have damaged it.
can it be a problem that it might not got fully attached during production?

The winbond itself looks fine and i didnt solder any way near it.

[PaulStoffregen]

I hope you can understand I'm only (sometimes) able to answer "what" on these sorts of over-the-internet hardware troubleshooting but rarely "how" or "why" things went wrong.

In this case, the processor isn't seeing the flash memory. Download error in Teensy loader after only a few blocks transmitted (enough to fill the RAM buffer the bootloader uses) is a pretty sure sign, as well as NXP open mode when it tries to boot. Those are the errors which happen when the flash chip isn't connected.

The diodes near the flash chip are used for power startup. Details on the T4 bootloader chip page. One connected VBAT, which isn't actually used unless you connect a coin cell. If the other diodes were damaged, you wouldn't get to this point. The hardware would not power up.

I can assure you the flash chip is tested twice on every Teensy. The first test is a bed-of-nails test which confirms all I/O pins and other hardware. It writes and verifies the 15 sec restore program into the flash, and sets the hardware lock so that portion of flash can never be erased or altered. The second test is for the USB, pushbutton and LED, which can't be fully checked on the bed of nails (but it does observe the LED's current change to the total power used). In the 2nd test, a human plugs in a USB cable and the LED blink program is written. The test fixture looks for Teensy to reboot and appear as the RawHID device as a result of the just-written program. The person performing the test also visually confirms the orange LED comes on. Obviously the flash needs to be fully functional for that test to pass.

Again, it's usually impossible to know how or why hardware got damaged, and sometimes when it's "dead" little info can be learned. But in this case, all the available info points to something went wrong with the flash chip or connection to the flash chip. Since the hardware is powering up, there's a pretty good chance it might work again if you can find and fix the problem.

[Dr.What]

Yes of course.

Curious how its possible that they are so sensitive?

I guess unless im able to somehow fix it im not eligible for a replacement as well, i did solder headers onto it after all.

Thanks for your time!

[Dr.What]

reheated all pins at 300°C and also the pins on the chip, did put the iron directly onto the chip too.
Same behavior, no change.
Used a toothbrush with 70% isopropanol 30% aqua dest. to brush off anything, rinse off anything.
Same behavior, no change.

Desoldered the pins next to the SD card slot, did put my soldering iron to full heat (480°C) and reheated all pins in proximity, did heat the chip and its pins.
Then used a scalpel blade and did cut around the chip itself with only applying minimal pressure / tried to scratch of carefully the surface next to the pins of the chip and the pins in proximity.

AND IT WORKED! well at least so far that the chip can be flashed, but it still seems to disconnect afterwards and only physical reconnect brings it back online.

17:43:11.916 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
17:43:11.917 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:43:11.917 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
17:43:11.917 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
17:43:11.917 (ports 5): found_usb_device, devinst=00000007
17:43:11.917 (ports 5): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:43:11.917 (ports 5): hiddev_from_devinst_list: iface=0
17:43:11.917 (ports 5): found_usb_device complete
17:43:11.918 (ports 5): hid, found devinst=0000000C
17:43:11.918 (ports 5): hid, path=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000#{4 d1e55b2-f16f-11cf-88cb-001111000030}
17:43:11.918 (ports 5): hid, opened handle
17:43:11.918 (ports 5): devinst=0000000C, location=usb:80001/4/0/1/1
17:43:11.918 (ports 5): vid=16C0, pid=0478, ver=0108, usepage=FF9C, use=0025
17:43:11.918 (ports 5): devpath=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000 #{4d1e55b2-f16f-11cf-88cb-001111000030}
17:43:11.918 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader
17:43:12.048 (loader): secure mode can not be locked: this is Standard Teensy
17:43:12.050 (loader): encryption is possible on this Teensy, but not yet configured
17:43:12.051 (loader): but without secure mode locked, encryption will NOT be secure!
17:43:12.053 (loader): Device came online, code_size = 8126464
17:43:12.054 (loader): Board is: Teensy 4.1 (IMXRT1062), version 1.08
17:43:12.062 (loader): File "C:\Users\birkm\AppData\Local\Temp\arduino_build_2 79091\AnalogReadSerial.ino.hex", 21504 bytes
17:43:12.064 (loader): File "AnalogReadSerial.ino.hex". 21504 bytes, 0% used
17:43:12.087 (loader): set background IMG_ONLINE
17:43:12.096 (loader): File "C:\Users\birkm\AppData\Local\Temp\arduino_build_2 79091\AnalogReadSerial.ino.hex", 21504 bytes
17:43:12.098 (loader): File "AnalogReadSerial.ino.hex". 21504 bytes, 0% used
17:43:12.121 (loader): elf appears to be for Teensy 4.1 (IMXRT1062) (8126464 bytes)
17:43:12.123 (loader): elf binary data matches hex file
17:43:12.125 (loader): elf file is for Teensy 4.1 (IMXRT1062)
17:43:12.126 (loader): using hex file
17:43:12.147 (loader): begin operation
17:43:12.175 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:43:12.175 (ports 5): nothing new, skipping HID & Ports enum
17:43:12.191 (loader): flash, block=0, bs=1024, auto=1
17:43:12.193 (loader): flash, block=1, bs=1024, auto=1
17:43:12.195 (loader): flash, block=2, bs=1024, auto=1
17:43:12.449 (loader): flash, block=3, bs=1024, auto=1
17:43:12.453 (loader): flash, block=4, bs=1024, auto=1
17:43:12.457 (loader): flash, block=5, bs=1024, auto=1
17:43:12.461 (loader): flash, block=6, bs=1024, auto=1
17:43:12.465 (loader): flash, block=7, bs=1024, auto=1
17:43:12.469 (loader): flash, block=8, bs=1024, auto=1
17:43:12.474 (loader): flash, block=9, bs=1024, auto=1
17:43:12.478 (loader): flash, block=10, bs=1024, auto=1
17:43:12.483 (loader): flash, block=11, bs=1024, auto=1
17:43:12.488 (loader): flash, block=12, bs=1024, auto=1
17:43:12.492 (loader): flash, block=13, bs=1024, auto=1
17:43:12.496 (loader): flash, block=14, bs=1024, auto=1
17:43:12.502 (loader): flash, block=15, bs=1024, auto=1
17:43:12.506 (loader): flash, block=16, bs=1024, auto=1
17:43:12.511 (loader): flash, block=17, bs=1024, auto=1
17:43:12.517 (loader): flash, block=18, bs=1024, auto=1
17:43:12.523 (loader): flash, block=19, bs=1024, auto=1
17:43:12.528 (loader): flash, block=20, bs=1024, auto=1
17:43:12.559 (loader): sending reboot
17:43:12.564 (loader): begin wait_until_offline
17:43:12.570 (loader): offline, waited 0
17:43:12.572 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
17:43:12.572 (ports 5): remove: loc=usb:80001/4/0/1/1
17:43:12.572 (ports 5): usb_remove: usb:80001/4/0/1/1
17:43:12.572 (ports 5): nothing new, skipping HID & Ports enum
17:43:12.580 (loader): end operation, total time = 0.431 seconds
17:43:12.586 (loader): set background IMG_REBOOT_OK
17:43:12.595 (loader): redraw timer set, image 14 to show for 1200 ms
17:43:12.652 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:43:12.652 (ports 5): nothing new, skipping HID & Ports enum
17:43:12.808 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:43:12.813 (loader): HID/win32: vid:0001 pid:0001 ver:0001
17:43:12.818 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:43:12.823 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:43:12.827 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:43:12.831 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
17:43:12.836 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
17:43:12.846 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
17:43:12.847 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:43:12.847 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
17:43:12.847 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0483&REV_0280
17:43:12.847 (ports 5): found_usb_device, devinst=0000001d
17:43:12.847 (ports 5): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0483, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:43:12.847 (ports 5): comport_from_devinst_list attempt
17:43:12.847 (ports 5): found_usb_device complete
17:43:12.847 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy 4.1) Serial
17:43:12.979 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:43:12.980 (ports 5): update_usb_device, devinst list change, old had 1, new has 2
17:43:12.980 (ports 5): comport_from_devinst_list attempt
17:43:12.980 (ports 5): found Ports in classguid_list at index=1
17:43:12.980 (ports 5): port COM12 found from devnode
17:43:12.980 (ports 5): usb_add: usb:80001/4/0/1/1 COM12 (Teensy 4.1) Serial
17:43:13.087 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
17:43:13.087 (ports 5): nothing new, skipping HID & Ports enum
17:43:13.304 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:43:13.305 (ports 5): nothing new, skipping HID & Ports enum
17:43:13.801 (loader): redraw, image 9
17:43:16.317 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
17:43:16.317 (ports 5): remove: loc=usb:80001/4/0/1/1
17:43:16.317 (ports 5): usb_remove: usb:80001/4/0/1/1
17:43:16.317 (ports 5): nothing new, skipping HID & Ports enum
17:43:16.363 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:43:16.363 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
17:43:16.363 (ports 5): nothing new, skipping HID & Ports enum
17:43:17.998 (ports 5): purge, name=COM12 (Teensy 4.1) Serial, loc=usb:80001/4/0/1/1, age=1.681 sec

[Dr.What]

17:58:10.867 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
17:58:10.867 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:58:10.867 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
17:58:10.867 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
17:58:10.867 (ports 5): found_usb_device, devinst=00000007
17:58:10.867 (ports 5): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:58:10.867 (ports 5): hiddev_from_devinst_list: iface=0
17:58:10.868 (ports 5): found_usb_device complete
17:58:10.868 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy) Bootloader
17:58:11.017 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:58:11.018 (ports 5): hid, found devinst=0000000C
17:58:11.018 (ports 5): hid, path=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000#{4 d1e55b2-f16f-11cf-88cb-001111000030}
17:58:11.018 (ports 5): hid, opened handle
17:58:11.018 (ports 5): devinst=0000000C, location=usb:80001/4/0/1/1
17:58:11.018 (ports 5): vid=16C0, pid=0478, ver=0108, usepage=FF9C, use=0025
17:58:11.018 (ports 5): devpath=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000 #{4d1e55b2-f16f-11cf-88cb-001111000030}
17:58:11.018 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader
17:58:11.111 (loader): secure mode can not be locked: this is Standard Teensy
17:58:11.113 (loader): encryption is possible on this Teensy, but not yet configured
17:58:11.115 (loader): but without secure mode locked, encryption will NOT be secure!
17:58:11.117 (loader): Device came online, code_size = 8126464
17:58:11.118 (loader): Board is: Teensy 4.1 (IMXRT1062), version 1.08
17:58:11.125 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
17:58:11.127 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
17:58:11.150 (loader): set background IMG_ONLINE
17:58:11.157 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
17:58:11.159 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
17:58:11.183 (loader): elf appears to be for Teensy 4.1 (IMXRT1062) (8126464 bytes)
17:58:11.185 (loader): elf binary data matches hex file
17:58:11.188 (loader): elf file is for Teensy 4.1 (IMXRT1062)
17:58:11.189 (loader): using hex file
17:58:11.212 (loader): begin operation
17:58:11.246 (loader): flash, block=0, bs=1024, auto=1
17:58:11.250 (loader): flash, block=1, bs=1024, auto=1
17:58:11.252 (loader): flash, block=2, bs=1024, auto=1
17:58:11.514 (loader): flash, block=3, bs=1024, auto=1
17:58:11.515 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:58:11.516 (ports 5): nothing new, skipping HID & Ports enum
17:58:11.519 (loader): flash, block=4, bs=1024, auto=1
17:58:11.531 (loader): flash, block=5, bs=1024, auto=1
17:58:11.535 (loader): flash, block=6, bs=1024, auto=1
17:58:11.540 (loader): flash, block=7, bs=1024, auto=1
17:58:11.544 (loader): flash, block=8, bs=1024, auto=1
17:58:11.551 (loader): flash, block=9, bs=1024, auto=1
17:58:11.555 (loader): flash, block=10, bs=1024, auto=1
17:58:11.560 (loader): flash, block=11, bs=1024, auto=1
17:58:11.565 (loader): flash, block=12, bs=1024, auto=1
17:58:11.571 (loader): flash, block=13, bs=1024, auto=1
17:58:11.575 (loader): flash, block=14, bs=1024, auto=1
17:58:11.605 (loader): sending reboot
17:58:11.612 (loader): begin wait_until_offline
17:58:11.616 (loader): offline, waited 0
17:58:11.619 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
17:58:11.620 (ports 5): remove: loc=usb:80001/4/0/1/1
17:58:11.620 (ports 5): usb_remove: usb:80001/4/0/1/1
17:58:11.620 (ports 5): nothing new, skipping HID & Ports enum
17:58:11.623 (loader): end operation, total time = 0.409 seconds
17:58:11.630 (loader): set background IMG_REBOOT_OK
17:58:11.636 (loader): redraw timer set, image 14 to show for 1200 ms
17:58:11.656 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:58:11.661 (loader): HID/win32: vid:0001 pid:0001 ver:0001
17:58:11.666 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:58:11.670 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:58:11.676 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
17:58:11.681 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
17:58:11.687 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
17:58:11.801 (serialmon 34): Begin, version=1.57, high-res time
17:58:11.801 (serialmon 34): listening for location: usb:80001/4/0/1/1
17:58:11.801 (serialmon 34): LoadLibrary cfgmgr32 ok
17:58:11.801 (serialmon 34): LoadLibrary ntdll ok
17:58:11.803 (serialmon 34): callback 0024
17:58:11.803 (serialmon 34): callback 0081
17:58:11.804 (serialmon 34): callback 0083
17:58:11.804 (serialmon 34): hWnd = 198740
17:58:11.805 (serialmon 34): loop stdin, ready=262143
17:58:11.806 (serialmon 34): nothing new, skipping HID & Ports enum
17:58:11.806 (loader): remote connection 4008 opened
17:58:11.891 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:58:11.891 (ports 5): nothing new, skipping HID & Ports enum
17:58:11.894 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
17:58:11.894 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:58:11.894 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
17:58:11.894 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0486&REV_0280
17:58:11.894 (ports 5): found_usb_device, devinst=00000018
17:58:11.894 (ports 5): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0486, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:58:11.894 (ports 5): hiddev_from_devinst_list: iface=1
17:58:11.895 (ports 5): found_usb_device complete
17:58:11.895 (serialmon 34): WM_DEVICECHANGE DBT_DEVICEARRIVAL
17:58:11.895 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy 4.1) RawHID
17:58:11.895 (serialmon 34): found_usb_device, id=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:58:11.895 (serialmon 34): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
17:58:11.895 (serialmon 34): found_usb_device, hwid=USB\VID_16C0&PID_0486&REV_0280
17:58:11.895 (serialmon 34): found_usb_device, devinst=00000006
17:58:11.895 (serialmon 34): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0486, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
17:58:11.895 (serialmon 34): hiddev_from_devinst_list: iface=1
17:58:11.896 (serialmon 34): found_usb_device complete
17:58:11.896 (serialmon 34): usb_add: usb:80001/4/0/1/1
17:58:11.896 (serialmon 34): ignoring partial USB device discovery (Windows XP issue?)
17:58:12.066 (serialmon 34): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:58:12.067 (serialmon 34): update_usb_device, devinst list change, old had 2, new has 5
17:58:12.067 (serialmon 34): hiddev_from_devinst_list: iface=1
17:58:12.067 (serialmon 34): 00000019: path=\\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0 000#{4d1e55b2-f16f-11cf-88cb-001111000030}
17:58:12.067 (serialmon 34): hid, found devinst=00000019
17:58:12.067 (serialmon 34): hid, found devinst=00000017
17:58:12.068 (serialmon 34): usb_add: usb:80001/4/0/1/1
17:58:12.068 (serialmon 34): Opened \\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0000#{ 4d1e55b2-f16f-11cf-88cb-001111000030} RawHID
17:58:12.329 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:58:12.330 (ports 5): update_usb_device, devinst list change, old had 1, new has 5
17:58:12.330 (ports 5): hiddev_from_devinst_list: iface=1
17:58:12.330 (ports 5): 0000001C: path=\\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0 000#{4d1e55b2-f16f-11cf-88cb-001111000030}
17:58:12.330 (ports 5): hid, found devinst=0000001C
17:58:12.330 (ports 5): hid, found devinst=0000001A
17:58:12.331 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0486 (Teensy 4.1) RawHID
17:58:12.835 (loader): redraw, image 9
17:58:15.287 (serialmon 34): teensy read ov error
17:58:15.287 (serialmon 34): teensy read error
17:58:15.290 (serialmon 34): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
17:58:15.290 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
17:58:15.290 (serialmon 34): remove: loc=usb:80001/4/0/1/1
17:58:15.290 (serialmon 34): usb_remove: usb:80001/4/0/1/1
17:58:15.290 (serialmon 34): Disconnect \\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0000#{ 4d1e55b2-f16f-11cf-88cb-001111000030}
17:58:15.290 (ports 5): remove: loc=usb:80001/4/0/1/1
17:58:15.290 (ports 5): usb_remove: usb:80001/4/0/1/1
17:58:15.290 (ports 5): nothing new, skipping HID & Ports enum
17:58:15.290 (serialmon 34): nothing new, skipping HID & Ports enum
17:58:15.303 (serialmon 34): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:58:15.304 (serialmon 34): nothing new, skipping HID & Ports enum
17:58:15.528 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
17:58:15.528 (ports 5): nothing new, skipping HID & Ports enum
17:58:16.954 (ports 5): purge, name=hid#vid_16c0&pid_0486 (Teensy 4.1) RawHID, loc=usb:80001/4/0/1/1, age=1.664 sec
17:58:17.814 (loader): remote connection 4008 closed

[kd5rxt-mark]

Curious how its possible that they are so sensitive?

@Dr.What:

Please take this post in the fully intended positive manner. I mean absolutely no malice with my comments !! I'm just attempting to give an alternate way to look at this particular problem, & hopefully some ways to potentially remedy the current situation.

Think for just a second about the number (I don't have any way to know for sure, but 1,000s, 10,000s, or maybe even 100,000s) of Teensy products that have been sold. Many users (myself included) regularly solder headers onto their own boards (personally, I've probably bought somewhere on the order of 50 T4.x boards, most without pins...not a huge sample, but enough to say with confidence that I've not experienced any particular sensitivity to adding pins with my Teensy units).

If there were really an excessive sensitivity to this process, surely there would have been many many more reports of such problems. Based upon the immediate responsiveness by PJRC to potential problems, evidence of which can easily be found in the past posts on this forum, if there were such a widespread problem, we can be almost certain that Paul would have already found & remedied such a problem. There have certainly been reported incidences of apparent damage during the pin soldering process, but it would appear to be very few compared to the implied number of units sold/delivered.

As you can well understand, it is impossible for any vendor such as PJRC to control and/or warrant what happens to their products after they leave the factory. Paul indicated in his post that every Teensy is double-checked as fully functional before it leaves his place. Some users have recommended in past forum posts that it might be prudent to test before even soldering headers. However, this would only serve as yet another check after the already performed factory double-check, so the likelihood of finding any faulty parts with this additional test is extremely low (certainly, not exactly zero), and you're currently well past the time when that might have been a beneficial possibility.

So, where does that leave you ?? Here are a few things that you might check/try:

- perform another visual inspection of the entire board (different lighting, different viewing angles, different magnifications, etc.)
- check for solder balls on/around the entire board, particularly around the FLASH
- if you have the ability to effectively solder SM components (correct flux, solder, iron, tip, ability to post-clean, etc. - from your previous post, it sounds like you do), you might try touching up anywhere that you suspect is not fully soldered - you're not likely to make things any worse, right ?!?!?
- and finally, for the most radical of things to try, if you have a toaster oven & you have some way to carefully monitor/control the temperature (& you're willing to retire it permanently from food duty )), you might try re-flowing the entire board (after fixing any components that appear to have been unsoldered by prior activities)

Best of luck & hopefully you can bring this particular T4 unit back to life !!

Mark J Culross
KD5RXT


EDIT: looks like you made some progress while I was composing my message !! MJC

[Dr.What]

I practically can reflash the Teensy over and over again when iam pressing the button after the first programming was finished, i can do this up to 3-4 times till the teensy finally fully disconnects and doesn't respond anymore until i physically reconnect it.


That does indeed is a bit over my competence.

18:08:08.790 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:08.791 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:08.791 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:08.791 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
18:08:08.791 (ports 5): found_usb_device, devinst=00000007
18:08:08.791 (ports 5): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:08.791 (ports 5): hiddev_from_devinst_list: iface=0
18:08:08.791 (ports 5): found_usb_device complete
18:08:08.792 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy) Bootloader
18:08:08.930 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:08.930 (ports 5): hid, found devinst=0000000C
18:08:08.930 (ports 5): hid, path=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000#{4 d1e55b2-f16f-11cf-88cb-001111000030}
18:08:08.930 (ports 5): hid, opened handle
18:08:08.930 (ports 5): devinst=0000000C, location=usb:80001/4/0/1/1
18:08:08.930 (ports 5): vid=16C0, pid=0478, ver=0108, usepage=FF9C, use=0025
18:08:08.930 (ports 5): devpath=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000 #{4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:08.931 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader
18:08:08.992 (loader): secure mode can not be locked: this is Standard Teensy
18:08:08.994 (loader): encryption is possible on this Teensy, but not yet configured
18:08:08.996 (loader): but without secure mode locked, encryption will NOT be secure!
18:08:08.998 (loader): Device came online, code_size = 8126464
18:08:08.999 (loader): Board is: Teensy 4.1 (IMXRT1062), version 1.08
18:08:09.006 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
18:08:09.008 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
18:08:09.031 (loader): set background IMG_ONLINE
18:08:09.039 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
18:08:09.041 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
18:08:09.065 (loader): elf appears to be for Teensy 4.1 (IMXRT1062) (8126464 bytes)
18:08:09.067 (loader): elf binary data matches hex file
18:08:09.072 (loader): elf file is for Teensy 4.1 (IMXRT1062)
18:08:09.075 (loader): using hex file
18:08:09.075 (serialmon 46): Begin, version=1.57, high-res time
18:08:09.075 (serialmon 46): listening for location: usb:80001/4/0/1/1
18:08:09.075 (serialmon 46): LoadLibrary cfgmgr32 ok
18:08:09.075 (serialmon 46): LoadLibrary ntdll ok
18:08:09.077 (serialmon 46): callback 0024
18:08:09.077 (serialmon 46): callback 0081
18:08:09.078 (serialmon 46): callback 0083
18:08:09.078 (serialmon 46): hWnd = 1378388
18:08:09.079 (serialmon 46): loop stdin, ready=262143
18:08:09.079 (serialmon 46): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:09.079 (serialmon 46): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:09.079 (serialmon 46): found_usb_device, devinst=00000003
18:08:09.079 (serialmon 46): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
18:08:09.079 (serialmon 46): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:09.079 (serialmon 46): hiddev_from_devinst_list: iface=0
18:08:09.080 (serialmon 46): found_usb_device complete
18:08:09.081 (serialmon 46): hid, found devinst=0000000B
18:08:09.081 (serialmon 46): usb_add: usb:80001/4/0/1/1
18:08:09.081 (serialmon 46): ignoring partial USB device discovery (Windows XP issue?)
18:08:09.100 (loader): begin operation
18:08:09.129 (loader): remote connection 1584 opened
18:08:09.133 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:09.134 (serialmon 46): hid, found devinst=0000000B
18:08:09.150 (loader): flash, block=0, bs=1024, auto=1
18:08:09.154 (loader): flash, block=1, bs=1024, auto=1
18:08:09.160 (loader): flash, block=2, bs=1024, auto=1
18:08:09.399 (serialmon 46): retry device discovery (Windows XP workaround)
18:08:09.400 (serialmon 46): hid, found devinst=0000000B
18:08:09.416 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:09.416 (ports 5): nothing new, skipping HID & Ports enum
18:08:09.453 (loader): flash, block=3, bs=1024, auto=1
18:08:09.460 (loader): flash, block=4, bs=1024, auto=1
18:08:09.469 (loader): flash, block=5, bs=1024, auto=1
18:08:09.474 (loader): flash, block=6, bs=1024, auto=1
18:08:09.480 (loader): flash, block=7, bs=1024, auto=1
18:08:09.485 (loader): flash, block=8, bs=1024, auto=1
18:08:09.491 (loader): flash, block=9, bs=1024, auto=1
18:08:09.496 (loader): flash, block=10, bs=1024, auto=1
18:08:09.501 (loader): flash, block=11, bs=1024, auto=1
18:08:09.507 (loader): flash, block=12, bs=1024, auto=1
18:08:09.512 (loader): flash, block=13, bs=1024, auto=1
18:08:09.518 (loader): flash, block=14, bs=1024, auto=1
18:08:09.549 (loader): sending reboot
18:08:09.554 (loader): begin wait_until_offline
18:08:09.559 (loader): offline, waited 0
18:08:09.563 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:09.563 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:09.564 (ports 5): remove: loc=usb:80001/4/0/1/1
18:08:09.564 (ports 5): usb_remove: usb:80001/4/0/1/1
18:08:09.564 (ports 5): nothing new, skipping HID & Ports enum
18:08:09.564 (serialmon 46): remove: loc=usb:80001/4/0/1/1
18:08:09.564 (serialmon 46): usb_remove: usb:80001/4/0/1/1
18:08:09.564 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:09.566 (loader): end operation, total time = 0.462 seconds
18:08:09.571 (loader): set background IMG_REBOOT_OK
18:08:09.577 (loader): redraw timer set, image 14 to show for 1200 ms
18:08:09.651 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:09.651 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:09.652 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:09.740 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:09.745 (loader): HID/win32: vid:0001 pid:0001 ver:0001
18:08:09.749 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:09.754 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:09.758 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:09.764 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
18:08:09.769 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
18:08:09.805 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:09.806 (ports 5): nothing new, skipping HID & Ports enum
18:08:09.841 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:09.841 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:09.841 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:09.841 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:09.841 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0486&REV_0280
18:08:09.841 (ports 5): found_usb_device, devinst=00000018
18:08:09.841 (ports 5): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0486, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:09.841 (ports 5): hiddev_from_devinst_list: iface=1
18:08:09.842 (serialmon 46): found_usb_device, id=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:09.842 (serialmon 46): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:09.842 (serialmon 46): found_usb_device, hwid=USB\VID_16C0&PID_0486&REV_0280
18:08:09.842 (serialmon 46): found_usb_device, devinst=00000017
18:08:09.842 (serialmon 46): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0486, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:09.842 (serialmon 46): hiddev_from_devinst_list: iface=1
18:08:09.842 (ports 5): found_usb_device complete
18:08:09.842 (serialmon 46): found_usb_device complete
18:08:09.842 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy 4.1) RawHID
18:08:09.842 (serialmon 46): usb_add: usb:80001/4/0/1/1
18:08:09.842 (serialmon 46): ignoring partial USB device discovery (Windows XP issue?)
18:08:09.980 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:09.980 (serialmon 46): update_usb_device, devinst list change, old had 2, new has 5
18:08:09.980 (serialmon 46): hiddev_from_devinst_list: iface=1
18:08:09.981 (serialmon 46): 0000001B: path=\\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0 000#{4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:09.981 (serialmon 46): hid, found devinst=0000001B
18:08:09.981 (serialmon 46): hid, found devinst=00000019
18:08:09.981 (serialmon 46): usb_add: usb:80001/4/0/1/1
18:08:09.981 (serialmon 46): Opened \\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0000#{ 4d1e55b2-f16f-11cf-88cb-001111000030} RawHID
18:08:10.244 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:10.244 (ports 5): update_usb_device, devinst list change, old had 1, new has 5
18:08:10.244 (ports 5): hiddev_from_devinst_list: iface=1
18:08:10.244 (ports 5): 0000001C: path=\\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0 000#{4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:10.245 (ports 5): hid, found devinst=0000001C
18:08:10.245 (ports 5): hid, found devinst=0000001A
18:08:10.245 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0486 (Teensy 4.1) RawHID
18:08:10.793 (loader): redraw, image 9
18:08:10.834 (serialmon 46): teensy read ov error
18:08:10.834 (serialmon 46): teensy read error
18:08:10.839 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:10.839 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:10.840 (serialmon 46): remove: loc=usb:80001/4/0/1/1
18:08:10.840 (serialmon 46): usb_remove: usb:80001/4/0/1/1
18:08:10.840 (serialmon 46): Disconnect \\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0000#{ 4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:10.840 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:10.840 (ports 5): remove: loc=usb:80001/4/0/1/1
18:08:10.840 (ports 5): usb_remove: usb:80001/4/0/1/1
18:08:10.840 (ports 5): nothing new, skipping HID & Ports enum
18:08:10.892 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:10.892 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:11.015 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:11.015 (ports 5): nothing new, skipping HID & Ports enum
18:08:11.150 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:11.151 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:11.151 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:11.151 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:11.151 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
18:08:11.151 (ports 5): found_usb_device, devinst=00000007
18:08:11.151 (ports 5): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:11.151 (ports 5): hiddev_from_devinst_list: iface=0
18:08:11.151 (ports 5): found_usb_device complete
18:08:11.151 (serialmon 46): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:11.151 (serialmon 46): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:11.151 (serialmon 46): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
18:08:11.151 (serialmon 46): found_usb_device, devinst=00000003
18:08:11.152 (serialmon 46): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:11.152 (serialmon 46): hiddev_from_devinst_list: iface=0
18:08:11.152 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy 4.1) Bootloader
18:08:11.152 (serialmon 46): found_usb_device complete
18:08:11.152 (serialmon 46): hid, found devinst=0000000B
18:08:11.152 (serialmon 46): usb_add: usb:80001/4/0/1/1
18:08:11.152 (serialmon 46): ignoring partial USB device discovery (Windows XP issue?)
18:08:11.210 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:11.211 (serialmon 46): hid, found devinst=0000000B
18:08:11.212 (serialmon 46): hid, found devinst=0000000B
18:08:11.235 (loader): secure mode can not be locked: this is Standard Teensy
18:08:11.239 (loader): encryption is possible on this Teensy, but not yet configured
18:08:11.243 (loader): but without secure mode locked, encryption will NOT be secure!
18:08:11.248 (loader): Device came online, code_size = 8126464
18:08:11.253 (loader): Board is: Teensy 4.1 (IMXRT1062), version 1.08
18:08:11.262 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
18:08:11.266 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
18:08:11.292 (loader): set background IMG_ONLINE
18:08:11.303 (loader): File "C:\Users\birkm\Documents\Arduino\blink_both\blink _fast_Teensy41.hex", 14452 bytes
18:08:11.307 (loader): File "blink_fast_Teensy41.hex". 14452 bytes, 0% used
18:08:11.334 (loader): elf appears to be for Teensy 4.1 (IMXRT1062) (8126464 bytes)
18:08:11.338 (loader): elf binary data matches hex file
18:08:11.342 (loader): elf file is for Teensy 4.1 (IMXRT1062)
18:08:11.347 (loader): using hex file
18:08:11.371 (loader): begin operation
18:08:11.402 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:11.403 (ports 5): hid, found devinst=0000000C
18:08:11.403 (ports 5): hid, path=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000#{4 d1e55b2-f16f-11cf-88cb-001111000030}
18:08:11.403 (ports 5): hid, opened handle
18:08:11.403 (ports 5): devinst=0000000C, location=usb:80001/4/0/1/1
18:08:11.403 (ports 5): vid=16C0, pid=0478, ver=0108, usepage=FF9C, use=0025
18:08:11.403 (ports 5): devpath=\\?\hid#vid_16c0&pid_0478#8&abecdd3&0&0000 #{4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:11.403 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader
18:08:11.460 (loader): flash, block=0, bs=1024, auto=1
18:08:11.464 (loader): flash, block=1, bs=1024, auto=1
18:08:11.467 (serialmon 46): retry device discovery (Windows XP workaround)
18:08:11.468 (serialmon 46): hid, found devinst=0000000B
18:08:11.469 (loader): flash, block=2, bs=1024, auto=1
18:08:11.717 (serialmon 46): retry device discovery (Windows XP workaround)
18:08:11.718 (serialmon 46): hid, found devinst=0000000B
18:08:11.749 (loader): flash, block=3, bs=1024, auto=1
18:08:11.754 (loader): flash, block=4, bs=1024, auto=1
18:08:11.761 (loader): flash, block=5, bs=1024, auto=1
18:08:11.768 (loader): flash, block=6, bs=1024, auto=1
18:08:11.775 (loader): flash, block=7, bs=1024, auto=1
18:08:11.782 (loader): flash, block=8, bs=1024, auto=1
18:08:11.787 (loader): flash, block=9, bs=1024, auto=1
18:08:11.792 (loader): flash, block=10, bs=1024, auto=1
18:08:11.798 (loader): flash, block=11, bs=1024, auto=1
18:08:11.803 (loader): flash, block=12, bs=1024, auto=1
18:08:11.809 (loader): flash, block=13, bs=1024, auto=1
18:08:11.814 (loader): flash, block=14, bs=1024, auto=1
18:08:11.843 (loader): sending reboot
18:08:11.848 (loader): begin wait_until_offline
18:08:11.858 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:11.858 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:11.859 (serialmon 46): remove: loc=usb:80001/4/0/1/1
18:08:11.859 (serialmon 46): usb_remove: usb:80001/4/0/1/1
18:08:11.859 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:11.859 (ports 5): remove: loc=usb:80001/4/0/1/1
18:08:11.859 (ports 5): usb_remove: usb:80001/4/0/1/1
18:08:11.859 (ports 5): nothing new, skipping HID & Ports enum
18:08:11.908 (loader): offline, waited 1
18:08:11.913 (loader): end operation, total time = 0.537 seconds
18:08:11.918 (loader): set background IMG_REBOOT_OK
18:08:11.925 (loader): redraw timer set, image 14 to show for 1200 ms
18:08:11.946 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:11.947 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:11.947 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:11.986 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:11.992 (loader): HID/win32: vid:0001 pid:0001 ver:0001
18:08:11.998 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:12.002 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:12.007 (loader): HID/win32: vid:046D pid:C093 ver:5300 usb:80001/3/0/2/3
18:08:12.012 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
18:08:12.022 (loader): HID/win32: vid:04F3 pid:30FD ver:0001
18:08:12.111 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:12.111 (ports 5): nothing new, skipping HID & Ports enum
18:08:12.121 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:12.121 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:12.121 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:12.121 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:12.121 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0486&REV_0280
18:08:12.121 (ports 5): found_usb_device, devinst=00000018
18:08:12.121 (ports 5): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0486, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:12.121 (ports 5): hiddev_from_devinst_list: iface=1
18:08:12.121 (serialmon 46): found_usb_device, id=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:12.121 (serialmon 46): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:12.121 (serialmon 46): found_usb_device, hwid=USB\VID_16C0&PID_0486&REV_0280
18:08:12.121 (serialmon 46): found_usb_device, devinst=00000017
18:08:12.121 (serialmon 46): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0486, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0486#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:12.121 (serialmon 46): hiddev_from_devinst_list: iface=1
18:08:12.122 (ports 5): found_usb_device complete
18:08:12.122 (serialmon 46): found_usb_device complete
18:08:12.122 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy 4.1) RawHID
18:08:12.122 (serialmon 46): usb_add: usb:80001/4/0/1/1
18:08:12.122 (serialmon 46): ignoring partial USB device discovery (Windows XP issue?)
18:08:12.285 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:12.285 (serialmon 46): update_usb_device, devinst list change, old had 1, new has 5
18:08:12.285 (serialmon 46): hiddev_from_devinst_list: iface=1
18:08:12.285 (serialmon 46): 0000001B: path=\\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0 000#{4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:12.286 (serialmon 46): hid, found devinst=0000001B
18:08:12.286 (serialmon 46): hid, found devinst=00000019
18:08:12.286 (serialmon 46): usb_add: usb:80001/4/0/1/1
18:08:12.286 (serialmon 46): Opened \\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0000#{ 4d1e55b2-f16f-11cf-88cb-001111000030} RawHID
18:08:12.439 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:12.440 (ports 5): update_usb_device, devinst list change, old had 1, new has 5
18:08:12.440 (ports 5): hiddev_from_devinst_list: iface=1
18:08:12.440 (ports 5): 0000001C: path=\\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0 000#{4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:12.441 (ports 5): hid, found devinst=0000001C
18:08:12.441 (ports 5): hid, found devinst=0000001A
18:08:12.441 (ports 5): usb_add: usb:80001/4/0/1/1 hid#vid_16c0&pid_0486 (Teensy 4.1) RawHID
18:08:12.914 (serialmon 46): teensy read ov error
18:08:12.914 (serialmon 46): teensy read error
18:08:12.919 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:12.919 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:12.920 (serialmon 46): remove: loc=usb:80001/4/0/1/1
18:08:12.920 (serialmon 46): usb_remove: usb:80001/4/0/1/1
18:08:12.920 (serialmon 46): Disconnect \\?\hid#vid_16c0&pid_0486&mi_01#9&5c8d2f2&0&0000#{ 4d1e55b2-f16f-11cf-88cb-001111000030}
18:08:12.920 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:12.920 (ports 5): remove: loc=usb:80001/4/0/1/1
18:08:12.920 (ports 5): usb_remove: usb:80001/4/0/1/1
18:08:12.920 (ports 5): nothing new, skipping HID & Ports enum
18:08:12.974 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:12.974 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:13.095 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:13.096 (ports 5): nothing new, skipping HID & Ports enum
18:08:13.126 (loader): redraw, image 9
18:08:13.230 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:13.231 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEARRIVAL
18:08:13.231 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:13.231 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:13.231 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
18:08:13.231 (ports 5): found_usb_device, devinst=00000007
18:08:13.231 (ports 5): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:13.231 (ports 5): hiddev_from_devinst_list: iface=0
18:08:13.231 (serialmon 46): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:13.231 (serialmon 46): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
18:08:13.231 (serialmon 46): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
18:08:13.231 (serialmon 46): found_usb_device, devinst=00000003
18:08:13.231 (serialmon 46): add: loc=usb:80001/4/0/1/1, class=HID, vid=16C0, pid=0478, ver=0108, serial=00134c0a, dev=\\?\usb#vid_16c0&pid_0478#00134c0a#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
18:08:13.231 (serialmon 46): hiddev_from_devinst_list: iface=0
18:08:13.231 (ports 5): found_usb_device complete
18:08:13.232 (serialmon 46): found_usb_device complete
18:08:13.232 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy 4.1) Bootloader
18:08:13.232 (serialmon 46): usb_add: usb:80001/4/0/1/1
18:08:13.232 (serialmon 46): ignoring partial USB device discovery (Windows XP issue?)
18:08:13.266 (serialmon 46): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:13.266 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
18:08:13.267 (serialmon 46): remove: loc=usb:80001/4/0/1/1
18:08:13.267 (serialmon 46): usb_remove: usb:80001/4/0/1/1
18:08:13.267 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:13.267 (ports 5): remove: loc=usb:80001/4/0/1/1
18:08:13.267 (ports 5): usb_remove: usb:80001/4/0/1/1
18:08:13.267 (ports 5): nothing new, skipping HID & Ports enum
18:08:13.300 (serialmon 46): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:13.301 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:13.301 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:13.423 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
18:08:13.424 (ports 5): nothing new, skipping HID & Ports enum
18:08:13.562 (serialmon 46): retry device discovery (Windows XP workaround)
18:08:13.563 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:13.813 (serialmon 46): retry device discovery (Windows XP workaround)
18:08:13.813 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:14.066 (serialmon 46): retry device discovery (Windows XP workaround)
18:08:14.066 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:14.317 (serialmon 46): retry device discovery (Windows XP workaround)
18:08:14.317 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:14.569 (serialmon 46): timeout
18:08:14.569 (serialmon 46): nothing new, skipping HID & Ports enum
18:08:14.961 (ports 5): purge, name=[no_device] (Teensy 4.1) Bootloader, loc=usb:80001/4/0/1/1, age=1.694 sec
18:08:15.084 (loader): remote connection 1584 closed

[Dr.What]

@Dr.What:

Please take this post in the fully intended positive manner. I mean absolutely no malice with my comments !! I'm just attempting to give an alternate way to look at this particular problem, & hopefully some ways to potentially remedy the current situation.

Think for just a second about the number (I don't have any way to know for sure, but 1,000s, 10,000s, or maybe even 100,000s) of Teensy products that have been sold. Many users (myself included) regularly solder headers onto their own boards (personally, I've probably bought somewhere on the order of 50 T4.x boards, most without pins...not a huge sample, but enough to say with confidence that I've not experienced any particular sensitivity to adding pins with my Teensy units).

If there were really an excessive sensitivity to this process, surely there would have been many many more reports of such problems. Based upon the immediate responsiveness by PJRC to potential problems, evidence of which can easily be found in the past posts on this forum, if there were such a widespread problem, we can be almost certain that Paul would have already found & remedied such a problem. There have certainly been reported incidences of apparent damage during the pin soldering process, but it would appear to be very few compared to the implied number of units sold/delivered.

As you can well understand, it is impossible for any vendor such as PJRC to control and/or warrant what happens to their products after they leave the factory. Paul indicated in his post that every Teensy is double-checked as fully functional before it leaves his place. Some users have recommended in past forum posts that it might be prudent to test before even soldering headers. However, this would only serve as yet another check after the already performed factory double-check, so the likelihood of finding any faulty parts with this additional test is extremely low (certainly, not exactly zero), and you're currently well past the time when that might have been a beneficial possibility.

So, where does that leave you ?? Here are a few things that you might check/try:

- perform another visual inspection of the entire board (different lighting, different viewing angles, different magnifications, etc.)
- check for solder balls on/around the entire board, particularly around the FLASH
- if you have the ability to effectively solder SM components (correct flux, solder, iron, tip, ability to post-clean, etc. - from your previous post, it sounds like you do), you might try touching up anywhere that you suspect is not fully soldered - you're not likely to make things any worse, right ?!?!?
- and finally, for the most radical of things to try, if you have a toaster oven & you have some way to carefully monitor/control the temperature (& you're willing to retire it permanently from food duty )), you might try re-flowing the entire board (after fixing any components that appear to have been unsoldered by prior activities)

Best of luck & hopefully you can bring this particular T4 unit back to life !!

Mark J Culross
KD5RXT


EDIT: looks like you made some progress while I was composing my message !! MJC

No offense taken.
I also did not intend to offend.

Well my first teensy was over a year ago, of course there wouldnt be any warranty on it anymore.
Well...cant help but am disappointed, though of course if i would know any better, well i would know what iam doing wrong in the first place.
from my point, i mean its not very hard to solder headers onto a pcb, so i fail to see how it can change the behavior of the teensy in the first place, as unless you have a tremor / Parkinsons disease...well i just cant find the reason, which doesnt mean i made a total rookie mistake.

The flash memory seems to be working now which still leaves open the question why i can flash it but its still powering down after the same time as before.

Yes maybe iam just totally unlucky being one in a million twice.

I mean, unless you have Parkinsons, you dont use overly much solder, the contacts are previously wetted with flux which i think is likely conductive while wet.
So the flux could get from the pins to the chips, but it should be gone when rinsed off after soldering and should any remain the resistance should be so high.... mhhhh well maybe i will record myself the next time iam doing it so if it fails, somebody else can look at it and tell me what i did wrong.

[Dr.What]

did compare the verbose output of both teensys now.

The healthy working one :

19:19:59.508 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
19:19:59.509 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0483#8917650#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:19:59.509 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
19:19:59.509 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0483&REV_0280
19:19:59.509 (ports 5): found_usb_device, devinst=0000002a
19:19:59.509 (ports 5): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0483, ver=0280, serial=8917650, dev=\\?\usb#vid_16c0&pid_0483#8917650#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:19:59.509 (ports 5): comport_from_devinst_list attempt
19:19:59.509 (ports 5): found_usb_device complete
19:19:59.509 (ports 5): usb_add: usb:80001/4/0/1/1 [no_device] (Teensy 4.1) Serial
19:19:59.610 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
19:19:59.610 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
19:19:59.610 (ports 5): update_usb_device, devinst list change, old had 1, new has 2
19:19:59.610 (ports 5): comport_from_devinst_list attempt
19:19:59.610 (ports 5): found Ports in classguid_list at index=1
19:19:59.610 (ports 5): port COM7 found from devnode
19:19:59.611 (ports 5): usb_add: usb:80001/4/0/1/1 COM7 (Teensy 4.1) Serial
19:19:59.939 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
19:19:59.940 (ports 5): nothing new, skipping HID & Ports enum
19:20:00.478 (serialmon 93): Begin, version=1.57, high-res time
19:20:00.478 (serialmon 93): listening for location: usb:80001/4/0/1/1
19:20:00.478 (serialmon 93): LoadLibrary cfgmgr32 ok
19:20:00.478 (serialmon 93): LoadLibrary ntdll ok
19:20:00.480 (serialmon 93): callback 0024
19:20:00.480 (serialmon 93): callback 0081
19:20:00.482 (serialmon 93): callback 0083
19:20:00.482 (serialmon 93): hWnd = 460926
19:20:00.482 (serialmon 93): loop stdin, ready=262143
19:20:00.483 (serialmon 93): found_usb_device, id=\\?\usb#vid_16c0&pid_0483#8917650#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:20:00.483 (serialmon 93): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
19:20:00.483 (serialmon 93): found_usb_device, hwid=USB\VID_16C0&PID_0483&REV_0280
19:20:00.483 (serialmon 93): found_usb_device, devinst=00000003
19:20:00.483 (serialmon 93): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0483, ver=0280, serial=8917650, dev=\\?\usb#vid_16c0&pid_0483#8917650#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:20:00.483 (serialmon 93): comport_from_devinst_list attempt
19:20:00.483 (serialmon 93): found Ports in classguid_list at index=1
19:20:00.483 (serialmon 93): port COM7 found from devnode
19:20:00.483 (serialmon 93): found_usb_device complete
19:20:00.484 (serialmon 93): usb_add: usb:80001/4/0/1/1
19:20:00.484 (serialmon 93): translate "COM7" -> "\\.\COM7"
19:20:00.504 (serialmon 93): GetDefaultCommConfig success
19:20:00.526 (serialmon 93): SetDefaultCommConfig success
19:20:00.526 (serialmon 93): Opened \\.\COM7 Serial
19:20:00.527 (ports 5): callback 001A
19:20:00.539 (loader): remote connection 3172 opened


The problematic one:


19:21:17.460 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
19:21:17.461 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:21:17.461 (ports 5): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
19:21:17.461 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0483&REV_0280
19:21:17.461 (ports 5): found_usb_device, devinst=0000001d
19:21:17.461 (ports 5): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0483, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:21:17.461 (ports 5): comport_from_devinst_list attempt
19:21:17.461 (ports 5): found Ports in classguid_list at index=1
19:21:17.461 (ports 5): port COM12 found from devnode
19:21:17.461 (ports 5): found_usb_device complete
19:21:17.461 (ports 5): usb_add: usb:80001/4/0/1/1 COM12 (Teensy 4.1) Serial
19:21:17.479 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
19:21:17.479 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
19:21:17.480 (ports 5): nothing new, skipping HID & Ports enum
19:21:17.806 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
19:21:17.807 (ports 5): nothing new, skipping HID & Ports enum
19:21:17.952 (serialmon 95): Begin, version=1.57, high-res time
19:21:17.952 (serialmon 95): listening for location: usb:80001/4/0/1/1
19:21:17.952 (serialmon 95): LoadLibrary cfgmgr32 ok
19:21:17.952 (serialmon 95): LoadLibrary ntdll ok
19:21:17.954 (serialmon 95): callback 0024
19:21:17.954 (serialmon 95): callback 0081
19:21:17.956 (serialmon 95): callback 0083
19:21:17.956 (serialmon 95): hWnd = 919682
19:21:17.956 (serialmon 95): loop stdin, ready=262143
19:21:17.957 (serialmon 95): found_usb_device, id=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:21:17.957 (serialmon 95): found_usb_device, loc=usb:80001/4/0/1/1 Port_#0001.Hub_#0003
19:21:17.957 (serialmon 95): found_usb_device, devinst=00000004
19:21:17.957 (serialmon 95): found_usb_device, hwid=USB\VID_16C0&PID_0483&REV_0280
19:21:17.957 (serialmon 95): add: loc=usb:80001/4/0/1/1, class=USB, vid=16C0, pid=0483, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
19:21:17.957 (serialmon 95): comport_from_devinst_list attempt
19:21:17.957 (serialmon 95): found Ports in classguid_list at index=1
19:21:17.957 (serialmon 95): port COM12 found from devnode
19:21:17.957 (serialmon 95): found_usb_device complete
19:21:17.958 (serialmon 95): usb_add: usb:80001/4/0/1/1
19:21:17.958 (serialmon 95): translate "COM12" -> "\\.\COM12"
19:21:17.979 (serialmon 95): GetDefaultCommConfig success
19:21:18.001 (serialmon 95): SetDefaultCommConfig success
19:21:18.001 (serialmon 95): Opened \\.\COM12 Serial
19:21:18.002 (ports 5): callback 001A
19:21:18.013 (loader): remote connection 3048 opened
19:21:18.017 (serialmon 95): callback 001A
19:21:22.145 (serialmon 95): teensy read ov error
19:21:22.145 (serialmon 95): teensy read error
19:21:22.149 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
19:21:22.150 (ports 5): remove: loc=usb:80001/4/0/1/1
19:21:22.150 (ports 5): usb_remove: usb:80001/4/0/1/1
19:21:22.150 (ports 5): nothing new, skipping HID & Ports enum
19:21:22.150 (serialmon 95): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
19:21:22.151 (serialmon 95): remove: loc=usb:80001/4/0/1/1
19:21:22.151 (serialmon 95): usb_remove: usb:80001/4/0/1/1
19:21:22.151 (serialmon 95): Disconnect \\.\COM12
19:21:22.151 (serialmon 95): nothing new, skipping HID & Ports enum
19:21:22.165 (serialmon 95): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
19:21:22.165 (serialmon 95): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
19:21:22.165 (serialmon 95): nothing new, skipping HID & Ports enum
19:21:22.319 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
19:21:22.319 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
19:21:22.320 (ports 5): nothing new, skipping HID & Ports enum
19:21:23.845 (ports 5): purge, name=COM12 (Teensy 4.1) Serial, loc=usb:80001/4/0/1/1, age=1.695 sec
19:21:23.973 (loader): remote connection 3048 closed


Black marked text is where the freshly bought teensy behaves differently and has a problem.
I guess read ov error means an over voltage error? or the inability to read / check for potential overvoltage?
Not sure what the callback 001A is.

If anybody knows anything, iam happy for any advise.

[Dr.What]

okay so apparently it works now.

apologies again i didn't want to be rude with asking about warranty.

with the thought of certain defeat i did rinse it with H2o and ethanol again, did even connect it while still being wet and it failed to initialize anything that time with the LED blinking twice or 4 times.
I did put the soldering iron to 480°C and just heated every pin quite a while, i did put the soldering iron with flat tip directly onto the Winbond chip, i put the shaft of the soldering iron onto the MIMXRT at 480°C and kept it there for a minute or so.
After it cooled down, it works now.
I would have never ever thought this could work, and iam a bit baffled.

How is it possible that i damage the soldering in the first place when being very careful and soldering the headers at low temp and being so brutal applying 480°C directly to the chips.
Yeah idea would be that with 480°C its likely the contacts reach a temperature that makes the solder melt again, but how is it possible that they become disconnected in the first place when using low temp and only applied at the pins?
Are microfilaments of solder a common thing? I didnt slide down the pins with the iron but touched each after another to make fully sure i dont form a connection between them.
Normally id be careful as if handling optical components, how can it be alive now?

anyway, happy its working :-)

Thanks for your time!


20:44:38.813 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
20:44:38.814 (ports 5): remove: loc=usb:80001/4/0/1
20:44:38.814 (ports 5): usb_remove: usb:80001/4/0/1
20:44:38.814 (ports 5): nothing new, skipping HID & Ports enum
20:44:38.822 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
20:44:38.822 (ports 5): nothing new, skipping HID & Ports enum
20:44:38.822 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
20:44:38.823 (ports 5): nothing new, skipping HID & Ports enum
20:44:40.464 (ports 5): purge, name=COM12 (Teensy 4.1) Serial, loc=usb:80001/4/0/1, age=1.650 sec
20:44:40.701 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
20:44:40.701 (ports 5): nothing new, skipping HID & Ports enum
20:44:40.703 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
20:44:40.703 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
20:44:40.703 (ports 5): found_usb_device, loc=usb:80001/4/0/1 Port_#0001.Hub_#0001
20:44:40.703 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0483&REV_0280
20:44:40.703 (ports 5): found_usb_device, devinst=00000005
20:44:40.703 (ports 5): add: loc=usb:80001/4/0/1, class=USB, vid=16C0, pid=0483, ver=0280, serial=12646500, dev=\\?\usb#vid_16c0&pid_0483#12646500#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
20:44:40.703 (ports 5): comport_from_devinst_list attempt
20:44:40.703 (ports 5): found_usb_device complete
20:44:40.704 (ports 5): usb_add: usb:80001/4/0/1 [no_device] (Teensy 4.1) Serial
20:44:40.723 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
20:44:40.724 (ports 5): update_usb_device, devinst list change, old had 1, new has 2
20:44:40.724 (ports 5): comport_from_devinst_list attempt
20:44:40.724 (ports 5): found Ports in classguid_list at index=1
20:44:40.724 (ports 5): port COM12 found from devnode
20:44:40.724 (ports 5): usb_add: usb:80001/4/0/1 COM12 (Teensy 4.1) Serial
20:44:41.075 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
20:44:41.076 (ports 5): nothing new, skipping HID & Ports enum

[PaulStoffregen]

How is it possible that i damage the soldering in the first place when being very careful and soldering the headers at low temp and being so brutal applying 480°C directly to the chips.

Again, answers about "how" and "why" over the internet are usually just blind guesswork.

But generally speaking, the BGA chips can handle a pretty incredible amount of heat if it is uniform across the whole chip. But if just one side or corner of the chip gets heated, BGA can have problems where uneven thermal expansion can stress the solder connections.

Whether that's what really happened, I can't say. But it is a problem we've seen occasionally, moreso with Teensy 3.5 and 3.6 where the BGA chip is 13mm which leaves little clearance to the pads on the edge of the board.

[Dr.What]

Again, answers about "how" and "why" over the internet are usually just blind guesswork.

But generally speaking, the BGA chips can handle a pretty incredible amount of heat if it is uniform across the whole chip. But if just one side or corner of the chip gets heated, BGA can have problems where uneven thermal expansion can stress the solder connections.

Whether that's what really happened, I can't say. But it is a problem we've seen occasionally, moreso with Teensy 3.5 and 3.6 where the BGA chip is 13mm which leaves little clearance to the pads on the edge of the board.

Of course, but your blind guesswork / the guesswork of the collective has way higher chance of success then my own.
Without the posts here i would have never ever applied heat to the teensy over a year ago and never would have applied THAT much heat to the new one yesterday.
I also would have never guessed that thermal expansion could have this effect on ceramic/solder. Of course only a guess now, but its the best guess and actually makes the most sense. Curious how you found out in the first place.
Guess one could apply a dye to the board, let it dry and then try to rip off the chip mechanically, if there is dye at the contacts it would mean no contact was there.

Anyway, thanks a lot for your time!

Happy Dezember time and stay healthy :-)