Forum Rule: Always post complete source code & details to reproduce any issue!
Page 56 of 63 FirstFirst ... 6 46 54 55 56 57 58 ... LastLast
Results 1,376 to 1,400 of 1559

Thread: K66 Beta Test

  1. #1376
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    Indeed - Bootloader fixes sound great! Will test when I see it. I take it this 'update' is a feature in Teensy.exe?

    EEPROM write in HSRUN, by dropping HSRUN at speed, seems to be working - KurtE tested. Just put it on a T_3.6 running Ethernet test, and SDHC, and Serial port loop through and made a post where others can do the same with a sketch include file (that post also has skeleton sketch for stand alone use):
    INCLUDE for RTC isr() with HSRUN DROP and RESTORE EEPROM WRITE

    Using that header file - You can do an EEPROM write in your code at any time with something like this:
    Code:
      HSRUN_DROP_BLOCK(  ) { // DO NO I/O in this block
        EEPROM[ RTCTestLoc ] = LastRTCval;
      }
    Thanks FrankB for the ridiculous idea to just drop HSRUN, it seems to be working perfectly well on the two T_3.6's I have at any speed 120 to 240 MHz. And thanks Duff for exposing the way cool _BLOCK() in use above in snooze! I hope this allows a way to have effective EEPROM use on T_3.6.
    Last edited by defragster; 09-14-2016 at 06:42 PM.

  2. #1377
    Senior Member
    Join Date
    Jul 2014
    Posts
    2,333
    Quote Originally Posted by defragster View Post
    Indeed - Bootloader fixes sound great! Will test when I see it. I take it this 'update' is a feature in Teensy.exe?
    My hunch is that Paul is talking about the MKL02 bootloader chip.
    Any mods will then only affect future Teensy or bootloader chip sales, which is fine for T3.5,6 and, as it seems, T3.2 or earlier are not affected.

  3. #1378
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    Quote Originally Posted by WMXZ View Post
    My hunch is that Paul is talking about the MKL02 bootloader chip.
    Any mods will then only affect future Teensy or bootloader chip sales, which is fine for T3.5,6 and, as it seems, T3.2 or earlier are not affected.
    Yes, that is the root of my question - can the bootloader chip be updated during programing?

  4. #1379
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,576
    Quote Originally Posted by defragster View Post
    Yes, that is the root of my question - can the bootloader chip be updated during programing?
    I will soon publish an update that ought to quite decisively answer your question.

    Please be patient. I'm working on it now....

  5. #1380
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    I knew you would - one way or another . . .

  6. #1381
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,576
    Ok, here is the update:

    Linux 32
    http://www.pjrc.com/teensy/beta/k66_...linux32/teensy

    Linux 64
    http://www.pjrc.com/teensy/beta/k66_...linux64/teensy

    Mac
    http://www.pjrc.com/teensy/beta/k66_...mac/teensy.zip

    Windows
    http://www.pjrc.com/teensy/beta/k66_...ows/teensy.exe

    To use this, first quit Teensy Loader if you have it running. Then run this new copy of Teensy Loader. Use Help > About (or Teensy > About on Mac) to check the version. It should say "1.31-boot-update". If you see 1.30 or older, quit Teensy Loader and try again. Only one instance can run, so if you have an older copy running, this new one can't start.

    Then use Arduino to upload any sketch. The update takes only a couple seconds.

    To check if it worked, open the Help > Verbose Info window. Turn off Auto mode and press the button on your Teensy. You should see it detected as "Board is: Teensy 3.6 (MK66FX1M0), version 1.03" in the verbose info. All the beta and preproduction boards shipped with version 1.02.

  7. #1382
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    Forbidden
    You don't have permission to access /teensy/beta/k66_boot_update/windows/teensy.exe on this server.


    http://www.pjrc.com/teensy/beta/k66_...ows/teensy.exe

    It is there - I just can't touch it . . . The others work to download
    Last edited by defragster; 09-15-2016 at 01:54 AM.

  8. #1383
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    5,422
    Hi Paul,

    You might want to put the Windows file into a zip file or something as my web browsers won't allow me to download an .exe (both Firefox and Edge)

  9. #1384
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    IE is a NO go too - the file is protected somehow. TeensyInstaller is an an exe and it works :: http://www.pjrc.com/teensy/td_130-be...inoInstall.exe

  10. #1385
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    5,422
    OK, I update T3.6 on Mac.

    Couple of quick questions:

    Is this a run once and then not needed again - so continue with Teensy loader that shipped with the latest version of Teensyduino?

    What about T3.5 beta boards, should I run it on it as well?

    Thanks

    Kurt

    P.S. - On Mac without other USB serial # fix shows back up as no serial #...

  11. #1386
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,576
    Quote Originally Posted by KurtE View Post
    Is this a run once and then not needed again - so continue with Teensy loader that shipped with the latest version of Teensyduino?
    Correct, just run it once.

    What about T3.5 beta boards, should I run it on it as well?
    Yes, please update Teensy 3.5 also.

  12. #1387
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,576
    Quote Originally Posted by KurtE View Post
    You might want to put the Windows file into a zip file
    Done.

    http://www.pjrc.com/teensy/beta/k66_...ows/teensy.zip

  13. #1388
    Senior Member
    Join Date
    Nov 2012
    Posts
    1,155
    I've tested the new Teensy.exe with the very large test file that I posted here and also with the version of the vocoder which uses more than 512kB. They both work.
    Excellent.

    Pete

  14. #1389
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    Done 3.6_Proto, 3.6_KS, 3,5_KS

    FYI:: bootupdate665.txt

  15. #1390
    Senior Member
    Join Date
    Nov 2012
    Posts
    1,155
    I've just stretched the test file to very close to 1MB and it works.
    Code:
    Sketch uses 1,045,584 bytes (99%) of program storage space. Maximum is 1,048,576 bytes.
    Global variables use 5,380 bytes (2%) of dynamic memory, leaving 256,764 bytes for local variables. Maximum is 262,144 bytes.
    Pete

  16. #1391
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    Of course no ser# on K66_PROTO. But is there something odd with that 'upgrade' on the PROTO unit? T_3.1 through TYQT still powers on in ~2 secs and prints - the K66_PROTO was at like 7 seconds? And missing the 'Hello world ...' part of first print.

    Seems to have a 5-6 second delay getting on USB? Found a working simple blink with Serial out - several I tried were losing 'line feeds'

    Tried switching to T_3.6_KS and it seemed to have ser# - but Windows machine hung hard for some reason? Will have to get back to that.

    T_3.6_KS seemed to be starting slower on my EEPROM work too?

  17. #1392
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,706
    Got back to PC (post 1391) - dead/hung - no keyboard light toggle or mouse or CrtlAltDel response - four teensys unplugged - not typical. The T_3.6_KS is fast and fine to boot. I'm not sure that bootloader upgrade isn't somehow not fitting for the PROTO units? It definitely takes 5-6 seconds to register on USB even now fresh after reset.

    And where the T_3.6_KS gets 'Hello World! ... 1138' the PROTO gets '6501' on the same sketch as the first line on TYQT. I do get this on IDE SerMon 'Hello World! ... 6001', more complete but still a long time and it requires a SerMon restart after it 'chimes' on as Windows USB connect.

    I had been using both about equally before for some too many dozens of EEPROM uploads and never saw such behavior. Going to set it aside until I power up the other desktop/hear something. Back to EEPROM uploading on T_3.6_KS and NO PROBLEMS!

    The T_3.6_KS for sure has a serial number showing in TYQT!

    I don't see anything from holding the button 18 seconds or longer - I repower and the old code comes up?:
    Quote Originally Posted by PaulStoffregen View Post
    ... One new feature will be added. If you hold the program button for 15 seconds (actually, between 13 to 17 seconds) the chip is fully erased, including eeprom data.
    About EEPROM write in HSRUN: I see three downloads of the RTC included new 'all in header' version. It works well for me to just drop from HSRUN a bit to do EEPROM writes at speed. ... more on that thread - with a code update tomorrow.

  18. #1393
    Senior Member
    Join Date
    Apr 2013
    Posts
    138
    Confirm update works on Teensy 3.6 on Windows 10 64bit

    Code:
    10:44:33: Bootloader update: 1% of estimated 8 seconds
    10:44:33: Bootloader update: 3% of estimated 8 seconds
    10:44:33: Bootloader update: 4% of estimated 8 seconds
    10:44:34: Bootloader update: 5% of estimated 8 seconds
    10:44:34: Bootloader update: 6% of estimated 8 seconds
    10:44:34: Bootloader update: 8% of estimated 8 seconds
    10:44:34: Bootloader update: 9% of estimated 8 seconds
    10:44:34: Bootloader update: 10% of estimated 8 seconds
    10:44:34: Bootloader update: 11% of estimated 8 seconds
    10:44:34: Bootloader update: 13% of estimated 8 seconds
    10:44:35: Bootloader update: 14% of estimated 8 seconds
    10:44:35: Bootloader update: 15% of estimated 8 seconds
    10:44:35: Bootloader update: 16% of estimated 8 seconds
    10:44:35: Bootloader update: 18% of estimated 8 seconds
    10:44:35: Bootloader update: 19% of estimated 8 seconds
    10:44:35: Bootloader update: 20% of estimated 8 seconds
    10:44:35: Bootloader update: 21% of estimated 8 seconds
    10:44:35: Bootloader update: 23% of estimated 8 seconds
    10:44:35: Bootloader update: 24% of estimated 8 seconds
    10:44:35: Bootloader update: 25% of estimated 8 seconds
    10:44:36: Bootloader update: 26% of estimated 8 seconds
    10:44:36: Bootloader update: 28% of estimated 8 seconds
    10:44:36: Bootloader update: 29% of estimated 8 seconds
    10:44:36: Bootloader update: 30% of estimated 8 seconds
    10:44:36: Bootloader update: 31% of estimated 8 seconds
    10:44:36: Bootloader update finished, 2.5 seconds
    Only this is interesting, going to 31% and finished?
    Last edited by Markus_L811; 09-15-2016 at 08:47 AM.

  19. #1394
    Senior Member
    Join Date
    Jul 2014
    Posts
    2,333
    Quote Originally Posted by defragster View Post
    Yes, that is the root of my question - can the bootloader chip be updated during programing?
    OK, now we know it, and to my surprise (or ignorance) it seems that bootloader chip can be programmed via USB.
    In hind-side, this makes sense, as SWD is 2-way.
    I guess, however, it still remains not a trivial undertaking.

  20. #1395
    Senior Member Wozzy's Avatar
    Join Date
    Jan 2013
    Location
    Philadelphia, Pennsylvania USA
    Posts
    354
    Correct, just run it once.
    Yes, please update Teensy 3.5 also.
    Paul,
    Is this just for Teensys currently in the field?
    Will future T3.5s and T3.6s ship with these bootloader updates already in place?

  21. #1396
    Senior Member
    Join Date
    May 2015
    Location
    San Francisco
    Posts
    157
    Success on 3.6_Proto, Mac OS El Capitan, HEX file built via PlatformIO.

  22. #1397
    Senior Member
    Join Date
    May 2015
    Location
    San Francisco
    Posts
    157
    Quote Originally Posted by blackketter View Post
    Success on 3.6_Proto, Mac OS El Capitan, HEX file built via PlatformIO.
    Also works on MacOS Sierra!

  23. #1398
    Senior Member+ manitou's Avatar
    Join Date
    Jan 2013
    Posts
    2,196
    Quote Originally Posted by PaulStoffregen View Post
    OK, I updated my K66 beta3 board with 32-bit teensy. all is well.

    I'll wait another day or so before updating my other K66 (proto) and K64 ... to see if any Murphy's Law effects are revealed.

  24. #1399
    Senior Member
    Join Date
    Nov 2012
    Posts
    1,155
    Not having any problem with the bootloader update with a K66 proto unit. The verbose info from teensy.exe is generated immediately when I push the reset button.

    Pete
    P.S. Win 7 Pro 64-bit. Arduino 1.6.11, TD 1.30 + the bootloader update
    Last edited by el_supremo; 09-15-2016 at 03:48 PM.

  25. #1400
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,576
    Quote Originally Posted by defragster View Post
    Got back to PC (post 1391) - dead/hung - no keyboard light toggle or mouse or CrtlAltDel response - four teensys unplugged - not typical. The T_3.6_KS is fast and fine to boot. I'm not sure that bootloader upgrade isn't somehow not fitting for the PROTO units? It definitely takes 5-6 seconds to register on USB even now fresh after reset.

    And where the T_3.6_KS gets 'Hello World! ... 1138' the PROTO gets '6501' on the same sketch as the first line on TYQT. I do get this on IDE SerMon 'Hello World! ... 6001', more complete but still a long time and it requires a SerMon restart after it 'chimes' on as Windows USB connect.
    @Defragster - I can't understand what you're saying.

Posting Permissions

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