Banner_AURIX_Security-Solution Banner_AURIX_Security-Solution Banner_AURIX_Security-Solution


infineon4engineers Facebook

infineon@google+ Google+

infineon@linkedin linkedin

infineon4engi@twitter twitter

infineon@youtube youtube

+ Reply to Thread
Results 1 to 6 of 6

Thread: Aurix 275 C-STEP Move code from RAM to FLASH

  1. #1
    Dilip.Reddy.Mavuram
    Guest

    Aurix 275 C-STEP Move code from RAM to FLASH

    Hello,

    I am currently using Infineon Triboard with Aurix 275 C-STEP.

    All the code is presently running from RAM. I want to move this to ROM.

    Please suggest the required changes in .lsl file(attachedtc27x.txt)

    Compiler: Tasking 4.3r3

    Thank you...!!!

    Regards,
    Dilip

  2. #2
    Hello Dilip.Reddy.Mavuram,

    unfortunately I cannot find any user-defined code sections in the .lsl file you attached. Are you sure you attached the right file?
    TASKING Field Application Engineer

  3. #3
    Dilip.Reddy.Mavuram
    Guest
    Hello,

    yeah...this is what i am using.

    Can u please tell me what exactly is missing?

    Is it .text.* section or something else.

    Thankyou...!!!

    Regards,
    Dilip

  4. #4
    According to your .lsl your code already executes from ROM. You have to add sections to execute them from RAM instead if that's your intention.

    E.g.

    group(run_addr= mem:mpe:dspr0, copy)
    {
    select ".text.project.function_executed_from_dspr0";
    }


    will execute the selected functions from DSPR0 ram.
    TASKING Field Application Engineer

  5. #5
    New Member New Member Vinod is on a distinguished road
    Join Date
    Mar 2017
    Posts
    1
    Points
    20
    But in this way i guess the function will be stored in the DSPR0 only during first flash operation. Once the system is reset the function will no longer be available in DSPR0. So how do we ensure it is copied to DSPR0 during every start up ?

  6. #6
    Beginner Beginner ulrichk is on a distinguished road
    Join Date
    Sep 2017
    Posts
    5
    Points
    85
    The _c_init function which is called by the C startup code takes care of initializing the functions. Because the 'copy' keyword is used in the group definition for the group to which the code sections which need to be initialized are assigned:

    group(run_addr= mem:mpe:dspr0, copy)
    {
    select ".text.project.function_executed_from_dspr0";
    }

    the linker is instructed to add the required copy information (start address in flash, target address in RAM and number of bytes to copy) to the copy table and this copy table is processed by the _c_init function. As a result the function is initialized before the 'main' function is called by the startup code.

    Best regards,
    Ulrich

    TASKING tools support

+ Reply to Thread
Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.