Teensyduino 1.59 Beta #3

Paul

Administrator
Staff member
Here is a third beta test for Teensyduino 1.59.

Arduino 2.0.x, all systems platforms:
use Boards Manager to install Teensy version 0.59.3
(to refresh versions, Shift-Ctrl-P and click "Arduino: Update Package Index")

Arduino 1.8.x, Linux 32 bit:
https://www.pjrc.com/teensy/td_159-beta3/TeensyduinoInstall.linux32

Arduino 1.8.x, Linux 64 bit:
https://www.pjrc.com/teensy/td_159-beta3/TeensyduinoInstall.linux64

Arduino 1.8.x, Linux ARM:
https://www.pjrc.com/teensy/td_159-beta3/TeensyduinoInstall.linuxarm

Arduino 1.8.x, Linux ARM64:
https://www.pjrc.com/teensy/td_159-beta3/TeensyduinoInstall.linuxaarch64

Arduino 1.8.x, MacOS (Catalina to Ventura)
https://www.pjrc.com/teensy/td_159-beta3/Teensyduino_MacOS_Catalina.zip

Arduino 1.8.x, Old MacOS (Mojave)
https://www.pjrc.com/teensy/td_159-beta3/TeensyduinoInstall.dmg

Arduino 1.8.x, Windows:
https://www.pjrc.com/teensy/td_159-beta3/TeensyduinoInstall.exe

PlatformIO, DIY beta support:
https://forum.pjrc.com/threads/71730


Changes since Teensyduino 1.59-beta2:

Fix const init on Wire, SPI, HardwareSerial
Update FlexIO_t4 - ??? (KurtE)
define SPI_HAS_NOTUSINGINTERRUPT
define WIRE_INTERFACES_COUNT and SPI_INTERFACES_COUNT
make availableForWrite virtual (Shawn Silverman)
remove old abs() and round() (mjs513)
CrashReport breadcrumbs improved
update example Makefile
fix Lockable Teensy auto-reboot with optimize smallest size with LTO
fix USB Touchscreen on Teensy 4.x with Windows
extmem_calloc() clears memory (Shawn Silverman)
add Print::vprintf() (Randy Palamar)
Audio improve AudioEffectWaveshaper initialization
Update ILI9488_t3 - ???
Update Keypad - Allow time for signals to settle
Update LittleFS - Add support for GigaDevice NOR Flash
Update RA8875 - ???
Update ST7735_t3 - ???
USBHost_t36 improve timers, fixes simultaneous transmit to 3+ devices
USBHost_t36 fix MIDI fast sustained receive
USBHost_t36 HID parser changes??? (KurtE)
USBHost_t36 RawHID improvements (KurtE)
USBHost_t36 Serial example update (KurtE)
teensy_secure add encrypthex_unlocksnvs option
Teensy monitor on Windows avoid 0 baud setting - not yet in IDE2 packages
 
@Paul - just updated IDE 2.1.1 no issues so now have b3 installed. Ditto for 1.8.19 - installed no issues. Will do a bit of testing now
 
Ran the problem code from this thread https://forum.pjrc.com/threads/7330...-else-same-code-bootloops?p=329705#post329705 to check "Fix const init on Wire, SPI, HardwareSerial" and it compiled and ran without hangs - acted same way as when I move Wire1 to setup:
Code:
Start setup
SerialAOG, SerialRTK, SerialGPS and SerialGPS2 initialized

Starting AutoSteer...
ADC Connecton FAILED!
Autosteer disabled, GPS only mode

Starting Ethernet...
Initializing ethernet with static IP address
Ethernet cable is not connected - Who cares we will start ethernet anyway.

Ethernet status OK
IP set Manually: 192.168.5.120

Ethernet IP of module: 192.168.5.120
Ethernet sending to IP: 192.168.5.255
All data sending to port: 9999
Ethernet GPS UDP sending from port: 5120
Ethernet NTRIP UDP listening to port: 2233
Ethernet AutoSteer UDP listening to & send from port: 8888

Starting IMU...
Swapping GPS ports...

Also ran usbhost update to check ps4 controller still connects: still works - just had to check.

EDIT: Also ran you sketch from https://forum.pjrc.com/threads/7317...-3-1-and-5-4-1?p=329151&viewfull=1#post329151

Code:
Serial: var #2 = 200002F8
Serial2: var #1 = 40190000
Serial2: var #2 = 20000FC0
Serial3: var #1 = 40188000
Serial3: var #2 = 20000F00
Serial4: var #1 = 4018C000
Serial4: var #2 = 20000F60
Serial5: var #1 = 401A0000
Serial5: var #2 = 200010E0
Serial6: var #1 = 40184000
Serial6: var #2 = 20000EA0
Serial7: var #1 = 4019C000
Serial7: var #2 = 20001080
Serial8: var #1 = 40194000
Serial8: var #2 = 20001020

setup
Wire: var #1 = 403F0000
Wire: var #2 = 60001F14
Wire1: var #1 = 403F8000
Wire1: var #2 = 60001E74
Wire2: var #1 = 403FC000
Wire2: var #2 = 60001E74
SPI: var #1 = 403A0000
SPI: var #2 = 20000438
SPI1: var #1 = 4039C000
SPI1: var #2 = 200003C8
SPI2: var #1 = 40394000
SPI2: var #2 = 20000358
Serial: var #1 = 40198000
Serial: var #2 = 200002F8
Serial2: var #1 = 40190000
Serial2: var #2 = 20000FC0
Serial3: var #1 = 40188000
Serial3: var #2 = 20000F00
Serial4: var #1 = 4018C000
Serial4: var #2 = 20000F60
Serial5: var #1 = 401A0000
Serial5: var #2 = 200010E0
Serial6: var #1 = 40184000
Serial6: var #2 = 20000EA0
Serial7: var #1 = 4019C000
Serial7: var #2 = 20001080
Serial8: var #1 = 40194000
Serial8: var #2 = 20001020
 
Last edited:
@Paul
Been playing around with the Arducam and decided to test on the Teensy 3.2 and looks like issue:
Fix const init on Wire, SPI, HardwareSerial

has the same issue not just the T4's. Probably missed that in the threads.
 
See this post for a fix for a bug in inplace_function.h (including an example program that shows the error):
https://forum.pjrc.com/threads/70986-Lightweight-C-callbacks?p=331086&viewfull=1#post331086

In short, there's a compile error when using a non-void return type and when either testing for or calling an unassigned function.
The post references this PR as a fix:
https://github.com/PaulStoffregen/cores/pull/717

Please see the comments in that PR; I'd love to have a discussion about it if there's any questions. Specifically, I've decided to use `std::__throw_bad_function_call()` instead of `std::abort()` because that's what `std::function` does now and `inplace_function` might do in the future if it's ever included in the C++ standard. I wanted the behaviour to be the same. However, `std::__throw_bad_function_call()` calls `std::terminate()`, which might output stuff on `stderr`, and `std::abort()` doesn't. I don't think this is much of a concern because that's the behaviour of today's `std::function` anyway, so why not make them the same?
 
Last edited:
Hi
Paul - I am using Teensy Loader 1.57 and I can see the COM6 for my Teensy 3.1 - but for Teensy 4.1 the Port does not show up? I can reset the Teensy4.1 I see the red Led but I can not load anything into Teeensy4.1 I have Verbose text enclosed where I change Ports on my computer in order to see if Teens 4.1 is reacting... Still I can not use this Teensy 4.1 - In EU its hard to get Teensy4.1 and prices are very high in compere to US - I could order a new Teensy from Us - but this would mean I need to wait for along time due to delivery...
Is this Teensy4.1 useless or I can do something to get it working?
Verbose log enclosed.View attachment VerboseTeensy 4.1.txt
 
If I compare Verbose of working Teensy 4.1 to not accepting Port Teensy 4.1 I get this: Meaning ??
 

Attachments

  • Verbose Compare Two Teensy4.1.jpg
    Verbose Compare Two Teensy4.1.jpg
    151 KB · Views: 90
Not Paul - but quick look shows this (after rejected upload of T_3.2 hex):
Code:
21:14:45.479 (loader): elf file is for Teensy 4.1 (IMXRT1062)
21:14:45.479 (loader): using hex file
21:14:45.494 (loader): begin operation
21:14:45.515 (loader): remote connection 1400 closed
21:14:45.515 (loader): remote connection 788 closed
21:14:45.521 (loader): flash, block=0, bs=1024, auto=1
21:14:45.521 (loader): flash, block=1, bs=1024, auto=1
21:14:45.522 (loader): flash, block=2, bs=1024, auto=1
21:15:15.529 (loader): program: write error

And then:
Code:
21:18:51.585 (loader): Board is: NXP IMXRT1062 ROM
21:18:51.589 (loader): begin operation
21:18:51.602 (loader): File "C:\Users\hp\AppData\Local\Temp\arduino_build_524086\sketch_sep02a.ino.hex", 21504 bytes
21:18:51.608 (loader): File "sketch_sep02a.ino.hex". 21504 bytes
21:18:51.614 (loader): set background IMG_ONLINE
21:18:51.622 (loader): nxp_write: success
21:18:51.628 (loader): nxp_write: success
21:18:51.630 (loader): HAB open mode, bootcfg=80018
21:18:51.634 (loader): Opps, NXP ROM in open mode, but we do not yet have code for this case :(
21:18:51.639 (loader): start ignoring usb:0/140000/0/4

First suggests an upload failed - then repeats of the "Opps" case follow.

Not sure if this is a problem with Cable? A cable that works for T_3.2 may not be high enough quality for use with T_4.x where USB runs 40 times faster.

Perhaps find a good cable to test and maybe do the T_4.1's 15 second Restore process:
> power T_4.1
> press button and hold until RED LED gives a Flash and release in 13-17 seconds
> Leave T_4.1 powered and watch RED LED for about a minute until it stops activity
-> T_4.1 should then be running a factory 1 second Blink

Try upload of a simple sketch with Serial to the T_4.1 ...
 
Hi, I tried 3 USB cables already - But see#10 - two Teensys 4.1 - one works other does not see the Port ? and Verbosen is not complete - why not ?
Somebody knows ? Is the second Teensy4.1 damaged or ? Can I reuse it - bring beck to life ?
Thanks
Mike
 
Hi, I tried 3 USB cables already - But see#10 - two Teensys 4.1 - one works other does not see the Port ? and Verbosen is not complete - why not ?
Somebody knows ? Is the second Teensy4.1 damaged or ? Can I reuse it - bring beck to life ?
Thanks
Mike

Do what @Defragster suggested.
....and maybe do the T_4.1's 15 second Restore process:
> power T_4.1
> press button and hold until RED LED gives a Flash and release in 13-17 seconds
> Leave T_4.1 powered and watch RED LED for about a minute until it stops activity
-> T_4.1 should then be running a factory 1 second Blink
 
I tried now 15 sec Restore - it is not happening - I do hear only Windows sound trying to reach the USB drive COM Port and in device manager I see Teensy looking for COM port (window opens and closes immediately trying to open COM Port) but not finding it...
 
Is this Teensy4.1 useless or I can do something to get it working?

First step is to use the 15 sec restore. Hold the pushbutton for 15 seconds. The red LED gives a quick blink when you're within the 4 second window to release the pushbutton. Full erase takes a long time, over 1 minute. The red LED will remain on solid. Let it finish. When done, you should see the red LED turn off and the orange LED (pin 13) starts blinking again.

The process restores everything back to how it was when Teensy shipped. In Arduino IDE, it will appear as a HID device, not a serial device / COM port. But once you successfully upload a program, of course the USB becomes whatever is selected in the Tools > USB Type menu. Just know to expect HID and not "everything must always be a serial port" as with traditional Arduino.
 
A couple of things to make note of:

If you have a brand new T4.x that's never been programmed (or a T4.x that's successfly completed the recovery procedure), it will not show up as a COM port. New/recovered T4.x devices show up as a HID device until programmed the first time. Also, new/recovered T4.x devices will run the "blink" sketch by default. You should compile & load the "blink" sketch as your first test with a new/recovered T4.x device by pressing the PROGRAM button on the device. This well also help to confirm that your cable works correctly.

Also, if/when you press the PROGRAM button, the T4.x device will go back into HID mode & wait for a download, so if your cable is not working, you should not expect to see the T4.x as a COM port if/when that is the case.

Hope that helps...

Mark J Culross
KD5RXT

EDIT: Paul types far faster than I can on my phone !!
 
Last edited:
I tried now 15 sec Restore - it is not happening - I do hear only Windows sound trying to reach the USB drive COM Port and in device manager I see Teensy looking for COM port (window opens and closes immediately trying to open COM Port) but not finding it...

Something is off.

Try the button press and hold until the flash to release as noted.

This does not involve the computer in any way and works on a USB Battery bank for instance. As long as the cable provides 5V power to USB connector this should complete.

Question: Is anything connected to the Teensy ... That is soldered? Any other changes to T_4.1 since unpacking?
 
A couple of things to make note of:

If you have a brand new T4.x that's never been programmed (or a T4.x that's successfly completed the recovery procedure), it will not show up as a COM port. New/recovered T4.x devices show up as a HID device until programmed the first time. Also, new/recovered T4.x devices will run the "blink" sketch by default. You should compile & load the "blink" sketch as your first test with a new/recovered T4.x device by pressing the PROGRAM button on the device. This well also help to confirm that your cable works correctly.

Also, if/when you press the PROGRAM button, the T4.x device will go back into HID mode & wait for a download, so if your cable is not working, you should not expect to see the T4.x as a COM port if/when that is the case.

Hope that helps...

Mark J Culross
KD5RXT


EDIT: Paul types far faster than I can on my phone !!

Thanks for tips - I did not know this - but now it seams like T4.1 wants to load blink sketch but than error comes up:

Yes I used this Teensy before - I have few of them but all other are used and build in ( I have taken one out to do a comparation with this one that is not cooperating with me...)
 

Attachments

  • Erasing_DWL error.png
    Erasing_DWL error.png
    165.4 KB · Views: 79
Download error usually means a dodgy USB cable which works well for 12 Mbit (most Arduino boards) but not 480 Mbit (used by Teensy 4.x).

Can also happen in extreme cases of other circuitry connected to Teensy and using a lot of power.
 
I know for cable issues with Teensy - I use dedicated cable - it works on other Teensy41 without a problem ...
Loading Log;
C:\Program Files (x86)\arduino-1.8.19\arduino-builder -dump-prefs -logger=machine -hardware C:\Program Files (x86)\arduino-1.8.19\hardware -tools C:\Program Files (x86)\arduino-1.8.19\tools-builder -tools C:\Program Files (x86)\arduino-1.8.19\hardware\tools\avr -built-in-libraries C:\Program Files (x86)\arduino-1.8.19\libraries -libraries C:\Users\hp\Documents\Arduino\libraries -fqbn=teensy:avr:teensy41:usb=serial,speed=600,opt=o2std,keys=en-us -ide-version=10819 -build-path C:\Users\hp\AppData\Local\Temp\arduino_build_847005 -warnings=none -build-cache C:\Users\hp\AppData\Local\Temp\arduino_cache_530159 -verbose C:\Program Files (x86)\arduino-1.8.19\examples\Teensy\Tutorial1\Blink\Blink.pde
C:\Program Files (x86)\arduino-1.8.19\arduino-builder -compile -logger=machine -hardware C:\Program Files (x86)\arduino-1.8.19\hardware -tools C:\Program Files (x86)\arduino-1.8.19\tools-builder -tools C:\Program Files (x86)\arduino-1.8.19\hardware\tools\avr -built-in-libraries C:\Program Files (x86)\arduino-1.8.19\libraries -libraries C:\Users\hp\Documents\Arduino\libraries -fqbn=teensy:avr:teensy41:usb=serial,speed=600,opt=o2std,keys=en-us -ide-version=10819 -build-path C:\Users\hp\AppData\Local\Temp\arduino_build_847005 -warnings=none -build-cache C:\Users\hp\AppData\Local\Temp\arduino_cache_530159 -verbose C:\Program Files (x86)\arduino-1.8.19\examples\Teensy\Tutorial1\Blink\Blink.pde
Using board 'teensy41' from platform in folder: C:\Program Files (x86)\arduino-1.8.19\hardware\teensy\avr
Using core 'teensy4' from platform in folder: C:\Program Files (x86)\arduino-1.8.19\hardware\teensy\avr
Detecting libraries used...
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-g++" -E -CC -x c++ -w -g -Wall -ffunction-sections -fdata-sections -nostdlib -std=gnu++14 -fno-exceptions -fpermissive -fno-rtti -fno-threadsafe-statics -felide-constructors -Wno-error=narrowing -mthumb -mcpu=cortex-m7 -mfloat-abi=hard -mfpu=fpv5-d16 -D__IMXRT1062__ -DTEENSYDUINO=157 -DARDUINO=10819 -DARDUINO_TEENSY41 -DF_CPU=600000000 -DUSB_SERIAL -DLAYOUT_US_ENGLISH "-IC:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy\\avr\\cores\\teensy4" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005\\sketch\\Blink.pde.cpp" -o nul
Generating function prototypes...
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-g++" -E -CC -x c++ -w -g -Wall -ffunction-sections -fdata-sections -nostdlib -std=gnu++14 -fno-exceptions -fpermissive -fno-rtti -fno-threadsafe-statics -felide-constructors -Wno-error=narrowing -mthumb -mcpu=cortex-m7 -mfloat-abi=hard -mfpu=fpv5-d16 -D__IMXRT1062__ -DTEENSYDUINO=157 -DARDUINO=10819 -DARDUINO_TEENSY41 -DF_CPU=600000000 -DUSB_SERIAL -DLAYOUT_US_ENGLISH "-IC:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy\\avr\\cores\\teensy4" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005\\sketch\\Blink.pde.cpp" -o "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005\\preproc\\ctags_target_for_gcc_minus_e.cpp"
"C:\\Program Files (x86)\\arduino-1.8.19\\tools-builder\\ctags\\5.8-arduino11/ctags" -u --language-force=c++ -f - --c++-kinds=svpf --fields=KSTtzns --line-directives "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005\\preproc\\ctags_target_for_gcc_minus_e.cpp"
Prevajanje skice...
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/precompile_helper" "C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy\\avr/cores/teensy4" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005" "C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-g++" -x c++-header -O2 -g -Wall -ffunction-sections -fdata-sections -nostdlib -MMD -std=gnu++14 -fno-exceptions -fpermissive -fno-rtti -fno-threadsafe-statics -felide-constructors -Wno-error=narrowing -mthumb -mcpu=cortex-m7 -mfloat-abi=hard -mfpu=fpv5-d16 -D__IMXRT1062__ -DTEENSYDUINO=157 -DARDUINO=10819 -DARDUINO_TEENSY41 -DF_CPU=600000000 -DUSB_SERIAL -DLAYOUT_US_ENGLISH "-IC:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy\\avr/cores/teensy4" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/pch/Arduino.h" -o "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/pch/Arduino.h.gch"
Using previously compiled file: C:\Users\hp\AppData\Local\Temp\arduino_build_847005\pch\Arduino.h.gch
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-g++" -c -O2 -g -Wall -ffunction-sections -fdata-sections -nostdlib -MMD -std=gnu++14 -fno-exceptions -fpermissive -fno-rtti -fno-threadsafe-statics -felide-constructors -Wno-error=narrowing -mthumb -mcpu=cortex-m7 -mfloat-abi=hard -mfpu=fpv5-d16 -D__IMXRT1062__ -DTEENSYDUINO=157 -DARDUINO=10819 -DARDUINO_TEENSY41 -DF_CPU=600000000 -DUSB_SERIAL -DLAYOUT_US_ENGLISH "-IC:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/pch" "-IC:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy\\avr\\cores\\teensy4" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005\\sketch\\Blink.pde.cpp" -o "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005\\sketch\\Blink.pde.cpp.o"
Compiling libraries...
Compiling core...
Using precompiled core: C:\Users\hp\AppData\Local\Temp\arduino_cache_530159\core\core_b0eed2ca4051c1f8d71b5c4b3efefb19.a
Linking everything together...
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-gcc" -O2 -Wl,--gc-sections,--relax "-TC:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy\\avr\\cores\\teensy4/imxrt1062_t41.ld" -mthumb -mcpu=cortex-m7 -mfloat-abi=hard -mfpu=fpv5-d16 -o "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.elf" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005\\sketch\\Blink.pde.cpp.o" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/..\\arduino_cache_530159\\core\\core_b0eed2ca4051c1f8d71b5c4b3efefb19.a" "-LC:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005" -larm_cortexM7lfsp_math -lm -lstdc++
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-objcopy" -O ihex -j .eeprom --set-section-flags=.eeprom=alloc,load --no-change-warnings --change-section-lma .eeprom=0 "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.elf" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.eep"
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-objcopy" -O ihex -R .eeprom "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.elf" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.hex"
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/teensy_secure" encrypthex TEENSY41 "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.hex"
No key .pem file found, skipping .ehex encryption
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/teensy_post_compile" -file=Blink.pde "-path=C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005" "-tools=C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/" -board=TEENSY41
Opening Teensy Loader...
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/stdout_redirect" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.sym" "C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-objdump" -t -C "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.elf"
"C:\\Program Files (x86)\\arduino-1.8.19\\hardware\\teensy/../tools/teensy_size" "C:\\Users\\hp\\AppData\\Local\\Temp\\arduino_build_847005/Blink.pde.elf"
Memory Usage on Teensy 4.1:
FLASH: code:9580, data:3992, headers:8952 free for files:8103940
RAM1: variables:4512, code:6912, padding:25856 free for local variables:487008
RAM2: variables:12384 free for malloc/new:511904
C:\Program Files (x86)\arduino-1.8.19\hardware\teensy/../tools/teensy_post_compile -file=Blink.pde -path=C:\Users\hp\AppData\Local\Temp\arduino_build_847005 -tools=C:\Program Files (x86)\arduino-1.8.19\hardware\teensy/../tools -board=TEENSY41 -reboot -port=usb:0/140000/0/2 -portlabel=(null) -portprotocol=(null)
No Teensy boards were found on any USB ports of your computer.
Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.
 

Attachments

  • Teensy41_Blink _ Arduino 1.8.19.png
    Teensy41_Blink _ Arduino 1.8.19.png
    129.4 KB · Views: 85
First, please understand this message is normal and expected if whatever program running on your Teensy has crashed in any way where it's no longer listening for USB communication.

Code:
No Teensy boards were found on any USB ports of your computer.
Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.

If you have a low quality USB cable or Teensy is connected to other stuff causing interference (the only likely causes for the Download Error you saw), those types of disruption of communication would also likely cause a Teensy which is running properly to be inaccessible.

Even if you're certain your USB cable is good, for the sake of troubleshooting I would recommend using a different cable and also test on a completely different computer, and if possible disconnect all other circuitry from your Teensy. Even if you don't want to question your USB cable, this really is the very best way to figure out whether your Teensy is damaged or something about you cable, PC and connected circuitry is interfering.

And at a risk of redundancy, I can say we've see Download Error many time on this forum. It's almost always low quality USB cables (the most common cause) or hubs or a PC with a flaky USB ports (rare, but has come up a couple times).

While it could theoretically be hardware damage to your Teensy, experience has shown hardware damage on the Teensy side results in a completely dead board. A variety of other types of partial damage have come up (like flash chip not connected, solder on pins near the crystals shorting the capacitors, etc), but we really haven't seen confirmed cases where USB is damaged in a way that partially works with reduced performance. A Teensy which is detected by Teensy Loader but shows Download Error is almost always caused by a poor quality USB cable.
 
Well note Paul, will repeat exercise tomorrow and come beck if needed.
Thanks for all answers and tips.
Mike
 
Do what @Defragster suggested.

I did this tests several time, with 5 different cables and on two computers ... I can get Teensy 4.1 only to a point where led blinks (sometimes just a not bright RED led) but I can not load a blink sketch into Teensy... . All I get to is as on pictures #19....So I have given up testing
 
I did this tests several time, with 5 different cables and on two computers ... I can get Teensy 4.1 only to a point where led blinks (sometimes just a not bright RED led) but I can not load a blink sketch into Teensy... . All I get to is as on pictures #19....So I have given up testing

Mike_58:

Time to go back to fundamentals & take small/repeatable steps, as we attempt tp get to the bottom of your problems.

Please perform the following & take (written) notes describing explicitly what happens on the red LED:
- press & hold the PROGRAM button, while starting a timer at the exact same time that the PROGRAM button is pressed
- write notes (including time of occurrence) anytime the red LED changes in any way (red LED blinks, gets brighter, gets dimmer, turns on, turns off, etc.)
- keep holding the PROGRAM button until 60 seconds has passed on the timer

Then post your notes. The contents of your notes should be sufficiently detailed such that anyone can repeat this same procedure & thus allow anyone to repeat/duplicate your same results (or easily identify any differences). After you post your notes, I'll post notes on what I see when performing the same test & we can compare notes (no pun intended) & then go forward from there . . .

Mark J Culross
KD5RXT
 
Back
Top