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

TMS570LS0714: Including sys_intvecs.asm in the TMS570 driver.lib file

Abrar Huq21
Intellectual 270 points
Part Number: TMS570LS0714

Hi,

We are using the IAR EWARM V8.22 and Micro-controller TMS570LS0714.

For our requirement, we have to make the following projects:
a) Driver library (which generates .lib file) - Contains the driver source code and header files, start up code, .asm files.
b) Application - Uses the driver.lib file and generates the user application.

For the driver library, we have included the file sys_intvecs.asm file containing the interrupt vectors for building the library.
For the application, we have included the driver.lib file, excluded sys_intvecs.asm and built the project to create .hex file. Upon viewing the hex file generated by the application, the interrupt vectors are not present.
But if we include the file sys_intvecs.asm in the application and build the project, the generated hex file contains the interrupt vectors.

Please could you let me know if there is something wrong with building the asm files as part of the lib and added to the project?
Since the application project would be given to customer, we cannot include the file sys_intvecs.asm in the application project.

Thanks and regards,
Abrar

  • 0
    TI__Guru**** 196256 points
    Hi Abrar,

    To map the interrupts routines to interrupt vectors, the application has to include the sys_intvecs.asm. sys_intvecs.asm contains assembly language directives that can be used to set up the ARM's interrupt vectors with branches to your interrupt routines.

    The linker command control file contains a SECTIONS directive that maps the .intvecs section into the memory locations 0x00-0x1F. Before running a C/C++ program, you must create the C/C++ run-time environment. The C/C++ boot routine performs this task using a function called _c_int00. The _c_int00 function is called by reset hardware which is defined in sys_intvecs.asm.