Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
S
Simple VME FMC Carrier 7 - SVEC7
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 12
    • Issues 12
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Projects
  • Simple VME FMC Carrier 7 - SVEC7
  • Issues
  • #88

Closed
Open
Opened Jul 06, 2020 by Grzegorz Daniluk@greg.d
  • Report abuse
  • New issue
Report abuse New issue

many traces have over-complicated routing, crossing layers multiple times

just a few (not all!) examples:

  • VMEPX_IRQ2_N goes multiple times from top to bottom again to top etc. while could be easily routed e.g. in L3.
  • VME_D_DIR around pin d13 of VME P1 connector could be continuously routed in L5, but instead it goes to L3 and back.
  • same for LCLK_N (X:7247mil Y:3588mil)
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: project/svec7#88