Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
HAL_BCM2835 HAL_BCM2835
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • RiscOS
    • SSources
  • HAL
  • HAL_BCM2835HAL_BCM2835
  • Merge requests
  • !22

Merged
Created Jan 23, 2023 by Ben Avison@bavisonDeveloper

Regularise polarity of safety catch across Compute Modules

  • Overview 0
  • Commits 1
  • Pipelines 2
  • Changes 1

The comment above ReadSafetyCatch about the CM4Lite catch pulling low was factually incorrect: it's always been a pull-up. It's just that we keep changing our minds about whether the catch is fitted for the Lite boards vs the ones with eMMC populated. I believe we eventually settled on CM4 and earlier boards being treated the same, therefore there is no longer any need to conditionally EOR the result based on the generation of board.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: CM4safetycatch