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.
Part Number: CC2652R
I am using CCS Version 10.1.0, XDCTools version 3.61.01.25, Simplelink SDK Version 4.20.00.35, and am compiling my project with TI v20.2.1.LTS. My OS is 64-bit Windows 10. My target device is CC2652R1F. I am programming it via the JTAG interface on the Launchpad.
In developing my Bluetooth application, I have been reviewing the Linker Command File for the Simple Peripheral example project. I noticed a couple input/output sections that I have not been able to find any documentation on. These include ".constdata", ".rodata", and ".emb_text". I have already reviewed the ARM Assembly Language Tools User's Guide, ARM Optimizing C/C++ Compiler User's Guide, and the ARM Compiler User's Guide without any luck. Are these sections created in one of the BLE stack libraries or are they entirely unnecessary? I am worried that not allocating them in my linker command file might cause arcane errors to be thrown by the stack.
Thank you for the assistance.
Assigning an expert to comment.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
Hi Andrew,After doing some research, I don't believe any of these sections are TI-specific or BLE-specific. ".constdata" and ".rodata" both seem to be used for storing constants. ".emb_text" appears to be used to store specific assembly instructions.
There is a small amount of information about ".constdata" in the arm compiler documentation here: (also mentions RO data)https://developer.arm.com/documentation/dui0151/a/using-scatter-loading-description-files/examples-of-specifying-region-and-section-addresses/placing-regions-at-fixed-addresses
There is some information about ".rodata" in this TI linker presentation:https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/166/A-Primer-on-Linker-Scripts-and-Command-Files.pdf
There is a small amount of information in the arm compiler documentation about ".emb_text" here:https://developer.arm.com/documentation/dui0472/c/using-the-inline-and-embedded-assemblers-of-the-arm-compiler/compiler-generation-of-embedded-assembly-language-functionsI hope this helps.Best Regards,Alec M
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. 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.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.