I've created: Ticket 2042 created in queue 'Tools'
to more fully describe and characterize the issue, clues, and workarounds I've been able to use.
XMOS 10.4 -- xrun: No available devices
-
landon
- Experienced Member
- Posts: 71
- Joined: Mon Sep 06, 2010 4:05 pm
-
FeR
- New User
- Posts: 3
- Joined: Thu Sep 23, 2010 3:05 pm
I got a board With a XS1-L1 some days ago and I get the same trouble.
I cannot to upload code to the chip which is connected through Xmos XTAG2 to the PC (Win XP sp3)
The console of Xmos developmetn tools shows the following:
xrun: No available devices
Error: F03034 Failed to fully run flash inquisitor.
I cannot to upload code to the chip which is connected through Xmos XTAG2 to the PC (Win XP sp3)
The console of Xmos developmetn tools shows the following:
xrun: No available devices
Error: F03034 Failed to fully run flash inquisitor.
-
landon
- Experienced Member
- Posts: 71
- Joined: Mon Sep 06, 2010 4:05 pm
After having worked with this for several weeks, by far the most prolific problem seems to be the variation:
"Target connection failed"
"Target is not responding"
It's maddening. If I could simply disconnect the device and reconnect it and have it work again, that would be one thing. But that doesn't always reset it - sometimes it does, but rarely. Sometimes getting out of XDev, unplugging the device, and coming back into the whole thing will work - sometimes not.
I simply cannot find a pattern that either causes this or provides a workaround for it....either would be progress, but it is just so random in both its cause and workaround, I can't find any pattern.
"Target connection failed"
"Target is not responding"
It's maddening. If I could simply disconnect the device and reconnect it and have it work again, that would be one thing. But that doesn't always reset it - sometimes it does, but rarely. Sometimes getting out of XDev, unplugging the device, and coming back into the whole thing will work - sometimes not.
I simply cannot find a pattern that either causes this or provides a workaround for it....either would be progress, but it is just so random in both its cause and workaround, I can't find any pattern.
-
landon
- Experienced Member
- Posts: 71
- Joined: Mon Sep 06, 2010 4:05 pm
I've tried to find out more information on this problem.
Despite the fact that it was supposedly a bug in CDT -> gdb communication fixed back in 2006, these problems I've seen, especially the target timeout problems are remarkably similar in symptoms to this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=119683
https://bugs.eclipse.org/bugs/show_bug.cgi?id=107571
http://dev.eclipse.org/mhonarc/lists/cd ... 05110.html
Landon
Despite the fact that it was supposedly a bug in CDT -> gdb communication fixed back in 2006, these problems I've seen, especially the target timeout problems are remarkably similar in symptoms to this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=119683
https://bugs.eclipse.org/bugs/show_bug.cgi?id=107571
http://dev.eclipse.org/mhonarc/lists/cd ... 05110.html
Landon
-
landon
- Experienced Member
- Posts: 71
- Joined: Mon Sep 06, 2010 4:05 pm
Does anyone know how to find XDev -> gdb communication logs? or for that matter, how to turn on logging between XDev and gdb so it might be possible to provide more information on these opaque types of debug, target connection errors?