• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 382 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM6442: CCS files - design for large PRU repository

Nick Saulnier
Guru** 110030 points

Part Number: AM6442

Hello team,

The OpenPRU repo is our new resource for PRU development across the AM243x, AM26x, AM62x, AM64x, and future devices: https://github.com/TexasInstruments/open-pru

We currently have over 330 unique PRU core projects, each of which has a unique example.projectspec file and makefile_projectspec file - I expect that number to be closer to 500 unique projects by the end of the year.
(for future readers, you can find the lists here:
examples: https://github.com/TexasInstruments/open-pru/blob/main/examples/readme.md
academy: https://github.com/TexasInstruments/open-pru/blob/main/academy/readme.md)

I am currently migrating all the common makefile code into a single top-level pru_rules.mak file, which will hopefully make maintaining all the unique makefiles easier going forward: https://github.com/TexasInstruments/open-pru/pull/115

Are there any suggestions yall have for simplifying management of all those CCS projectspec files? Not sure if CCS would be able to make use of a similar "include common file" architecture, or if yall have any other ideas?

Thanks,

Nick