CC2640R2L: Can not find file rom_sysbios.aem3

Mariano

Part Number: CC2640R2L
Other Parts Discussed in Thread: SYSBIOS, CC2640R2F

Hello everyone.

I bought a new mac mini and now I am with problem to build projects in my new envinroment. In my previous installation everything was working fine.

CCS - 12.5.0.00007
XDCTOOLS - xdctools_3_51_03_28_core
COMPILER - ti-cgt-arm_18.12.5.LTS
SDK - simplelink_cc2640r2_sdk_5_30_00_03
Python - 3.11.6

I imported the sample simple_peripheral and simple_peripheral_oad_offchip for testing the new environment, but the build is not working, specially the linker phase. I also convert all pythons scripts to use the 3.11.6 version. The build of the stack and app seems ok, just the linker is failing.

<Linking>
error #10008-D: cannot find file "/......../simple_peripheral_cc2640r2lp_app/TOOLS/src/sysbios/rom_sysbios.aem3"
error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "simple_peripheral_cc2640r2lp_app.out" not built

Maybe the script that copy the file to destiny directory does not have permission for that? What does script copy the file rom_sysbios.aem3 ??

Can anyone help me?? Thank you in advanced.

over 1 year ago

0 Alex Fager over 1 year ago

TI__Genius 10221 points

Hello Mariano,

I hope you are doing well. I looks like you have all the required dependencies to make it work (are you running macOS Mojave?) Release Notes (ti.com). If you try to build other projects, like empty under drivers does it build or not build as well?

Have you also tried all the necessary steps as listed in the BLE quick start guide? TI Drivers Quick Start — SimpleLink CC2640R2 SDK Quick Start Guide 4.20.00.xx documentation.

Thanks,
Alex F

0 Mariano over 1 year ago in reply to Alex Fager

Intellectual 285 points

I am running on macOS Sonoma. Drivers projects like pinInterrupt and pwmled2 built successfully. Just projects related to blestack have the issue described above.

Why the drivers projects copy the rom_sysbios.aem3 file correctly and other not??

+1 Mariano over 1 year ago in reply to Alex Fager

Intellectual 285 points

Alex

I executed manually the makefile of directory "/......../simple_peripheral_cc2640r2lp_app/TOOLS/src/sysbios/" and the files were generated as expected.

0 Alex Fager over 1 year ago in reply to Mariano

TI__Genius 10221 points

Hello Mariano,

Good to hear you found a workaround. To confirm you are able to successfully build (and test) BLE SDK projects?

Thanks,
Alex F

0 Mariano over 1 year ago in reply to Alex Fager

Intellectual 285 points

Yeahh, with this workaround is possible build and test BLE SDK projects.

Just out of curiosity, the sample simpleperipheral_central is not discovering anything, you have any tip for that ??

0 Alex Fager over 1 year ago in reply to Mariano

TI__Genius 10221 points

Hello Mariano,

Did you already follow the readme guide in the example? If so, do you see any Putty output similar to the image below? And are you trying to discover via a phone, or by the device itself?

0 Mariano over 1 year ago in reply to Alex Fager

Intellectual 285 points

Yeahh I am checking the messages in terminal. The sample with multi role I can discovering other devices but I can not connect to them.

I have another launchpad running a simple_peripheral on CC2642R1 chip with ble5stack which I connect of a mobile device normally.

The multi role running on CC2640R2F with blestack does not connect to CC2642R1. In the terminal of CC2640R2 I can the following messages : connHandle 0 paring and Disconnected!

0 Alex Fager over 1 year ago in reply to Mariano

TI__Genius 10221 points

Hello Mariano,

For this issue can we create a separate new thread (with the title along the lines BLESTACK does not connect to CC2642R1), and also when creating that thread link to this original thread (so I can get BLE expert to look in detail at your specific issue).

Thanks,
Alex F

Bluetooth®︎

Bluetooth forum

CC2640R2L: Can not find file rom_sysbios.aem3