fix(ci): wire up the TI mmWave SDK path baked into the ccstudio image #42
Labels
No labels
Category
App
Category
Documentation
Category
Firmware
Category
Hardware
Category
Qms
PR_Size
L
PR_Size
M
PR_Size
S
PR_Size
XL
PR_Size
XS
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Very Low Priority
Size
Epic
Size
Feature
Size
Task
Status
Blocked
Status
Draft
Status
Needs-review
Team
Board
Team
Dev
Team
Management
Type
Bug
Type
Capa
Type
Improvement
Type
New-feature
Type
Regulatory
Type
Usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
opendutchsolutions.public/hal_awr6843#42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
testing/CMakeLists.txt'sTI_MMWAVE_SDK_PATHauto-detection only checks a few local dev-machine paths ($ENV{HOME}/ti/..., two/mnt/...mounts) -- none of which exist on the actualccstudioCI runner, soti_hal_comparisonalways skips on CI (confirmed in #40's CI log:no local TI mmWave SDK found).Inspected the
whuzfb/ccstudio:20.2-ubuntu24.04-mmwimage directly (docker run --rm --entrypoint sh whuzfb/ccstudio:20.2-ubuntu24.04-mmw -c 'find / -maxdepth 6 -iname "*mmwave_sdk*"') and confirmed the SDK is in fact baked in, at/opt/ti/mmwave_sdk_03_06_02_00-LTS, withpackages/ti/common/sys_common.hpresent -- exactly the file the existing candidate-search logic checks for.Scope
/opt/ti/mmwave_sdk_03_06_02_00-LTS/packagestotesting/CMakeLists.txt'sTI_MMWAVE_SDK_PATHcandidate listti_hal_comparisontestsFunctional Impact
None -- CI/build-tooling only, no product/driver code changes.
Regulatory Impact
None
QMS Impact
None
Risk Impact
No -- existing risk coverage sufficient.
Related Issues / PRs
Relates to #16, #40