Regarding Processor Expert

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Regarding Processor Expert

Jump to solution
538 Views
sheetanshkaushi
Contributor III

Hi! I am very new to Codewarrior(Version 5.9) using MCU: MC9S08AW60A. As i have had experience with AVR and C/C++ programming, i am comfortable with the programming aspect. But i am stumped because of a very peculiar problem.

 

Consider the simple example:

//Code Begins

#include <hidef.h> /* for EnableInterrupts macro */
#include "derivative.h" /* include peripheral declarations */

 

void main(void) {

  EnableInterrupts; /* enable interrupts */
  /* include your code here */
 
  PTFDD = 0xFF; //my two lines of code.
  PTFD = 0xFF;

 

  for(;;) {
    __RESET_WATCHDOG(); /* feeds the dog */
  } /* loop forever */
  /* please make sure that you never leave main */
}

//Code Ends

 

Now, before debug, i  use "Device Initialization" option and open up the PROCESSOR EXPERT  to check if the pins are configured as expected. Note: I DID NOT MAKE ANY CHANGES, i  just had a look. and consequently closed it after saving the .prm file. And if i try to debug now it says:

 

Link Error   : L1119: Vector allocated at absolute address 0xFFFE overlaps with sections placed in segment .absSeg117


Link Error   : Link failed

 

Yes, i am a noob. I am pretty sure that the answer to this will be very easy for your expertise, so please be patient and give me an explanation. Also very likely is the fact that i am not using the Processor Expert properly, none the less i am very much willing to learn.Thanks in advance.

Labels (1)
0 Kudos
1 Solution
356 Views
CrasyCat
Specialist III

Hello

To remove the error message L1119 remove the line

      VECTOR 0 _Startup

from your .prm file


CrasyCat

View solution in original post

0 Kudos
2 Replies
357 Views
CrasyCat
Specialist III

Hello

To remove the error message L1119 remove the line

      VECTOR 0 _Startup

from your .prm file


CrasyCat

0 Kudos
356 Views
sheetanshkaushi
Contributor III

Thank you Catherine, that did solve the issue.

0 Kudos