AM5728: DSP c66x AM5728

Ilya Fedusiv

Part Number: AM5728
Other Parts Discussed in Thread: SYSBIOS

I have RTOS project for DSP c66
I want to configure interrupt to use sys_nirq1.

Code I used:

1
2
3
4
    HwiP_Params_init(&hwip_params);
    hwip_params.priority = 0x20;
    hwip_handle = HwiP_create(IrqId, (HwiP_Fxn)&IrqFunction, &hwip_params);
    HwiP_enableInterrupt(IrqId);
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    HwiP_Params_init(&hwip_params);
    hwip_params.priority = 0x20;
    hwip_handle = HwiP_create(IrqId, (HwiP_Fxn)&IrqFunction, &hwip_params);
    HwiP_enableInterrupt(IrqId);

Question is about variable IrqId;

I found in AM572x manual reference next table on page 4128. Table 17-3

DSP1_IRQ_33 2 CTRL_CORE_DSP1_IRQ_32_33[24:16] 2 EXT_SYS_IRQ_1 External interrupt (active low) via sys_nirq1 pin

I tried:
IrqId = 33
IrqId = 2
And
IrqId = 1.

But it does not work.

Also interesting, that
hwip_params.triggerSensitivity = OSAL_ARM_GIC_TRIG_TYPE_EDGE;
this parameter triggerSensitivity is removed for dsp.

Kr,
Ilya Fedusiv

over 3 years ago

0 Fabiana Jaimes over 2 years ago

TI__Mastermind 18080 points

Hi Ilya,

I am currently involving the appropriate expert on this thread. In the meantime, could you take a look at these related E2E threads?:

AM5728: IRQ_USER0 interrupt in C66x DSP - Processors forum - Processors - TI E2E support forums

Thank you,

Fabiana Jaimes

0 Parth Nagpal over 2 years ago in reply to Fabiana Jaimes

TI__Mastermind 42135 points

Hi Ilya,

Can you please confirm that the pinmuxing is proper? By default it the pin is not muxed to sys_nirq.

Regards,
Parth

0 Stanley Liu over 2 years ago in reply to Parth Nagpal

TI__Guru 50045 points

In addition to Parth's comment, please note that by sys_nirq1 signal is connected to IRQ_CROSSBAR_2 which is then routed to DSP1_IRQ_33 by default in CTRL_CORE_DSP1_IRQ_32_33 register.

DSP1_IRQ_33 is then connected to EVT33 inside DSP_INTC.

DSP INTC has an interrupt mux to select interrupt from EVTs to a specific DSP CPU interrupt number, which is the interrupt number you pass into HWI API.

HwiP is OSAL API which is mapped to HWI in SYSBIOS. You should refer to SYSBIOS HWI API to understand the parameters used.

If you prefer, you can use HWI API directly from SYSBIOS, instead of calling HwiP from OSAL.