Forum Rule: Always post complete source code & details to reproduce any issue!
Page 1 of 4 1 2 3 ... LastLast
Results 1 to 25 of 77

Thread: Teensy Loader slow to start up

  1. #1

    Teensy Loader slow to start up

    I've just built a new Linux PC and have installed all my development stuff, including Arduino IDE 1.8.13 and Teensy Loader 1.53. While they both work and I'm able to upload sketches to a Teensy 3.2 they both take ~25 seconds to load up. This means that as soon as the IDE is available and a sketch is loaded, if I then click Upload I get an error message in a couple of seconds that says the Teensy Loader couldn't be found. I then wait for another 20+ seconds and the loader finally appears. I can then click Upload again and it does exactly what it's supposed to do.

    This PC is a brand new build with Intel i7 Core 10, 32GB RAM running Ubuntu 20.04.1. It has very little loaded on it outside of the standard offerings, Eclipse and a couple of other applications I use. I'm planning on using the Teensy in a MIDI application so I had tried to install ubuntustudio-controls for testing which in turn installed a low latency kernel. I've since removed Ubuntu Studio, but I'm still left with the low latency kernel (I think).

    Launching Teensy Loader by itself also takes 20+ seconds, and the verbose info doesn't really help because it's not logging anything until it starts up as far as I can tell. I've also set my Arduino IDE to No Proxy an not to check for updates, neither of which helped. On the IDE splash screen the text at the bottom that updates as the IDE goes through it's startup steps doesn't show anything until just a few seconds before launch. So both applications seem to be waiting on one of the first things they try, and although I have no concrete idea as to what this might be I'm starting to think it's network related.

    I think the problem lies with my network driver. Since I bought all new kit for this PC build it turns out that the particular Realtek network driver isn't available in Ubuntu release yet and I had to manually install it, (and the change in kernel meant I had to re-install it). Regardless as to whether it is a network issue I'm sure it's something particular to this machine as I have no issues with my older Linux laptop running the same versions of IDE and loader. Any help or advice on what I can do to troubleshoot this and get to the root of the problem would be greatly appreciated. While it's not show stopping it is annoying.

  2. #2
    Anyone? Just some pointers as to what to look at would be helpful.

  3. #3
    Junior Member
    Join Date
    Feb 2021
    Posts
    12
    Have you found a solution for this. I have the same situation with a newly setup Ubuntu 20.04.2 LTS. It takes about 25 secs for the initial startup of the Teensy Loader which causes the first Verify or Load to fail. As you mentioned it's not a show stopper. Just curious as to what is the initial delay to the start up of the Teensy Loader.

  4. #4
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,906
    @KurtE just put some #20.??? version of Ubuntu on a machine IIRC - not sure if this shows there?

    NOTE: I saw this on Windows 10 for a brief period some time back - it just 'went away' - that is Doubly unhelpful perhaps as relevant ... but something made it slow to start like 15 seconds IIRC ... and then all has been well since ... Though I typically use TyCommander for uploading and wouldn't notice most weeks.

    So perhaps look into TyCommander integration and usage? For Linux you get to pull github and self build it ... github.com/Koromix/tytools

  5. #5
    Junior Member
    Join Date
    Feb 2021
    Posts
    12
    Thanks for the TyCommander suggestion. The Linux build and install was successful. Will take a closer look at usage.

  6. #6
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,906
    Glad that works. There are pending changes to TyCommander where it will pass the RTC time on upload - not sure that is on github. But that shows something specific to starting the loader - not the system otherwise.

    Note: I found that on Windows - once TeensyLoader was started it worked fine for 'retry' - it was just that 'first use' startup that was lagging and not ready in time. So starting it in advance - still took 15 secs - but was then ready for first upload.

  7. #7
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    646
    Just chiming in to add that I recently installed Ubuntu 20.04 on one of my work computers and it happens to take a while to bring Teensy loader up the first time. Verify / load fails until it (eventually) comes up. Happy to help with any potential tests.

  8. #8
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    I'm still on Ubuntu 18. Maybe its time to finally upgrade....

  9. #9
    It definitely seems to be a 20.04 issue. I have an old 32bit machine out in the shop running 18.04, (I think), and the same version of Teensy loader and that works fine. I still have the same issue with my 20.04 setup.

  10. #10
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    I just upgraded to from Ubuntu 18.04 to 20.04. Teensy Loader comes up quickly for me on the new system.

    Will try soon with a clean 20.04 install in a VM. If that doesn't reproduce it, I'll get a real machine for testing, but that might take several days...

  11. #11
    I'm happy to help with any testing. In addition to the machine in my OP I have a new HP All-in-one that I just set up to dual boot Windows and Ubuntu 20.04. I have loaded Teensyduino on it but not yet tested it. I also have a good laptop with 18.04 for comparison.

  12. #12
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    646
    Likewise, I have a couple work computers that I still need to put new operating systems on and can use them to try fresh installs of different operating systems for testing.

    I took a screen cast of the issue that I'm seeing. Again, on a recent install of Ubuntu 20.04 with whatever the newest versions of Arduino and Teensyduino are:
    https://youtu.be/sUbP_qepHQ4

    You'll notice that it takes several tries with upload before the Teensy Loader launches, right at the end of the video. From that point forward, if I leave Teensy Loader up, everything works fine.

    Obviously not a huge deal, but could be confusing to a new user.

  13. #13
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    I was finally able to reproduce this problem inside a virtual machine.

    Hope to get to the bottom of this soon and find a fix for 1.54-beta7.

  14. #14
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    I'm continuing to work on this problem. The root cause seems to be related to appmenu-gtk2-module not installed by default, so Ubuntu 19.10 and 20.04 don't support programs using the older GTK2 APIs. Seems Teensy Loader isn't the only program affected.

    https://itsfoss.community/t/solved-a...ntu-20-04/4578

    https://launchpad.net/ubuntu/bionic/...nu-gtk2-module

    Currently we're supporting compatibility all the way back to Ubuntu 14.04. I'm trying to find a way to fix this without requiring Ubuntu 20.04 to install appmenu-gtk2-module, but also without breaking compatibility with older Linux systems. Not simple, it seems...

  15. #15
    Senior Member
    Join Date
    Oct 2015
    Location
    Roma (IT, EU)
    Posts
    360
    GTK2 dev package is still available on Ubuntu 20 (libgtk2.0-dev).
    Not sure if it helps.

  16. #16
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    Looks like Ubuntu 18.04 is the oldest (of the LTS releases) which builds a fast startup Teensy Loader for Ubuntu 20.04. The 18.04 build at least loads on 16.04, but it can't run at all on 14.04 due to C library versions.

    Ubuntu also stopped publishing a 32 bit desktop. Looks like 17.04 was the very last 32 bit version. There are some alternate Ubuntu desktops still supporting 32 bits. But maybe this is a sign it's finally time to stop publishing a 32 bit x86 installer?

  17. #17
    I have trouble with GTK2/3 compatibility all the time and usually have to install additional libraries. I just found out about lack of 32bit support when I tried to upgrade my shop PC. It's impossible to keep up to date with everything it seems.

  18. #18
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    Ok, here's a fix for the slow startup issue on Ubuntu 20.04.

    https://www.pjrc.com/teensy/td_154-b...nstall.linux64

    I also put some work into the long-standing bug where Teensy Loader consumes excessive CPU time while sitting idle.

    So far I've tested in a few virtual machines, but only one real hardware machine which was a 18.04 -> 20.04 upgrade which doesn't show the same problem as a fresh 20.04 install.

    Please let me know how this looks on your system?

  19. #19
    Junior Member
    Join Date
    Feb 2021
    Posts
    12
    Sorry to report Paul. After install of the new version it still takes approx 25 secs for the Loader to startup. If fails initial Verify. This is a fresh install of Ubuntu 20.04.

  20. #20
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    646
    Ditto, it doesn't fix it on my Ubuntu 20.04 either.

  21. #21
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    FWIW, the problem as I understand it is the GTK developers completely changed how menus work. It's apparently a lot more complicated than just code inside 1 program, as the new system allows each window's menus to appear elsewhere, kind of like how Macintosh always has the menu bar at the top of the screen rather than on each window.

    To provide backwards compatibility for programs using the old menu API, they created when Ubuntu calls "appmenu-gtk2-module". It supposedly detects when a program is trying to do menus the old way and does the new complicated way (which I so do not fully understand). But somehow programs do miraculously work anyway, but after a 25 to 30 second timeout waiting for whatever type of communication is used by the new scheme.

    This all leads to 2 problems:

    Because appmenu-gtk2-module didn't exist until now, old program which need it have no way of indicating this to the system (unless they're packaged by .deb format and list it as a dependency). So if you have an old program on your hard drive which did menus the old way, there's no error or warning that is really needs appmenu-gtk2-module.

    When appmenu-gtk2-module isn't installed (a fresh Ubuntu 20.04 doesn't install it, but an upgrade install does) you get this annoying delay problem, and again there's no way to give any sort of error or warning that your system is missing appmenu-gtk2-module.


    For Teensy Loader, the only viable solution is to start using the new menu API. It just isn't practical to tell everyone they have to install appmenu-gtk2-module when the end-user experience is so bad and lacks any way to give a useful message about what package is missing. But the 2 big downsides is we can't have compatibility with very old Linux distros, and because Ubuntu doesn't publish a 32 bit desktop distro anymore, this means the end of Teensy's support for Linux x86-32 bit.

    Until now, we were compatible all the way back to 14.04 (farther back was limited to incompatible libudev and libusb libraries). Now I'm not sure if we'll be able to work farther back than 18.04. Teensy Loader does at least run on 16.04 but I don't have 16.04 on any real hardware so I can't say whether it actually works.

  22. #22
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,073
    Quote Originally Posted by MikeH View Post
    After install of the new version it still takes approx 25 secs for the Loader to startup.
    Can you do a couple quick checks?

    When it does finally appear, what version does Help > About say?

    The file in your {Arduino}/hardware/tools/teensy is supposed to be 7809344 bytes and should have this sha1sum:

    Code:
    paul@preston:~/teensy > sha1sum arduino-1.8.13/hardware/tools/teensy
    ea99f1c8c1ae6e7ac52ee7cbca90e7caaabd667b  arduino-1.8.13/hardware/tools/teensy

  23. #23
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    646
    Quote Originally Posted by PaulStoffregen View Post
    Can you do a couple quick checks?

    When it does finally appear, what version does Help > About say?

    The file in your {Arduino}/hardware/tools/teensy is supposed to be 7809344 bytes and should have this sha1sum:

    Code:
    paul@preston:~/teensy > sha1sum arduino-1.8.13/hardware/tools/teensy
    ea99f1c8c1ae6e7ac52ee7cbca90e7caaabd667b  arduino-1.8.13/hardware/tools/teensy
    Hi Paul,

    Can confirm the sha1sum and Teensy Loader 1.54-beta6b

    Click image for larger version. 

Name:	Screenshot from 2021-02-18 13-27-51.png 
Views:	18 
Size:	478.9 KB 
ID:	23737

  24. #24
    Junior Member
    Join Date
    Feb 2021
    Posts
    12
    I confirm same file size and sha1sum value. Version is 1.54-beta6b.

    I've been reading about the changes that have and are happening with GTK. The initial reason I got into Linux was to keep good old hardware functioning because Windows was a beast for them. Especially for Laptops. I now use Linux exclusively for writing programs for the Teensy.

  25. #25
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    8,984
    On my 20.04 machine, which matches your setup:
    Code:
    kurt@kurt-XPS-8300:~/Desktop$ sha1sum arduino-1.8.13/hardware/tools/teensy
    ea99f1c8c1ae6e7ac52ee7cbca90e7caaabd667b  arduino-1.8.13/hardware/tools/teensy
    The Teensy App appeared to come up quickly.

    Still have the other issue that if you not using Serial, but instead SEREMU it does not reboot the teensy and the Serial Monitor does not work.
    Code:
    12:52:40.250 (post_compile 1): Begin, version=1.54-beta6b
    12:52:40.342 (loader): Teensy Loader 1.54-beta6b, begin program
    12:52:40.353 (loader): Listening for remote control on port 3149
    12:52:40.353 (loader): initialized, showing main window
    12:52:40.451 (loader): remote connection 9 opened
    12:52:40.451 (post_compile 1): Sending command: comment: Teensyduino 1.54-beta6b - LINUX64 (teensy_post_compile)
    12:52:40.451 (loader): remote cmd from 9: "comment: Teensyduino 1.54-beta6b - LINUX64 (teensy_post_compile)"
    12:52:40.452 (loader): remote cmd from 9: "status"
    12:52:40.458 (post_compile 1): Status: 0, 0, 0, 0, 0, 0, /tmp/arduino_build_577333/, mtp-test.ino.hex
    12:52:40.458 (post_compile 1): Sending command: dir:/tmp/arduino_build_269703/
    12:52:40.458 (loader): remote cmd from 9: "dir:/tmp/arduino_build_269703/"
    12:52:40.458 (post_compile 1): Sending command: file:mtp-test.ino.hex
    12:52:40.459 (loader): remote cmd from 9: "file:mtp-test.ino.hex"
    12:52:40.486 (loader): File "mtp-test.ino.hex". 124408 bytes, 12% used
    12:52:40.493 (loader): remote cmd from 9: "status"
    12:52:40.493 (post_compile 1): Status: 1, 0, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:40.493 (post_compile 1): Sending command: auto:on
    12:52:40.494 (loader): remote cmd from 9: "auto:on"
    12:52:40.494 (post_compile 1): Disconnect
    12:52:40.504 (loader): remote connection 9 closed
    12:52:40.522 (post_compile 2): Begin, version=1.54-beta6b
    12:52:40.522 (loader): remote connection 9 opened
    12:52:40.522 (post_compile 2): Sending command: comment: Teensyduino 1.54-beta6b - LINUX64 (teensy_post_compile)
    12:52:40.522 (loader): remote cmd from 9: "comment: Teensyduino 1.54-beta6b - LINUX64 (teensy_post_compile)"
    12:52:40.523 (loader): remote cmd from 9: "status"
    12:52:40.523 (post_compile 2): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:40.523 (post_compile 2): Disconnect
    12:52:40.533 (post_compile 3): Running teensy_reboot: /home/kurt/Desktop/arduino-1.8.13/hardware/teensy/../tools/teensy_reboot
    12:52:40.533 (loader): remote connection 9 closed
    12:52:40.533 (loader): remote connection 9 opened
    12:52:40.533 (loader): remote connection 9 closed
    12:52:40.534 (reboot 4): Begin, version=1.54-beta6b
    12:52:40.534 (reboot 4): location = /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:52:40.534 (reboot 4): portlabel = /dev/bus/usb/001/008 Bootloader
    12:52:40.534 (reboot 4): Only location /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1 will be tried
    12:52:40.534 (reboot 4): portprotocol = Teensy
    12:52:40.550 (loader): remote connection 9 opened
    12:52:40.553 (reboot 4): add device: subsys=usb, type=usb_device, location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:52:40.553 (reboot 4):   devnode=/dev/bus/usb/001/009, subsystem=usb, ifacenum=-1
    12:52:40.553 (reboot 4): add child:  subsys=usb, type=usb_interface, location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.0
    12:52:40.553 (reboot 4):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:52:40.553 (reboot 4):   model=34 (Teensy 3.6)
    12:52:40.553 (reboot 4): add child:  subsys=usb, type=usb_interface, location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.1
    12:52:40.553 (reboot 4):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:52:40.554 (reboot 4): add child:  subsys=hid, type=(null), location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.1/0003:16C0:04D1.0007
    12:52:40.554 (reboot 4):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:52:40.554 (reboot 4): add child:  subsys=hidraw, type=(null), location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.1/0003:16C0:04D1.0007/hidraw/hidraw5
    12:52:40.554 (reboot 4):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:52:40.554 (reboot 4):   devnode=/dev/hidraw5, subsystem=hidraw, ifacenum=1
    12:52:40.566 (reboot 4): found Teensy Loader, version 1.54
    12:52:40.566 (reboot 4): Sending command: show:arduino_attempt_reboot
    12:52:40.598 (loader): remote cmd from 9: "show:arduino_attempt_reboot"
    12:52:40.598 (loader): got request to show arduino rebooting message
    12:52:40.600 (reboot 4): Sending command: comment: Teensyduino 1.54-beta6b - LINUX64 (teensy_reboot)
    12:52:40.601 (loader): remote cmd from 9: "comment: Teensyduino 1.54-beta6b - LINUX64 (teensy_reboot)"
    12:52:40.601 (loader): remote cmd from 9: "status"
    12:52:40.601 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:40.601 (reboot 4): hid_send_feature, opened /dev/hidraw5
    12:52:40.601 (reboot 4): error sending reboot command to /dev/hidraw5
    12:52:40.601 (loader): remote cmd from 9: "status"
    12:52:40.601 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:40.601 (reboot 4): status read, retry 0
    12:52:40.702 (loader): remote cmd from 9: "status"
    12:52:40.702 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:40.702 (reboot 4): status read, retry 1
    12:52:40.802 (loader): remote cmd from 9: "status"
    12:52:40.802 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:40.802 (reboot 4): status read, retry 2
    12:52:40.902 (loader): remote cmd from 9: "status"
    12:52:40.902 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:40.902 (reboot 4): status read, retry 3
    12:52:41.003 (loader): remote cmd from 9: "status"
    12:52:41.003 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.003 (reboot 4): status read, retry 4
    12:52:41.103 (loader): remote cmd from 9: "status"
    12:52:41.103 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.103 (reboot 4): status read, retry 5
    12:52:41.204 (loader): remote cmd from 9: "status"
    12:52:41.204 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.204 (reboot 4): status read, retry 6
    12:52:41.304 (loader): remote cmd from 9: "status"
    12:52:41.304 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.304 (reboot 4): status read, retry 7
    12:52:41.405 (loader): remote cmd from 9: "status"
    12:52:41.405 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.405 (reboot 4): status read, retry 8
    12:52:41.505 (loader): remote cmd from 9: "status"
    12:52:41.505 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.505 (reboot 4): status read, retry 9
    12:52:41.605 (loader): remote cmd from 9: "status"
    12:52:41.606 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.606 (reboot 4): status read, retry 10
    12:52:41.706 (loader): remote cmd from 9: "status"
    12:52:41.706 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.706 (reboot 4): status read, retry 11
    12:52:41.806 (loader): remote cmd from 9: "status"
    12:52:41.807 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.807 (reboot 4): status read, retry 12
    12:52:41.907 (loader): remote cmd from 9: "status"
    12:52:41.907 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:41.907 (reboot 4): status read, retry 13
    12:52:42.007 (loader): remote cmd from 9: "status"
    12:52:42.007 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.007 (reboot 4): status read, retry 14
    12:52:42.108 (loader): remote cmd from 9: "status"
    12:52:42.108 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.108 (reboot 4): status read, retry 15
    12:52:42.208 (loader): remote cmd from 9: "status"
    12:52:42.208 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.208 (reboot 4): status read, retry 16
    12:52:42.309 (loader): remote cmd from 9: "status"
    12:52:42.309 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.309 (reboot 4): status read, retry 17
    12:52:42.409 (loader): remote cmd from 9: "status"
    12:52:42.409 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.409 (reboot 4): status read, retry 18
    12:52:42.510 (loader): remote cmd from 9: "status"
    12:52:42.510 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.510 (reboot 4): status read, retry 19
    12:52:42.610 (loader): remote cmd from 9: "status"
    12:52:42.610 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.610 (reboot 4): status read, retry 20
    12:52:42.710 (loader): remote cmd from 9: "status"
    12:52:42.711 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.711 (reboot 4): status read, retry 21
    12:52:42.811 (loader): remote cmd from 9: "status"
    12:52:42.811 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.811 (reboot 4): status read, retry 22
    12:52:42.911 (loader): remote cmd from 9: "status"
    12:52:42.911 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:42.911 (reboot 4): status read, retry 23
    12:52:43.012 (loader): remote cmd from 9: "status"
    12:52:43.012 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.012 (reboot 4): status read, retry 24
    12:52:43.112 (loader): remote cmd from 9: "status"
    12:52:43.112 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.112 (reboot 4): status read, retry 25
    12:52:43.213 (loader): remote cmd from 9: "status"
    12:52:43.213 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.213 (reboot 4): status read, retry 26
    12:52:43.313 (loader): remote cmd from 9: "status"
    12:52:43.313 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.313 (reboot 4): status read, retry 27
    12:52:43.414 (loader): remote cmd from 9: "status"
    12:52:43.414 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.414 (reboot 4): status read, retry 28
    12:52:43.514 (loader): remote cmd from 9: "status"
    12:52:43.514 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.514 (reboot 4): status read, retry 29
    12:52:43.614 (loader): remote cmd from 9: "status"
    12:52:43.615 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.615 (reboot 4): status read, retry 30
    12:52:43.715 (loader): remote cmd from 9: "status"
    12:52:43.715 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.715 (reboot 4): status read, retry 31
    12:52:43.815 (loader): remote cmd from 9: "status"
    12:52:43.816 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.816 (reboot 4): status read, retry 32
    12:52:43.916 (loader): remote cmd from 9: "status"
    12:52:43.916 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:43.916 (reboot 4): status read, retry 33
    12:52:44.016 (loader): remote cmd from 9: "status"
    12:52:44.016 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.016 (reboot 4): status read, retry 34
    12:52:44.117 (loader): remote cmd from 9: "status"
    12:52:44.117 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.117 (reboot 4): status read, retry 35
    12:52:44.217 (loader): remote cmd from 9: "status"
    12:52:44.217 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.217 (reboot 4): status read, retry 36
    12:52:44.318 (loader): remote cmd from 9: "status"
    12:52:44.318 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.318 (reboot 4): status read, retry 37
    12:52:44.418 (loader): remote cmd from 9: "status"
    12:52:44.418 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.418 (reboot 4): status read, retry 38
    12:52:44.518 (loader): remote cmd from 9: "status"
    12:52:44.519 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.519 (reboot 4): status read, retry 39
    12:52:44.619 (loader): remote cmd from 9: "status"
    12:52:44.619 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.619 (reboot 4): status read, retry 40
    12:52:44.719 (loader): remote cmd from 9: "status"
    12:52:44.720 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.720 (reboot 4): status read, retry 41
    12:52:44.820 (loader): remote cmd from 9: "status"
    12:52:44.820 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.820 (reboot 4): status read, retry 42
    12:52:44.920 (loader): remote cmd from 9: "status"
    12:52:44.921 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:44.921 (reboot 4): status read, retry 43
    12:52:45.021 (loader): remote cmd from 9: "status"
    12:52:45.021 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.021 (reboot 4): status read, retry 44
    12:52:45.121 (loader): remote cmd from 9: "status"
    12:52:45.121 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.121 (reboot 4): status read, retry 45
    12:52:45.222 (loader): remote cmd from 9: "status"
    12:52:45.222 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.222 (reboot 4): status read, retry 46
    12:52:45.322 (loader): remote cmd from 9: "status"
    12:52:45.322 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.322 (reboot 4): status read, retry 47
    12:52:45.423 (loader): remote cmd from 9: "status"
    12:52:45.423 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.423 (reboot 4): status read, retry 48
    12:52:45.523 (loader): remote cmd from 9: "status"
    12:52:45.523 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.523 (reboot 4): status read, retry 49
    12:52:45.624 (loader): remote cmd from 9: "status"
    12:52:45.624 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.624 (reboot 4): status read, retry 50
    12:52:45.724 (loader): remote cmd from 9: "status"
    12:52:45.724 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.724 (reboot 4): status read, retry 51
    12:52:45.824 (loader): remote cmd from 9: "status"
    12:52:45.825 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.825 (reboot 4): status read, retry 52
    12:52:45.925 (loader): remote cmd from 9: "status"
    12:52:45.925 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:45.925 (reboot 4): status read, retry 53
    12:52:46.025 (loader): remote cmd from 9: "status"
    12:52:46.026 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.026 (reboot 4): status read, retry 54
    12:52:46.126 (loader): remote cmd from 9: "status"
    12:52:46.126 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.126 (reboot 4): status read, retry 55
    12:52:46.226 (loader): remote cmd from 9: "status"
    12:52:46.226 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.226 (reboot 4): status read, retry 56
    12:52:46.327 (loader): remote cmd from 9: "status"
    12:52:46.327 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.327 (reboot 4): status read, retry 57
    12:52:46.427 (loader): remote cmd from 9: "status"
    12:52:46.427 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.427 (reboot 4): status read, retry 58
    12:52:46.528 (loader): remote cmd from 9: "status"
    12:52:46.528 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.528 (reboot 4): status read, retry 59
    12:52:46.628 (loader): remote cmd from 9: "status"
    12:52:46.628 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.628 (reboot 4): status read, retry 60
    12:52:46.729 (loader): remote cmd from 9: "status"
    12:52:46.729 (reboot 4): Status: 1, 1, 0, 0, 0, 0, /tmp/arduino_build_269703/, mtp-test.ino.hex
    12:52:46.729 (reboot 4): status read, retry 61
    12:52:46.829 (reboot 4): Teensy did not respond to a USB-based request to automatically reboot.
    12:52:46.830 (loader): remote connection 9 closed
    12:57:46.646 (serialmon 5): Begin, version=1.54-beta6b
    12:57:46.646 (serialmon 5): listening for location: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:57:46.659 (loader): remote connection 9 opened
    12:57:46.662 (serialmon 5): add device: subsys=usb, type=usb_device, location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:57:46.662 (serialmon 5):   devnode=/dev/bus/usb/001/009, subsystem=usb, ifacenum=-1
    12:57:46.662 (serialmon 5): add child:  subsys=usb, type=usb_interface, location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.0
    12:57:46.662 (serialmon 5):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:57:46.662 (serialmon 5):   model=34 (Teensy 3.6)
    12:57:46.663 (serialmon 5): add child:  subsys=usb, type=usb_interface, location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.1
    12:57:46.663 (serialmon 5):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:57:46.663 (serialmon 5): add child:  subsys=hid, type=(null), location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.1/0003:16C0:04D1.0007
    12:57:46.663 (serialmon 5):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:57:46.663 (serialmon 5): add child:  subsys=hidraw, type=(null), location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.1/0003:16C0:04D1.0007/hidraw/hidraw5
    12:57:46.663 (serialmon 5):   parent location=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4.1
    12:57:46.663 (serialmon 5):   devnode=/dev/hidraw5, subsystem=hidraw, ifacenum=1
    12:57:46.663 (serialmon 5): can't open /dev/hidraw5
    12:57:58.372 (loader): Verbose Info event
    Code:
    kurt@kurt-XPS-8300:~/github/MTP_t4$ dmesg | tail -30
    [  818.018838] wlp2s0b1: associated
    [  818.028470] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211:  txop exceeded phylen 159/256 dur 1778/1504
    [  818.075303] wlp2s0b1: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:91:82:a1:0d:bb
    [  818.182577] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211:  txop exceeded phylen 137/256 dur 1602/1504
    [  818.182841] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0b1: link becomes ready
    [  820.286185] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
    [ 1186.029281] usb 1-1.4.1: new full-speed USB device number 7 using ehci-pci
    [ 1186.142449] usb 1-1.4.1: New USB device found, idVendor=16c0, idProduct=0476, bcdDevice= 2.77
    [ 1186.142453] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 1186.142456] usb 1-1.4.1: Product: Teensy MTP Disk/Serial
    [ 1186.142458] usb 1-1.4.1: Manufacturer: Teensyduino
    [ 1186.142460] usb 1-1.4.1: SerialNumber: 5791040
    [ 1186.462998] cdc_acm 1-1.4.1:1.0: ttyACM0: USB ACM device
    [ 1186.463359] usbcore: registered new interface driver cdc_acm
    [ 1186.463360] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
    [ 1187.906730] usb 1-1.4.1: usbfs: process 2180 (gvfs-gphoto2-vo) did not claim interface 0 before use
    [ 1188.064748] usb 1-1.4.1: USB disconnect, device number 7
    [ 1188.289301] usb 1-1.4.1: new full-speed USB device number 8 using ehci-pci
    [ 1188.398095] usb 1-1.4.1: New USB device found, idVendor=16c0, idProduct=0478, bcdDevice= 1.03
    [ 1188.398099] usb 1-1.4.1: New USB device strings: Mfr=0, Product=0, SerialNumber=1
    [ 1188.398101] usb 1-1.4.1: SerialNumber: 0008D620
    [ 1188.399492] hid-generic 0003:16C0:0478.0006: hidraw5: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:00:1a.0-1.4.1/input0
    [ 1190.112729] usb 1-1.4.1: USB disconnect, device number 8
    [ 1190.337289] usb 1-1.4.1: new full-speed USB device number 9 using ehci-pci
    [ 1190.446998] usb 1-1.4.1: New USB device found, idVendor=16c0, idProduct=04d1, bcdDevice= 2.77
    [ 1190.447001] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 1190.447003] usb 1-1.4.1: Product: Teensy MTP Disk
    [ 1190.447005] usb 1-1.4.1: Manufacturer: Teensyduino
    [ 1190.447006] usb 1-1.4.1: SerialNumber: 5791040
    [ 1190.448413] hid-generic 0003:16C0:04D1.0007: hidraw5: USB HID v1.11 Device [Teensyduino Teensy MTP Disk] on usb-0000:00:1a.0-1.4.1/input1
    kurt@kurt-XPS-8300:~/github/MTP_t4$
    As I mentioned in beta thread, also did not work for USB Type = keyboard.

    This sketch does run OK if edit setup to allow MTP + Serial USBType

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •