Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training




Loading

Relacatable vector, error address MTUX

Posted by oriol on October 6, 2011
Hi.
I'm using FreeRtos with GNURX (RX62N) in HEW.
In hardware manual i see that after S12AD interrupt, exist various address reserved ( from 0x019C to 0x01C4). When i see your code in RelocatableVectors in vects.c show this:

//;0x0194 AD3_ADI3
(fp)INT_Excep_AD3_ADI3,
//;0x0198 Reserved
(fp)0,
//;0x019C Reserved
(fp)0,
//;0x01A0 TPU0_TGI0A
(fp)INT_Excep_TPU0_TGI0A,
//;0x01A4 TPU0_TGI0B
(fp)INT_Excep_TPU0_TGI0B,

this means that TGIOA interrut is in adress 0x01A0?? this adress should be reserved according to hardware manual because this interrupt should be in 0x01C8.

Thanks for all.
Regards

RE: Relacatable vector, error address MTUX

Posted by Richard on October 6, 2011
“When i see your code in RelocatableVectors in vects.c show this:”


It is not my code. If you look at the top of the file you will see:

/***********************************************************************/
/* */
/* FILE :vects.c */
/* DATE :Wed, Aug 25, 2010 */
/* DESCRIPTION :Vector Table */
/* CPU TYPE :Other */
/* */
/* This file is generated by KPIT GNU Project Generator. */
/* */
/***********************************************************************/



Looking at the file, I see something completely different, as shown below:

const fp HardwareVectors[] FVECT_SECT  = {
//;0xffffff80 Reserved
(fp)0,
//;0xffffff84 Reserved
(fp)0,
//;0xffffff88 Reserved
(fp)0,
//;0xffffff8C Reserved
(fp)0,
//;0xffffff90 Reserved
(fp)0,
//;0xffffff94 Reserved
(fp)0,
//;0xffffff98 Reserved
(fp)0,
//;0xffffff9C Reserved
(fp)0,
//;0xffffffA0 Reserved
(fp)0,
//;0xffffffA4 Reserved
(fp)0,
//;0xffffffA8 Reserved
Etc.


However, if there is a problem with the code you should submit a bug with KPIT.

Regards.



RE: Relacatable vector, error address MTUX

Posted by oriol on October 6, 2011
Hi. Thanks for your reply.

The problem is not here. the problem is that from vector adress 0x019C to 0x01C4 should be reserved because in hardware manual is reserved. In this code generate with KPIT GNU generator this adrees are filled with other interrupts that no correspond with this vector adress.

In good code should be:

//;0x019C Reserved
(fp)0,
//;0x01A0 Reserved
(fp)0,
//;0x01A4 Reserved
(fp)0,
//;0x01A8 Reserved
(fp)0,
//;0x01AC Reserved
(fp)0,
//;0x01B0 Reserved
(fp)0,
//;0x01B4 Reserved
(fp)0,
//;0x01B8 Reserved
(fp)0,
//;0x01BC Reserved
(fp)0,
//;0x01C0 Reserved
(fp)0,
//;0x01C4 Reserved
(fp)0,
//;0x01C8 MTU0_TGIA0
(fp)INT_Excep_MTU0_TGIA0,


but in the code with KPIT gnu generator is:

//;0x019C  Reserved
(fp)0,
//;0x01A0 TPU0_TGI0A
(fp)INT_Excep_TPU0_TGI0A,
//;0x01A4 TPU0_TGI0B
(fp)INT_Excep_TPU0_TGI0B,
//;0x01A8 TPU0_TGI0C
(fp)INT_Excep_TPU0_TGI0C,
//;0x01AC TPU0_TGI0D
(fp)INT_Excep_TPU0_TGI0D,
//;0x01B0 TPU0_TCI0V
(fp)INT_Excep_TPU0_TCI0V,
//;0x01B4 Reserved
(fp)0,
//;0x01B8 Reserved
(fp)0,
//;0x01BC TPU1_TGI1A
(fp)INT_Excep_TPU1_TGI1A,
//;0x01C0 TPU1_TGI1B
(fp)INT_Excep_TPU1_TGI1B,
//;0x01C4 Reserved
(fp)0,

thanks


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.


Free TCP/IP and file system demos for the RTOS


Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists