Zynq exception handler

xuelin.tian at qkmtech.com xuelin.tian at qkmtech.com
Thu Sep 29 04:32:03 UTC 2016

OK, I will go through these. Thanks a lot.

Best wishes,
Tim Tian
xuelin.tian at qkmtech.com
From: Chris Johns
Date: 2016-09-29 12:22
To: xuelin.tian at qkmtech.com; users at rtems.org
Subject: Re: Zynq exception handler
On 29/09/2016 13:38, xuelin.tian at qkmtech.com wrote:
> I check the arm4-exception-default.S to see that, there are a few
> default handlers for ARM exceptions. But the default handlers are just
> to store the CPSR and return address. I may want to add some more to
> these. Because when I define some functions, error (multiple definition)
> comes up. Any hints about this? Thank you.
Have a look in my debug server code which I am developing. You can find 
it here 
There are a couple of levels you can use to manage the error. The first 
is via the RTEMS interfaces. Look in init.c at the line:
#define CONFIGURE_INITIAL_EXTENSIONS { .fatal = fatal_extension }
Any of the error traps will end up here for you with a suitable frame to 
decode the issue. This is preferred.
If you need to get down to the hardware have a look in 
rtems-dbserver-arm.c and the rtems_dbserver_target_enable call. It 
updates the CP15 directly to have control pass directly to local 
exception handlers. This code also shows how to use naked handlers. You 
need to know how to handle the exception when at this level.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20160929/cd9efc44/attachment-0002.html>

More information about the users mailing list