• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Embedded Software » BIOS » BIOS forum » build_p674.h Not Getting Populated
Share
BIOS
  • Forum
  • Announcements
Options
  • Subscribe via RSS

build_p674.h Not Getting Populated

build_p674.h Not Getting Populated

This question is answered
Mark Skidmore
Posted by Mark Skidmore
on Jun 19 2012 19:24 PM
Intellectual720 points

I'm migrating from DSP/BIOS to SYS/BIOS (CCSv5.2.2, BIOS 6.33.05.46, XDC Tools  3.23.03.53)  and my ProjectHome\Debug\configPkg\package\cfg\build_p674.h file is not getting populated correctly. Below are its contents:

/*
 *  Do not modify this file; it is automatically
 *  generated and any modifications will be overwritten.
 *
 * @(#) xdc-y25
 */

#include <xdc/std.h>

extern int xdc_runtime_Startup__RESETFXN__C;

extern int xdc_runtime_Startup_reset__I;

extern int xdc_runtime_Startup__EXECFXN__C;

extern int xdc_runtime_Startup_exec__E;

As a result, I'm getting many errors of the nature:

Description    Resource    Path    Location    Type
#20 identifier "AlarmEventTaskFreeQueue" is undefined    UmmRuntimeModule.cpp    /Vibration Monitor    line 130    C/C++ Problem

I have these (relevant lines) in my cfg file:

bios.SEM.create("AlarmEventTaskPoolSemaphore");
bios.SEM.instance("AlarmEventTaskPoolSemaphore").comment = "Alarm Event Task Pool";

Why is the build_p674.h () file not getting populated?

Although I was working on this problem previously (http://e2e.ti.com/support/embedded/bios/f/355/t/193719.aspx) and am getting the same problem, I have completely restarted this project from scratch.This project includes the generated RTSC platform package (from the migration tool) whereas the previous project did not.

Latest cfg file is attached (8585.VibrationMonitor.cfg).

Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Scott Gary
    Posted by Scott Gary
    on Jun 20 2012 17:15 PM
    Verified Answer
    Verified by David Friedland
    Genius10040 points

    Mark,

    In your attached 8585.VibrationMonitor.cfg file these two lines are commented out:

    //bios.SEM.create("AlarmEventTaskPoolSemaphore");
    //bios.SEM.instance("AlarmEventTaskPoolSemaphore").comment = "Alarm Event Task Pool";

    I’m wondering why, and if maybe this is causing an earlier error that is resulting in the short .h file.  Is this possible, or is the attached .cfg not your latest?

    Scott

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Mark Skidmore
    Posted by Mark Skidmore
    on Jun 20 2012 17:46 PM
    Intellectual720 points

    I commented them out because I tried using the XGCONF tool to add the same semaphore:

    var AlarmEventTaskPoolSemaphoreParams = new Semaphore.Params();
    AlarmEventTaskPoolSemaphoreParams.instance.name = "AlarmEventTaskPoolSemaphore";
    Program.global.AlarmEventTaskPoolSemaphore = Semaphore.create(null, AlarmEventTaskPoolSemaphoreParams);

    Whether I use

    bios.SEM.create("AlarmEventTaskPoolSemaphore");
    bios.SEM.instance("AlarmEventTaskPoolSemaphore").comment = "Alarm Event Task Pool";

    or the XGCONF tool as shown above (and comment out accordingly), my build_p674.h (1108.build_p674.h) is not getting populated.

    My cfg file has everything I need that should be in the build_p674.h file. Why aren't the contents of the cfg file getting produced in the build_p674.h file?

    Latest config file is attached (3225.VibrationMonitor.cfg)

    I appreciate your help. Thanks.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Mark Skidmore
    Posted by Mark Skidmore
    on Jun 27 2012 10:13 AM
    Intellectual720 points

    I commented these out because I tried doing this at the bottom of the file:

    var Semaphore = xdc.useModule('ti.sysbios.knl.Semaphore');
    var AlarmEventTaskPoolSemaphoreParams = new Semaphore.Params();
    AlarmEventTaskPoolSemaphoreParams.instance.name = "AlarmEventTaskPoolSemaphore";
    Program.global.AlarmEventTaskPoolSemaphore = Semaphore.create(null, AlarmEventTaskPoolSemaphoreParams);

    but had no luck. Whether I use the bios.SEM.create(...) and bios.SEM.instance(...).comment or the lines above, I still get the same result: No populated build_p.674.h file...

    Latest config file is attached - 0245.VibrationMonitor.cfg

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • David Friedland
    Posted by David Friedland
    on Jul 03 2012 10:10 AM
    Genius13410 points

    Mark,

    Can this thread be closed now, or are you still working this issue?

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Mark Skidmore
    Posted by Mark Skidmore
    on Jul 04 2012 21:27 PM
    Intellectual720 points

    Go ahead and close it...thanks to all who attempted to help.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

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.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
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