I am making an XN file for chaining two L16 SliceKit boards together.
There is a node for XScope on the original single L16 SliceKit xn file.
How do I set up the XScope for the second L16 board?
Do I setup a second XScope Node for the second board?
Do I just setup a link to the XScope Node from the second board?
I have attached the xn file.
XScope on dual board setup
-
- XCore Addict
- Posts: 204
- Joined: Sun Jun 01, 2014 10:25 pm
XScope on dual board setup
You do not have the required permissions to view the files attached to this post.
-
- Experienced Member
- Posts: 111
- Joined: Sun Mar 06, 2011 11:39 pm
There's no need to do any additional setup for XScope on multiple tiles. Just make sure that NodeId in the XScope link matches the NodeId of the node where the XTAG-2 plugs in (0 in my case).
I see in the code you attached there is a Node declaration that involves a Service and XScope stuff. I'm not sure where you got that from, but it wasn't necessary for me. I had Xscope working across all four Tiles with 2x SliceKit Core boards.
One more thing: The Node Type declaration in your XN file keeps changing. For the SliceKit, it should be Type="XS1-L1A" for every node.
Code: Select all
<Link Encoding="2wire" Delays="4,4" Flags="XSCOPE">
<LinkEndpoint NodeId="0" Link="X0LA" />
<LinkEndpoint RoutingId="0x8000" Chanend="1" />
</Link>
One more thing: The Node Type declaration in your XN file keeps changing. For the SliceKit, it should be Type="XS1-L1A" for every node.
-
- XCore Addict
- Posts: 204
- Joined: Sun Jun 01, 2014 10:25 pm
I copied the xscope stuff from the SliceKit-L16 xn file which I understood to be the most current.
I had to change the type and package info back to the way it was in the SliceKit-L2 xn file because the ethernet module didn't like it.
I had to change the type and package info back to the way it was in the SliceKit-L2 xn file because the ethernet module didn't like it.
-
- XCore Addict
- Posts: 204
- Joined: Sun Jun 01, 2014 10:25 pm
oops I forgot to say that it is working.....
-
- Experienced Member
- Posts: 111
- Joined: Sun Mar 06, 2011 11:39 pm
I'm glad you got it working.
I just checked the most recent version of SLICEKIT-L16.xn and I'm curious what the purpose of the additional node service stuff for XScope is for.
I don't think it was there in earlier versions and it doesn't seem to be critical to basic XScope functionality. So I posted a question in the Xcore Q&A.
Edit: It probably enables PC to XMOS data transfer through XScope during runtime, which would be very useful. There doesn't seem to be any documentation on it yet though.
I just checked the most recent version of SLICEKIT-L16.xn and I'm curious what the purpose of the additional node service stuff for XScope is for.
Code: Select all
<Nodes>
<Node Id="2" Type="device:" routingId="0x8000">
<Service Id="0" Proto="xscope_host_data(chanend c);">
<Chanend Identifier="c" end="3"/>
</Service>
</Node>
</Nodes>
Edit: It probably enables PC to XMOS data transfer through XScope during runtime, which would be very useful. There doesn't seem to be any documentation on it yet though.