• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 1466 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.

[App project + BLE project]: Merging two different projects

Hsa S
Expert 2570 points


Hello TI,

I am working on two different app projects (Application project (pin Interrupt application, which has only application project from 'simplelink' and SPPBLE profile project which has (application+BLE Stack) for cc26xx, and these two belongs to two different work spaces. I want to merge these two so that my pinInterrupt application run with SPPBLE profile project. Please suggest me the key step points of merging at this stage. 

Please suggest~

Thanks n Regards

  • 0
    TI__Guru**** 171224 points
    Hi,

    From the tools and IDE standpoint, there is no straightforward or automated way to merge two projects, therefore I can offer some hints.

    You will have to manually and carefully cover the following details:
    - Merge both projects' compiler and linker include files and libraries. The biggest pitfall is to check if there are any incompatibilities between include files (redefinition of functions and variables, for example) and libraries (functions with the same name but different functionality).
    - Merge the additional compiler and linker options. The biggest pitfalls are related to clashing options (one project turns something off, while another turns it on) and optimizations (in rare cases the code may not work correctly if optimized too much or too little).
    - Merge the startup_ccs.c files of both projects (if it exists). Certain devices have a startup_ccs.c source file that contains the allocation for the interrupt vector table. This may be tricky if there are conflicting interrupts being used by different routines.
    - Merge the linker CMD file of both projects. This usually is pretty easy, but if one of the projects requires that certain elements must be allocated at conflicting memory places with the other, this may require more work to test it.
    - Merge the TI-RTOS .cfg files. This may override the previous two steps (as the linker .cmd file and the interrupts are automatically assigned and generated), but will require careful inspection of conflicting tasks, semaphores and its intrinsic priorities. Also, the device drivers must accommodate both projects (different functions may clash when calling into the device driver)
    - Merge your custom code itself. This is usually somewhat easier as you are familiar with the code.

    That is all I can think about the process of merging the files. If you are having something application or RTOS specific, I strongly suggest you to send additional questions to the device and the TI-RTOS forums, as the experts there are much more knowledgeable about these aspects.

    Hope this helps,
    Rafael