Aha, I didn't see until now who was the last poster on that XTAG thread you linked to - none other than DIYINHK :)
He's quite right - the smd USB connector on the XTAG-3 is very flimsy.
:) The SMD connector should be ok since you have already confirmed that Device Manager can see the XTAG tool. This takes USB traffic and valid power for the XMOS CPU on the XTAG tool to enumerate. A lot of handshakes occur for the USB device to be listed in the Device Manager tree. This is good news. If in doubt, have a close inspection of the SMD pads - are they wiggling around when you carefully dock the mating USB cable ? Keep the USB 2.0 cable short as some cables are not of the best quality.
We recall an imported KODI box which lost video and the issue was just that, the HDMI connector pins were gliding around on the top surface so had to repair with a hot air SMD tool gun.
Very strange on the results you are noting in the command prompt. Be sure that you are shelling into the DOS / command prompt using Start -> Programs -> XMOS -> command prompt. Then you are inside the shelled environment of the XMOS tool chain. By doing the same with my older XP box at home:
If I run xflash <ENTER> then I see: xflash: no input file
if I run xrun -l then I see:
Code: Select all
Available XMOS Devices
----------------------------
No Available Devices Found
which is correct since at this time, all my XMOS tools are at work. No XTAG hardware is connected to this immediate PC.
Are you running any Anti-virus program (Antivir, etc.) ? If yes, shut it off and perform a fresh installation of the tool chain. You must see the above output to move forward - at this time, the target CPU and hardware is not related to these faults. The XMOS tools chain is not working correctly yet.
Another thought is to consider to run the xtimecomposer tool -> import a small XCORE-200 sample program and attempt to run on hardware -> what does the GUI xtimecomposer tool show as the hardware ? That is, if the GUI version of the tool is able to see the XTAG tool then you are in good shape. The gui interface should offer the serial # of the XTAG tool. Just another approach to confirm the hardware and software are properly enumerated and installed correctly. As long as you do not save to flash, it is safe to consider this test. The XTAG tool is used to inject the compiled code into the target hardware's CPU RAM for immediate testing.
For example, for another XMOS tool = sTARTKIT, note the XTAG tool screen in figure 21 here:
http://www.xcore.com/viewtopic.php?f=44&t=2497
posted on our company server:
http://www.softio.com/doc/xmos_tutorial_v11.pdf
* figure 21
* be sure to select the REFRESH LIST and if required, unplug the XTAG tool and re-dock onto your PC and then select the REFRESH LIST button again to populate the serial # off your XTAG PCB
Again, this has to work to move forward.
Thanks for sticking with this, mon2, much appreciate your time & advice.
No worries. More exciting than fixing my squealing dryer. Just found a good you tube video on how to fix that - more work for tomorrow.
edit:
Did you do the following ? It is recommended for all XTAG tools and USB ports:
XMOS_XTAG_WINDOWS7_STARTUP_TIME with the value 500
http://www.xcore.com/viewtopic.php?f=47&t=3944
Highly recommended if you have not done this already. Apparently some motherboard USB host controllers are raising issues with the tools.
edit2:
http://www.xcore.com/download/file.php?id=1375