-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB compatibility with Windows #742
Comments
I've extensively tested this on win7 and win10, node 0.10.3-x86, 0.12.0-x86, 4.2.6-x64, 4.4.4-x64, 5.5.0-x64 and 6.2.0-x64 Seems to be the proper DFU id per referece in link above -
|
🎉 Good news! We got our windows 7 and windows 10 laptops detecting the Tessel 2 and running blinkie.
|
Dude... This is heroic! |
Thank you @gdibble ,finally got my tessel working! |
(: Thanks everyone --- @dcustodio that makes me happy |
Everything was fine up to step 8 and it said No tessels detected. I unplugged the tessel2 and plugged it back in and it just installed the drivers itself, amazing! @gdibble I love you man!!! |
🎉 on a side note: one goodie of many more coming soon ... tessel-toggle-power |
@rwaldron @johnnyman727 @dcustodio @Coder2012 hey thanks guys, i'm so happy to have helped |
Not working for me :( I also gave this (https://gist.github.com/tcr/992978a5dbe5bff2e18f495c5c0973c3) option a try but it failed too. |
I got it working after installing the driver (using Zadig) in DFU mode. |
Nice job @wmmihaa! Would you mind posting some details: Version of Windows, Version of Node.js, sequential steps to your success? I am hoping we can use successes to 1) correlate the key steps, 2) help others. Here's what we did on 15 or more Windows 7 systems today for the class - and just to note, I verified that Node.js LTS 4.4.5 works fine as well,
|
@gdibble I ran it on Win10 x64 with node 4.4.5. I could not get it working using Zadig after connecting the board. I could install the driver, but when running I then tried the same process but starting the board in DFU mode and success :) |
#awesome feedback, thx @wmmihaa |
btw our 2nd Nodejs class + #NodeBots w/ Tessel 2 went awesome Here's all the code that they worked on and we made public to share with others doing the same: |
@gdibble super glad to hear that! With regards to this issue, I think we should keep it open until we have a one line command to run to restore "tainted" computers that have the old drivers. |
I'm going to close this because it's unlikely we'll have the time to build a temporary command to fix Windows machines with old device drivers. If anyone is still hitting this, please follow the instructions posted above to fix. |
not sure if the problems are old drivers, I had the exact same issue with a brand new windows 10. |
Closing reduced visibility of these steps to almost zero |
@gdibble how so? Would you be content with me locking the thread and adding a comment with the link at the bottom? |
@johnnyman727 I only say that because those of us who use github often understand to search closed issues and we are familiar with finding things which may be hidden or obscured by the issue-status/etc. Unfortunately ppl unfamiliar with github or searching the web may not be as lucky to find the closed issue. I'm just thinking of reaching as many ppl who may need help. ;) |
This mostly worked. But then I upgraded the firmware with Now
However, reinstalling the USB drivers with Zadig seemed to fix it. I guess that makes sense, but it would be useful to have that documented somewhere. I was hoping the firmware upgrade would have some fixes for the Windows issues and was sad it momentarily made it worse. |
Hi Jon, On Fri, Aug 19, 2016 at 3:53 AM Joe Andrieu notifications@github.com
|
I followed all the instructions but then got the below error when trying to run Just to confirm, this is the reset button? I couldn't find a diagram anywhere online so went for the only button I could see. However it still apparently didn't enable DFU mode. Maybe there's another reset button somewhere, extraordinarily well hidden? Any help would be appreciated.
|
@Arrow7000 did the blue LED start blinking at 1Hz when you plugged it in with the button pressed firmly? That would indicate that it is in DFU mode. |
That is the reset button. |
Hi. Another n00b struggling with new T2 on Win10 64bit here :-/ |
@Sygyzmundovych It should be. I've seen that as well. |
So I may be able to help myself and others, what does the perpetual 'Detected a Tessel that may be booting' when running t2 list mean? Is it a USB comm error essentially? |
@rlramirez77 as you may know, there are two processors on Tessel. One is the MediaTek which runs Linux (and Node when you deploy a JS project). The other is the SAMD21 which handles the module ports and USB communications. The SAMD21 boots relatively fast (on the order of milliseconds or less) but has to wait for Linux on the MediaTek to fully boot and open a SPI channel to it. The MediaTek sends commands (like 'turn this GPIO high') to the SAMD21 over this channel and the SAMD21 relays USB comms to the MediaTek (like 'what is the name of this Tessel). The 'Detected a Tessel that may be booting' means that the SAMD21 has initialized but it is still waiting for that SPI channel to the MediaTek to open up. It usually takes 20-30 seconds for this to happen after power is supplied. |
@johnnyman727 I did know/assume much of that in your 1st paragraph; it is not an uncommon architecture currently. What I did not know is two-fold from your reply:
On 2. it seems to me that a bad Linux boot/flash state might explain my dilemma - it certainly is not being patient enough. I was trying to get a USB host attached BLE adapter working on the T2 before it became unusable, so I may have stepped in it by myself :-) I am more than willing to purchase a new T2 and am confident now that it would work as it should, but also assume you and the other Devs would like to know what the root cause is. My T2 is a paperweight :-) First, I'll see if I can at least SSH back into the T2 over ETH. If not, can J401 or another header be used to attached a Segger to re-flash the uC; and/or sideload the appropriate build of OpenWRT? Russ |
@rlramirez77 it would be great if you could make a reproducible case for that but if not, no worries. Your SAMD21 can actually overwrite the flash memory of the MediaTek. You can try using |
@johnnyman727 That worked far too well - no more brick, thanks! |
@johnnyman727 Thanks a ton! worked like a charm. |
I'm teaching
10060 kids on Node.js/Tessel2 in a few weeks and can only get Windows laptops for all the kids. Mac works great but I can't arrange that many OSX systems. I've built out projects for the students, but the dark ☁️ cloud is nothing happens w/o working systems for coding.Having a lot of trouble with Windows. t2-cli reports it isn't installing the usb drivers. Of course this is the same issue others report - the cli just reports "Detected a Tessel that may be booting. No Tessels found."
I read all the threads over the weekend and tried everything here from the custom/old usb branches and firmware (thanks for those, jon) to WinUSB driver install, node x86 and x64 v4.2.6, v4.4.4, v5.1.0, v6.1.0, etc etc etcetera.
That was on a Win10 box over the weekend. Today I'm sitting here with a colleague trying the same things with Win7. Not luck yet 😿
If there's a secret recipe for Windows or an unreleased update to help, please post anything.
The text was updated successfully, but these errors were encountered: