xcore-200 Slicekit XK-SK-X200-ST

Technical questions regarding the XTC tools and programming with XMOS.
Post Reply
hessa59
Active Member
Posts: 37
Joined: Sat Mar 18, 2017 7:19 pm

xcore-200 Slicekit XK-SK-X200-ST

Post by hessa59 »

Has anybody tried the new xcore -200 slicekit? XK-SK-X200-ST

Is it easy to get up and running in composer 14.3?

Does it work with the old slice cards?

Is there any example code available for it?

Any help would be greatly appreciated!


User avatar
infiniteimprobability
XCore Legend
Posts: 1126
Joined: Thu May 27, 2010 10:08 am
Contact:

Post by infiniteimprobability »

Not sure how much you trust this (coming from an XMOS insider..) but my 2c/2p is:
Has anybody tried the new xcore -200 slicekit? XK-SK-X200-ST
Yes. And it works very well. SDRAM slice actually works on this one (signal integrity much better)
Is it easy to get up and running in composer 14.3?
Yes. It's very similar to previous ones although the xlink for xscope debug has moved. Here's an early xn file for it...
SLICEKIT-XC200-X1.xn
xc200 xn
(2.68 KiB) Downloaded 268 times
SLICEKIT-XC200-X1.xn
xc200 xn
(2.68 KiB) Downloaded 268 times
Does it work with the old slice cards?
Yes
Is there any example code available for it?
Not specifically - but then again it's just a glorified breakout board so the examples would be related more to the slices than the core board itself
matthew1
Active Member
Posts: 48
Joined: Mon Oct 19, 2015 2:12 pm

Post by matthew1 »

The XN file for this board is included in 14.3 by default but needs adding manually to previous 14.x tools versions. Take a look at the HW manual for more info:

https://www.xmos.com/download/private/x ... 1.0%29.pdf

For example code, we use the USB HID demo AN00129 and the gigabit ethernet demo AN00199 as part of the manufacturing test flow for the kit, you could have a play with these.

Thanks,

Matthew.
User avatar
akp
XCore Expert
Posts: 578
Joined: Thu Nov 26, 2015 11:47 pm

Post by akp »

When will the xCORE 200 be back in stock in Digikey? Digikey is saying 11/1/2018, is that accurate?
Post Reply