Bit of a strange one this.
I have been trying to run my Quad XC-1A project from a linux machine. Starting everything up requires an xgdb session to be connected to each processor, then a header program run on each of them within a second, then the main program to be loaded and executed on each processor (see here for the full steps: https://github.com/tomcarter259/Quad-XC ... /README.md)
On Windows this works fine, but on Linux I get "Program exited normally" whenever I run the header program.
Obviously I'm using the same hardware for both OSs and I'm using the same version of the tools.
What's more, I am able to run programs that only require a single XMOS processor using both xrun and xgdb fine on linux. It seems to fail at establishing the xlinks but I fail to see how the OS could affect this.
Does anybody have any ideas or any pointers as to how I could go about debugging this?
Thanks in advance.
Tom
Linux + xgdb problem
-
- Member++
- Posts: 28
- Joined: Tue Mar 15, 2011 3:29 pm
-
- Member++
- Posts: 28
- Joined: Tue Mar 15, 2011 3:29 pm
Just an update to say that this problem is present when running any program using multiple XC-1As, including the Duals XC-1A project (https://xcore.com/projects/dual-xc-1as)
Everything points to a failure to establish the xlinks between the processors as each program exits after roughly 1 second.
I have tried using binaries that were compiled on windows incase it was the compilation under linux that was causing the problem.
Everything points to a failure to establish the xlinks between the processors as each program exits after roughly 1 second.
I have tried using binaries that were compiled on windows incase it was the compilation under linux that was causing the problem.