Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

Linking issue in OMAP-L138 DSP+ARM9 LCDK with SYSBIOS to drive StarterWare

$
0
0

Hello

Yesterday, I just repeated what Sam had done (of this thread) last year. 

http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/259301.aspx

First, I have created a SYS/BIOS (v6.4) project (as simple as a "hello" RTOS code, a Timer only) for LCDKOMAPL138's ARM core, and it worked just fine (with a Timer spinning correctly).  This proved the backbone TI-RTOS was working.  Then, I tried pulling in another known good StarterWare (1.10.04.01)'gpio' sample project with some initialization functions sitting in the main(), prior to entering the BIOS_start().  The result is almost the same: my LCDKOMAPL138 crashes at the PSCModuleControl function, only at different address HWREG(0x01E27000 + offset).

1) Why SYSBIOS stop working once I add StarterWare?  Is there any comment from TI or any pioneers?  Thank you!

My guessing is that I should do some reconfiguration on RTOS’s .cfg file, but I do not see any problem about memory conflict like in a linker command file (no .cmd file anyway).  As I tried to edit the .cfg file, I simply got two empty columns [Package Name and CPU Core].  I was not allowed to do any edit/view for  .cfg reconfiguration. Thus, we could not trace how the system has crashed and we have no access to edit/view it. 

2) How do I manage the .cfg file (or any .cmd if needed) for RTOS to work with StarterWare)?

Please help!  

Thank you!

YeuShyr


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>