Skip to content

Update OPEN_PRU product version to 2026.01.00#140

Merged
nsaulnier-ti merged 2 commits into
TexasInstruments:mainfrom
pratheesh:fix/issue-108-open-pru-version
Jun 25, 2026
Merged

Update OPEN_PRU product version to 2026.01.00#140
nsaulnier-ti merged 2 commits into
TexasInstruments:mainfrom
pratheesh:fix/issue-108-open-pru-version

Conversation

@pratheesh

Copy link
Copy Markdown
Contributor

Fixes #108

The OPEN_PRU product version was stale at 07.03.01. This updates it to the 2026.01.00 release version in the two places the issue identifies:

  1. .metadata/product.jsonversion field
  2. SysConfig files for MCU+ cores — the --product OPEN_PRU@<ver> pin in @cliArgs/@v2CliArgs

Only the OPEN_PRU@ product version is changed; MCU_PLUS_SDK@07.03.01 is intentionally left untouched (separate product, out of scope for this issue).

16 files changed, version-string-only edits.

CI: all three workflows (Makefile CI, GNU Toolchain CI, CCS Build — full device matrix) pass on this change on my fork.

@qodo-code-review

qodo-code-review Bot commented Jun 13, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📎 Requirement gaps (0)

Context used

Grey Divider


Action required

1. @cliArgs exceeds 129 columns 📘 Rule violation ⚙ Maintainability
Description
The updated SysConfig @cliArgs/@v2CliArgs comment lines are longer than the 129-column hard
limit, reducing readability and violating the repository line-length requirement. These are
configuration command strings and should be wrapped/split to stay within limits.
Code

academy/getting_started_labs/c_and_inline_assembly/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[R4-5]

+ * @cliArgs --device "AM263x_beta" --part "AM263x" --package "ZCZ" --context "r5fss0-0" --product "MCU_PLUS_SDK@07.03.01" --product "OPEN_PRU@2026.01.00"
+ * @v2CliArgs --device "AM2634" --package "NFBGA (ZCZ)" --context "r5fss0-0" --product "MCU_PLUS_SDK@07.03.01" --product "OPEN_PRU@2026.01.00"
Evidence
PR Compliance ID 22 sets a hard 129-column limit, and PR Compliance ID 31 requires wrapping long
configuration command strings. The modified @cliArgs/@v2CliArgs lines in the cited .syscfg
files are single-line command strings that clearly exceed 129 columns.

academy/getting_started_labs/c_and_inline_assembly/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]
examples/LCD_interface/mcuplus/am243x-lp/r5fss0-0_freertos/example.syscfg[4-5]
Best Practice: Repository guidelines
Best Practice: Learned patterns

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Several modified `.syscfg` files contain very long single-line `@cliArgs`/`@v2CliArgs` command strings that exceed the 129-column hard limit.

## Issue Context
These lines were modified in this PR (OPEN_PRU version bump) and now violate repository line-length requirements for source/config files.

## Fix Focus Areas
- academy/getting_started_labs/assembly_code/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]
- academy/getting_started_labs/c_and_assembly/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]
- academy/getting_started_labs/c_and_inline_assembly/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]
- academy/getting_started_labs/c_code/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]
- academy/gpio/gpio_toggle/am261x-lp/r5fss0-0_freertos/example.syscfg[4-5]
- academy/gpio/gpio_toggle/am263px-lp/r5fss0-0_freertos/example.syscfg[4-5]
- academy/gpio/gpio_toggle/am263x-lp/r5fss0-0_freertos/example.syscfg[4-5]
- academy/intc/intc_mcu/am261x-lp/r5fss0-0_freertos/example.syscfg[4-5]
- academy/intc/intc_mcu/am263px-cc/r5fss0-0_freertos/example.syscfg[4-5]
- academy/intc/intc_mcu/am263px-lp/r5fss0-0_freertos/example.syscfg[4-5]
- academy/intc/intc_mcu/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]
- academy/intc/intc_mcu/am263x-lp/r5fss0-0_freertos/example.syscfg[4-5]
- examples/LCD_interface/mcuplus/am243x-lp/r5fss0-0_freertos/example.syscfg[4-5]
- examples/empty/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]
- examples/empty_c/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg[4-5]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Bump OPEN_PRU product version to 2026.01.00 in metadata and SysConfig pins
🐞 Bug fix ⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

Walkthroughs

Description
• Update OPEN_PRU product metadata version from 07.03.01 to 2026.01.00.
• Re-pin SysConfig CLI args to OPEN_PRU@2026.01.00 across affected examples.
• Leave MCU_PLUS_SDK product pins unchanged to avoid unintended SDK upgrades.
Diagram
graph TD
  S["SysConfig example.syscfg"] --> T(["SysConfig (GUI/CLI)"]) --> R(["Product resolver"]) --> P[("OPEN_PRU@2026.01.00")]
  M[".metadata/product.json"] --> R
  T --> C(["CCS import/build"]) --> P
  subgraph Legend
    direction LR
    _f["File"] ~~~ _t(["Tool"]) ~~~ _p[("Product")]
  end
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Centralize OPEN_PRU version in a shared template
  • ➕ Avoids repeated pins across many example.syscfg files
  • ➕ Reduces future version-drift risk
  • ➖ Requires a generation step or template engine for example files
  • ➖ May not fit existing repo workflow for checked-in SysConfig outputs
2. Remove explicit OPEN_PRU pin and rely on environment default
  • ➕ Eliminates stale pin failures when OPEN_PRU updates
  • ➕ Less maintenance across examples
  • ➖ Build/import becomes environment-dependent and less reproducible
  • ➖ Harder to diagnose mismatched tool/product installations

Recommendation: For an immediate fix to #108, directly updating the pinned OPEN_PRU version in product.json and the SysConfig headers is the most reliable and least disruptive approach. Longer term, consider templating or generating the SysConfig header pins from a single source of truth to prevent the same drift from recurring, but that’s a broader workflow change than this issue warrants.

Grey Divider

File Changes

Other (16)
product.json Bump OPEN_PRU product metadata version to 2026.01.00 +1/-1

Bump OPEN_PRU product metadata version to 2026.01.00

• Updates the OPEN_PRU product.json version field from 07.03.01 to 2026.01.00 so tools resolve the correct product release.

.metadata/product.json


example.syscfg Re-pin SysConfig OPEN_PRU product to 2026.01.00 +2/-2

Re-pin SysConfig OPEN_PRU product to 2026.01.00

• Updates @cliArgs and @v2CliArgs to reference OPEN_PRU@2026.01.00 while leaving MCU_PLUS_SDK@07.03.01 unchanged.

academy/getting_started_labs/assembly_code/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg


example.syscfg Re-pin SysConfig OPEN_PRU product to 2026.01.00 +2/-2

Re-pin SysConfig OPEN_PRU product to 2026.01.00

• Updates @cliArgs and @v2CliArgs OPEN_PRU product pin from 07.03.01 to 2026.01.00 for this lab solution.

academy/getting_started_labs/c_and_assembly/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg


example.syscfg Re-pin SysConfig OPEN_PRU product to 2026.01.00 +2/-2

Re-pin SysConfig OPEN_PRU product to 2026.01.00

• Changes the OPEN_PRU product pin in the SysConfig generation arguments to OPEN_PRU@2026.01.00.

academy/getting_started_labs/c_and_inline_assembly/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg


example.syscfg Re-pin SysConfig OPEN_PRU product to 2026.01.00 +2/-2

Re-pin SysConfig OPEN_PRU product to 2026.01.00

• Updates the SysConfig header CLI arguments to use OPEN_PRU@2026.01.00 for product resolution consistency.

academy/getting_started_labs/c_code/solution/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in GPIO toggle SysConfig (AM261x LP) +2/-2

Update OPEN_PRU pin in GPIO toggle SysConfig (AM261x LP)

• Bumps the OPEN_PRU product pin to 2026.01.00 in both v1 and v2 SysConfig CLI argument headers.

academy/gpio/gpio_toggle/am261x-lp/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in GPIO toggle SysConfig (AM263Px LP) +2/-2

Update OPEN_PRU pin in GPIO toggle SysConfig (AM263Px LP)

• Replaces OPEN_PRU@07.03.01 with OPEN_PRU@2026.01.00 in the stored SysConfig generation args.

academy/gpio/gpio_toggle/am263px-lp/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in GPIO toggle SysConfig (AM263x LP) +2/-2

Update OPEN_PRU pin in GPIO toggle SysConfig (AM263x LP)

• Updates the OPEN_PRU product pin to 2026.01.00 in @cliArgs and @v2CliArgs, keeping the MCU_PLUS_SDK pin intact.

academy/gpio/gpio_toggle/am263x-lp/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in INTC MCU SysConfig (AM261x LP) +2/-2

Update OPEN_PRU pin in INTC MCU SysConfig (AM261x LP)

• Adjusts the SysConfig generation argument header to reference OPEN_PRU@2026.01.00 for this example.

academy/intc/intc_mcu/am261x-lp/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in INTC MCU SysConfig (AM263Px CC) +2/-2

Update OPEN_PRU pin in INTC MCU SysConfig (AM263Px CC)

• Bumps OPEN_PRU pinned version to 2026.01.00 in both CLI argument variants stored in the .syscfg header.

academy/intc/intc_mcu/am263px-cc/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in INTC MCU SysConfig (AM263Px LP) +2/-2

Update OPEN_PRU pin in INTC MCU SysConfig (AM263Px LP)

• Updates OPEN_PRU version pin to 2026.01.00 while preserving the existing MCU_PLUS_SDK pin.

academy/intc/intc_mcu/am263px-lp/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in INTC MCU SysConfig (AM263x CC) +2/-2

Update OPEN_PRU pin in INTC MCU SysConfig (AM263x CC)

• Switches OPEN_PRU@07.03.01 to OPEN_PRU@2026.01.00 in stored SysConfig CLI arguments for this configuration.

academy/intc/intc_mcu/am263x-cc/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in INTC MCU SysConfig (AM263x LP) +2/-2

Update OPEN_PRU pin in INTC MCU SysConfig (AM263x LP)

• Bumps the OPEN_PRU product pin to 2026.01.00 in both @cliArgs and @v2CliArgs for this example.

academy/intc/intc_mcu/am263x-lp/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in LCD interface SysConfig (AM243x LP) +2/-2

Update OPEN_PRU pin in LCD interface SysConfig (AM243x LP)

• Updates OPEN_PRU product pin to 2026.01.00 while leaving MCU_PLUS_SDK_AM243x@10.00.00 unchanged.

examples/LCD_interface/mcuplus/am243x-lp/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in empty example SysConfig (AM263x CC) +2/-2

Update OPEN_PRU pin in empty example SysConfig (AM263x CC)

• Bumps OPEN_PRU pinned version to 2026.01.00 in the SysConfig header CLI arguments.

examples/empty/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg


example.syscfg Update OPEN_PRU pin in empty_c example SysConfig (AM263x CC) +2/-2

Update OPEN_PRU pin in empty_c example SysConfig (AM263x CC)

• Updates the OPEN_PRU product pin from 07.03.01 to 2026.01.00 for consistent SysConfig resolution.

examples/empty_c/mcuplus/am263x-cc/r5fss0-0_freertos/example.syscfg


Grey Divider

Qodo Logo

@nsaulnier-ti

Copy link
Copy Markdown
Collaborator

Must also update docs/tagging_checklist.md to update .metadata/product.json in addition to .metadata/.tirex/package.tirex.json

@nsaulnier-ti nsaulnier-ti left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

must update docs/tagging_checklist.md

pratheesh added a commit to pratheesh/open-pru that referenced this pull request Jun 25, 2026
Per maintainer review on PR TexasInstruments#140 (issue TexasInstruments#108): the OPEN_PRU version
field lives in both .metadata/.tirex/package.tirex.json and
.metadata/product.json. Update the tagging checklist so future tags
bump both files, not just the tirex package descriptor.
@pratheesh

Copy link
Copy Markdown
Contributor Author

@nsaulnier-ti good catch — done in f66c7fd. The Update the .metadata version section of docs/tagging_checklist.md now lists both files to bump on a tag:

* `.metadata/.tirex/package.tirex.json`
* `.metadata/product.json`

This matches the actual version edits in this PR, so future tags won't miss .metadata/product.json.

pratheesh and others added 2 commits June 25, 2026 08:36
The OPEN_PRU product version was stale at 07.03.01 in product.json and
in every SysConfig file pinning the OPEN_PRU product. Bump all of them
to the 2026.01.00 release version so SysConfig product resolution and
CCS imports reference the correct product.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Per maintainer review on PR TexasInstruments#140 (issue TexasInstruments#108): the OPEN_PRU version
field lives in both .metadata/.tirex/package.tirex.json and
.metadata/product.json. Update the tagging checklist so future tags
bump both files, not just the tirex package descriptor.
@nsaulnier-ti nsaulnier-ti force-pushed the fix/issue-108-open-pru-version branch from f66c7fd to 5fcebbc Compare June 25, 2026 13:36
@nsaulnier-ti nsaulnier-ti merged commit 4a118c2 into TexasInstruments:main Jun 25, 2026
14 checks passed
pratheesh-ti pushed a commit that referenced this pull request Jun 26, 2026
The column-length best practices (79 soft / 129 hard) were written for
hand-authored source. SysConfig example.syscfg files are machine-
generated: their @cliArgs/@v2CliArgs header lines are single-line
command strings that exceed column 129 by construction and cannot be
wrapped without breaking the tool's round-trip.

Treating those lines as violations produces false-positive review flags
on any PR that touches a .syscfg file (for example the OPEN_PRU version
bump in #108/#140, which only edited a token inside pre-existing long
lines). Make the exemption explicit, consistent with the existing
markdown/.txt carve-out, so automated and human reviewers stop flagging
generated content.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update OPEN_PRU version from 07.03.01

3 participants