• Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 1317 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Grace Feedback – enabling and disabling modules

Antonio Espirito-Santo
Expert 2855 points

Dear all,


I’m working with the GraCE tool.

If the digital IO module is enabled and configured, the GPIO_init.c file is generated with the configuration code as defined in the GraCE GUI. After that, if the IO module is disabled, the file isn’t automatically removed from the file system. I think this situation happens because if you enable it again, makes sense to restore the previous configuration.  Unfortunately, when the IO module is re-enabled the information from the GPIO_init.c is lost.

Best Regards,

AES

  • TI__Intellectual 1690 points

    Hi,

    Thanks for the feedback.

    Disabling and re-enabling a peripheral deletes the information that was previously entered in the graphical view. This is done to allow for a "fresh start". Actually, this is the only use case for disabling the GPIO view. Almost every peripheral uses GPIOs and it wouldn't be good if you assign a peripheral function to a pin which isn't configured by Grace.

    Best Regards,

    Michael

**Attention** This is a public forum