This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF Open Mesh change PPI

Hi, would there be any drawback in setting TIMER_PPI_CH_START to 11 to maximize the number of free PPI for application. 14->15 should be free to use in timeslot and ppis are only used in timeslots for the mesh if I understand correctly.

Parents
  • Hi,

    As long as you keep track of the PPIs for your own application, and make sure there aren't any conflicts, there shouldn't be any problems with changing the PPI channels for the mesh timer. In fact, version v0.7.0 and up don't use the PPI channels at all. They might be used in future releases though, so I wouldn't start throwing them out completely unless strictly necessary.

    You'll be fine moving them up to 11, now and in the future :) In fact, you can move them all the way up to 13, as the last slot is only used for timestamping, and cannot be assigned a PPI channel as the timer_control module is today. This is unlikely to change.

Reply
  • Hi,

    As long as you keep track of the PPIs for your own application, and make sure there aren't any conflicts, there shouldn't be any problems with changing the PPI channels for the mesh timer. In fact, version v0.7.0 and up don't use the PPI channels at all. They might be used in future releases though, so I wouldn't start throwing them out completely unless strictly necessary.

    You'll be fine moving them up to 11, now and in the future :) In fact, you can move them all the way up to 13, as the last slot is only used for timestamping, and cannot be assigned a PPI channel as the timer_control module is today. This is unlikely to change.

Children
No Data
Related