infineon4engi@twitter twitter

infineon4engineers Facebook

infineon@linkedin linkedin

infineon@youtube youtube


+ Reply to Thread
Results 1 to 4 of 4
  1. #1
    Intermediate Intermediate Ing99 is on a distinguished road
    Join Date
    Oct 2013
    Location
    Germany
    Posts
    84
    Points
    495.546875

    How to inactivate an app without deleting it

    Hi Infineon,

    a new problem and a new idea.

    We have a pc board with many interfaces, e.g. ethernet and ethercat, but not all customers order all interfaces. To minimize costs, the pick and place machine only places the components needed on the pc board. When no ethernet or no ethercat is ordered, then no phy is placed.

    But then the original code doesn't run any more. When no eth phy is present, the code detects this, runs on ETH_LWIP_ERROR_PHY_DEVICE_ID and stops.

    To solve the problem, we have to delete the app, run solver and generate code. But this approach has a big drawback: now we have to maintain as many code versions as hardware versions exist (at the moment 4 versions).
    There should be a possibility to inactivate an app, which means: the app is still loaded, the solver processes the app as before and occupies the needed resources, but 'Generate Code' doesn't generate any code and the code works like if the app has not been added.
    This problem appears only at interfaces which use external components the XMC checks as present.

    At the moment, as workaround, we delete the generated files of ethcat or ethnet and deactivate the init call. This must be done again after each 'Generate Code'. Combined with deactivation of our own code parts accessing the apps by a compiler switch, this runs. But we would prefer an official solution like a checkbox or context menue function 'Inactivate App' and then the app is inactive and at the app tree greyed out or so. Please is there a chance for?


    Best Regards
    Wolfgang
    Last edited by Ing99; Aug 9th, 2019 at 08:02 AM.

  2. #2

    Infineon Employee
    Infineon Employee
    jferreira will become famous soon enough
    Join Date
    Oct 2012
    Posts
    653
    Hi,

    The DAVE_Init function is defined as weak function that you can override.

    Regards,
    Jesus
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

  3. #3
    Intermediate Intermediate Ing99 is on a distinguished road
    Join Date
    Oct 2013
    Location
    Germany
    Posts
    84
    Points
    495.546875
    Hi Jesus,

    thanks for your answer,
    but fct DAVE_Init called by fct main() isn't declared weak, I think you are speaking of fct SystemInit().

    I also see no chance to solve the problem via SDK. It's only a Dave internal solution possible.

    Regards,
    Wolfgang

  4. #4

    Infineon Employee
    Infineon Employee
    jferreira will become famous soon enough
    Join Date
    Oct 2012
    Posts
    653
    Hi,

    The DAVE_Init is defined as weak function in DAVE.c:

    __WEAK DAVE_STATUS_t DAVE_Init(void)


    Check you have the latest Device Pack installed.


    Regards,
    Jesus
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

Tags for this 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.