Hi Paul,
At a guess this is a restriction on the topologies that can be recognised automatically.
You should be able to route this by creating your own routing tables, and specifying them in the XN file, using <RoutingTable> and its friends.
You will have to read the document on the XConnect architecture to work out how to direct traffic.
XN: <https://www.xmos.com/download/private/X ... 3944A).pdf>
XConnect: <https://www.xmos.com/download/private/x ... 1.0%29.pdf>
Cheers,
Henk
Error XN11049 with more than 2 L2's
-
- Respected Member
- Posts: 347
- Joined: Wed Jan 27, 2016 5:21 pm
-
- Experienced Member
- Posts: 64
- Joined: Tue Oct 05, 2010 7:33 pm
Thanks, Henk. I'll have a look.
I'm not sure that specifying routing tables was implemented in 11.11.1, but it should be easy to test.
Paul
I'm not sure that specifying routing tables was implemented in 11.11.1, but it should be easy to test.
Paul
-
- Respected Member
- Posts: 347
- Joined: Wed Jan 27, 2016 5:21 pm
No, you will need newer tools!
Sorry, I missed that you are limited to v11 tools.
Cheers
Henk
Sorry, I missed that you are limited to v11 tools.
Cheers
Henk
-
- Experienced Member
- Posts: 64
- Joined: Tue Oct 05, 2010 7:33 pm
No problem. It's the penalty for being an early adopter.
Thanks again!
Paul
Thanks again!
Paul