OMAPL138 using DSP work on ARM

Nian

Other Parts Discussed in Thread: OMAPL138, SYSBIOS

Hi all,

I design a image process project by CMOS sensor, it is working when I only use C6748 processor.

Now, I change this project for arago-linux, writing makefile by myself and booting linux.

I using slaveloader to startup dsp, the processor have done initialization, but interrupts not work and processor break down.

I don't have the ideas for this problem, the interrupts have different design on dsp and arm?

over 7 years ago

0 Titusrathinaraj Stalin over 7 years ago

TI__Guru** 116100 points

Dear Nian,
Yes, DSP application uses the direct PHYSICAL address access but Linux virtual address, also problem may occur due to resource conflict.
processors.wiki.ti.com/.../OMAP-L137_Audio_Drivers_in_the_DSP_+_Linux

Try to use notify module for HW interrupts in SYSLINK.
processors.wiki.ti.com/.../IPC_Notify_Drivers_and_Transports
processors.wiki.ti.com/.../SysLink_UserGuide

0 Shankari G over 7 years ago

TI__Mastermind 43955 points

Hi Nian,

Nian said:
Now, I change this project for arago-linux, writing makefile by myself and booting linux.
I using slaveloader to startup dsp, the processor have done initialization, but interrupts not work and processor break down.I don't have the ideas for this problem, the interrupts have different design on dsp and arm?

For this, you have to use syslink which is available for OMAPL138.

you can start up with running the syslink examples and then you can include the image processing project as a DSP app.

http://processors.wiki.ti.com/index.php/MCSDK_OMAPL138_User_Guide_Chapter_Exploring#Syslink

http://processors.wiki.ti.com/index.php/OMAP-L138_LCDK_Linux_Software_Developer's_Guide#Steps_to_Build_SysLink

0 Nian over 7 years ago in reply to Shankari G

Prodigy 110 points

Thanks Shankari for your reply and suggest.

Yes, I imitate syslink examples to build my project, but VPIF and LCDC interrupt is using hw_interrupt to design.
Is it the reason why my processor break down?

like it

Hwi_Params_init(&params);
params.eventId = SYS_INT_VPIF_INT;
params.enableInt = FALSE;
Hwi1 = Hwi_create(8, &VPIFIsr, &params, &eb);
if (Hwi1 == NULL)
{
System_printf("Hwi_create() failed for VPIF!\n");
BIOS_exit(0);
}

0 Nian over 7 years ago in reply to Titusrathinaraj Stalin

Prodigy 110 points

Hi Titus S.,
I just use messageQ module in my project.
If I need using HW interrupts, I have to also use notify module?

0 Titusrathinaraj Stalin over 7 years ago in reply to Nian

TI__Guru** 116100 points

Yes, as wiki said, we can use notify module to handle the hardware interrupts.
I would like to recommend you to use the simple GPIO interrupt in DSP code with Linux running to understand the SYSBIOS HWI.
Also I don't have much information on SYSBIOS, you can check with SYSBIOS folks in SYSBIOS (TI-RTOS) e2e forum.

Processors

Processors forum

OMAPL138 using DSP work on ARM