Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • YARR YARR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 40
    • Merge requests 40
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • YARR
  • YARRYARR
  • Issues
  • #83

Closed
Open
Created Oct 23, 2020 by Bruce Joseph Gallop@bgallopMaintainer

Query about TxCore shutdown

One of the features of the Strips ASICs is the output of HPR packets which are sent every 1ms.

The current scanConsole code does most of the shutdown of processing in reverse, but it calls TxCore::disableCmd and TxCore::disableRx after finishing the analysis. This means that HPRs that arrive after the data processor has been shut down are lost (also the memory leaks).

I was wondering whether this is something that would benefit from moving somewhere else. So, should disableRx be done before the data processor shutdown?

Assignee
Assign to
Time tracking