Page 1 of 4

TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 17:35
by Gotang
Hi guys just got a jtag programming cable usb (jtag smt2)
was following gadgets video on how to flash tf330 card for a reference but cant get impact to see the cable
is there a trick to this cant seem to find a driver when i plugged it in windows seemed to find it no problem
using Windows 10 impact 10.1
all help welcome
as itching to try the new firmware for the tf536 fingers crossed this gets it working
gotang

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 17:41
by terriblefire
Couple of ?s

1. Where did you buy it?
2. What does it say its called in device manager.

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 19:19
by terriblefire
One other thing.. If your windows 10 is 64 bit then you will need to use the 64 bit version of Impact to access USB. I'm not sure 10.1 has a 64 bit version.

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 19:26
by PaulJ_2.0
I'm not sure about that cable type, I can say that this one is fine if used with the bundled software and drivers:
https://www.ebay.co.uk/itm/291950283440

It comes with Impact 13 (cracked) and both 32bit and 64bit drivers.

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 21:42
by GadgetUK164
Gotang wrote: 03 Aug 2020 17:35 Hi guys just got a jtag programming cable usb (jtag smt2)
was following gadgets video on how to flash tf330 card for a reference but cant get impact to see the cable
is there a trick to this cant seem to find a driver when i plugged it in windows seemed to find it no problem
using Windows 10 impact 10.1
all help welcome
as itching to try the new firmware for the tf536 fingers crossed this gets it working
gotang
Do you have a link to the cable you purchased?

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 21:47
by Gotang
PaulJ_2.0 wrote: 03 Aug 2020 19:26 I'm not sure about that cable type, I can say that this one is fine if used with the bundled software and drivers:
https://www.ebay.co.uk/itm/291950283440

It comes with Impact 13 (cracked) and both 32bit and 64bit drivers.
Mine is very like that slight diff model number but got zero software with it dohhhh
You guys mite have hit on it I'm useing windows 10 and it's not 32bit have a old laptop with xp on will give that ago tomorrow see if I can get that going if anyone knows where I can get. A copy of the let's say modeifide software that works with Windows 10 pm me a link cheers guys
as allways greatfull for all the help you lot are the best
gotang

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 21:54
by Gotang
Bought it from ebay guys
hears the link
Screenshot_20200803_214845_com.ebay.mobile.jpg
Think it's cos I'm useing windows 10 could be wrong

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 21:57
by terriblefire
I think your hitting the 64bit java issue. 32bit java cant see those USB devices on a 64 bit machine.

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 23:37
by GadgetUK164
The wierd thing though - my machine I have Impact installed on is Win 10 64 bit... I just cannot remember what I did when I installed Impact.

Re: TF536 firmware upgrade impact 10.1 cable not found problem

Posted: 03 Aug 2020 23:38
by terriblefire
GadgetUK164 wrote: 03 Aug 2020 23:37 The wierd thing though - my machine I have Impact installed on is Win 10 64 bit... I just cannot remember what I did when I installed Impact.
I installed the programming tools for ISE 14.7. Its the only one that works with Win 10.

EDIT: I'm able to use it with XC3SPROG so thats actually good enough for me right now.

EDIT2: I suspect that cable came with a hacked windrvr6.sys

Code: Select all

Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
Cable connection failed.