• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 806 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARTX166 stack

Marco Cortecchia

Hi to all ,

I'm writing an application using ARTX166 and PK166 ( all updated to last versions ) . I'm writing it for an our board that use XC167CI 32F40F with external RAM 1 Mbit ( 16 bit multiplexed bus ) , located at 0x4C0000 .

When I compile the application , the stack of OS ( size 200 byte ) is automatically located on external RAM , but I would like to locate it on Internal RAM ( maybe IDATA at 0xF600 ) .

My application is time critical ( engine control unit ) , so I realy need to do so .

How can I configure the OS to locate stack at this position ?

Parents
  • 0 in reply to Franc Urbanc

    Thank You Franc . It work fine .

    I would like to made the same with global variable declared inside AR_RESOURCE.C :

    OS_ID os_psq[16];
    void *os_msg[16];

    That the linker locate on external RAM .
    I try to change this with :

    OS_ID NEAR_MEM os_psq[16];
    void* NEAR_MEM os_msg[16];

    I compile the ARTX166 for my memory model ( compact ) , and can see that it work fine . To made it working I set also ( PROJECT TARGET setting ) Near memory RAM to 16 kByte, in this way my external RAM is considered FDATA .

    1) Can I can have some collateral effects with this modify to ARTX166 ?

    2) Do You know a better way to force the linker to don't thread like NDATA ( Maybe linker directive ) ?

    Many thanks for your help

Reply
  • 0 in reply to Franc Urbanc

    Thank You Franc . It work fine .

    I would like to made the same with global variable declared inside AR_RESOURCE.C :

    OS_ID os_psq[16];
    void *os_msg[16];

    That the linker locate on external RAM .
    I try to change this with :

    OS_ID NEAR_MEM os_psq[16];
    void* NEAR_MEM os_msg[16];

    I compile the ARTX166 for my memory model ( compact ) , and can see that it work fine . To made it working I set also ( PROJECT TARGET setting ) Near memory RAM to 16 kByte, in this way my external RAM is considered FDATA .

    1) Can I can have some collateral effects with this modify to ARTX166 ?

    2) Do You know a better way to force the linker to don't thread like NDATA ( Maybe linker directive ) ?

    Many thanks for your help

Children
No data