I've been working for some time now with xSCOPE and it seems that every time I start an XC application, the first xSCOPE function call (e.g. xscope_int) on a probe doesn't get through to the host application connected on the other side of an xSCOPE connection.
Does this happen to anyone else and can someone please explain why this is happening?
Thanks
First xSCOPE function call Topic is solved
-
zivke
- Member
- Posts: 11
- Joined: Fri Aug 01, 2014 12:21 pm
-
peter
- XCore Addict
- Posts: 230
- Joined: Wed Mar 10, 2010 12:46 pm
All data sent should be received, so this seems wrong. Are you writing your own xSCOPE host library? Can you give an example of your device and host code?
-
zivke
- Member
- Posts: 11
- Joined: Fri Aug 01, 2014 12:21 pm
This only happens when the xscope_bytes function is used and it is a bug (<= v14.1.2) that will be fixed in the next version of XMOS tools.
-
XMatt
- XCore Addict
- Posts: 147
- Joined: Tue Feb 23, 2010 6:55 pm
The workaround for this until the new tools release is,
1. Use the xscope_core_bytes() function, this does not have the issue
or
2. Use the xscope_bytes() function but always pad your data to at least 8 bytes.
1. Use the xscope_core_bytes() function, this does not have the issue
or
2. Use the xscope_bytes() function but always pad your data to at least 8 bytes.