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.

rts430x lib build taking long time

Part Number: MSP-EXP430F5529
Other Parts Discussed in Thread: TRF7970A

Tool/software: TI C/C++ Compiler

I am trying to build the example project located in sloa227a (for an MSP-EXP430F5529LP Launchpad and TRF7970A Boosterpack), but am getting a warning accompanied by extremely long build times.  I'm using Code Composer Studio v7.4.0.00015 and Compiler TI v16.9.9.LTS.

"warning #10366-D: automatic library build: using library "C:\ti\ccsv7\tools\compiler\ti-cgt-msp430_16.9.9.LTS\lib\rts430x_lc_ld_eabi.lib" for the first time, so it must be built.  This may take a few minutes."

The build has already lasted more than 30 minutes with no sign of completion.  What is rts430x anyway?  What might I look for to speed things up?

Thanks,

Adam J.

  • Adam Johnson 537 said:
    What is rts430x anyway?

    It is the compiler runtime support (RTS) library.  It contains the startup code, along with standard C library functions like memcpy.  In your case, the full name of the library is rts430x_lc_ld_eabi.lib.  

    The compiler package contains the most common variants of the RTS library.  If it contained all possible variants, the package is too large to be a practical download.  The linker automatically determines which variant of the RTS library is required.  If it is not present, it is built.  When that occurs, a diagnostic like this is issued ...

    Adam Johnson 537 said:
    "warning #10366-D: automatic library build: using library "C:\ti\ccsv7\tools\compiler\ti-cgt-msp430_16.9.9.LTS\lib\rts430x_lc_ld_eabi.lib" for the first time, so it must be built.  This may take a few minutes."

    With regard to ...

    Adam Johnson 537 said:
    The build has already lasted more than 30 minutes

    That's unusual.  On most systems, it usually takes around 5 minutes.  My first guess is that your PC is having a problem of some sort.  Perhaps the hard drive is nearly full.  Could this be the case?

    Thanks and regards,

    -George

  • Hello Adam,
    please run Resource Monitor and check Disk, Memory and CPUs utilization when compiling.
    What is your PC config?
  • George, Tom,

    I left my computer compiling, seemingly stuck at 62%, and when I arrived at work the next morning it had completed. According to Windows, my hard drive has 262 GB free of 470 GB. My machine runs Windows 10 Pro x64 with 16 GB RAM and Intel Core-i7-6700 @2.6 GHz.

    Any chance this could be because I was using a non-administrative Windows account? Or maybe because of antivirus (I'm running Trend Micro Security Agent, which I can't turn off without IT approval)?

    Could a corrupt Code Composer workspace cause this?

  • Adam,

    please run Resource Monitor and check Disk, Memory and CPUs utilization when compiling.
    Without monitoring your comp. resources everything is guessing.
    Up to 8 instances of the C compiler should run in parallel.
  • I'm not very familiar with Windows Resource Explorer. Is there a way I can gather data to present it here?
    When I run the compiler, it no longer stops to build the rts430x_lc_ld_eabi.lib file, so I'm not sure how to recreate my issue, but if I do a rebuild I can see several instances of acpia430.exe, asm430.exe, cg430.exe. Is that what I'm looking for?
  • Windows Resource Monitor, not Explorer.

    Looks like this:

    If compilation takes so long, probably you have lack of I/O performance.

  • Here are some screenshots as Code Composer Studio starts up, as well as rebuilding a project.  Total time to start and rebuild is about 8 minutes.

    Code Composer Studio Starting up:

    Rebuilding 1:

    Rebuilding 2:

    Rebuilding 3 (about 56% complete):

    Rebuilding finished:

  • 8 minutes is much better than over 30m.
    CPU utilization @ 60% points to a HDD bottleneck.
    If you have HDD you can replace it with SSD.
    With SSD you should get 5-6 minutes.
  • My drive is solid state already :(

    I can't reproduce the really long build time, since the .lib file has already been built. But I can live with 8 minutes for now. I'm thinking I'll just mark this thread as resolved, and if something else comes up that takes much longer, then I'll start a related question.

    Thanks for your time!

    Adam J.
  • SSDs dramatically loose performance when are utilized @ 80-90% or more.
    More then 50% is free on yours.
    For next SSD select the one with huge I/Os per sec.