Masking single interrupts question

Masking single interrupts question

[Thomas Klöber]

[-- Attachment #1: Type: text/plain, Size: 645 bytes --]

Hello,

I am porting eCos to the Infineon Tricore TC1796 and have a question regarding 
the HAL_INTERRUPT_MASK / -UNMASK macros.

On the TC1796, each of up to 181 active interrupt sources must be assigned a 
priority (1-255), which also defines its vector number. Single interrupts 
only can be disabled by the corresponding source, not by priority level. 
Unfortunately, there is also no (simple) way, to find out, which source 
actually is set to a given priority.

eCos, on the other hand, expects interrupts to be maskable by their vector 
number, so what can I do, to accomplish this?

Thanks in advance & regards,

Thomas

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Masking single interrupts question

[Alessandro Valenti]

Do you plan to use, into your application, a run-time customized 
interrupt prioritization?
If not, you can insert a 1:1 mapping of all of 181 sources into 181 
different priority levels and use a biunivoc mapping table.

Bye,
Alessandro.

Thomas Klöber wrote:
> Hello,
> 
> I am porting eCos to the Infineon Tricore TC1796 and have a question regarding 
> the HAL_INTERRUPT_MASK / -UNMASK macros.
> 
> On the TC1796, each of up to 181 active interrupt sources must be assigned a 
> priority (1-255), which also defines its vector number. Single interrupts 
> only can be disabled by the corresponding source, not by priority level. 
> Unfortunately, there is also no (simple) way, to find out, which source 
> actually is set to a given priority.
> 
> eCos, on the other hand, expects interrupts to be maskable by their vector 
> number, so what can I do, to accomplish this?
> 
> Thanks in advance & regards,
> 
> Thomas