CCS/OMAP-L138: OMAP-L138/SYSBIOS:

George Rodionov

Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAPL138, , TMDSLCDK138

Tool/software: Code Composer Studio

Hello!

I'm using MityDSP-L138 with PROCESSOR-SDK-RTOS-OMAPL138 (Windows 10). I want to work with kernels ARM9 and C67x using SYS/BIOS 6.76.
With C67x none problems, but with ARM the next problem:

After load into memory program start on address 0xC303AD24.
When I run program in ARM9 - the program hang on after BIOS_start(), the idle loop start and do 100 - 1300 loops (it's constant value after download programm into memory by JTAG XDS100v3).
After it (100 - 1300 loops) the ARM9 hand on (programm debug counter stop into idle loop) and start run in the section where is no symbols are defined (address 0x00082BC4 for example).
What is happend? What am I wrong about?

After I run ARM9, I can't connect into C67xx.

May it be program or data memory overlaps?

over 5 years ago

0 Rex Chang over 5 years ago

TI__Guru 50170 points

Hi, George,

Are you using Critilcal Link SDK? What's the Kernel version?

Rex

0 Sahin Okur over 5 years ago

TI__Mastermind 27355 points

Hello,

Please share which target configuration you are using and which examples you are trying to run. Please also share GEL output on the console when connecting to the ARM and DSP core.

You can also check ROV for any errors. Tools > ROV Classic/Runtime Object View > BIOS > Scan for Errors.

Regards,
Sahin

0 George Rodionov over 5 years ago in reply to Rex Chang

Expert 1210 points

No I do not use Critical Link SDK. I using pdk_omapl138_1_0_10, try different Kernel, now it is bios_6_76_04_02.

George

0 George Rodionov over 5 years ago in reply to Sahin Okur

Expert 1210 points

Target Configuration XDS100 v3 for OMAPL138 (OMAPL138 - ARM9 and C674x Floating point DSP with PRU).

I try to run simple application with periodic blinking led.

GEL output for ARM:

ARM9_0: Output: Memory Map Cleared.
ARM9_0: Output: ---------------------------------------------
ARM9_0: Output: Enabling Full EVM PSCs...
ARM9_0: Output: PSC Enable Complete.
ARM9_0: Output: ---------------------------------------------
ARM9_0: Output: DSP Wake Complete.
ARM9_0: Output: ---------------------------------------------

Gel output for DSP:

C674X_0: Output: Memory Map Cleared.
C674X_0: Output: ---------------------------------------------
C674X_0: Output: Memory Map Setup Complete.
C674X_0: Output: ---------------------------------------------

ROV errors:

The blinking led example on C67xx (work):

omapl138_c67xx.zip

The project for ARM9 (do not work):

omapl138_arm9.zip

George.

0 George Rodionov over 5 years ago in reply to Sahin Okur

Expert 1210 points

Do you can advice me something?

Geroge

0 Sahin Okur over 5 years ago in reply to George Rodionov

TI__Mastermind 27355 points

Hello,

Do you see the blinking LED at all when running the ARM program? Do other examples work?

It is not clear whether those ROV errors are actual errors or red herrings, can you try increasing your stack size to see if it helps?

Regards,
Sahin

0 George Rodionov over 5 years ago in reply to Sahin Okur

Expert 1210 points

Hello!

I try run two examples - UART_BasicExample_lcdkOMAPL138_armDMATestproject, GPIO_LedBlink_lcdkOMAPL138_armTestProject. Results the same.

System stack size = 131072

Heap size = 65536

Do not work.

I using OMAP-L138, but examples for TMDSLCDK138. Could this be the reason?

0 George Rodionov over 5 years ago in reply to George Rodionov

Expert 1210 points

I thought it was strange in the GPIO_LedBlink_lcdkOMAPL138_armTestProject I see the next strange thing before execution function BIOS_start().

too much semaphore object.

For other device I once fogot initialize semaphore and project crached too. But in case simple project for OMAP-L138 device I do not use semaphore. For other device I once fogot initialize semaphore and project crached too. But in case simple project for OMAP-L138 device I do not use semaphore.

0 George Rodionov over 5 years ago in reply to George Rodionov

Expert 1210 points

I thought it was strange too.

0 George Rodionov over 5 years ago in reply to Sahin Okur

Expert 1210 points

Hello!

I tried almost all examples and tests - none work. Trobles arise after BIOS_start(). I have not an idea to solve it.

George.

0 Sahin Okur over 5 years ago in reply to George Rodionov

TI__Mastermind 27355 points

George,

As you suspected, this may be because the Processor SDK examples are for the LCDK. Since you are using the Mity EVM, there may be some porting effort involved. If you can, we recommend beginning development with the LCDK.

Can you try running the examples provided at the link below? These are not supported by TI but we can at least rule out any issues with your hardware.

https://support.criticallink.com/redmine/boards/10/topics/1500

Regards,
Sahin

Code Composer Studio™︎

Code Composer Studio forum

CCS/OMAP-L138: OMAP-L138/SYSBIOS: