[U-Boot] Vector set up in u-boot for OMAP3530.

[U-Boot] Vector set up in u-boot for OMAP3530.

[Rahanesh]

Hi All,
 
I am trying to port a RTOS to OMAP3530 board. I use CCSv4 and XDS510 PP +
JTAG emulator  to connect to the board.
 
I am trying to set up vector table for a my custom RTOS.
 
ARM provides 0x0000:0000 and 0xFFFF:0000  as the Vector base address.
 
I planned to use 0x0000:0000 for my development. 
 
I have decided to hard-code the opcode for the corresponding branches  to
the loactions respectively.(0x00000000 to 0x0000001C)
 
When i write to 0x00000000 location , i get a prefetch abort exception. Why
am i not able to write to 0x00000000?
 
How did U boot handle this? How did U boot set  up Vector table?
 
Can anyone help me please?
 
 
 
 
Regards
Rahanesh
 
 
 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.

[U-Boot] Vector set up in u-boot for OMAP3530.

[Nishanth Menon]

Rahanesh said the following on 03/04/2009 01:23 PM:
> I am trying to set up vector table for a my custom RTOS.
>  
> ARM provides 0x0000:0000 and 0xFFFF:0000  as the Vector base address.
>  
> I planned to use 0x0000:0000 for my development. 
>  
> I have decided to hard-code the opcode for the corresponding branches  to
> the loactions respectively.(0x00000000 to 0x0000001C)
>  
> When i write to 0x00000000 location , i get a prefetch abort exception. Why
> am i not able to write to 0x00000000?
>   
Some basics on interrupt vector handling on cortex_a8: CP15 coprocessor
forallows:
* legacy high and low interrupt vectors
* also allows you to program interrupt vector of your choosing.
please read the ARM architecture Manual and the ARM technical reference
manual for further information.
if you look at the OMAP3 TRM, you will find 0x0 belonging to GPMC
address space, unless you mapped something there, ARM will not find an
vector to execute.
>  
> How did U boot handle this? How did U boot set  up Vector table?
>   
in OMAP3, we have rom code which setups a trampoline vector in SRAM.
this is piggybacked to handle the interrupts. the omap3 code probably
does not use interrupts extensively at this stage, but yeah, that is one
way to do it.. but you would need ROM Code executing prior to your code
to get this.

one way to go about this is to enable MMU and map 0x0 to which ever
address space you want (if you want to use the "old style" of doing arm
interrupts..

>   
>
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.
>
>   
Please... we have this long aversion to this form of copyright
information tailer.. please do not claim that it is always present for
mails from you company.. if so, use a different mail id such as gmail etc..


Regards,
Nishanth Menon