• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 463 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.

RTOS/AM5746: How to build/debug "boot.asm" by CCS in PROCESSOR-SDK-RTOS-AM57X

matusan
Guru 10235 points
Part Number: AM5746

Tool/software: TI-RTOS

Hello, TI Experts,

 

Our customer sent us questions about CCS rebuild/debug the below "boot.asm" in PROCESSOR-SDK-RTOS-AM57X 05_02_00_10.

- “C:\ti\bios_6_73_01_01\packages\gnu\targets\arm\rtsv7A\boot.asm”

 

And we tried to rebuild/debug by using GPIO_LedBlink_idkAM574x_armTestProject like below;

1:Import CCS project “GPIO_LedBlink_idkAM574x_armTestProject” & build.

2:Copy & modify "boot.asm" file. Then, delete "Debug" folder & Build.

3:We can found proper break behavior at modified code line in "boot.asm".

Please refer attached pdf, in detail.

 

Question:

We understand like below;

     - GPIO_LedBlink_idkAM574x_armTestProject.out is generated by modified boot.asm in CCS properly.

Is this understanding correct?

 

We would appreciate if you tell us the recommended way of CCS rebuild/debug the "boot.asm" file.

 

Best regards,

 boot_modify.pdf

  • 0
    TI__Guru** 116170 points
    Matusan,

    Yes. that is the correct procedure to update or override the default behavior of an existing function or code in BIOS libraries. When you include a source file with the same name in the application, the linker with use the symbol from the application rather than link to the function in the BIOS library as the symbols or functions defined in the application have precedence/priority in the linking process. To explain further during the link step linker will find two boot.o files, one that is compiled from BIOS RTS library and one that is defined at application level and the linker will choose the symbols from the boot.o that is in the application which allows the application to alter the default behavior.

    We do the same thing for modifying the behavior or timer module or any other functions that may be defined in BIOS. this allows user to over ride the behavior of the function as defined in BIOS without requiring them to update the release package that is provided by TI.

    Regards,
    Rahul

    PS: This concept is explained well in the section "Overriding symbols" in the following article:
    www.bottomupcs.com/libraries_and_the_linker.xhtml
  • 0 in reply to Rahul Prabhu
    Guru 10235 points
    Hi,

    Thank you very much for your detail explanation.
    I really appreciate your help.
    I will send the answer to the customer.

    Best regards,