[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RES: SIS aplication interrupted with rtems4.8



It works for me too (RTEMS 4.8.1).

The address you received in your error message (0x020001f0) is the default
address for the watchdog timeout trap, which has the opcode for a "ta 0"
instruction (91d02000).

I don't know if you have a modified version of SIS (don't remember now what
does SIS do to the watchdog, nor the BSP) but it's clear that your boot
loader is disabling the watchdog. Try to write something in the Watchdog
Trap Door Set MEC register at the beginning of your code to disable the
watch dog.

Regards,

Fabr?cio de Novaes Kucinskis - DEA / INPE
------------------------------------------------
Onboard Data Handling Group - SUBORD
Aerospace Electronics Division
Brazilian National Institute for Space Research


-----Mensagem original-----
De: rtems-users-bounces at rtems.org [mailto:rtems-users-bounces at rtems.org] Em
nome de Joel Sherrill
Enviada em: segunda-feira, 9 de mar?o de 2009 12:57
Para: Nicolas Horro
Cc: RTEMS Users
Assunto: Re: SIS aplication interrupted with rtems4.8

Nicolas Horro wrote:
> Hello,
>
> I'm compiling this test application which in the real hardware (ERC32)
> performs ok, but with the SIS BSP (RTEMS 4.8) ends interrupted by an
> IU error mode. Anybody is getting the same error?
>   
Runs for me with the CVS head.  I had sparc/sis built
and installed for testing something else so just threw the code at it.

Do you have MANAGERS=all in your Makefile or do you have
stubs?

--joel
> regards,
>
> Nicol?s Eduardo Horro
>
>
> --- init.c --------------------------------------------------
>
> #include <bsp.h>
>
> /* RTEMS */
> #include <rtems.h>
> #include <stdio.h>
>
> rtems_task Init( rtems_task_argument argument )
> {
>   printf(" *** RTEMS Application *** \n\n\r");
>   while(1) {
>     rtems_task_wake_after(1000);
>     printf(".\n\r");
>   }
> }
>
> /**************** START OF CONFIGURATION INFORMATION ****************/
> #define CONFIGURE_INIT
> #define CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER
> #define CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER
> #define CONFIGURE_MAXIMUM_TASKS             1
> #define CONFIGURE_RTEMS_INIT_TASKS_TABLE
> #define CONFIGURE_EXTRA_TASK_STACKS         (3 * RTEMS_MINIMUM_STACK_SIZE)
> #include <rtems/confdefs.h>
> /****************  END OF CONFIGURATION INFORMATION  ****************/
>
>
> --- stdout --------------------------------------------------
>
>   ERC32 boot loader
>
>   system clock     : 16.0 MHz
>   baud rate        : 38400 baud
>   rom              : 4096 K, 9 ws
>   ram              : 4096 K, 1 bank(s), 0/0 ws (r/w)
>   edac             : disabled
>   parity           : disabled
>   dma              : enabled
>   watchdog         : disabled
>   i/o area 0       : 512 B, 0 ws (enabled without parity)
>   i/o area 1       : 512 B, 3 ws (enabled without parity)
>   i/o area 2       : 512 B, 3 ws (enabled without parity)
>   i/o area 3       : 128 K, 7 ws (enabled without parity)
>   ext. interrupt 0 : low level
>   ext. interrupt 1 : low level
>   ext. interrupt 2 : low level
>   ext. interrupt 3 : low level
>   ext. interrupt 4 : low level
>
>   initialising ram memory
>   loading .text
>   loading .data
>   loading .jcr
>
>   starting application
>
>  *** RTEMS Application ***
>
> IU in error mode (128)
>  16777220  020001f0  91d02000  Address 0x020001f0 is out of bounds.
> _______________________________________________
> 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