Enabling ARM Interrupts in the "Boot Images" example

Hi OBond,

Is it okay for you if any interrupt based code works on ARM core ?

The interrupts I tried are CHIP_SIG2 and Timer1. Both run perfectly if the code is run through a debugger.

If it works with debugger then the problem could be from AIS convertion side.

How did you flash the images into flash media ?

After both arm.out and dsp.out are ready, I call "HexAIS_OMAP-L137 -o omap.bin DSP.out ARM.out". The resulted omap.bin is written to the SPI flash memory byte-by-byte beginning fro the address 0x00000000 and the board is reset.

Try to change the ini file which is selected by default.

Titusrathinaraj,thank you for the advice. Do you mean the ini file used by HexAIS_OMAP-L137.exe? Most settings which I checked are adjusted for more reliable data transfer from the PC to OMAP flash memory chip. In my case the file content and the flash memory records are verified, so it is guaranteed that the binary file is properly transferred.

Hi OBond,

Your issue may have one of the reason mentioned at following TI wiki.

http://processors.wiki.ti.com/index.php/OMAP-L138_Bootloader#Why_does_my_program_work_in_CCS_but_doesn.27t_boot_from_Flash.3F

I checked the steps listed in the document. None of them seem to be relevant.

It looks for me like the problem may be in the default asm files which I copied from "quickStartOMAPL1x_rCSL" ARM examples. In particular, the ASM9_handler.asm takes care about only three interrupts:

    .global SWI_handler
    .global IRQ_handler
    .global FIQ_handler

- and ignores the rest, nothing for pre-fetch abort, data abort, undefined instruction, etc.

Hi OBond,

Could you attach your CCS project here ?

Are you running any example code or porting anything ?

Titusrathinaraj,I attached the ARM project to this message. The DSP part is basically copied from the example that I mentioned, it simply takes the entry point address from ARM's memory map to enable it and then monitors a shared memory address continuously updated by ARM. As I already wrote, without interrupts enabled ARM runs fine, but if the Timer1 interrupt is enabled it will freeze immediately, if only CHIP_SIG is enabled it will freeze right after the bit is set by DSP.

Thank you!

Hi OBond,

Sorry for the delayed responses.

I'm able to reproduce the problem with your ARM app that not able to generate interrupts after I flashed into flash.

I'm working on it and let me update.

Thank you, I hope this issue has a solution :)

Hi OBond,

I also pasted the three required asm files (ARM9_handler.asm, ARM9_initstack.asm and ARM9_intvecs.asm) in the ARM project directory. After the arm project is compiled I update the entry point address DEVICE_ARM_UBL_LOAD_ADDR in the DSP code and expect it to run with the interrupts supported. The interrupts I tried are CHIP_SIG2 and Timer1. Both run perfectly if the code is run through a debugger. But if I try to run from flash the ARM code crashes immediately after the first interrupt happens. With interrupts disabled (enable_IRQ() commented out) the ARM runs perfectly even from the flash memory (LEDs blink, a record in shared RAM is updated continuously). The ARM is in the supervisor mode (switched in boot.asm, CPSR mode bits are 10011).

Have you tried Quick start CSL packages ARM examples ?

Titusrathinaraj, yes, I used these examples, but none of them run with ARM interrupts from flash.

In general, I think I found the reason why the interrupts don't run. The DSP is using PRUSS tpo setup vectors on ARM and in TI's example it takes care about reset vector only. I am going to try to fully implement the vector table through PRUSS.

Hi OBond,

Sorry for the delay on providing the solution/fix and thanks for your patience.

Also I saw the difference on starterware code between ARM and DSP examples of OMAPL138 and unfortunately OMAPL137 does not have starterware.

"system_config" library had been used for ARM app which is doing some interrupt configuring stuffs.

Earlier, I have flashed and worked with interrupt based starterware code on OMAPL138 processor.

http://processors.wiki.ti.com/index.php/StarterWare

http://processors.wiki.ti.com/index.php/StarterWare_01.10.01.01_User_Guide#Interrupt_Controller

Hi OBond,

Please refer to the following thread and seems to be what we are facing now.

http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/30196.aspx

The setup code has

_call_swi(ARM_PRIV_MODE_KEY);

for this. I also used boot.asm taking care about moving to the supervisor mode, both did not help.

I just tested the "with library" code, it really works, thank you very much :) 

Hi OBond,

I'm glad that you are able to fix the problem.

Hello,

I have exactly the same issue. ARM runs from flash without interrupt. Once I include interrupt ARM start but no interrupt is triggered.

Would you please provide a solution.

do we need to change the PRUS code in the DSP ubl or modify the asm files that handle the mapping interrupt in the ARM side.

Thanks for the support. 

Can you please create a new post for your problem with your setup in detail ?