OMAPL138B-EP: McASP Project Error

Nayan Gite

Prodigy 60 points

Part Number: PROCESSOR-SDK-OMAPL138

Hi,

I got the following error when I was running McASP project.

xdc.runtime.Main: "src/mcasp_drv.c", line 4181: assertion failure

And the line 4181 is: assert(0U != timeout);

Can you let me know what the issue is?

over 3 years ago

0 Rohini Chavan over 3 years ago

Prodigy 120 points

Part Number: PROCESSOR-SDK-OMAPL138

Hi,

I got the following error when I was running mcasp project.

xdc.runtime.Main: "src/mcasp_drv.c", line 4181: assertion failure

And the line 4181 is: assert(0U != timeout);

Can you let me know what the issue is?

0 Jianzhong Xu over 3 years ago in reply to Rohini Chavan

TI__Guru 59225 points

Hello,

The problem you're having is identical to the one reported by this thread. Please refer to the discussions there for information, especially Rahul's response about hardware setup (quoted below):

Now that you have the components setup correctly. Can you indicate what your LCDK setup looks like. Have yo setup the boot mode pins to UART and connected to CCS. Please confirm that PLL0 and PLL1 are setup using the GEL files. Also since you are testing audio example please make sure that you have audio line in and Audio line out connected.

CCS and LCDK Setup : http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_how_to_guides.html#omap-l138-c6748-lcdk-hardware-setup

McASP Example: http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_device_drv.html#id192

If you go the line number of the assert, you will see that the error occurs when there is timeout when trying to setup the global transmit control register "mcaspBitSetGblXCtl" . If you can put a scope and on the MCASP clock and frame sync pins, you should be able to see if the clock is showing up as expected and the framesync is generated.

Regards,

Jianzhong

Processors

Processors forum

OMAPL138B-EP: McASP Project Error