Arduino 1.6.2 support

Status
Not open for further replies.
Paul:
I have a 3.1 on my Win7 system (as above) - In addition to an LC
> I accidentally hit IDE UPLOAD, instead of Verify (with board set to LC)
> - get the cross 'not compiled for this board' error as it defaulted to a 3.1 not my LC
> TeensyDuino image does not clear to 'press button'
> I push button (and re-push) on my LC, it is wholly ignored by TeensyDuino - per 'verbose'
> Even though I pushed LC button it still sees the 3.1 as online
> - take 3.1 offline
> Push LC button
> - it won't program from that state - stills says 'device still online'
> Power down LC, Repower, Push button on
> - it won't program from that state - stills says 'device still online'

Including an image of the TeensyD screen, If I close TeensyD it recovers:
TD122_badUpload.png

This happened accidentally (since Upload was only 1.21 choice) - but it seems similar to other ways to confuse TeensyD as noted above. The way out seems to be to restart TeensyD? It has 'Halted' the Teensy it touched and left it that way and also not restored TeensyD to a usable state after the error. I don't know if this relates to having the second Teensy online - or just recovery from 'not compiled ...'

Here is a Verbose TeensyD file that follows from steps above.
View attachment Upload1.22.txt
 
Last edited:
I want to try retracing your steps here, but....

defragster said:
Paul:
I have a 3.1 on my Win7 system (as above) - In addition to an LC
> I accidentally hit IDE UPLOAD, instead of Verify (with board set to LC)
> - get the cross 'not compiled for this board' error as it defaulted to a 3.1 not my LC
> TeensyDuino image does not clear to 'press button'
> I push button (and re-push) on my LC, it is wholly ignored by TeensyDuino - per 'verbose'
> Even though I pushed LC button it still sees the 3.1 as online
> - take 3.1 offline
Click to expand...

At this step, I don't know precisely what "take 3.1 offline" means. Could you be more specific?

To follow these steps, do I physically unplug the USB cable to the 3.1? Or do something else?

> Push LC button
> - it won't program from that state - stills says 'device still online'
> Power down LC, Repower, Push button on
> - it won't program from that state - stills says 'device still online'
Click to expand...
 
Yes, unplug the indicated teensy

I got some Digistump programming units that switch the USB power line so you don't have to work the micro plug

I'll do the same steps on my Win8 box shortly before and after the updated platforms.txt. I'm a bit distracted as I may have turfed i2c pins on both an LC and a 3.1 as I did this.

edit> It may act differently depending on if the LC or 3.1 is seen as the first unit.
 
Last edited:
Win8.1 system w/IDE 1.6.3 and 1.22b3 and install included platforms.txt::

System has been running a 3.1, I plugged in an LC and compiled InterruptBlink for LC with UPLOAD
19:23:57: Incompatible file, showing warning dialog (it saw the 3.1 first)
Unplugged the 3.1 (skipped the LC button press - no changes follow that)
TeensyD UI stuck on the image indicated in #76
(repeated) Press LC Button - fails to program [Bold below]:

-unplug & re-plug LC { LC starts prior sketch } :: 19:33:05: Device went offline

Press LC Button and same result - no attempt to program - No Dialog pop-up, no UI change from #76:

19:23:57: elf size appears to be 63488
19:23:57: elf binary data matches hex file
19:23:57: Code size from .elf file = 63488
19:23:57: Incompatible file, showing warning dialog
19:23:57: remote cmd: "status"
19:23:57: status data sent
19:23:57: remote connection closed
19:23:57: HID/win32: HidD_GetPreparsedData ok, device still online :)
19:25:36: Verbose Info event
19:26:21: Device went offline
19:26:21: HID/win32: vid:045E pid:00F9 ver:0002
19:26:21: HID/win32: vid:045E pid:00F9 ver:0002
19:26:21: HID/win32: vid:045E pid:00F9 ver:0002
19:26:21: HID/win32: vid:045E pid:00E1 ver:0007
19:26:21: HID/win32: vid:16C0 pid:0478 ver:0102
19:26:21: HID/win32: usage_page:FF9C, usage:0020
19:26:21: Device came online, code_size = 63488
19:26:21: Board is: Teensy LC (MKL26Z64), version 1.02
19:26:21: File "T_InterruptBlink.cpp.hex". 10460 bytes, 16% used
19:26:21: HID/win32: HidD_GetPreparsedData ok, device still online :)
19:26:40: Device went offline
19:26:40: HID/win32: vid:045E pid:00F9 ver:0002
19:26:40: HID/win32: vid:045E pid:00F9 ver:0002
19:26:40: HID/win32: vid:045E pid:00F9 ver:0002
19:26:40: HID/win32: vid:045E pid:00E1 ver:0007
19:26:40: Device came online, code_size = 63488
19:26:40: Board is: Teensy LC (MKL26Z64), version 1.02
19:26:40: File "T_InterruptBlink.cpp.hex". 10460 bytes, 16% used
19:26:41: HID/win32: HidD_GetPreparsedData ok, device still online :)
19:26:47: Device went offline
19:26:47: HID/win32: vid:045E pid:00F9 ver:0002
19:26:47: HID/win32: vid:045E pid:00F9 ver:0002
19:26:47: HID/win32: vid:045E pid:00F9 ver:0002
19:26:47: HID/win32: vid:045E pid:00E1 ver:0007
19:26:47: Device came online, code_size = 63488
19:26:47: Board is: Teensy LC (MKL26Z64), version 1.02
19:26:47: File "T_InterruptBlink.cpp.hex". 10460 bytes, 16% used
19:26:47: HID/win32: HidD_GetPreparsedData ok, device still online :)
19:33:05: Device went offline
19:33:05: HID/win32: vid:045E pid:00F9 ver:0002
19:33:05: HID/win32: vid:045E pid:00F9 ver:0002
19:33:05: HID/win32: vid:045E pid:00F9 ver:0002
19:33:05: HID/win32: vid:045E pid:00E1 ver:0007
19:34:17: Device came online, code_size = 63488
19:34:17: Board is: Teensy LC (MKL26Z64), version 1.02
19:34:17: File "T_InterruptBlink.cpp.hex". 10460 bytes, 16% used
19:34:18: HID/win32: HidD_GetPreparsedData ok, device still online :)
19:35:11: Device went offline
19:35:11: HID/win32: vid:045E pid:00F9 ver:0002
19:35:11: HID/win32: vid:045E pid:00F9 ver:0002
19:35:11: HID/win32: vid:045E pid:00F9 ver:0002
19:35:11: HID/win32: vid:045E pid:00E1 ver:0007
19:35:11: Device came online, code_size = 63488
19:35:11: Board is: Teensy LC (MKL26Z64), version 1.02
19:35:11: File "T_InterruptBlink.cpp.hex". 10460 bytes, 16% used
19:35:12: HID/win32: HidD_GetPreparsedData ok, device still online :)
Click to expand...
 
Last edited:
I've uploaded a 4th and likely final 1.22 beta test, which rolls up several small fixes. LedControl is updated, and ADC and i2c_t3 are included.

My plan is to finalize 1.22 this weekend.
 
Paul: Went to 1.22b4 on Win8. Verify works fine without user error, a cross upload mistake is most easily fixed with a TeensyDuino restart.

Forgot to set Board to LC for second unit thinking it was another 3.1, got "Incompatible file...". UI 'image' went to that in #76 with Err Dialog.

Went ahead and pressed button on the 3.1, and it is ignored - no sign in Verbose, as before.

This time I unplugged the LC and pressed the 3.1 button and now it see's the button, but won't proceed, though it was compiled for 3.1, it is still in error state of failed LC.

Other TeensyD Program/Reset UI icons were active - I lost track of when it programmed based on Serial Output as I was expecting TeensyD UI to go to "Press Button..." - but it was stuck in a similar fashion. The steps will take you down the path if you want to follow.
 

Attachments

  • 122b4_Program.txt
    16.8 KB · Views: 187
I'm planning to make a final 1.22 release this afternoon. If anyone has any feedback or knows of any "show stopper" bugs, now's the last chance to speak up before 1.22 is official.
 
1.22b4 Works for me on Windows 7/8 w/1/6/3 - Verify works if I remember to use it - Can't wait for next weeks release ;-)

Been a busy 7 weeks just installing tool updates. Hopefully 1.6.3&1.22 will stick for while until the .cc folks come up with some stable (Beta Tested) improvements worth the effort. I see 20K download growth - I suppose that is all the IDE variant files?

When you get to looking at TeensyD app (re: msg#69 para #4) be sure to spend a couple minutes with TyQt - it ID's and lists all active Teensy's (if seen running or not it seems) - works well on Windows - assume at least as well on others. It has built in Monitor and will do an instance for each ACTIVE port (unlike IDE single instance)

Finally tried it with 1.22, It plays well with Verify then hit TyQt house icon/ 'Bootloader'. I'll post notes on that thread: TyQt
 
Last edited:
Status
Not open for further replies.
Back
Top