Jeff Hill wrote:
> What symptoms did you observe that led to finding this fix? I just read that
> Kate observed a hang (which I assume means that RTEMS shut down).
>
When I posted the original message in June, the IOC hung for a while
and rebooted itself. At that time, I was using the RTEMS-mvme2307
default exception handler. Also, there were other bugs in the
Oms58 motor driver, which complicated the issue.
Recently, I modified the improved exception handler that Till wrote for
the SVGM PPC board, and incorporated it into the mvme5500 board.
By doing so, the symptom is that RTEMS shuts down and leaves
information about the stack traces and register context. With those
information, Till was able to trace back manually using a disassembled
dump of the code.
The lesson I learn is that one can actually debug the RTEMS application.
The key point is to sharpen the skill of understanding the assembly codes.
P.S. : The source codes of the mvme5500 BSP will be available
upon request next week. I will post this again after I update the
the cexp and GeSys to the latest release that Till posted
on his "RTEMS Evaluation CD".
Cheers,
Kate
- References:
- RE: ca_repeater bug (probably observable only on RTEMS) Jeff Hill
- Navigate by Date:
- Prev:
RE: Understand the EPICS fdmgr functions Jeff Hill
- Next:
Re: ca_repeater bug (probably observable only on RTEMS) Kate Feng
- 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
- Navigate by Thread:
- Prev:
RE: ca_repeater bug (probably observable only on RTEMS) Jeff Hill
- Next:
Re: ca_repeater bug (probably observable only on RTEMS) Kate Feng
- 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
|