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

Thread: Teensyduino 1.43 Beta #2

Hybrid View

  1. #1
    Administrator Paul's Avatar
    Join Date
    Oct 2012
    Posts
    346

    Teensyduino 1.43 Beta #2

    Here is a second beta test for Teensyduino 1.43.


    Old beta download links removed. Please use the latest version:
    https://www.pjrc.com/teensy/td_download.html


    Changes since Teensyduino 1.43-beta1

    Fix for Arduino 1.8.6 startup (Arduino issue #7917)
    Fix SerialPlotter for Ports(Teensy)
    USBHost_t36 fix for Gigabyte keyboard (thanks KurtE)
    OctoWS2811 update movie2serial.pde
    Remove BYTE define, previously for pre-1.0 Arduino compatibility
    Update WS2812Serial documentation
    Improve installer help dialog on Windows

  2. #2
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Is anyone running MacOS Mojave beta?

  3. #3
    Yeah I canít wait for testing. Downloading now.. 1.43#1 give me pains and mess. Couple libraries broken and no chance to compile any sketch with Teensy 3.2/3.1 on MacBook Pro ElCapitan 10.11.06
    Unfortunately I overwritten 1.43#1 and now I cannot get back to 1.42
    I had same problems with WS2812Serial and so on

  4. #4
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Quote Originally Posted by Diodac View Post
    Unfortunately I overwritten 1.43#1 and now I cannot get back to 1.42
    You can always just download a fresh copy of Arduino 1.8.5 and install 1.42 into that copy.

    The installers don't support downgrading, because each installer has no way to know which files need to be deleted because they were added by future version installers.

  5. #5
    Senior Member+ mjs513's Avatar
    Join Date
    Jul 2014
    Location
    New York
    Posts
    4,517
    I did a simple test with SerialPlotter and it does work as long as u have some sort of delay in the delay in the loop (I used a delay(1) for test. If you don't have a delay it works and eventually hangs the sketch to the point I have to go into task manager and kill the whole java process.
    Code:
    void setup() {
      Serial.begin(115200);
    }
    
    void loop() {
      Serial.print(1); Serial.print(",");
      Serial.print(2); Serial.print(",");
      Serial.print(3); Serial.print(",");
      Serial.println(4);
      
      //delay(1);
    }
    One other thing I just noticed (I am assuming by design) though. If I use COMx(teensy 3.x) I can see data streaming on the serial monitor and the plotter. However, if I use COMx(teensy) not it printed to the serial monitor or plotter. Just a note.

    Mike

  6. #6
    Senior Member
    Join Date
    Nov 2012
    Posts
    1,197
    I moved the offending libraries back into the libraries directory and arduino-1.8.6_1.43_b2 starts up without any problems, although it is a bit slower.
    When I run arduino_debug, it prints out some, but not all, of those plus a few more that it didn't complain about before. Then it prints them all out another 3 times. But under normal startup I don't see that anyway so no biggie.

    Pete

  7. #7

    Talking

    Quote Originally Posted by el_supremo View Post
    I moved the offending libraries back into the libraries directory and arduino-1.8.6_1.43_b2 starts up without any problems, although it is a bit slower.
    When I run arduino_debug, it prints out some, but not all, of those plus a few more that it didn't complain about before. Then it prints them all out another 3 times. But under normal startup I don't see that anyway so no biggie.

    Pete
    Teensy 3.2, 1.43.2 on 1.8.6 on OSX El Capitan 10.11.06

    Exploration menu
    slowly.. slowly like turtle, huge lags, once even close down when I try go through menu.

    Compilation
    Now all libs is ok, I was able compiled my very complex code witch interrupts, and deep level setting, DMA, Timers, ADC and so on. Couple of Tabs.
    I was surprised, because any errors and compilation was around 50% faster than on 1.8.5!!!!
    Much better than 1.43.1 but the lags is weird during menu exploration.
    It was the same thing with 1.42 when was beta 7 or so, I don't remember now, exactly but after installation proper 1.42 lagging problem disappear.
    I hope get soon beta 3 without lags. But Im happy that now I get it to work.

    Thank you Paul, for your hard work for better stuff.

  8. #8
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Yikes, there should *never* be a kernel panic! Everything Teensyduino does is user-mode stuff using Apple's published APIs. No kernel driver stuff is ever installed.

  9. #9
    Quote Originally Posted by PaulStoffregen View Post
    Yikes, there should *never* be a kernel panic! Everything Teensyduino does is user-mode stuff using Apple's published APIs. No kernel driver stuff is ever installed.
    I know that should be, but after reset I got, well know mac users , welcome screen inform me about that.

    I also keep attention on others programs, but they working fine
    just in case first now I will do some refreshments on my machine, and again installing fresh java and other configuration things.
    Because we need be sure that my machine running without any problems. Tracking issues will be more accuracy.

  10. #10
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Can you help me with a little more info, so I can try to figure out what's causing the lag?

    First, if your Mac isn't displaying the time with seconds in the menu bar, click the time and choose "Open Date & Time Preferences". The click the "Clock" tab and check the "Display time with seconds" box. Then you should see the time in your menu bar showing seconds.

    When the lag happens again, please write down the time to the nearest second. Or if it happens multiple times, get the time to the nearest second for each lag. Just a few recorded is plenty, and even 1 would tremendously help, with the corresponding verbose info.

    A minute or two later, ideally after another upload to Teensy, go into the Teensy Loader's Help > Verbose Info. Please copy all the log from around those times (maybe a minute before and after each) and post it here. Of course, also tell me those times you wrote down, since the verbose info won't actually tell me when the Arduino GUI lagged.

    To figure out what's going wrong and causing those lags, I really need you to capture that verbose info so I can see the detailed log of what really was done. The answer is probably buried in all that info, but I can't see what really happened until you capture this verbose info during one the lags.

  11. #11
    Okay Paul not a problem, I will keep records when happens and what I done in this time.
    I remember that the same things happened on 1.42 and when lags get Arduino hang, mac restating itself with kernel panic, it happens also by Java but Iím not 100% sure now. At this time situation looking almost the same. Okay I will collect issues and writing it here.

  12. #12
    Quote Originally Posted by PaulStoffregen View Post
    Can you help me with a little more info, so I can try to figure out what's causing the lag?

    First, if your Mac isn't displaying the time with seconds in the menu bar, click the time and choose "Open Date & Time Preferences". The click the "Clock" tab and check the "Display time with seconds" box. Then you should see the time in your menu bar showing seconds.

    When the lag happens again, please write down the time to the nearest second. Or if it happens multiple times, get the time to the nearest second for each lag. Just a few recorded is plenty, and even 1 would tremendously help, with the corresponding verbose info.

    A minute or two later, ideally after another upload to Teensy, go into the Teensy Loader's Help > Verbose Info. Please copy all the log from around those times (maybe a minute before and after each) and post it here. Of course, also tell me those times you wrote down, since the verbose info won't actually tell me when the Arduino GUI lagged.

    To figure out what's going wrong and causing those lags, I really need you to capture that verbose info so I can see the detailed log of what really was done. The answer is probably buried in all that info, but I can't see what really happened until you capture this verbose info during one the lags.
    Here is just 12s compilation verbose info, between this time I go quickly to menu system and of course get lags but i didn't see in verbose nothing to indicate that problem. Any way, compilation was successful. If i not touch menu all working nice, much faster compile than 1.8.5/1.42
    Time lags 00:37:18 to the end of compilation, but compile in the background.

    Code:
    00:37:14.918 (ports 5): got command: "list"
    00:37:20.537 (loader): file changed
    00:37:20.554 (loader): File "Digidoo___pixel_FastLed_lib.ino.hex". 27260 bytes, 10% used
    00:37:20.730 (post_compile 19): Begin, version=1.43-beta2
    00:37:20.731 (loader): remote connection 19 opened
    00:37:20.746 (post_compile 19): Sending command: comment: Teensyduino 1.43-beta2 - MACOSX (teensy_post_compile)
    00:37:20.746 (loader): remote cmd from 19: "comment: Teensyduino 1.43-beta2 - MACOSX (teensy_post_compile)"
    00:37:20.758 (loader): remote cmd from 19: "status"
    00:37:20.777 (post_compile 19): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:20.777 (post_compile 19): Disconnect
    00:37:20.848 (ports 5): got command: "list"
    00:37:20.848 (ports 5): got command: "list"
    00:37:20.859 (post_compile 20): Begin, version=1.43-beta2
    00:37:20.995 (loader): remote connection 19 closed
    00:37:21.009 (loader): remote connection 19 opened
    00:37:21.016 (post_compile 20): Sending command: comment: Teensyduino 1.43-beta2 - MACOSX (teensy_post_compile)
    00:37:21.025 (loader): remote cmd from 19: "comment: Teensyduino 1.43-beta2 - MACOSX (teensy_post_compile)"
    00:37:21.042 (loader): remote cmd from 19: "status"
    00:37:21.061 (post_compile 20): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:21.061 (post_compile 20): Disconnect
    00:37:21.124 (post_compile 21): Running teensy_reboot: /Users/user/Desktop/Arduino 1.8.6 TeensyDuino/Arduino.app/Contents/Java/hardware/teensy/../tools/teensy_reboot
    00:37:21.373 (loader): remote connection 19 closed
    00:37:21.389 (loader): remote connection 19 opened
    00:37:21.404 (reboot 22): Begin, version=1.43-beta2
    00:37:21.404 (reboot 22): location = /dev/cu.usbmodem4275401
    00:37:21.404 (reboot 22): portlabel = /dev/cu.usbmodem4275401 (Teensy)
    00:37:21.404 (reboot 22): portprotocol = serial
    00:37:21.404 (reboot 22): Serial device /dev/cu.usbmodem4275401 will be tried first
    00:37:21.404 (reboot 22): USB device add callback
    00:37:21.405 (reboot 22):   loc=4100000, vid=16C0, pid=0489, ver=0275, ser=4275400
    00:37:21.405 (reboot 22):   actual serailnum=427540
    00:37:21.623 (loader): remote connection 19 closed
    00:37:21.638 (loader): remote connection 19 opened
    00:37:21.645 (reboot 22): USB device remove callback
    00:37:21.645 (reboot 22): Serial add callback
    00:37:21.646 (reboot 22):   name=/dev/cu.usbmodem4275401, loc=4100000, vid=16c0, pid=0489, ver=0275
    00:37:21.674 (reboot 22): Serial remove callback
    00:37:21.692 (reboot 22): HID Manager started
    00:37:21.693 (reboot 22): found Teensy Loader, version 1.43
    00:37:21.693 (reboot 22): Sending command: show:arduino_attempt_reboot
    00:37:21.868 (loader): remote cmd from 19: "show:arduino_attempt_reboot"
    00:37:21.877 (loader): got request to show arduino rebooting message
    00:37:21.888 (reboot 22): Sending command: comment: Teensyduino 1.43-beta2 - MACOSX (teensy_reboot)
    00:37:21.898 (loader): remote cmd from 19: "comment: Teensyduino 1.43-beta2 - MACOSX (teensy_reboot)"
    00:37:21.912 (loader): remote cmd from 19: "status"
    00:37:21.926 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:21.926 (reboot 22): do_reset (serial) /dev/cu.usbmodem4275401
    00:37:21.949 (loader): remote cmd from 19: "status"
    00:37:21.967 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:21.967 (reboot 22): status read, retry 0
    00:37:22.069 (loader): remote cmd from 19: "status"
    00:37:22.086 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:22.086 (reboot 22): status read, retry 1
    00:37:22.137 (ports 5): Serial remove callback
    00:37:22.137 (ports 5): USB device remove callback
    00:37:22.137 (ports 5): remove, loc=4100000
    00:37:22.137 (ports 5): usb_remove: usb:4100000
    00:37:22.137 (ports 5): del device: location=4100000
    00:37:22.345 (loader): remote cmd from 19: "status"
    00:37:22.373 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:22.373 (reboot 22): status read, retry 2
    00:37:22.465 (ports 5): USB device add callback
    00:37:22.466 (ports 5):   loc=4100000, vid=16C0, pid=0478, ver=0103, ser=00068614
    00:37:22.466 (ports 5):   actual serailnum=427540
    00:37:22.466 (ports 5):   found prior teensy at this loc, age=0.328
    00:37:22.466 (ports 5):     name: [no_device] (Teensy 3.2) Bootloader
    00:37:22.628 (loader): remote cmd from 19: "status"
    00:37:22.654 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:22.654 (reboot 22): status read, retry 3
    00:37:22.755 (loader): remote cmd from 19: "status"
    00:37:22.772 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:22.772 (reboot 22): status read, retry 4
    00:37:22.873 (loader): remote cmd from 19: "status"
    00:37:22.888 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:22.888 (reboot 22): status read, retry 5
    00:37:22.990 (loader): remote cmd from 19: "status"
    00:37:23.006 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.006 (reboot 22): status read, retry 6
    00:37:23.112 (loader): remote cmd from 19: "status"
    00:37:23.134 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.134 (reboot 22): status read, retry 7
    00:37:23.235 (loader): remote cmd from 19: "status"
    00:37:23.247 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.247 (reboot 22): status read, retry 8
    00:37:23.350 (loader): remote cmd from 19: "status"
    00:37:23.362 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.362 (reboot 22): status read, retry 9
    00:37:23.463 (loader): remote cmd from 19: "status"
    00:37:23.475 (reboot 22): Status: 1, 1, 0, 4, 0, 0, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.475 (reboot 22): status read, retry 10
    00:37:23.499 (loader): HID/macos: attach callback
    00:37:23.505 (ports 5): HID add callback, vid=16c0, pid=0478, ver=0103, loc=4100000, use=ff9c:21
    00:37:23.505 (ports 5):   found prior teensy at this loc, age=1.040
    00:37:23.505 (ports 5):     name: HID=16c0:0478.ff9c.21 (Teensy 3.2) Bootloader
    00:37:23.537 (loader): Device came online, code_size = 262144
    00:37:23.544 (loader): Board is: Teensy 3.2 (MK20DX256), version 1.03
    00:37:23.562 (loader): File "Digidoo___pixel_FastLed_lib.ino.hex". 27260 bytes, 10% used
    00:37:23.571 (loader): set background IMG_ONLINE
    00:37:23.590 (loader): File "Digidoo___pixel_FastLed_lib.ino.hex". 27260 bytes, 10% used
    00:37:23.601 (loader): elf size appears to be 262144
    00:37:23.608 (loader): elf binary data matches hex file
    00:37:23.615 (loader): Code size from .elf file = 262144
    00:37:23.623 (loader): begin operation
    00:37:23.663 (loader): remote cmd from 19: "status"
    00:37:23.686 (loader): flash, block=0, bs=1024, auto=1
    00:37:23.708 (loader): flash, block=1, bs=1024, auto=1
    00:37:23.729 (loader): flash, block=2, bs=1024, auto=1
    00:37:23.744 (reboot 22): Status: 1, 1, 1, 5, 0, 1, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.747 (loader): flash, block=3, bs=1024, auto=1
    00:37:23.798 (loader): flash, block=4, bs=1024, auto=1
    00:37:23.816 (loader): remote cmd from 19: "status"
    00:37:23.830 (loader): flash, block=5, bs=1024, auto=1
    00:37:23.838 (reboot 22): Status: 1, 1, 1, 5, 0, 1, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.846 (loader): flash, block=6, bs=1024, auto=1
    00:37:23.865 (loader): flash, block=7, bs=1024, auto=1
    00:37:23.881 (loader): flash, block=8, bs=1024, auto=1
    00:37:23.895 (loader): remote cmd from 19: "status"
    00:37:23.903 (reboot 22): Status: 1, 1, 1, 5, 0, 1, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:23.915 (loader): flash, block=9, bs=1024, auto=1
    00:37:23.932 (loader): flash, block=10, bs=1024, auto=1
    00:37:23.951 (loader): flash, block=11, bs=1024, auto=1
    00:37:23.967 (loader): flash, block=12, bs=1024, auto=1
    00:37:23.987 (loader): flash, block=13, bs=1024, auto=1
    00:37:24.016 (loader): flash, block=14, bs=1024, auto=1
    00:37:24.033 (loader): flash, block=15, bs=1024, auto=1
    00:37:24.054 (loader): remote cmd from 19: "status"
    00:37:24.069 (loader): flash, block=16, bs=1024, auto=1
    00:37:24.070 (reboot 22): Status: 1, 1, 1, 5, 0, 1, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:24.087 (loader): flash, block=17, bs=1024, auto=1
    00:37:24.105 (loader): flash, block=18, bs=1024, auto=1
    00:37:24.128 (loader): flash, block=19, bs=1024, auto=1
    00:37:24.145 (loader): remote cmd from 19: "status"
    00:37:24.156 (reboot 22): Status: 1, 1, 1, 5, 0, 1, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:24.181 (loader): flash, block=20, bs=1024, auto=1
    00:37:24.216 (loader): remote cmd from 19: "status"
    00:37:24.229 (reboot 22): Status: 1, 1, 1, 5, 0, 1, /var/folders/t1/dsfnhz7j74zgcd17ng12p0c00000gn/T/arduino_build_923298/, Digidoo___pixel_FastLed_lib.ino.hex
    00:37:24.236 (loader): flash, block=21, bs=1024, auto=1
    00:37:24.268 (loader): flash, block=22, bs=1024, auto=1
    00:37:24.280 (reboot 22): status read, retry 11
    00:37:24.280 (reboot 22): Success
    00:37:24.280 (reboot 22): Disconnect
    00:37:24.296 (ports 5): got command: "list"
    00:37:24.491 (loader): remote connection 19 closed
    00:37:24.511 (loader): flash, block=23, bs=1024, auto=1
    00:37:24.531 (loader): flash, block=24, bs=1024, auto=1
    00:37:24.548 (loader): flash, block=25, bs=1024, auto=1
    00:37:24.567 (loader): flash, block=26, bs=1024, auto=1
    00:37:24.624 (loader): sending reboot
    00:37:24.633 (loader): begin wait_until_offline
    00:37:24.648 (loader): HID/macos: status: ok
    00:37:24.792 (ports 5): HID remove callback
    00:37:24.792 (ports 5): HID add callback, vid=16c0, pid=0478, ver=0103, loc=4100000
    00:37:24.792 (ports 5): USB device remove callback
    00:37:24.792 (ports 5): remove, loc=4100000
    00:37:24.792 (ports 5): usb_remove: usb:4100000
    00:37:24.792 (ports 5): del device: location=4100000
    00:37:24.816 (loader): HID/macos: detach callback: is currently open device
    00:37:24.830 (loader): offline, waited 3
    00:37:24.842 (loader): end operation, total time = 1.212 seconds
    00:37:24.851 (loader): set background IMG_REBOOT_OK
    00:37:24.861 (loader): redraw timer set, image 14 to show for 1200 ms
    00:37:25.062 (ports 5): USB device add callback
    00:37:25.063 (ports 5):   loc=4100000, vid=16C0, pid=0489, ver=0275, ser=4275400
    00:37:25.063 (ports 5):   actual serailnum=427540
    00:37:25.063 (ports 5):   found prior teensy at this loc, age=0.271
    00:37:25.063 (ports 5):     name: [no_device] (Teensy 3.2) Serial+MIDI
    00:37:25.215 (loader): HID/macos: number of devices found = 0
    00:37:25.227 (loader): HID/macos: no devices found (empty set)
    00:37:26.062 (loader): redraw, image 9
    I spend all night for testing other configuration.


    beta 143.2 with Arduino 1.8.5 any problem I found. Compilation faster around 15-20% than 1.42 version. Any lags and slow down, all working nice.
    An alternative for now - use 1.43 with A1.8.5

    A1.8.6 solo without Tensyduino - even like that, lags when menu exploration
    Of course I use only T3.2 for test.

    That is a GUI Arduino problem and Java regarding to the lags and slow down during exploration, I hope that we get soon patch for that bug.
    Any way I will looking for solution with guys from GitHub #7935 maybe we manage fix up Ardu, I think that is a not big deal todo. Please test links below.

    Paul I will track my work, if I find bugs or so, bounding with Teensy I let you know.
    Sory for my English that is my second language.

    code using one of the following:

    ⬇️ http://downloads.arduino.cc/javaide/pull_requests/arduino-PR-7935-BUILD-760-linux32.tar.xz
    ⬇️ http://downloads.arduino.cc/javaide/pull_requests/arduino-PR-7935-BUILD-760-linux64.tar.xz
    ⬇️ http://downloads.arduino.cc/javaide/pull_requests/arduino-PR-7935-BUILD-760-windows.zip
    ⬇️ http://downloads.arduino.cc/javaide/pull_requests/arduino-PR-7935-BUILD-760-macosx.zip
    ⬇️ http://downloads.arduino.cc/javaide/pull_requests/arduino-PR-7935-BUILD-760-linuxarm.tar.xz

    ℹ️ The linuxarm build is still experimental and may not be always available.
    Last edited by Diodac; 08-28-2018 at 01:48 AM.

  13. #13
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Similar issue reported on Arduino's bug tracker (presumably not using Teensy)

    https://github.com/arduino/Arduino/issues/7924

  14. #14
    Junior Member
    Join Date
    Aug 2013
    Posts
    7
    I haven't tested this with 1.43 yet, but it appears that teensy 3.2 hardware with the teensyduino 1.42 and arduino 1.8.5 has a USB buffering issue.

    Code:
    void setup()
    {
    	Serial.begin(9600);
    }
    
    void loop()
    {
    	static uint8_t buf[4096];
    
    	for(unsigned i = 0 ; i < sizeof(buf) ; i++)
    	{
    		while(1)
    		{
    			int c = Serial.read();
    			if (c == -1)
    				continue;
    			buf[i] = c;
    			break;
    		}
    	}
    
    	// and check for proper pattern
    	// every 4 bytes should increment
    	uint32_t x = ((uint32_t*) buf)[0];
    
    	unsigned fail = 0;
    
    	for(unsigned i = 0 ; i < sizeof(buf) ; i+=4, x += 1)
    	{
    		uint32_t y = ((uint32_t*) buf)[i/4];
    
    		if (y == x)
    			continue;
    
    		Serial.print(i, HEX);
    		Serial.print(" ");
    		Serial.print(x, HEX);
    		Serial.print("!=");
    		Serial.print(y, HEX);
    		Serial.println();
    		fail++;
    	}
    
    	if (fail != 0)
    	{
    		Serial.print("FAIL ");
    		Serial.println(fail);
    	}
    
    	// and simulate a flash write delay to force USB buffering
    	delay(10);
    }
    Feed this with serial data from:
    Code:
    #!/usr/bin/perl
    use warnings;
    use strict;
    
    for(my $x = 0 ; $x < 8*1024*1024 ; $x+=1)
    {
            print pack("V", $x);
    }
    After a few megabytes it gets an failure when the previous 64 bytes are replayed:

    Code:
    ......22C FD88B!=FD8AB
    230 FD88C!=FD8AC
    234 FD88D!=FD8AD
    238 FD88E!=FD8AE
    23C FD88F!=FD8AF
    240 FD890!=FD8B0
    244 FD891!=FD8B1
    248 FD892!=FD8B2
    24C FD893!=FD8B3
    250 FD894!=FD8B4
    254 FD895!=FD8B5
    258 FD896!=FD8B6
    25C FD897!=FD8B7
    260 FD898!=FD8B8
    264 FD899!=FD8B9
    268 FD89A!=FD8BA
    2A8 FD8AA!=FD7AA
    2AC FD8AB!=FD7FB
    2B0 FD8AC!=FD7FC
    2B4 FD8AD!=FD7FD
    2B8 FD8AE!=FD7FE
    2BC FD......
    With 1.6.8 and an ancient teensyduino this error never occurs. What's interesting is only that 64 byte block is in error; the stream re-synchronizes afterwards.
    Last edited by hudson; 08-26-2018 at 10:52 PM.

  15. #15
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Quote Originally Posted by hudson View Post
    With 1.6.8 and an ancient teensyduino this error never occurs.
    The regression definitely started with version 1.36.

    1.36 didn't change anything significant in the USB serial code, but we did jump from gcc 4.8 to 5.4.

    The other thing I've discovered is the bug only happens (using 1.43-beta2) with -O2 optimization, which is "Faster" in Tools > Optimize. With -O1, -O3, -Os or -Og, the bug doesn't happen.

    I've tracked it down to usb_dev.c. Putting a pragma at the top to force that file compiled with different optimization "solves" the problem. But I've put hours into trying to compile individual functions with different optimize attributes, with very little success learning which function is responsible. When almost any of the functions use -O2, the bug happens.

    I'm not ready to conclude this is a bona-fide compiler bug. It may be some very subtle bug in the code which just hasn't mattered.

    At this point, I'm still undecided on what best thing to do for a 1.43 release. Maybe just put a pragma in the file? Or maybe change the default optimization to -O3, just in case this really is a subtle compiler bug with -O2?

  16. #16
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Just to confirm, I run this and did manage to reproduce the error. Will investigate soon...

    Click image for larger version. 

Name:	sc.png 
Views:	72 
Size:	58.8 KB 
ID:	14566

  17. #17
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    10,413
    Paul - about your text in :: https://forum.pjrc.com/threads/53380...l=1#post186104

    How does ADMIN versus "non-admin ZIP" install on Windows relate? i.e. 'non-admin' seems to be extra verbiage.

  18. #18
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    10,413
    Paul: post #13 shows T_3.2 - did you confirm with that … on any other T_LC or 3.5, 3.6 at -O2?

  19. #19
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    I briefly confirmed it happens on 3.6, but otherwise I've done all my testing on 3.2.

    This test takes quite some time to send as 32 megs of data, due to the inefficient receive code and the 10 ms delay for buffering, plus 12 Mbit/sec USB bandwidth limit. When the problem is present, I found a single run usually but not always reproduces the problem. Doing 2 or 3 runs per test makes this a very slow process. I ran it hundreds of times last night...

  20. #20
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    As a first quick fix, I've added this to usb_dev.c

    https://github.com/PaulStoffregen/co...511f5b6f72e373

  21. #21
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    10,413
    Quote Originally Posted by PaulStoffregen View Post
    As a first quick fix, I've added this to usb_dev.c

    https://github.com/PaulStoffregen/co...511f5b6f72e373
    Better to hide the symptom than let it show up. Not a single MCU does point to compile issue. That is a lot of code/time to search and run repro.

  22. #22
    Paul, not sure if you have run across this yet but out of curiosity i installed arduino as a windows app and as a result teensyduino was, for me, impossible to install. there was no suitable path listed in the teensyduino installer. as a matter of fact arduino as an app was not even listed in windows "programs and features" as uninstallable. i guess this is the next phase as i had never seen arduino as an app before. anyway, by right clicking on arduino as listed in the windows menu i was able to uninstall and then just download arduino and install the old way.

  23. #23
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    10,413
    Quote Originally Posted by defragster View Post
    Quote Originally Posted by dkryder View Post
    Paul, not sure if you have run across this yet but out of curiosity i installed arduino as a windows app and as a result teensyduino was, for me, impossible to install. there was no suitable path listed in the teensyduino installer. as a matter of fact arduino as an app was not even listed in windows "programs and features" as uninstallable. i guess this is the next phase as i had never seen arduino as an app before. anyway, by right clicking on arduino as listed in the windows menu i was able to uninstall and then just download arduino and install the old way.
    @dkryder - follow link in the post above - this is a known issue and attempt to detect and provide notice is underway. What installer was used and what was shown on failure?

  24. #24
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,133
    Quote Originally Posted by dkryder View Post
    installed arduino as a windows app and as a result teensyduino was, for me, impossible to install
    Did you run this 1.43-beta2 installer? Or were you using 1.42 or any prior version?

    I ask because the help dialog (which shows when you click the "?" button beside the "Next" button that won't enable) was redesigned. Still a big unanswered question is whether this new design is effective at informing people about the Windows App version. So I'm asking if you ran this beta, or any prior version before the help dialog redesign.

  25. #25
    yes, i was using 1.43-beta2 linked at the top of this page. and i had just fresh installed the arduino as a windows app which was installed by the windows app store. additionally, it was the only arduino copy installed on this machine.

Posting Permissions

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