Teensy.exe "problem"

[teensyforu]

Hi, I just got Teensy 3.6!!
This is my first playing with electronic so I probably dont know much
I am trying to play around but I have "problem" with teensy.exe
I am using version 1.3 on Windows 7
What I heard is when I connect teensy first time it should blink until you press button.
So I opened up the program and pressed button and nothing happened.
I know it support to change the example picture (one that saying "Press Button on Teensy to manually enter Program Mode) but nothing happen.
I looked drivers and everything seems find. So i just give it try and compile different speed blink and I pressed button and nothing happened. (I also installed teensyduno, had trouble first but figure only support older version of arduino program).
So I turned off completely and restart. Same as before except when I press button it will compile but still on teensy I dont see connection picture as other people are having.
Is it support to act like this or some problem?

-Verbose from Teensy-
19:03:29: remote connection opened
19:03:29: remote cmd: "comment: Teensyduino 1.30 - WINDOWS"
19:03:29: remote cmd: "dir:C:\Users\Main\AppData\Local\Temp\build9eb696f640e1fe156ffd502ca37ddca4.tmp\"
19:03:29: remote cmd: "file:Blink.pde.hex"
19:03:29: File "Blink.pde.hex". 20636 bytes, 2% used
19:03:29: remote cmd: "status"
19:03:29: status data sent
19:03:29: remote connection closed
19:03:58: Device came online, code_size = 1048576
19:03:58: Board is: Teensy 3.6 (MK66FX1M0), version 1.03
19:03:58: File "Blink.pde.hex". 20636 bytes, 2% used
19:03:58: set background IMG_ONLINE
19:03:58: File "Blink.pde.hex". 20636 bytes, 2% used
19:03:58: elf size appears to be 1048576
19:03:58: elf binary data matches hex file
19:03:58: Code size from .elf file = 1048576
19:03:58: begin operation
19:03:58: flash, block=0, bs=1024, auto=1
19:03:58: flash, block=1, bs=1024, auto=1
19:03:58: flash, block=2, bs=1024, auto=1
19:03:58: flash, block=3, bs=1024, auto=1
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:58: HID/win32: waiting for device
19:03:59: HID/win32: waiting for device
19:03:59: HID/win32: waiting for device
19:03:59: flash, block=4, bs=1024, auto=1
19:03:59: flash, block=5, bs=1024, auto=1
19:03:59: flash, block=6, bs=1024, auto=1
19:03:59: flash, block=7, bs=1024, auto=1
19:03:59: HID/win32: waiting for device
19:03:59: flash, block=8, bs=1024, auto=1
19:03:59: flash, block=9, bs=1024, auto=1
19:03:59: flash, block=10, bs=1024, auto=1
19:03:59: HID/win32: waiting for device
19:03:59: flash, block=11, bs=1024, auto=1
19:03:59: flash, block=12, bs=1024, auto=1
19:03:59: HID/win32: waiting for device
19:03:59: flash, block=13, bs=1024, auto=1
19:03:59: flash, block=14, bs=1024, auto=1
19:03:59: HID/win32: waiting for device
19:03:59: flash, block=15, bs=1024, auto=1
19:03:59: flash, block=16, bs=1024, auto=1
19:03:59: flash, block=17, bs=1024, auto=1
19:03:59: HID/win32: waiting for device
19:03:59: flash, block=18, bs=1024, auto=1
19:03:59: flash, block=19, bs=1024, auto=1
19:03:59: flash, block=20, bs=1024, auto=1
19:03:59: HID/win32: waiting for device
19:03:59: sending reboot
19:03:59: begin wait_until_offline
19:03:59: offline, waited 4
19:03:59: end operation
19:03:59: set background IMG_REBOOT_OK
19:03:59: redraw timer set, image 14 to show for 1200 ms
19:04:00: redraw, image 9
19:11:52: Device came online, code_size = 1048576
19:11:52: Board is: Teensy 3.6 (MK66FX1M0), version 1.03
19:11:52: File "Blink.pde.hex". 20636 bytes, 2% used
19:11:52: set background IMG_ONLINE
19:11:52: File "Blink.pde.hex". 20636 bytes, 2% used
19:11:52: elf size appears to be 1048576
19:11:52: elf binary data matches hex file
19:11:52: Code size from .elf file = 1048576
19:11:52: begin operation
19:11:52: flash, block=0, bs=1024, auto=1
19:11:52: flash, block=1, bs=1024, auto=1
19:11:52: flash, block=2, bs=1024, auto=1
19:11:52: flash, block=3, bs=1024, auto=1
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: HID/win32: waiting for device
19:11:52: flash, block=4, bs=1024, auto=1
19:11:52: flash, block=5, bs=1024, auto=1
19:11:52: HID/win32: waiting for device
19:11:52: flash, block=6, bs=1024, auto=1
19:11:52: flash, block=7, bs=1024, auto=1
19:11:52: flash, block=8, bs=1024, auto=1
19:11:52: HID/win32: waiting for device
19:11:52: flash, block=9, bs=1024, auto=1
19:11:52: flash, block=10, bs=1024, auto=1
19:11:52: flash, block=11, bs=1024, auto=1
19:11:52: flash, block=12, bs=1024, auto=1
19:11:52: flash, block=13, bs=1024, auto=1
19:11:52: HID/win32: waiting for device
19:11:52: flash, block=14, bs=1024, auto=1
19:11:52: flash, block=15, bs=1024, auto=1
19:11:52: flash, block=16, bs=1024, auto=1
19:11:52: flash, block=17, bs=1024, auto=1
19:11:52: HID/win32: waiting for device
19:11:52: flash, block=18, bs=1024, auto=1
19:11:52: flash, block=19, bs=1024, auto=1
19:11:52: flash, block=20, bs=1024, auto=1
19:11:52: HID/win32: waiting for device
19:11:52: sending reboot
19:11:52: begin wait_until_offline
19:11:52: offline, waited 4
19:11:52: end operation
19:11:52: set background IMG_REBOOT_OK
19:11:52: redraw timer set, image 14 to show for 1200 ms
19:11:54: redraw, image 9

 

[defragster]

At first glance Teensy Verbose shows it saw and programmed your T_3.6. Perhaps restart your computer and open the IDE and try the process again to see if anything changes. Help / About in the IDE will indicate on the pop up info the TeensyDuino version - and then Verify will open Teensy.exe and help about and Verbose will indicate what you show above and you should be good to go with a valid sketch sent to the Teensy.

Perhaps try the sketch listed in this posting: Can-t-communicate-with-Teensy-3-2-through-Teensyduino?.

Then change the 1000 indicated below to a smaller or larger number to change the blink rate:

void loop() {
  if ( emilBlink > [U]1000[/U] ) {

 

[PaulStoffregen]

So I opened up the program and pressed button and nothing happened.

From all the info you posted, it looks like quite a lot happened, completely reprogramming your Teensy within about 1 second.

Perhaps you're reprogramming it with the same (or very similar) LED blink, so the behavior you observe before and after programming looks the same, and the reprogram goes so quickly (relative to the blink speed) that it's difficult to even visually tell if reprogramming happened?

 

[defragster]

Paul confirmed what I posted prior.

That linked sketch also prints to Serial if you have a Serial Monitor active you will see dots printed. Perhaps easier than watching blinks would be to change the quote "." in the following line to a letter of the alphabet like "A" to know you changed it:

Serial.print([U]"."[/U]);

 

[KurtE]

Or simply change the delays for the blinks so, you will see a different blink pattern

 

[defragster]

I assumed that was part of the effort in OP - I mentioned time change in post 2 - having the sketch switch also gives clear unique behavior to know it worked. If that works he should be golden.