Help a new developer. When I'm in the MAIN tab of the Debug Configurations (for a new xCORE Application), the drop-down list of Targets is empty. (Below "Device Options, run on hardware..."). How does this list get populated? Seems like I should see either my XMOS chip or the dev kit name appearing here, right? (screen shot attached)
Even though the field is blank, I can run the debug configuration. My project is the sample audio project "app_usb_aud_xk_216_mc"; my C/C++ app is the .xe file generated when I built the code. Yet, when I start the debug, my hardware is not configured according to the settings I've made in the makefile. I suspect it's because I have not identified a physical target here, and the device is actually running older code.
xTIME composer version:Community_14.2.3 (build 15642, Oct-17-2016
xTIMEcomposer: debug configurations: where is TARGET hw list Topic is solved
-
- Member++
- Posts: 16
- Joined: Tue Oct 04, 2016 11:27 pm
xTIMEcomposer: debug configurations: where is TARGET hw list
You do not have the required permissions to view the files attached to this post.
View Solution
-
- XCore Legend
- Posts: 1913
- Joined: Thu Jun 10, 2010 11:43 am
Hi redfart (now that is a very unique name). Correct that you should see that field being populated. Do you have a XMOS kit of some sort ?
See here for a close up for the XMOS StartKit ($15 USD from Digikey):
https://www.element14.com/community/ser ... detail.png
Full tutorial is posted here:
https://www.element14.com/community/gro ... e-programs
If you do have any XMOS hardware then experiment by testing some other USB port (non USB 3.0 / USB 3.1 is one idea). Some have reported issues with USB 3.x ports during enumeration. Post back if you still are unable to locate your attached h/w.
See here for a close up for the XMOS StartKit ($15 USD from Digikey):
https://www.element14.com/community/ser ... detail.png
Full tutorial is posted here:
https://www.element14.com/community/gro ... e-programs
If you do have any XMOS hardware then experiment by testing some other USB port (non USB 3.0 / USB 3.1 is one idea). Some have reported issues with USB 3.x ports during enumeration. Post back if you still are unable to locate your attached h/w.
-
- Member++
- Posts: 16
- Joined: Tue Oct 04, 2016 11:27 pm
Hi, thanks for the quick response. Yes, I am running the dev kit "XK-AUDIO-216-MC-ABL" (xcore 200 multichannel audio). I thought I'd followed all setup steps correctly. THere's not much tutorial that comes with the kit; just tech data
-
- Member++
- Posts: 16
- Joined: Tue Oct 04, 2016 11:27 pm
Forgot to mention - I am debugging the HW with an XMOS XTAG3 1V2 (jtag debugger). It enumerates successfully as a USB device, type: LibUSB-Win32 Devices
-
- XCore Legend
- Posts: 1913
- Joined: Thu Jun 10, 2010 11:43 am
Review this thread:
https://www.xcore.com/forum/viewtopic.php?f=44&t=2497
Are you using a USB hub or plugging direct into your PC ? Although it is very possible that there is a hub controller present on your motherboard.
https://www.xcore.com/forum/viewtopic.php?f=44&t=2497
Are you using a USB hub or plugging direct into your PC ? Although it is very possible that there is a hub controller present on your motherboard.
-
- Member++
- Posts: 16
- Joined: Tue Oct 04, 2016 11:27 pm
THAT WAS IT!!!
I was plugging the XTAG-3 into my laptop's docking station's USB port. Originally, I had plugged it directly into the laptop. I moved it back to the laptop's USB jack, and now my hardware is running my configuration. The XTAG-3 also shows up in the debug config's TARGET field (after doing a "refresh list")
Yes, I am running Windows 7-64, just like the users in the thread you linked to. Thank you!
I was plugging the XTAG-3 into my laptop's docking station's USB port. Originally, I had plugged it directly into the laptop. I moved it back to the laptop's USB jack, and now my hardware is running my configuration. The XTAG-3 also shows up in the debug config's TARGET field (after doing a "refresh list")
Yes, I am running Windows 7-64, just like the users in the thread you linked to. Thank you!