BIOS

Browse by Tags

BIOS

Welcome to the BIOS Section of the TI E2E Support Community. Ask questions, share knowledge, explore ideas, and help solve problems with fellow engineers. To post a question, click on the forum tab then "New Post".

Tags
You have subscribed to this tag. To view or manage your tag subscriptions, click here.   Close
You have unsubscribed from this tag. To view or manage your tag subscriptions, click here.   Close
You are currently viewing:
DSP/BIOS Link
Related Posts

  • Forum Post: access c++ objects / structs in shared memory

    Dominique Holzwarth
    hi all consider the following pseudo code snippet for a GPP side application: Uint16* DataBufPtr = 0; // there are various types of structs / classes defined: typedef struct myObj1{ int a, short b, int c; } MyObj1; typedef struct myObj2{ char x, float y[1000]; } MyObj2; ...
    on Feb 25, 2010

  • Forum Post: Problem to get CCS 3.3 dsp-app running via dsplink on OMAP-L138

    Bastian
    Hello, i have trouble on an OMAP-L138 (linux,dsplink 1_65_00_01, bios 5_33_06, ccs v3.3) system. i have an application which should be loaded into the dsp via a Linux-GPP-App using PROC_attach and PROC_start. This application is compiled on CCS 3.3 . I have a lot of trouble to get this done. ...
    on Apr 9, 2010

  • Forum Post: Re: Problem to get CCS 3.3 dsp-app running via dsplink on OMAP-L138

    Arnie Reynoso
    Loading a DSPLink DSP-side application (*.put) via emulator versus begin loaded via the ARM -side application using PROC call will cause the DSP application to hang. The DSP application requires some handshaking on the DSP-side when DSPlink is being uses. If you want to test your application on the...
    on Apr 9, 2010

  • Forum Post: Re: dsplink building issue & question CCS

    Arnie Reynoso
    I'm not sure what is the cause of the failure. In the past, other have have issue with re-building DSPlink on a Window host PC due the Cygwin (or similar type tools) on a WINPC. Remove any such tools from your system path and attempt to re-build DSPlink and its examples. Information can be found...
    on Apr 9, 2010

  • Forum Post: HWI Sem Task combination prevents CHNL communication to return from SIO_reclaim on L138

    Bastian
    Hello, we would like to run a dspbios link application on an OMAPL138 board. The application is loaded via the gpp into the dsp. We have a task derived from the loop example running a CHNL communication which works fine running it alone. We have also a task with some audio processing using HWI`s and...
    on Apr 23, 2010

  • Forum Post: overlapping sections : .printf and .DDR2$heap

    Samuel Nobs
    Hello folks When I'm linking my DSP/BIOS / DSPlink project, I see that sometimes the .printf and .DDR2$heap section are overlapping in the *.map file: tconf-generated linker script (excerpt): ... GROUP { .const: align = 0x8 {} .printf (COPY): {} } > DDR2 .args: align=4 fill=0 { *(...
    on Jun 9, 2010

  • Forum Post: DSPLINK-problem while installing SDK

    Rico Schulze
    while walking through the getting started guide i get a failure in " Step 2: Configure what platform you are building DSPLink for " of the building the OMAP SDK - guide. performing perl config/bin/dsplinkcfg.pl --platform=OMAPL1XX --nodsp=1 --dspcfg_0=OMAPL1XXGEMSHMEM --dspos_0=DSPBIOS5XX...
    on Jun 23, 2010

  • Forum Post: DSP/BIOS Link performance

    tobias4080
    Hi all, I'm using DSP/BIOS Link 1.63 on an OMAPL137. My message queue transport is shared memory, zero copy. It takes only 60 us for the DSP to send the message with MSGQ_put, but it takes almost 5 ms before the ARM receives the message with MSGQ_get. Any ideas what's taking so long...
    on Jul 1, 2010

  • Forum Post: Do I need Code Composor Studio for project developmanet?

    CalvinTai
    Dear all: I'm quite new for Ti's DSP. I use SEED-DEC137 platform, which is based on OMAP-L137. After setup Vmware, Ubuntu and tool-chain, I can successfully compile and run all DSPlink examples. The question is: I don't need debug feature, should I still need to install Code Composer Studio...
    on Sep 2, 2010

  • Forum Post: DSPBIOS/LINK question on OMAP-L137

    Dmitry K
    Hi, All I have board very similar to evmomapl137. External interfaces routed a little bit different, but i've managed to go though the initilization My board have 32MB SDRAM (instead of 64). Linux is up and running with mem=16Mb parameters. Currently my problem is that I'm unable to...
    on Sep 20, 2010

  • Forum Post: DSPBIOS Link API Referance manual?

    Brian Flinn
    Hello Is it true that the only API referance guid for DSPBIOS Link is by reading the header files from the Doxygen lists in {dsplink} / doc / index.html and then drilling down through them? Or is there a .pdf API DspBios Link API referance manual? Thanks Brian
    on Feb 14, 2011

  • Forum Post: DSPLink program(.out ) size problem( wince omap-l138 )

    arthur14426
    Hi all Our R&D environment is OMAP-L138 WINCE6.0 platform using DSPLink 1.65.00.03 . We want to know what limit in developing DSP side program, such as every section's max size,... Thanks
    on Mar 31, 2011

  • Forum Post: NOTIFY module problem

    JBakamovic
    Hi, I'm experiencing some problems while trying to send notifications to ARM Linux from DSP/BIOS task and can't get it work (step 8 in DSP/BIOS part below). My setup is OMAP3530 with DSP/BIOS 5.32 and DSP/BIOS Link 1.65.00.03. Development tool used is CCS v4. What I'm basically trying to...
    on Apr 23, 2011

  • Forum Post: Can multiple ARM applications communicate with one DSP executable on MityDSPL138?

    Wei Zhang73439
    Hi, We have the following problems and need your help. Background: We have developed one ARM application and one DSP executable with RIngIO as communication mechanism between them. ARM application loads the DSP executable. DSP-side uses one task. All of this is for one channel. Now we need to...
    on May 6, 2011

  • Forum Post: Error 'no schema file was found' when converting Tconf script to RTSC configuration script file

    Sivakumar Thulasingam
    I have BIOS configuration file (.tcf) that created on BIOS v5.x. I want to convert this to RTSC file using XDC tool, so that I can use BIOS v6 and project that uses RTSC configuration file. I have CCS 4.2.3.00004. But I got error while running xs comand that says 'no schema file was found. I have...
    on May 6, 2011

  • Forum Post: DSP MMU Fault

    rajesh peddi
    Hello, I am trying to run an application using the my codec, the application is crashing and showing the error message. @0x000b9a19:[T:0x4001ebb0] ZZ - main> Welcome to app's main(). @0x000ba4b5:[T:0x4001ebb0] ZZ - App-> Application started. in the function parse command line arguments...
    on May 10, 2011

  • Forum Post: Using CCS to create CLK project from DSP-BIOS 5.41 examples directory. Compiler generates errors in clk.tcf file.

    William Macre73633
    Configuration: CCS V4.2.2 Target OMAP 3530 C64+ DSP-BIOS 5.41.07.24 JTAG-560-USB->20Pin Both the clk.c and the mutex.c example programs fail to compile with the same error message: -----------------------------------------------------------------------------------------...
    on May 12, 2011

  • Forum Post: A DSP/BIOS based McASP driver question?

    Tianhua Chu
    Can somebody answer this: As introduced by "BIOSPSP_McASP_Driver_Design", after calling Mcasp_Open() with DMA driven or not, can I call Mcasp_Submit() to send data stream right away, or I should call Mcasp_Control() with Mcasp_IOCTL_START_PORT to start the state machine first? And...
    on Jun 15, 2011

  • Forum Post: Building DSPLink 1.65.00.03

    Harsh Gupta
    Hi everyone, I’m currently working on the BeagleBoard xM Rev B. I’ve booted up the board successfully with a demo Angstrom image (bootloaders + kernel image + filesystem) which I downloaded from : http://www.angstrom-distribution.org/demo/beagleboard . I now want to install...
    on Jun 21, 2011

  • Forum Post: Problem linking with a static lib under CCSv5 with SC-MCSDK for C66xx target

    Tony Hanratty
    I have two CCSv5 projects. One builds to an executable and runs OK on the target hardware (TMDXSCBP6618X), the other builds to a RTSC static library and compiles OK with no errors. However, if I reference a function in the static lib from the executable project, and make the static lib project a dependency...
    on Jul 21, 2011

  • Forum Post: Use of Zero Copy Link Driver with DSP/BIOS Link

    James Sierp
    Hi TI, First a bit of background, I am supporting a product that was developed using the OMAP5912 OSK as a reference design, and using the 2.4 series Linux kernel provided in the Montavista starter kit. The code compilation is done on a Linux host machine, not using CCS. I have ported DSP/BIOS...
    on Sep 26, 2011

  • Forum Post: Intermittent McASP failure Issue

    Steven Kenny
    Hi Anyone, I've been struggling with an intermittent issue and hoping someone might have some suggestions or seen something like this before. The setup: DSPBIOS: v5.33.03 DSPLINK: v1.64 DM648 BIOSPSP: v1.10.03 EDMA3_LLD: v1.05.00 XDC: v3.10.03 CG6X: v6.1.08 GPP is an Atom running Linux...
    on Oct 31, 2011

  • Forum Post: DSP/BIOS 5 vs SYS/BIOS 6 and DSPLink version suggestions?

    Judson Wilson
    I have played around with both versions a little bit, and have read various docs and wikis. SYS/BIOS 6 appears to be very feature rich, however when I look at the code size benchmarks it appears that the code size bloat has been on an exponential path for every subrevision. This worries me because...
    on Nov 21, 2011

  • Forum Post: OMAP3530EVM DSPLINK FFT/IFFT Problem

    Elias Kokkinis
    Hello, I am using the OMAP3530EVM by Mistral and I am familiarizing myself with DSPLINK and DSPLIB. I have used the readwrite example and have modified it to get an input buffer from analog input pass it on to the DSP, fetch back unaltered and put it on the analog audio output. The ARM processor...
    on Dec 2, 2011

  • Forum Post: Making sense of the DSPLink Memory map

    Louis Dupont
    I'm about to change the DSPLink's (v. 1.65.00.03) memory map but I'm trying to make sense of the default memory map first. The default memory map is based on the OMAP L137 evaluation platform on which 64MB of SDRAM are available. Out of these 64MB the first 32MB (0xC0000000-0xC2FFFFFF) are...
    on Dec 4, 2011
12

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use