<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://e2e.ti.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>OMAP-L13x, AM1x and C674x Processors Forum - Recent Threads</title><link>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42.aspx</link><description>This forum supports technical questions related to silicon and hardware of the compatible AM1x, OMAPL13x and C674x ARM9 processors. These devices share common IP cores, interfaces, and software support so general questions are applicable to all. To enable </description><dc:language>en-US</dc:language><generator>6.x Production</generator><item><title>Where to set the Pin Mux (boot strap, u-boot, kernel or rootfs)</title><link>http://e2e.ti.com/thread/267285.aspx</link><pubDate>Sat, 25 May 2013 06:14:07 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7d6e47cc-1c2e-4c25-a16d-ca12c723c6ab</guid><dc:creator>Sreenivas Kowtharapu</dc:creator><slash:comments>0</slash:comments><comments>http://e2e.ti.com/thread/267285.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/267285/rss.aspx</wfw:commentRss><description>&lt;p&gt;hi ,&lt;/p&gt;
&lt;p&gt;I am using AM1808, i want to remove the Ethernet (i.e EMAC (MMI)) and use URAT0, to do this where i have to set the PIN Mux values.&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;Sreenivas&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>L138: No external XDS560 Trace for both ARM/DSP?</title><link>http://e2e.ti.com/thread/267269.aspx</link><pubDate>Fri, 24 May 2013 22:33:04 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:55c0da94-9cb3-445b-aba6-fd7636f36e70</guid><dc:creator>Paul Singh</dc:creator><slash:comments>0</slash:comments><comments>http://e2e.ti.com/thread/267269.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/267269/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;When I was configuring CCS ≫ Tools ≫ Trace Control, I found among the five options &amp;ldquo;ETB, 560 V2 Trace, 560 Trace Pod, Pro Trace, None&amp;rdquo;:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;ARM could only select ETB or None&lt;/li&gt;
&lt;li&gt;C674X could only select &amp;ldquo;None&amp;rdquo;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;as shown in the screenshot below:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/42/7360.trace_5F00_control.jpg"&gt;&lt;img border="0" alt=" " src="http://e2e.ti.com/resized-image.ashx/__size/550x0/__key/communityserver-discussions-components-files/42/7360.trace_5F00_control.jpg" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I further checked &amp;ldquo;Table 5-145. DSP Debug Features&amp;rdquo; and &amp;ldquo;Table 5-146. ARM Debug Features&amp;rdquo; in SPRS586C and found&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;ARM has only ETB/ETM, but no ability to transfer CPU information to an external receiver like XDS560 Trace&lt;/li&gt;
&lt;li&gt;DSP has only AET, no ETB, no ability to interface with XDS560 Trace&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/42/7450.debug_5F00_features.jpg"&gt;&lt;img border="0" alt=" " src="http://e2e.ti.com/resized-image.ashx/__size/550x0/__key/communityserver-discussions-components-files/42/7450.debug_5F00_features.jpg" /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Am I correct with these observations?&lt;/p&gt;
&lt;p&gt;And I guess the best I can use for the two cores are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;ARM: ETB&lt;/li&gt;
&lt;li&gt;DSP: AET&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>SPI’s CSDEF bits</title><link>http://e2e.ti.com/thread/260962.aspx</link><pubDate>Wed, 24 Apr 2013 16:39:13 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:55699579-fe6e-4a4b-b66a-7b43886f545e</guid><dc:creator>Paul Singh</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/260962.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/260962/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We have a question with L138&amp;rsquo;s SPI1&amp;rsquo;s chip select function.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For &amp;lsquo;SPI Default Chip Select Register (SPIDEF)&amp;rsquo;, all its seven bits[7-0] CSDEF[n] as described by TRM SPRUH77 are writable. However, the register view of CCS displays only one bit CSDEF0.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We currently have only attached a single device (SPI flash) to SPI1 port, so it is difficult to test other chip select pins. But does the screenshot here means the CCS display is incorrect, or the TRM contains incorrect information?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/42/4466.CSDEF.jpg"&gt;&lt;img alt=" " src="http://e2e.ti.com/resized-image.ashx/__size/550x0/__key/communityserver-discussions-components-files/42/4466.CSDEF.jpg" border="0" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Linux freeze when launching SYSBIOS app</title><link>http://e2e.ti.com/thread/267223.aspx</link><pubDate>Fri, 24 May 2013 18:28:02 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:f8735932-5c0d-4fac-a692-ca34e42a758d</guid><dc:creator>Stephane Mutz</dc:creator><slash:comments>0</slash:comments><comments>http://e2e.ti.com/thread/267223.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/267223/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m starting on OMAPL137. I have a working Linux (MV5). I want to start prototyping a DSP application. I have some simple code on CCS5 that plays with GPIOs. It is compiled with SYSBIOS (but not using it for the GPIO at this moment). I can compile and connect to the board. When I load the program and suspend the DSP at entry point, the linux is running fine. As soon as I execute the initialization code (before calling main() ), the linux freezes.&lt;/p&gt;
&lt;p&gt;I suspect a resource conflict vut I have not been able to pinpoint it. I have tried to deconfigure SYSBIOS to what seems a bare version (no clock, no timers, ...) but it didn&amp;#39;t solve the probelm. Any advice?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Memory map for the Omap-L138 ARM</title><link>http://e2e.ti.com/thread/267086.aspx</link><pubDate>Fri, 24 May 2013 08:33:42 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:220277e5-f8bd-4f60-8eb9-359b61c7e2b3</guid><dc:creator>Walter Snafu</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/267086.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/267086/rss.aspx</wfw:commentRss><description>&lt;p&gt;I&amp;#39;m trying to setup a linker command file for the OMAP-L138 to use with CCS.&amp;nbsp; For the ARM core in particular.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve tried to locate the memory map for the ARM core, but no luck.&amp;nbsp; I looked in the OMAP-L138 Tech Ref manual.&amp;nbsp; (page 108, for example).&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Where can I find a memory map for the ARM core?&lt;/p&gt;
&lt;p&gt;Thanks for your help.&lt;/p&gt;
&lt;p&gt;UPDATE:&amp;nbsp; I just noticed that CCS can supply a sample linker command file for the OMAP-L138, which includes a memory map for the ARM core.&amp;nbsp; However, it only includes a memory map for the 64kB ROM (which I can&amp;#39;t program or use), and the 8kB local RAM.&amp;nbsp; But it doesn&amp;#39;t give a memory map for the 16 kB instruction cache and the 16 kB data cache.&amp;nbsp; Perhaps I have the wrong assumptions.&amp;nbsp; I assumed I could &amp;#39;freeze&amp;#39; my code into the 16kB instruction cache, thereby keeping it local to the ARM (and unperturbed by the DSP)&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Some questions about fast RTS lib for C6748</title><link>http://e2e.ti.com/thread/266871.aspx</link><pubDate>Thu, 23 May 2013 13:22:00 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:eedb691c-db41-40e6-b8f2-5301c9948585</guid><dc:creator>Tiger Xu</dc:creator><slash:comments>1</slash:comments><comments>http://e2e.ti.com/thread/266871.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266871/rss.aspx</wfw:commentRss><description>&lt;p&gt;&lt;span style="font-size:small;"&gt;I have some questions about fast rts lib for C6748:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:small;"&gt;1. What&amp;#39;s the relations between mathlib, mathlib rts, rts lib, run-time-support arithmetic routines and fastRTS lib? Do they have totally same math functions? The main &lt;/span&gt;&lt;span style="font-size:small;"&gt;difference is the execution speed? which one is recommended in C6748?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:small;"&gt;2. At the beginning, I used RTS lib through including mathf.h in my code file. Although I can&amp;#39;t find any RTS lib information in the linker option in CCS3.3, some RTS &lt;/span&gt;&lt;span style="font-size:small;"&gt;lib routines, such as log10f and powf, can work correctly in my programs. Then, I want these math functions to execute faster and try to use the fast RTS lib. I installed the c67xRTS lib(c67xmathlib_2_01_00_00). But I finally got a awful results after I included the c67fastMath.h in my code file and linked the 674xfastMath.lib in the linker option. Some codes and the execution results(CPU Execute Cycles) are listed below, it seems that these routines in RTS or fast RTS lib don&amp;#39;t execute so fast as supposed. Both cj_rx_rs_I[i] and t are local variables in a function.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:small;"&gt;&amp;nbsp;value of cj_rx_rs_I[i]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -2842.252&amp;nbsp;&amp;nbsp; -2481.925&amp;nbsp;&amp;nbsp; -1151.185&amp;nbsp; -5563.792&amp;nbsp;&amp;nbsp; 1475.33&amp;nbsp;&amp;nbsp; -941.9764&amp;nbsp;&amp;nbsp;&amp;nbsp; 7095.919&lt;/span&gt;&lt;br /&gt;&lt;span style="font-size:small;"&gt;-----------------------------------------------------------------------------------------------------------------------------------------------&lt;/span&gt;&lt;br /&gt;&lt;span style="font-size:small;"&gt;t=cj_rx_rs_I[i]*cj_rx_rs_I[i];&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1631&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 676&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 664&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1222&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1031&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1052&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1620&lt;/span&gt;&lt;br /&gt;&lt;span style="font-size:small;"&gt;t=powf(cj_rx_rs_I[i],2.0);&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1600&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1608&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1652&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1477&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1596&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1031&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1570&lt;/span&gt;&lt;br /&gt;&lt;span style="font-size:small;"&gt;t=powsp(cj_rx_rs_I[i],2.0);&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1799&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1964&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1615&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1482&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1439&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 673&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1125&lt;/span&gt;&lt;br /&gt;&lt;span style="font-size:small;"&gt;t=1/cj_rx_rs_I[i];&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;1419&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1635&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2119&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1746&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1800&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2034&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1571&lt;/span&gt;&lt;br /&gt;&lt;span style="font-size:small;"&gt;t=recipsp(cj_rx_rs_I[i]);&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1517&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1134&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1626&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1210&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1418&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1233&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1612&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size:small;"&gt;3. Why do c62x64xFastRTS lib and c67xFastRTS have different routines? Can c62x64xFastRTS lib be used in C6748? I want to use the &amp;quot;mpysp&amp;quot; routine to achieve a faster execution speed.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>DSP evaluation board for audio amplitude modulation with 40kHz carrier?</title><link>http://e2e.ti.com/thread/266913.aspx</link><pubDate>Thu, 23 May 2013 15:31:36 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:dcb174e3-944c-4832-acd2-b95edb568e2d</guid><dc:creator>Christoph Friebel</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/266913.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266913/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;i hope this is the right forum, this is my first post here...&lt;/p&gt;
&lt;p&gt;I&amp;#39;m a student and need some advice in choosing the right and affordable dsp evaluation board.&lt;/p&gt;
&lt;p&gt;For a project i need to do some real time amplitude modulation with an audio signal (music) and a 40-45 kHz carrier.&lt;/p&gt;
&lt;p&gt;This signal needs to be amplified afterwards to be send on a ultrasonic transmitter grid.&lt;/p&gt;
&lt;p&gt;Now i&amp;#39;m afraid to choose the wrong evaluation board and the audio outputs and DACs can&amp;#39;t handle the 45 kHz...&lt;/p&gt;
&lt;p&gt;Is the LCDK L138 Evaluation board suitable or do you know an other affordable evaluation board that can manage this?&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;d be very grateful for any help or advice.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Thank you in advance&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Christoph&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>OMAP L138 LCDK New CCS user</title><link>http://e2e.ti.com/thread/267049.aspx</link><pubDate>Fri, 24 May 2013 04:15:35 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:bfc92d1c-4c36-4724-9b58-5ca71b923b85</guid><dc:creator>Dave Szuter</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/267049.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/267049/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I got my LCDK and XDS100v2 yesterday and successfully booted it up.&amp;nbsp; Today I downloaded the offline version of CCS 5.4 (monster zip file) for Windows.&amp;nbsp; When it asked which&amp;nbsp;components I wanted installed I chose OMAP and XDS100 only.&amp;nbsp; I figured OPAP would cover the L138 but apparently it does not.&amp;nbsp; When I fired it up it had examples for OMAP 3 and 4, but not 1 series.&amp;nbsp; I probably should have installed C6000 or maybe&amp;nbsp;C6000 Arm + dsp, but I didn&amp;#39;t.&amp;nbsp; So now what do I do? I still have the large install folder.&amp;nbsp; I would like to install examples for both cores of the L138, as well as SYSBIOS tools, EZFlo, and others, (pretty much all things related&amp;nbsp;to OMAP L138 LCDK)&amp;nbsp;but not sure how.&amp;nbsp; Please advise.&amp;nbsp; I really wish there were better instructions for us new folks.&amp;nbsp; I have litterally spent weeks sorting though the thousands of&amp;nbsp;docs and wikis you guys&amp;nbsp;have, and I still can&amp;#39;t find a simple&amp;nbsp;set of instructions to get CSS set up for my particular platform.&amp;nbsp; Please help.&amp;nbsp; Thanks in advance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>OMAP-L138 DSP+Arm9 Dev Kit (LCDK):  Beginner question</title><link>http://e2e.ti.com/thread/266653.aspx</link><pubDate>Wed, 22 May 2013 18:41:24 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:414007eb-b28b-4f45-9e8d-d2f8011ded8a</guid><dc:creator>francois duchesneau</dc:creator><slash:comments>1</slash:comments><comments>http://e2e.ti.com/thread/266653.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266653/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;We recently purchased the&amp;nbsp; &lt;a rel="nofollow" title="OMAP-L138 DSP+Arm9 Dev Kit (LCDK)" href="http://www.ti.com/tool/tmdxlcdk138"&gt;OMAP-L138 DSP+Arm9 Dev Kit (LCDK)&lt;/a&gt;&amp;nbsp; with a XDS100v2 Jtag emulator.&amp;nbsp; Our goal for now is to only use the C6748 DSP processor.&amp;nbsp; We&amp;#39;ve able to run several examples projecst from the StarterWare ( &lt;em&gt;pdk_C6748_2_0_0_0\C6748_StarterWare_1_20_03_03&lt;/em&gt; ) without too much problems.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Unfortunately, we came up some issues&amp;nbsp; while debugging (running) the code in CCS.&amp;nbsp; For example, we tested the McASP demo (&lt;em&gt;pdk_C6748_2_0_0_0\C6748_StarterWare_1_20_03_03\build\c674x\cgt_ccs\c6748\lcdkC6748\mcasp&lt;/em&gt;)&amp;nbsp; and the first time we debug/run it, it works fine.&amp;nbsp; The issue come&amp;nbsp; when we terminate the debugging and restart the debugging. Generally, the application stop working correctly (even if the same code is executed).&amp;nbsp; We have to manually reset&amp;nbsp; the dev board before doing the debug to get it working again. Is it a normal behavior or a manipulation from our part?&lt;/p&gt;
&lt;p&gt;Also, from time to time, while debuging, the device get held in reset and we have to remove the power to get it out of this state.&amp;nbsp; What kind of manipulations can cause that?&lt;/p&gt;
&lt;p&gt;We&amp;#39;re using the OMAP-L138_LCDK.gel file (ti/ccsv5/ccs_base/emulation/board/lcdkomapl138/gel/OMAP-L138_LCDK.gel) with CCS v5.3.&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;Francois&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>SPI Interface error Message(OMAP-L137)</title><link>http://e2e.ti.com/thread/266729.aspx</link><pubDate>Thu, 23 May 2013 02:10:50 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:6ebd2e6c-af88-44e4-8f32-eed08f36995b</guid><dc:creator>JG Kim</dc:creator><slash:comments>5</slash:comments><comments>http://e2e.ti.com/thread/266729.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266729/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi, I use L137.&lt;/p&gt;
&lt;p&gt;I want spi interface.&lt;/p&gt;
&lt;p&gt;I success /dev/spidev0.0&lt;/p&gt;
&lt;p&gt;spi.c &lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; [0]={&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .modalias = &amp;quot;spidev&amp;quot;,&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .mode = SPI_MODE_0,&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .max_speed_hz = 6500000,&amp;nbsp;&amp;nbsp; &amp;nbsp;/* max sample rate at 3V */&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .bus_num=1,&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .chip_select=0,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;/p&gt;
&lt;p&gt;&lt;span id="result_box" class="short_text" lang="en"&gt;&lt;span class="hps"&gt;When you run the&lt;/span&gt; &lt;span class="hps"&gt;test&lt;/span&gt; &lt;span class="hps"&gt;program,&lt;/span&gt; &lt;span class="hps"&gt;an error occurs.&lt;/span&gt;&lt;/span&gt;(spidev_test.c)&lt;/p&gt;
&lt;p&gt;&lt;span id="result_box" class="short_text" lang="en"&gt;&lt;span class="hps"&gt;The error message&lt;/span&gt; &lt;span class="hps"&gt;is as follows&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;//=====================================&lt;/p&gt;
&lt;p&gt;Internal error: Oops: 17 [#1]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;Modules linked in:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;CPU: 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;PC is at davinci_spi_bufs_prep+0xc/0x47c&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;LR is at davinci_spi_bufs_dma+0xec/0x49c&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;pc : [&amp;lt;c0230fa4&amp;gt;]&amp;nbsp;&amp;nbsp;&amp;nbsp; lr : [&amp;lt;c023228c&amp;gt;]&amp;nbsp;&amp;nbsp;&amp;nbsp; Not tainted&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;sp : c04d5ea0&amp;nbsp; ip : c04d5eb0&amp;nbsp; fp : c04d5eac&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;r10: c04d4000&amp;nbsp; r9 : c04f3800&amp;nbsp; r8 : c34abef4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;r7 : c04f3aa0&amp;nbsp; r6 : c05f3be0&amp;nbsp; r5 : c03336a8&amp;nbsp; r4 : 00000000&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;r3 : 00000008&amp;nbsp; r2 : 00000000&amp;nbsp; r1 : c04f3aa0&amp;nbsp; r0 : c04f3800&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;Flags: nZCv&amp;nbsp; IRQs on&amp;nbsp; FIQs on&amp;nbsp; Mode SVC_32&amp;nbsp; Segment kernel&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;Control: 5317F&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;Table: C34A4000&amp;nbsp; DAC: 00000017&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;Process dm_spi.1 (pid: 178, stack limit = 0xc04d4258)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;Stack: (0xc04d5ea0 to 0xc04d6000)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;5ea0: c04d5efc c04d5eb0 c023228c c0230fa8 c04d4000 00000000 c04f3800 00000001&amp;nbsp; &amp;nbsp;&lt;br /&gt;5ec0: 00000001 c04d5ed0 c0049d70 01e12000 c04d5efc c34abef4 00000000 c34abec8&amp;nbsp; &amp;nbsp;&lt;br /&gt;5ee0: 00000000 c04f3aa0 c04f3800 c04d4000 c04d5f34 c04d5f00 c0230b5c c02321b0&amp;nbsp; &amp;nbsp;&lt;br /&gt;5f00: c04f3ad4 00000000 c04d5f54 80000013 c05732a0 c04d4000 c04f3aa4 00000000&amp;nbsp; &amp;nbsp;&lt;br /&gt;5f20: c02309d8 c04f3aa0 c04d5f6c c04d5f38 c00615b4 c02309e8 c05732b8 c05732a8&amp;nbsp; &amp;nbsp;&lt;br /&gt;5f40: 00000002 00000000 c05732a8 c04d4000 c05732a0 c05732b0 00000002 c04d5f84&amp;nbsp; &amp;nbsp;&lt;br /&gt;5f60: c04d5fcc c04d5f70 c0061dbc c00614e4 00000001 00000000 00000000 00010000&amp;nbsp; &amp;nbsp;&lt;br /&gt;5f80: 00000000 00000000 c05d4600 c00499b4 00100100 00200200 ffffffff ffffffff&amp;nbsp; &amp;nbsp;&lt;br /&gt;5fa0: 00000000 c05732a0 c04d4000 c0061cb4 c0471dd8 00000000 00000000 00000000&amp;nbsp; &amp;nbsp;&lt;br /&gt;5fc0: c04d5ff4 c04d5fd0 c0064da4 c0061cc4 ffffffff ffffffff 00000000 00000000&amp;nbsp; &amp;nbsp;&lt;br /&gt;5fe0: 00000000 00000000 00000000 c04d5ff8 c005172c c0064ccc 61747320 25206574&amp;nbsp; &amp;nbsp;&lt;br /&gt;Backtrace:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;[&amp;lt;c0230f98&amp;gt;] (davinci_spi_bufs_prep+0x0/0x47c) from [&amp;lt;c023228c&amp;gt;] (davinci_spi_b)&lt;br /&gt;[&amp;lt;c02321a0&amp;gt;] (davinci_spi_bufs_dma+0x0/0x49c) from [&amp;lt;c0230b5c&amp;gt;] (bitbang_work+0)&lt;br /&gt;[&amp;lt;c02309d8&amp;gt;] (bitbang_work+0x0/0x2d8) from [&amp;lt;c00615b4&amp;gt;] (run_workqueue+0xe0/0x1)&lt;br /&gt;[&amp;lt;c00614d4&amp;gt;] (run_workqueue+0x0/0x170) from [&amp;lt;c0061dbc&amp;gt;] (worker_thread+0x108/0)&lt;br /&gt;[&amp;lt;c0061cb4&amp;gt;] (worker_thread+0x0/0x144) from [&amp;lt;c0064da4&amp;gt;] (kthread+0xe8/0x128)&amp;nbsp; &amp;nbsp;&lt;br /&gt;[&amp;lt;c0064cbc&amp;gt;] (kthread+0x0/0x128) from [&amp;lt;c005172c&amp;gt;] (do_exit+0x0/0xa24)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;&amp;nbsp;r7 = 00000000&amp;nbsp; r6 = 00000000&amp;nbsp; r5 = 00000000&amp;nbsp; r4 = 00000000&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br /&gt;Code: e89da800 e1a0c00d e92dd800 e24cb004 (e5923010)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;/=====================================&lt;/p&gt;
&lt;p&gt;Help plz.&lt;/p&gt;
&lt;p&gt;regard,&lt;/p&gt;
&lt;p&gt;JG KIM&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Omap L138 synchronization of 64 bit values ( e.g. double ) between ARM and C6000 DSP</title><link>http://e2e.ti.com/thread/255786.aspx</link><pubDate>Tue, 02 Apr 2013 08:03:01 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5afdfbd4-d753-4997-9d6d-cde902b1f344</guid><dc:creator>Rob van de Voort</dc:creator><slash:comments>12</slash:comments><comments>http://e2e.ti.com/thread/255786.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/255786/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I was wondering if the access to 64 bit values between ARM and C6000 can be synchronized so the access &lt;br /&gt;looks atomic for ARM and C6000, do examples of this exist somewhere?&lt;br /&gt;&lt;br /&gt;I was thinking of creating a function or macro to explicitly mark this synchronization but was searching for instructions or means&lt;br /&gt;of synchronization that are present in the OMAP L138 to ease this process. &lt;br /&gt;The C6000 supports instructions to load/store a double word [LDDW/STDW],&lt;br /&gt;The ARM core supports GCC atomic builtins&amp;nbsp;&lt;a href="http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Atomic-Builtins.html"&gt;http://gcc.gnu.org/onlinedocs/gcc-4.2.0/gcc/Atomic-Builtins.html&lt;br /&gt;&lt;/a&gt;The GCC builtins ( gcc 4.4+ )generate &amp;nbsp;ARM instructions ( which can be regarded as atomic ) but do not take into account the C6000 i presume.&lt;br /&gt;We are compiling code for Arm Linux EABI so this synchronization may be handled in our driver for the C6000 application.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Questions:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;1. Do any&amp;nbsp;helpful&amp;nbsp;instructions exist to synchronize the C6000 and ARM when accessing 64 bit values,&lt;br /&gt;&amp;nbsp; &amp;nbsp; or does this require a custom implementation?&lt;br /&gt;2. Any suggestions on how to implement 64 bit synchronization between ARM and C6000 ( do examples exist? )&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Rob&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>AISgen binary serial flash format for OMAPL138</title><link>http://e2e.ti.com/thread/266618.aspx</link><pubDate>Wed, 22 May 2013 16:11:47 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:43d2f505-74eb-4311-b7d7-e0f0c7b3fd06</guid><dc:creator>Kevin Halloran</dc:creator><slash:comments>3</slash:comments><comments>http://e2e.ti.com/thread/266618.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266618/rss.aspx</wfw:commentRss><description>&lt;p&gt;We are able to program a LogicPD OMAPL138 SOM with no problem using AISgen &amp;amp; sfh_OMAP-L138.exe using a serial port on the EVM.&amp;nbsp; That is fine initially but now we need to program the serial boot flash in the field for upgrades.&amp;nbsp; We already have drivers for the serial flash but the question is the .bin file that is output by AISgen is this just the binary image to feed the serial boot flash starting at address 0?&amp;nbsp; I ran AISgen with output to a .h file which creates an integer array and it looks that way but just want to confirm.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kev&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>dynamic control of PINMUX registers between Hi-Z and any valid pin function</title><link>http://e2e.ti.com/thread/267042.aspx</link><pubDate>Fri, 24 May 2013 02:57:02 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:5f469a8b-0f59-4788-a770-6245e01300c0</guid><dc:creator>Naoki kawada</dc:creator><slash:comments>0</slash:comments><comments>http://e2e.ti.com/thread/267042.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/267042/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I have a question about the dynamic control of PINMUX registers between Hi-Z and any valid pin function on C674x platform.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;One of my customers wants to use some GPIOs as an output or Hi-Z, and they switch the pin feature dynamically in there system.&lt;br /&gt;Please note, during Hi-Z pin condition,&amp;nbsp;1.485V～1.815V can be served to GPIO pin.&lt;/p&gt;
&lt;p&gt;So, I suggested them to control PINMUX registers dynamically when the pins are required to be Hi-Z.&lt;br /&gt;&lt;span&gt;&lt;br /&gt;But now I&amp;#39;m wondering if this could be really allowed in the device HW point of view...&lt;br /&gt;&lt;/span&gt;Could you please let me know if this can be TI&amp;#39;s recommended solution to realize the customer&amp;#39;s requirement ?&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;br /&gt;Kawada&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>DSP won't wake ARM after power on reset</title><link>http://e2e.ti.com/thread/266682.aspx</link><pubDate>Wed, 22 May 2013 20:13:33 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7a4af561-77b9-46ea-a32a-05534dfd3b7b</guid><dc:creator>Rob Tice1</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/266682.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266682/rss.aspx</wfw:commentRss><description>&lt;p&gt;I am using a custom board based around an OMAP-L138. I have a pull down resistor on TRST and a pull up on RESETn. When the board powers on, it does a power on reset and latches the boot pins (I can confirm this by connecting with my JTAG and looking at the SYSCFG0 register). The DSP then comes out of RESET. I would then expect it to wake the ARM core and follow the steps laid out in this wiki:&lt;/p&gt;
&lt;p&gt;http://processors.wiki.ti.com/index.php/OMAP-L138_Bootloader#After_Reset&lt;/p&gt;
&lt;p&gt;However, after I power on, I connect to the DSP and use the debug GEL script and I notice that the DSP did not wake up the ARM. When I manually wake the ARM from a GEL file I can view its registers. If I run any GEL scripts on the ARM core, the ARM seems to go into reset again and I get 0x0BAD0BAD in all of the memory locations. After this, if I run the debug GEL on the DSP core, it says the ARM is powered on. If I try to reconnect to the ARM core after this, CCS crashes and restarts my computer for me (how nice of it...). My suspicion is that the DSP bootloader is bad, or the ARM is being woken up on power up but is going into RESET for some reason. Has anyone seen similar behavior before?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Rob&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>How do I get a new file into the Audio_SOC_Example make?</title><link>http://e2e.ti.com/thread/266679.aspx</link><pubDate>Wed, 22 May 2013 19:59:24 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:2db0ce51-c85f-4fb6-a9ae-18643bfa3cbc</guid><dc:creator>Tom Izard</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/266679.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266679/rss.aspx</wfw:commentRss><description>&lt;p&gt;I have the Audio_SOC_Example up and running (CCS V5.1, Ubuntu 10.4, OMAPL138). I want to add code to the build but when I add a file in the project explorer (I right clicked on the project, selected add files, copy) it appears in the explorer but does not get added to the make, so any references fail during the link.&amp;nbsp; What am I missing?&amp;nbsp; Note: If I click on the added file itself and try to build just the file, CCS complains that there is no rule to make it.&amp;nbsp; But this is true of the existing files too.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Tom&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Is a bug of the EDMA3 in omap-138 ?  help :)</title><link>http://e2e.ti.com/thread/266586.aspx</link><pubDate>Wed, 22 May 2013 14:58:09 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:7f1e918f-af76-4bcb-83b9-a28c0528f880</guid><dc:creator>liang xu</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/266586.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266586/rss.aspx</wfw:commentRss><description>&lt;p&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;I&amp;#39;m &amp;nbsp;learning &amp;nbsp;how to&amp;nbsp;move data by EDMA3 of&amp;nbsp;omap-138 DSP, then I find a problem about the&amp;nbsp;Edma3 completed interrupt:&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;span&gt;Usually，after&amp;nbsp;edma3 completes, the bit correponding to TCC will appear&amp;nbsp;in reg &amp;ldquo;IPR&amp;rdquo;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;However a problem&amp;nbsp;appears &amp;nbsp;:&amp;nbsp;&amp;nbsp;when using&amp;nbsp;omap-138, if the tcc number is same to the channel ID, the transfer and the completed interrupt is OK;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;If the tcc number is different to the channel ID, &amp;nbsp;the tranfer is succes, but the completed interrupt is abnormal: DSP can&amp;#39;t run to ISR of edma3, and the value of IPR &amp;nbsp;is always 0.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;Is there some Bug in&amp;nbsp;edma3 of&amp;nbsp;omap-138? Thanks very much:)&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>A/D converter to be used with SD Card implementation on OMAP-L138 EVM</title><link>http://e2e.ti.com/thread/265453.aspx</link><pubDate>Thu, 16 May 2013 15:48:02 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:1d605bc3-3c50-405b-8aa0-e95520f516fc</guid><dc:creator>Tariq Siddiqui</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/265453.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/265453/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi Tariq,&lt;/p&gt;
&lt;p&gt;I am using OMAP-L138 EVM and looking for ADC that operates over 10 MSPS. It is desirable that given ADC would work with SD card implementation.&amp;nbsp;&lt;span style="font-size:12px;"&gt;I am building a data acquisition system which gathers large amount of real-time data to SD card. I know there has been huge multiplexing to OMAP-L138 which doesn&amp;#39;t allow many peripheral to be used at the same time.&amp;nbsp;Please advise which ADC would be compatible with OMAPL138 and does allow SD card implementation.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I would really appreciate your help.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;-Tariq&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>How to do PARAM link in EDMA3 using EDMA3LDD [dsp6738]</title><link>http://e2e.ti.com/thread/264162.aspx</link><pubDate>Fri, 10 May 2013 12:55:21 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:b56cb12d-d63b-49ca-a69a-79d20249b512</guid><dc:creator>Ashish Mishra1</dc:creator><slash:comments>6</slash:comments><comments>http://e2e.ti.com/thread/264162.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/264162/rss.aspx</wfw:commentRss><description>&lt;p&gt;Can any one please guide me gow to put the PARAM is self link mode in dsp 6738.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Using Linux , i had use function &amp;quot;edma_link(write_dma_chan,write_dma_chan);&amp;quot;.&lt;/p&gt;
&lt;p&gt;But i am not sure how to do the same in DSP code .&lt;/p&gt;
&lt;p&gt;EDMA3CCPaRAMEntry write_paramSet ;&lt;/p&gt;
&lt;p&gt;unsigned int retval = 0u; &lt;br /&gt; &lt;br /&gt; // Request DMA channel and TCC &lt;br /&gt; retval = EDMA3RequestChannel(SOC_EDMA30CC_0_REGS,write_chType,write_chNum,write_tccNum,write_evtQ);&lt;br /&gt; if (TRUE == retval)&lt;br /&gt; {&lt;br /&gt; // Fill the PaRAM Set with transfer specific information &lt;br /&gt; write_paramSet.srcAddr = (unsigned int)(addr_1_buff);&lt;br /&gt; write_paramSet.destAddr = (unsigned int)(EMIF_CHIP5_BASE + (BRAM_ADDR+OFFSET));&lt;br /&gt; write_paramSet.aCnt = (unsigned short)acnt;&lt;br /&gt; write_paramSet.bCnt = (unsigned short)bcnt;&lt;br /&gt; write_paramSet.cCnt = (unsigned short)ccnt;&lt;br /&gt; write_paramSet.srcBIdx = 0; &lt;br /&gt; write_paramSet.destBIdx = 0; &lt;br /&gt; write_paramSet.srcCIdx = 0;&lt;br /&gt; write_paramSet.destCIdx = 0;&lt;br /&gt; &lt;br /&gt; write_paramSet.linkAddr = (unsigned short)0xFFFFu; &amp;nbsp; &amp;nbsp;---------------??????????????&lt;br /&gt; write_paramSet.bCntReload = 1; &lt;br /&gt; write_paramSet.opt = 0u;&lt;br /&gt; // Src &amp;amp; Dest are in INCR modes &lt;br /&gt; write_paramSet.opt &amp;amp;= 0xFFFFFFFCu;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I want the param to be in a self link so that i preserve un-necessary time being wastage in&lt;/p&gt;
&lt;p&gt;initilizing the parameters again and again ....&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank You,&lt;/p&gt;
&lt;p&gt;Ashish Mishra &amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;i tried something like this :-&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Resource Conflict error</title><link>http://e2e.ti.com/thread/265565.aspx</link><pubDate>Fri, 17 May 2013 05:07:35 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:c058b2df-f807-4339-9b54-86d43cdfd54d</guid><dc:creator>Kalaiyarasan ES</dc:creator><slash:comments>1</slash:comments><comments>http://e2e.ti.com/thread/265565.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/265565/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; I am using omapl138 for my project.&amp;nbsp; i am using Ti DVSDK v4.3.0.6. We are using Linux on ARM and DSP Bios v5.41 on DSP, dsplink came with DVSDK.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; In my DSP executable, When i place my DSP Code in L2 RAM (start at 0x11808000 ) ,I am facing a run time exception error. When CPU try to execute instruction at the address (0x11808000), DSP processor results in UTL_Halt. I have given screen shot of error below.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/42/4807.Utl_5F00_Hlt_5F00_DSPApp.png"&gt;&lt;img src="http://e2e.ti.com/resized-image.ashx/__size/550x1365/__key/communityserver-discussions-components-files/42/4807.Utl_5F00_Hlt_5F00_DSPApp.png" alt=" " border="0" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Please let me know why i am getting this error. How to overcome this error.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks &amp;amp; regards,&lt;/p&gt;
&lt;p&gt;KALAIYARASAN S&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>ROM Status Code: 0x000000BF</title><link>http://e2e.ti.com/thread/266395.aspx</link><pubDate>Tue, 21 May 2013 21:20:57 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:3094928d-eca0-44f5-a9c2-7491c3ed64e2</guid><dc:creator>Rob Tice1</dc:creator><slash:comments>3</slash:comments><comments>http://e2e.ti.com/thread/266395.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266395/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hello All,&lt;/p&gt;
&lt;p&gt;I am bringing up a custom board based on a OMAP-L138 and am having a few issues connecting via JTAG. I have the unit in Emulation Debug boot mode and have verified this via SYSCFG0 register. When I connect to the ARM it says the processor is Running. When I try to run a GEL file or pause the ARM processor I get the error:&lt;/p&gt;
&lt;p&gt;&lt;span style="background-color:#ffffff;color:#ff0000;"&gt;ARM9_0: Trouble Halting Target CPU: Error 0x00000020/-2011 Error during: Execution, &amp;nbsp;An internal error occurred in which an illegal action (0x00000000) was requested while disconnected.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color:#000000;"&gt;I can successfully connect to the DSP core and run certain parts of GEL files. If I try to change the PLL frequencies I get the error:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="color:#ff0000;"&gt;Trouble Reading Memory Block at 0xb0000008 on Page 0 of Length 0x4:&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;Error 0x00000002/-1202&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;Error during: Memory,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;If I select yes and force the processor to stop accessing shared RAM I get the next error:&lt;/p&gt;
&lt;p&gt;Trouble Reading Memory Block at 0x1840020 on Page 0 of Length 0x4:&lt;br /&gt;Error 0x00000002/-1060&lt;/p&gt;
&lt;p&gt;And then I have to disconnect from the JTAG and restart my computer to reconnect again. When I run a diagnostics test on the C674X I get the following:&lt;/p&gt;
&lt;p&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: ---------------------------------------------&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: | BOOTROM Info |&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: ---------------------------------------------&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: ROM ID: d800k176-47-48 &lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: Silicon Revision UNKNOWN&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: Boot pins: 30&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: Boot Mode: Emulation Debug&lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;C674X_0: GEL Output: &lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;ROM Status Code: 0x000000BF &lt;/span&gt;&lt;br /&gt;&lt;span style="color:#ff0000;"&gt;Description:C674X_0: GEL Output: Error code not recognized&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;and then the rest of the register status&amp;#39;s are printed. &lt;span style="color:#000000;"&gt;I assume there&amp;#39;s an issue relating to the UNKNOWN Silicon Revision and the ROM Status code not recognized errors. &amp;nbsp;I would also assume, since I am in JTAG boot mode, that the ARM should not be running and should be sitting in Idle. Any help would be greatly appreciated.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Rob&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>OMAP-L138 UPP port - receiver and transmitter.</title><link>http://e2e.ti.com/thread/266358.aspx</link><pubDate>Tue, 21 May 2013 18:12:20 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:06420a72-3017-4c14-8fdc-4d0d2919a225</guid><dc:creator>WENBO LI</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/266358.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266358/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I would like to use UPP port of OMAP L138 to receive the data from an ADC device. The UPP transmitter&amp;nbsp;won&amp;#39;t be used. In this case, I have following questions:&lt;/p&gt;
&lt;p&gt;1). While I am using the UPP receiver pins, shall I still be able to use the UPP transmitter pins for GPIO purpose?&lt;/p&gt;
&lt;p&gt;2).&amp;nbsp;Because I only use the UPP receiver,&amp;nbsp;I do not&amp;nbsp;need to feed a clock to the UPP_2xTXCLK. Correct?&amp;nbsp;&amp;nbsp;Can I use the UPP_2xTXCLK pin as an GPIO?&lt;/p&gt;
&lt;p&gt;3). In order to use the UPP to receive a 16-bit wide data from ADC, I think I must use Channel A (not Channel B) to receive the 16-bit parallel data in format D[0...15]. Correct?&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Wenbo&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>How to Debug DSP core for OMAP-L138</title><link>http://e2e.ti.com/thread/266423.aspx</link><pubDate>Wed, 22 May 2013 02:23:41 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:cd5e4c39-d375-4b84-ac73-7dcd10e51070</guid><dc:creator>Keldy</dc:creator><slash:comments>1</slash:comments><comments>http://e2e.ti.com/thread/266423.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266423/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m using omap-l138 (arm +dsp), i using CCSV4 to write and compile my DSP code while i&amp;#39;m using wind river (VxWork) to compile ARM code.&lt;/p&gt;
&lt;p&gt;after i compile my DSP in CCSV4, i&amp;#39;ll copy DSP image to VxWork folder to compile, VxWork will load the DSP image after booting up ARM.&lt;/p&gt;
&lt;p&gt;Since i using two different IDE, how i debug DSP code using JTAG?&lt;/p&gt;
&lt;p&gt;Or is there anywhere to use printf() inside DSP code to output something to UART terminal ?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Keldy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>EDMA3 Channel Controller 0 UART2 Transmit</title><link>http://e2e.ti.com/thread/261833.aspx</link><pubDate>Mon, 29 Apr 2013 14:37:05 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:4e651619-1683-4711-8861-5582f860b1c1</guid><dc:creator>Chris Davis1</dc:creator><slash:comments>1</slash:comments><comments>http://e2e.ti.com/thread/261833.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/261833/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Per: &lt;a href="http://www.ti.com/lit/ds/symlink/omap-l138.pdf"&gt;http://www.ti.com/lit/ds/symlink/omap-l138.pdf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Table 5-14, page 108.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m trying to run UART2 in DMA mode but there is no event # for UART2 Transmit.&amp;nbsp;&amp;nbsp;Is it possible to set UART2 into DMA mode?&amp;nbsp; Is the blank event 31 UART2 Transmit?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Chris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>davinci arago recipe query</title><link>http://e2e.ti.com/thread/264350.aspx</link><pubDate>Sun, 12 May 2013 17:09:07 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:df9f8842-c5f0-4f41-aa15-bda23437d6d0</guid><dc:creator>Manish Vishwanathrao Badarkhe</dc:creator><slash:comments>2</slash:comments><comments>http://e2e.ti.com/thread/264350.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/264350/rss.aspx</wfw:commentRss><description>&lt;p&gt;&lt;a href="http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/264350.aspx"&gt;(Please visit the site to view this file)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hi All&lt;/p&gt;
&lt;p&gt;I am facing issue while building arago recipe for da830-omapl137-evm.&lt;/p&gt;
&lt;p&gt;I have u-boot and kernel bb file for da830-omapl137-evm. Following below steps in order to build setup for da830-evm.&lt;/p&gt;
&lt;p&gt;Case 1.&lt;/p&gt;
&lt;p&gt;Build steps:&lt;/p&gt;
&lt;p&gt;a. Followed a link http://www.arago-project.org/wiki/index.php/Setting_Up_Build_Environment in order to make arago recipe setup&lt;/p&gt;
&lt;p&gt;b. Use command MACHINE=da830-omapl137-evm bitbake -b arago/recipes/linux/linux-davinci_3.3.0-psp03.22.00.02.bb &lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; to build a recipe for linux.&lt;/p&gt;
&lt;p&gt;Result:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp; Build get stops while cloning source code for linux kernel but if I do explicit cloning its working fine.&lt;/p&gt;
&lt;p&gt;Case 2:&lt;/p&gt;
&lt;p&gt;Build steps:&lt;/p&gt;
&lt;p&gt;a. Followed a link http://www.arago-project.org/wiki/index.php/Setting_Up_Build_Environment in order to make arago recipe setup&lt;/p&gt;
&lt;p&gt;b. Use command:MACHINE=da830-omapl137-evm bitbake virtual/kernel to build a recipe for linux&lt;/p&gt;
&lt;p&gt;Results:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Build takes wrong bb file for compilation and hence unable to create proper images for linux.&lt;/p&gt;
&lt;p&gt;Please let me know whether Case 1 or Case 2 is proper to build kernel using arago recipe. If Case 1 is proper then how I can make clone to work fine?&lt;/p&gt;
&lt;p&gt;If case 2 is proper then what change is required to pick proper bb file?&lt;/p&gt;
&lt;p&gt;Please see attached .tar for bb files.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Manish Badarkhe&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>C6748 LCDK kit</title><link>http://e2e.ti.com/thread/266371.aspx</link><pubDate>Tue, 21 May 2013 18:55:03 GMT</pubDate><guid isPermaLink="false">cb01d8b2-d089-468d-babb-77d1d8683490:ece7a50f-3263-4ac7-807e-fd297d6ac8d6</guid><dc:creator>Madhu Vatte</dc:creator><slash:comments>1</slash:comments><comments>http://e2e.ti.com/thread/266371.aspx</comments><wfw:commentRss>http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/266371/rss.aspx</wfw:commentRss><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;We have the C6748 (LCDK) kit and was going to start playing with that.&amp;nbsp; The problem we are running into is access to all the GPIOs that we need to use.&amp;nbsp; If there is a version of DSP evaluation kit in a similar family that gave us easy access to the GPIOs and other peripherals (PWMs, SPI buses, etc.) it would be much more conducive for our development. &amp;nbsp;We did not find any other kits on TI website. &amp;nbsp;Are there any third party companies which have the kits based on C6748 with more GPIO access?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Madhu&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>