1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Problem with mca R7.2 and Rontec XFlash |
From: | Mark Rivers <[email protected]> |
To: | "'Zachary Brown'" <[email protected]>, "[email protected]" <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Mon, 11 Feb 2013 20:11:22 +0000 |
You can diagnose problems like this by turning on asynTrace on the underlying serial port. In order to have the asynTrace output not impact the performance significantly
you can send the output to a file: # Send the asynTrace output to a file. Substitute the name of your asyn port for the serial device below. asynSetTraceFile “serial1”,0,”serial_output.txt” # ASYN_TRACEIO_HEX asynSetTraceIOMask “serial1”,0,4 # ASYN_TRACE_ERROR and ASYN_TRACEIO_DRIVER asynSetTraceMask “serial1”,0,9 To turn off the debugging output # ASYN_TRACE_ERROR
asynSetTraceMask “serial1”,0,1 To set the file back to stderr asynSetTraceFile “serial1”,0,”” The output file will give you a series of time-stamped messages when messages were sent to the device and when replies were received. That should help to determine if the
serial I/O is the bottleneck. Are you running at the fastest possible baud rate? Mark From: [email protected] [mailto:[email protected]]
On Behalf Of Zachary Brown Hi, |