Interrupts not working when USB IAP(AN10711) is used

Sorry for being a little dumb here.
But, I am actually using a ready hex file provided by the vendor of the board (mostly AN10711 based) for USB IAP programmer.

I have no control over the code of IAP.

IAP works like this...
While power up, if I keep P0.15 low, it enters IAP mode, if I keep it high, it jumps directly to user program mode (starting from 0x2000).

Will it still be possible for me to use interrupts or I should have the code of IAP to use interrupt.

Sorry for being a little dumb here.
But, I am actually using a ready hex file provided by the vendor of the board (mostly AN10711 based) for USB IAP programmer.

I have no control over the code of IAP.

IAP works like this...
While power up, if I keep P0.15 low, it enters IAP mode, if I keep it high, it jumps directly to user program mode (starting from 0x2000).

Will it still be possible for me to use interrupts or I should have the code of IAP to use interrupt.

The limitations above apply to the bootloader (see AN10711). The bootloader should disable interrupts while flashing your program. You have full control over IAP - you have the bootloader source as well, not?

I think you misunderstood the issue.
I have 2 programs now.

1. USB_IAP.hex : loaded at location 0x0:0x1FFF
2. my_prog.bin : loaded from 0x2000:0x2100 via IAP.

Now my_prog.bin has already been loaded via IAP.

Now, when I reset the board, first IAP will run, but as entry to bootloader is not asserted, it will jump to my_prog.bin.

Now, my_prog.bin is using timer interrupt.
So, when my_prog.bin is running, (and IAP is not running), will I be able to use interrupt?

I checked the Startup.s file and couldn't figure out much.
I do not have code for USB_IAP.hex.
I have code of my_prog.bin.

Now, what changes will I have to make to make interrupt of my_prog.bin work.

Per, your inputs will be much appreciated.
Tamir, thanks to being with me on this.

Urvish Gohil => Now, what changes will I have to make to make interrupt of my_prog.bin work.

Per => A program that is loaded at a different place need to remap the interrupt vector table. There are settings in the startup file to do this - copying the interrupt vector table into RAM and remap to that address. Without remapping, the processor would search for an interrupt handler within your boot loader code.

On the Startup file of my_prog.bin:
Set Options-> Asm-> Conditional Assembly Control Symbols: RAM_INTVEC REMAP RAM_MODE

And check what RAM_INTVEC REMAP RAM_MODE will do for you.

Thanks John for that wonderful and easy explanation.
While I did get what Per said, but didn't know how to do it.

Right now I do not have access to the board.
Will post here the my observation as soon as I get it(Hope to keep some smileys than).

Hi John,
I just tried adding "RAM_INTVEC REMAP RAM_MODE" but it didn't worked.

Here is what I tried.
1. I just wrote a prog in keil which toggles 2 port pins. 1st by a while loop, 2nd by timer.
2. Without adding anything I simulated it in keil. (IROM1 still from 0x0, No remapping)
3. This works well and I see both of the port pins toggling.

Now I made a simple change of Adding "RAM_INTVEC REMAP RAM_MODE".
I recompiled the code and simulated.
Here, I saw that, as soon as int is occurred, LPC jumps to "LDR PC, [PC, #-0x0FF0]", but does not move from that point.

Moreover, I see words REMAP and RAM_MODE in Startup.s but not the RAM_INTVEC.
I am using Startup.s provided by keil only.

KEIL has quite a lot startup.s/LPCooxx.s
You need another startup.s like this:
rtime.felk.cvut.cz/.../lpc21xx-boot

+# Memory Mapping (when Interrupt Vectors are in RAM)
+ .equ MEMMAP, 0xE01FC040 /* Memory Mapping Control */
+.ifdef RAM_INTVEC
+ LDR R0, =MEMMAP
+ MOV R1, #2
+ STR R1, [R0]
+.endif

I think what I have is exactly this only.

; Memory Mapping (when Interrupt Vectors are in RAM)
MEMMAP          EQU     0xE01FC040      ; Memory Mapping Control
                IF      :DEF:REMAP
                LDR     R0, =MEMMAP
                IF      :DEF:EXTMEM_MODE
                MOV     R1, #3
                ELIF    :DEF:RAM_MODE
                MOV     R1, #2
                ELSE
                MOV     R1, #1
                ENDIF
                STR     R1, [R0]
                ENDIF

By defining REMAP and RAM_MODE, this will do exactly what your code snippets does with RAM_INTVEC.

In the Startup.s that I am using, what shown above is the only place where REMAP and RAM_MODE is used. There are no other defines.

I guess your startup.s is very like this one:

forum.sparkfun.com/viewtopic.php

If so, you need to figure out how it accomplishes what Per told you.

And, I don't think you can easily simulate USB_IAP.hex + my_prog.bin, it would be easier to run them on the real hardware.

Are you using this:
ics.nxp.com/.../
==> Boot Loader V2.12 for LPC213x and LPC214x (Apr 12, 2007)
And it does not provide source code for bootloader (USB_IAP.hex)?

Take a look at this: it is for LPC23xx.
http://www.keil.com/forum/13707/

See if you can debug your my_prog.bin like the below.
After all of that, I start my Debug Session. The Disassembly Window shows the Machine Code/ASM Code of the Bootloader (without the Source Code). Then, the Bootloader jumps to my application. So that, I get the state while the Bootloader just finishes its work, and pass the control to my application. I can observe the CPSR and the R13/SP of Supervisor Mode etc, to see if the solutions works properly.

John,
I did try the changes on hardware also. Yes, you are correct that simulation cannot be always correct.

BTW, I didn't find this connected to this issue.
"Are you using this:

Here is what I am using
"">www.nxp.com/search

BTW,
Right now I am looking at "http://www.keil.com/forum/13707/" which you gave.
Though this tread is for different uC and App Not is also different (AN10759), I think the idea should be same.

Thanks for the pointer. Will have a look at it and post the conclusion here.

Meanwhile, if there is something new, I would be glad to take it.

www.nxp.com/.../LPC2000_Series_Secondary_Bootloader.zip

The above link is not for USB_IAP either. I am sorry.

www.sparkfun.com/.../94

LPC2148 USB Bootloader Tutorial
by zagGrad | August 04, 2008 | 17 comments

This link should provide everything you need, except it may not be designed for your hardware, and it is not for KEIL toolchain.

.if (RAM_MODE==0)
/* Relocate .data section (Copy from ROM to RAM) */
                LDR     R1, =_etext
                LDR     R2, =_data
                LDR     R3, =_edata
                CMP     R2, R3
                BEQ     DataIsEmpty
LoopRel:        CMP     R2, R3
                LDRLO   R0, [R1], #4
                STRLO   R0, [R2], #4
                BLO     LoopRel
DataIsEmpty:
.endif