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.

XDC-Error: Can't find the library lib/Boot.aem3

Other Parts Discussed in Thread: CONTROLSUITE

Hello TI-RTOS-Experts,

Because I wanted to try the new SPI support in TI-RTOS for concerto devices, I downloaded CCSv5.4 and TI-RTOS_1_10_00_23.

I didn't want to ruin my current CCSv5.3 installation (has happened to me with previous ccs updates..), so I installed this new installation to "C:\ti_ccs54\". I don't think this should do any harm..?

When I started CCS, new products were discovered and everything, and then I created a new "Empty TI-RTOS Project" from the New-Project-Wizard. I didn't make any changes, and just clicked on "Build", and I got this output at console:

**** Build of configuration Debug for project m3 ****

"C:\\ti_ccs54\\ccsv5\\utils\\bin\\gmake" -k all 
'Building file: ../empty.cfg'
'Invoking: XDCtools'
"C:/ti_ccs54/xdctools_3_25_00_48/xs" --xdcpath="C:/ti_ccs54/tirtos_1_10_00_23/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/bios_6_35_01_29/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/ipc_1_25_03_15/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/ndk_2_22_03_20/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/uia_1_03_00_02/packages;C:/ti_ccs54/ccsv5/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.concertoM3:F28M35H52C1 -r release -c "C:/ti_ccs54/ccsv5/tools/compiler/arm_5.0.4" --compileOptions "-g --optimize_with_debug" "../empty.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring empty.xem3 from package/cfg/empty_pem3.cfg ...
js: "C:/ti_ccs54/xdctools_3_25_00_48/packages/xdc/cfg/Main.xs", line 46: XDC runtime error: can't find the library 'lib/Boot.aem3' specified by package ti.catalog.arm.cortexm3.concertoInit.  It wasn't found along the path 'C:/ti_ccs54/tirtos_1_10_00_23/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/bios_6_35_01_29/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/ipc_1_25_03_15/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/ndk_2_22_03_20/packages;C:/ti_ccs54/tirtos_1_10_00_23/products/uia_1_03_00_02/packages;C:/ti_ccs54/ccsv5/ccs_base;C:/ti_ccs54/xdctools_3_25_00_48/packages;..;'.
gmake.exe: *** [package/cfg/empty_pem3.xdl] Error 1
gmake.exe: *** Deleting file `package/cfg/empty_pem3.xdl'
gmake.exe: *** [package/cfg/empty_pem3.xdl] Deleting file `package/cfg/empty_pem3.h'
gmake.exe: *** [package/cfg/empty_pem3.xdl] Deleting file `package/cfg/empty_pem3.c'
js: "C:/ti_ccs54/xdctools_3_25_00_48/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake: *** [configPkg/compiler.opt] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

Then, I tried the demo-application from the Resource-Explorer: the same error. Then, I tried my own custom project: With the old TI-RTOS-version it has no errors, but when I change the includes to the new verison, I get the same errors.

Then, I tried downloading the file "Boot.aem3" from somewhere in the Internet. I found some version of it, and copied it in the desired directory. Then my console output said, that some other libraries were missing, too.

What can I do? Thank you very much for your help!

- Philipp

  • Hi Philipp,

    As noted in the release notes for 1.10.00.23, TI-RTOS has stopped support for LM3 devices. The LM3 devices are not supported in TivaWare. TI-RTOS is using TivaWare now instead of Stellarisware (which had the LM3 support).

    We'll still support the LM3 devices with patch releases off the 1.01 branch. We have a 1.01.01 release in the works now to get a couple bug fixes. I expect that a release will be available in the Sept. timeframe.

    Todd

  • Hi Todd,

    I somehow forgot to say this: I am using a Concerto Device, just the normal EVM-DockingStation with a Controlcard (TMDXDOCKH52C1).

    This branch was not discontinued, I hope? The problem must be located somewhere else..

    Thanks for your help,

    Philipp

    /edit: I just installed CCSv5.4, ControlSUITE3.2.2 and TI-RTOS 1.10.00.23 on another computer to C:\ti\...: the same problem! Some more details:

    I first installed CCSv5.4.0.00091 and chose all the compilers and tools I need (and possibly some more). The installation ran through, then I installed ControlSUITE, and then TI-RTOS. Then I rebooted, and afterwards started CCS. It discovered new software and restarted itself.

    Then I created a new workspace in C:\ti\workspace and created a new CCS Project. I chose some test-title, the processor F28M35H52C1 (ARM) and the project-prototype "Empty" from TI-RTOS. After this, I just clicked the Hammer-Symbol in CCS to Build this project-prototype, and I got the console output I posted in the first post.

    /edit2: I checked some paths and ran the windows-search, if could find the Boot.aem3-File somewhere on my computer, but I could only find the versions from the older TI-RTOS-realease (1.01.00.25 with xdctools 3.24.06.63). The corresponding directories on the new TI-RTOS-version are empty!

    Most of the *aem3-Files exist in both new and old TI_RTOS-version, but after a quick look at the files I could see that for example the auto_init.aem3 is also missing in the new version.

    I guess I should not use the files from the older version? When I copy the following files from my older TI-RTOS-installation to the same directories in the new installation, the Build-Process succeeds:

    - ...\xdctools_3_25_00_48\packages\ti\catalog\arm\cortexm3\concertoInit\lib\Boot.arm3

    - ...\xdctools_3_25_00_48\packages\ti\targets\arm\rtsarm\lib\auto_init.aem3

    - ...\xdctools_3_25_00_48\packages\ti\targets\arm\rtsarm\lib\boot.aem3

    - ...\xdctools_3_25_00_48\packages\ti\targets\arm\rtsarm\lib\ti.targets.arm.rtsarm.aem3

    But can I use these files without any worries? I don't want to run into any unpredictable errors like wrong pointers or anything later ...

  • Problem solved!

    I just used the newer version of xdctools! (v3.25.02.70)

    This should definitely not cause me any trouble, right?