• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 635 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

PROCESSOR-SDK-AM335X: How to set Entry Point Address in SYSBIOS

PROCESSOR-SDK-AM335X: Where Are the Symbols Defined?

Christopher Weber
Genius 4995 points
Part Number: PROCESSOR-SDK-AM335X


Hello,

The POST BUILD step of the example app GPIO_LedBlink_bbbAM335x_armTestProject calls (using PDK 1.0.17 and CCS 10.1.1)

${TI_PDK_INSTALL_DIR}/packages/pdkAppImageCreate.bat

Where is ${TI_PDK_INSTALL_DIR} defined??

Because I've searched every place I can find, and the closest I come are values that have "COM_" slapped in front of them.

There is no ${TI_PDK_INSTALL_DIR}...   does this environment just arbitrarily slap "COM_" in front of SOME of the variables?


  • 0
    TI__Expert 8885 points

    Hi Christopher,

    Our expert Jianzhong, who is assigned for this thread is on vacation and will be able to respond in the week of June 21. Please note delay in the response on this thread.

    Thanks

  • 0 in reply to Aravind Batni
    TI__Expert 8885 points

    Hi Christopher,

    If your question is only limited to understanding from where TI_PDK_INSTALL_DIR  is getting defined. It is from the eclipse plugin:

    Example:

    plugins/com.ti.pdk.am335x.product_1.0.17/META-INF/MYKEY.SF:5:Created-By: 1.8.0_131 (Oracle Corporation)
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:5: id="com.ti.pdk.am335x.product_1.0.17"
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:14: <extension point="org.eclipse.rtsc.xdctools.ui.productInfo">
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:15: <repository location="../../../packages"/>
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:16: <docs location="../../../docs"/>
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:18: installLocation="../../.."
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:27: id="com.ti.pdk.am335x"
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:30: rootMacroName="TI_PDK_INSTALL_DIR"/>
    plugins/com.ti.pdk.am335x.product_1.0.17/plugin.xml:35: productTypeId="com.ti.pdk.am335x"

  • 0 in reply to Aravind Batni
    Genius 4995 points

    Aravind,

    Where is Ki?  He can usually answer my questions too.

    I am spending DAYS AND DAYS unraveling how this mess works, because it's doing all this stuff under the covers and hides it from the user...

    My question comes from this process being BROKEN.  And as I try to figure out what is wrong, I go further and further down these holes...

    See this:

    e2e.ti.com/.../3728873

    The app FAILS TO START.  Turns out the bootstrap is BAD.  

    This is created by the tool pdkAppImageCreate.bat

    The BATCH file calls arm-none-eabi-objcopy.exe  WHICH IS IS NOT FUNCTIONING CORRECTLY.  IT IS DEFECTIVE from what I can tell.

    There are several of these arm-none-eabi-objcopy.exe files.   Which one is being called??

    It appears to be using the one in  ${TI_PDK_INSTALL_DIR}/packages

    My project DOES NOT EVEN SET THE PDK

    So.. How does it know to use the XML file you told me??   How does it know to use "C:\ti\ccs1011\ccs\eclipse\plugins\com.ti.pdk.am335x.product_1.0.17_1.0.17" ??

    Where in that XML file does it actually specify the folder...  WHICH arm-none-eabi-objcopy.exe to use??

    ( C:\ti\ccs1011\ccs\tools\compiler\gcc-arm-none-eabi-7-2017-q4-major-win32\bin or C:\ti\gcc-arm-none-eabi-7-2018-q2-update\bin ??)

    The one to use is coming from CG_TOOL_ROOT...   So where is THAT getting set from??  What is "BUILD SYSTEM"?   Because that isn't in the XML either.

    If TI actually tested this stuff, I wouldn't be spending DAYS trying to trouble where things break.  I'm not a TI employee.  I shouldn't be diagnosing TI's defects and trying to figure out work around's.

    -CSW

  • +1 in reply to Christopher Weber
    TI__Expert 8885 points

    Hi CSW,

    The CCS is based on eclipse project. It understands the eclipse plugins for the component. I do not know how much you would like to learn or you are required to learn about eclipse plugins etc. 

    You can discuss details on eclipse plugins etc with CCS teams may be in a different thread.

    All the components under PDK are eclipse components, the RTSC search path discovers all these components and you can select the component you would like to use for your CCS project.

    If you pick PDK 1.0.17 for AM335x, it would have the path setup for compile until the base dir that is defined in the eclipse plugin.

    As far as the PDK is concerned, they undergo nightly regressions and tests and checks before release.

    If you are seeing something fundamental failing out of the box (release component without your tweaks), probably it may be your setup (most of the times).

    On the thread you referenced, you seem to look for how to setup entry point for TIRTOS, which other TI expert is working with you.

    So, As far as this thread is concerned, I think you can close the thread and you probably got the answer to how this variable value is set.

    For the other thread, (e2e.ti.com/.../3728873) I would wait for the TI expert to come back from vacation and respond to you.

    Thanks

  • 0 in reply to Aravind Batni
    Genius 4995 points

    Aravind,

    The standard answer is always "use the demo"...  Well those have so much under the covers stuff, it's difficult to figure out what is going on...

    And a "Demo" doesn't cut it when you have a massive project that you need to bring up to date.  I don't need to tell everyone to rewrite it from scratch into a demo project because those settings are magically there and no support to bring them over from the current project.

    In the meantime, I guess we have to wait for the one guy to get back from vacation to discuss the executable in the compiler which does not appear to work correctly...