Some RTEMS Questions

[Doyle, Bryon Thomas (Bryon)]

Hello, yes I just realized that I should have been a little more specific in terms of the CPU error I described. What I mean is that it causes the SYSTEM ERR LED to light up on a CSB472 board, which I believe means a double machine check exception has occured. And as a result the CPU hangs and a reset is required and the contents of the registers are lost. I had inserted some commands that used the underlying boot monitor on the board to dump out statements into memory to trace execution, and from what I have gathered it does not enter any of the timer ISR routines that are in C. Later this afternoon, I plan to hook up a BDI2000 JTAG debugger to the board and step through the execution and gather more information about the error that is occurring. Thanks for your help.

Bryon Doyle
Summer Intern, Bell Labs
Lucent Technologies

-----Original Message-----
From: Thomas Doerfler [mailto:Thomas.Doerfler at imd-systems.de]
Sent: Friday, July 08, 2005 10:54 AM
To: Doyle, Bryon Thomas (Bryon)
Cc: 'rtems-users at rtems.com'
Subject: Re: Some RTEMS Questions


Hi,

there are many things that might lead to the "CPU error" you mentioned.
What kind of debugging environment do you have, it would be great if you
could set breakpoints somewhere early in the timer isr, just to check
out, whether the CPU error occurs IN the timer ISR or due to the fact
that the CPU does not even reach it.

Or you could give a more detailes info about the kind of CPU error that
occurs, what exception is taken, what is the content of the
corresponding syndrome registers?

wkr,
Thomas.

Doyle, Bryon Thomas (Bryon) schrieb:
> Chris, Thank you very much for your response. I managed to correct the task deletion problem by changing some code around. I made the task delete itself after printing out "hello world", instead of the rtems_delete(RTEMS_SELF) being called in the Init task, it is called in my user_task. The problem that I have now seems to involve the Interrupt handler, more specifically the Timer interrupt. I have confirmed that the timer values are set properly my using memory dumps during the driver initialization. However, RTEMS seems to not enter the routine that processes a "tick". It performs an operation that results CPU error when the interrupt occurs. I have tried to look through the interrupt handlers for the PPC405, but it is in assembly and I am hesitant to fiddle around with that level of detail in RTEMS. I was wondering if anybody had experienced similar troubles with the interrupts in general for a PowerPC 405 or 403?  I think that the problem lies in some parameter that is
 n!
>  ot being set properly during the configuration of RTEMS, but so far I have not been able to find it. Thanks for any help.
> 
> Bryon Doyle
> Summer Intern, Bell Labs
> Lucent Technologies
> 
>