Sign in
Search 68hc12
Subscribe to 68hc12
68hc12 by Keywords
68HC1 | 812A4 | 9S12DP256 | Bootloader | CodeWarrior | D60A | Debugger | DP256 | ECT | EEPROM | EVB | Flash | HC1 | HCS12 | I2C | IAR | ICC1 | Interrupts | LCD | M68KIT912DP256 | MC9S12DP256 | MC9S12DP256B | Metrowerks | Motor | MSCAN | Multilink | PLL | Quadrature | SDI | SPI | Transceiver | XFC
Ads
Discussion Groups
See Also
Discussion Groups | 68HC12 | ProcessorExpert & Interrupts in RAM
Join our technical discussions about Freescale Microcontrollers: M68HC12. (Freescale Semiconductor is a Subsidiary of Motorola).
ProcessorExpert & Interrupts in RAM - Relson, David - Dec 11 10:37:00 2005
I've enabled "interrupts in RAM" to allow interrupts to be handled by
the boot loader or the user application (according to which program is
active).
I've noticed that if ProcessorExpert has NVMemory's interrupts enabled,
in Vector.c it uses NVMemory_Interrupt rather than TargCpu_INT29. With
this setting, the interrupt ignores the address in IntTable (in RAM) and
always goes to the boot loader's NVMemory_Interrupt (in FLASH).
Isn't this incorrect behavior?
Of course I don't fully understand ProcessorExpert, so I may be wrong
about this. If I'm wrong, would someone enlighten me?
If I'm correct that this behavior is wrong, it's a bug in
ProcessorExpert, no? Anybody have a fix?
Regards,
David
Note: My workaround is to turn off ProcessorExpert and make Vector.c
point where I think it should be pointing.
______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.
(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )
the boot loader or the user application (according to which program is
active).
I've noticed that if ProcessorExpert has NVMemory's interrupts enabled,
in Vector.c it uses NVMemory_Interrupt rather than TargCpu_INT29. With
this setting, the interrupt ignores the address in IntTable (in RAM) and
always goes to the boot loader's NVMemory_Interrupt (in FLASH).
Isn't this incorrect behavior?
Of course I don't fully understand ProcessorExpert, so I may be wrong
about this. If I'm wrong, would someone enlighten me?
If I'm correct that this behavior is wrong, it's a bug in
ProcessorExpert, no? Anybody have a fix?
Regards,
David
Note: My workaround is to turn off ProcessorExpert and make Vector.c
point where I think it should be pointing.
______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.
(You need to be a member of 68hc12 -- send a blank email to 68hc12-subscribe@yahoogroups.com )