LPCXpresso interrupts' declaration for LPC2103

[markpe666]

Hello,

I have just moved from the Keil uVision to LPCXpresso and encountered a problem right from the start.

in uVision interrupts are declared this way:

void FIQ_Handler ( void )__irq;
void IRQ_Handler ( void )__irq;

void TIMER2_irq ( void )__irq;

void TIMER1_irq ( void )__irq;

void TIMER0_irq ( void )__irq;
and so on.

This way does not work with LPCXpresso 8.2.2.

Can anybody describe the way to do it the right way, please?

[markpe666]

Hi Felipe,

Wouldn't it be easier to say " look in the GCC Compiler Manual" instead of making the impression that you know and I don't ?

Kind regards and thanks for your attention,

Mark 

[markpe666]

Hello,

As I said above, interrupt declaration issue is no longer a problem.

I am not using any standard evaluation board, so I don't have any HW debugging link, therefore I am looking for a ready reference design exactly for LPC2103 to avoid inserting checkpoints in my software and download it to the microcontroller to see how far it goes. It is very time consuming and inefficient. Having a working reference design would perhaps cast some light on the problem.

Best regards,

Mark

[markpe666]

Hi Felipe,

thank you for your reply.  I have already figured out the way to declare interrupt, yet there is another problem with LPCXpresso or with my coding.

I compiled and successfully run an application under the Keil uVision. Then I ported that application ( mainly interrupt declarations and some startup file tuning ).

When I download the .hex result into my LPC2103 it does absolutely nothing.

Looking for solution I searched the archives and found absolutely no reference designs for 210x controllers.

Perhaps you know where to download such design from?

LPCXpress has some designs, but the closest is for 29xx controller, which does not come even close to 2103

So I still have noclue what I am doing wrog.

[FelipeGarcia]

Hi Mark,

I highly recommend you to debug your program carefully to see what part of the code is causing this issue. It is really hard to narrow down the issue if you just load the hex file before debugging.

Best regards,

Felipe

[FelipeGarcia]

Hello,

You can use the project wizard on the Quickstart Panel to create a new project for the part you are using. Then you can copy the required files from the appropriate code bundle.

You can also see other LPCOpen packages to see the correct way to declare interrupts.

Best regards,

Felipe