what exception model should I use ?

Joel Sherrill joel.sherrill at OARcorp.com
Fri Apr 11 13:14:38 UTC 2008


阎淼 wrote:
> Hi,
>   I am using psim to run some startup code under gdb. I'm not using
> psim to emulate a whole broad, just testing startup code. But when
> executing privileged intructions like mtmsr, mtspr , the program dies
> with the following message:
>
>    cpu 1, cia 0x10000c : program interrupt - privileged instruction
>    program terminated with signal ?, Unknow signal
>    The grogram no longer exists.
>
>   I test score603e bsp, it dies too, but psim bsp seem to work. I also
> use the psim/tools/psim-gdb script, but the results is the same.  Are
> their any special configuration options that I miss?
>
>   
Only the psim BSP is going to work with the psim simulator in gdb. Any
other BSP is going to match a real piece of hardware and will very likely
touch registers or memory locations that are not simulated by psim.

--joel
> 在 08-4-7,Joel Sherrill<joel.sherrill at oarcorp.com> 写道:
>   
>> Thomas Doerfler wrote:
>>     
>>> Hi,
>>>
>>> the information in the README is no longer correct (at least for
>>> CVS-HEAD). I will fix this ASAP.
>>>
>>> Nevertheless, the 603e is covered in the mpc6xx stuff (e.g. in the
>>> mpc52xx and the mpc83xx), so you should be able to use the new exception
>>> handling anyway.
>>>
>>> If you would use the old exception handling stuff, your port would not
>>> be compatible with any upcoming version of RTEMS.
>>>
>>>
>>>       
>> ========================================================
>> Here Ye! Here Ye!!
>>
>> It has been proclaimed that there is no longer an old versus new
>> exception model in RTEMS. In RTEMS CVS, each port has a single
>> exception model.
>>
>> As part of this proclamation, the phrases "old exceptions"
>> and "new exceptions" shall henceforth be banished from the
>> vocabulary of residents of the Kingdom of RTEMS. All uses of
>> said phrases shall be cast into the CVS history dungeon and
>> replaced by phrases such as "simple vectored" or "PIC vectored".
>> ========================================================
>>
>> The PowerPC suffered from old/new because we were too conservative
>> to kill "old exception" BSPs and gave people literally 8 YEARS to convert
>> before killing the "old exception" code.
>>
>> This has been a long standing area of confusion and we can move forward
>> to remove this horrible terminology which ONLY impacts the PowerPC.
>>
>> I will try to write a Wiki entry on this so we can start pointing to that.
>>
>> I would hate to have to reinstate the stocks or public flogging. :-D
>>
>> --joel
>>     
>>> wkr,
>>> Thomas.
>>>
>>>
>>> 阎淼 schrieb:
>>>
>>>       
>>>> Hi,
>>>>
>>>>    I am using rtems4.8,  and the README file is allocated at
>>>> c/src/lib/libcpu/powerpc, some of the contents:
>>>>
>>>>   -------------------------------------------------------------------------------------------
>>>>    At this time, support is included for the following PowerPC
>>>> family members using the new exception processing model:
>>>>
>>>>   + mpc505
>>>>   + mpc5xx (5xx devices other than 505/509)
>>>>   + mpc6xx
>>>>   + mpc750
>>>>   + mpc821
>>>>   + mpc823 (uses mpc821 directory)
>>>>   + mpc850 (uses mpc860 directory)
>>>>   + mpc860
>>>>   + mpc8260
>>>>
>>>> The following PowerPC family members are supported but
>>>> still use the old exception processing model:
>>>>
>>>>   + ppc403
>>>>   + ppc405 (uses ppc403 directory)
>>>>   + ppc6xx (no libcpu support)
>>>> ------------------------------------------------------------------------------------------------
>>>>  so I thought ppc603e is supported by old exception processing model.
>>>>
>>>> and If I use new exception processing, I should just use code under
>>>> c/src/lib/libcpu/powerpc/new-exception, right?
>>>>
>>>> do I need to define any special macros ?
>>>>
>>>> 2008/4/6, Thomas Doerfler (nt) <Thomas.Doerfler at imd-systems.de>:
>>>> Hi,
>>>>
>>>> this is simple, use the new one, because the "old" is no longer supported.
>>>>
>>>> which README did you consult? which RTEMS version are you using?
>>>>
>>>> wkr,
>>>> Thomas.
>>>>
>>>>  ü schrieb:
>>>>
>>>> | Hi,
>>>> |    I have a ppc603e based borad, which exception model should I use,
>>>> | new or old?( I think it should be old exception model accroding to the
>>>> | README file).
>>>> |    and what macro should I define to chose between the two? and where
>>>> | can I find the clock driver support, is it similar to ppc403?
>>>> | _______________________________________________
>>>> | rtems-users mailing list
>>>> | rtems-users at rtems.com
>>>> | http://rtems.rtems.org/mailman/listinfo/rtems-users
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> rtems-users mailing list
>>>> rtems-users at rtems.com
>>>> http://rtems.rtems.org/mailman/listinfo/rtems-users
>>>>
>>>>         
>>> --
>>> --------------------------------------------
>>> embedded brains GmbH
>>> Thomas Doerfler           Obere Lagerstr. 30
>>> D-82178 Puchheim          Germany
>>> Tel. : +49-89-18 90 80 79-2
>>> Fax  : +49-89-18 90 80 79-9
>>> email: Thomas.Doerfler at embedded-brains.de
>>> PGP public key available on request
>>>
>>> Diese Nachricht ist keine gescha"ftliche Mitteilung im Sinne des EHUG.
>>> _______________________________________________
>>> rtems-users mailing list
>>> rtems-users at rtems.com
>>> http://rtems.rtems.org/mailman/listinfo/rtems-users
>>>
>>>       
>> --
>> Joel Sherrill, Ph.D.             Director of Research & Development
>> joel.sherrill at OARcorp.com        On-Line Applications Research
>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>>   Support Available             (256) 722-9985
>>
>>
>>
>>     
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985





More information about the users mailing list