XTAG-3 debug log hanging?
Posted: Wed Sep 19, 2018 12:41 pm
Is there any chance that logging to XTAG-3 may hang? (Update: The xTC is fine after this, but seems to have lost connection with my target)
If so, is there a chance that this will then freeze the rest of my code? This depends on how it's connected I guess, if the I/O server may block on interface of channel calls.
I will blink a LED just to see of there is activity when it seems to stop. Of course I also need to scope activity to dig further. However, I would have liked to hear other user's experience with logging also.
Will the XTAG-3 LEDs still blink if the XC code runs if the USB SW on my machine is not responding? xTIMEcomposer does not display my log any more, but apart from that all seems fine with xTC.
The XTAG-3 is connected to an xCore-200 eXplorerKIT (1702-000101).
If it may hang, what could I possible try to make it not hang? Shorter cable? Some driver issue (below)?
The whole thing detects 433 MHz lowest signal level from a startKIT with an RFM69 radio every 10 seconds. The debug log (about 500 chars) is done between the receptions.
I also have an SPI comm on the eXplorerKIT (that does not run very fast) that might hang, but it is very well surveilled. I use lib_spi 3.0.2.
When things stop (after hours or days) it's always hard to find the cause.
---
XTAG-3 is (full data below, Norwegian headings I'm afraid) connected via a 1m USB cable to OS X 10.11.6 (El Capitan) with xTC Community_14.3.3 (build 22296, Apr-19-2018) and running JTAG I/O server. JRE is 1.8.0_144. I know that 1.8.1 181 build 13 is available. However, I have kept this old'ish version because xTC 14.3.3 will not do flashing etc. with newer versions. (See [1])
XMOS XTAG-3:
Produkt-ID: 0xf7d4
Leverandør-ID: 0x20b1
Versjon: 10.06
Serienummer: XD00t_8JmqnHNZCF
Hastighet: Opptil 480 Mb/sek.
Produsent: XMOS
Sted-ID: 0x14200000 / 9
Tilgjengelig strøm (mA): 1000
Strømkrav (mA): 500
Ekstra driftsstrøm (mA): 0
[1] xTIMEcomposer and not(?) macOS High Sierra
If so, is there a chance that this will then freeze the rest of my code? This depends on how it's connected I guess, if the I/O server may block on interface of channel calls.
I will blink a LED just to see of there is activity when it seems to stop. Of course I also need to scope activity to dig further. However, I would have liked to hear other user's experience with logging also.
Will the XTAG-3 LEDs still blink if the XC code runs if the USB SW on my machine is not responding? xTIMEcomposer does not display my log any more, but apart from that all seems fine with xTC.
The XTAG-3 is connected to an xCore-200 eXplorerKIT (1702-000101).
If it may hang, what could I possible try to make it not hang? Shorter cable? Some driver issue (below)?
The whole thing detects 433 MHz lowest signal level from a startKIT with an RFM69 radio every 10 seconds. The debug log (about 500 chars) is done between the receptions.
I also have an SPI comm on the eXplorerKIT (that does not run very fast) that might hang, but it is very well surveilled. I use lib_spi 3.0.2.
When things stop (after hours or days) it's always hard to find the cause.
---
XTAG-3 is (full data below, Norwegian headings I'm afraid) connected via a 1m USB cable to OS X 10.11.6 (El Capitan) with xTC Community_14.3.3 (build 22296, Apr-19-2018) and running JTAG I/O server. JRE is 1.8.0_144. I know that 1.8.1 181 build 13 is available. However, I have kept this old'ish version because xTC 14.3.3 will not do flashing etc. with newer versions. (See [1])
XMOS XTAG-3:
Produkt-ID: 0xf7d4
Leverandør-ID: 0x20b1
Versjon: 10.06
Serienummer: XD00t_8JmqnHNZCF
Hastighet: Opptil 480 Mb/sek.
Produsent: XMOS
Sted-ID: 0x14200000 / 9
Tilgjengelig strøm (mA): 1000
Strømkrav (mA): 500
Ekstra driftsstrøm (mA): 0
[1] xTIMEcomposer and not(?) macOS High Sierra