Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Sign in
W
White Rabbit core collection
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 29
    • Issues 29
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Schedules
  • Wiki
    • Wiki
  • image/svg+xml
    Discourse
    • Discourse
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • Projects
  • White Rabbit core collection
  • Issues
  • #81

Closed
Open
Opened Apr 03, 2019 by Maciej Lipinski@lipinskimm
  • Report abuse
  • New issue
Report abuse New issue

select/ready signals for communication with SFP/1Wire

In the VFC-HD board, the access to SFP eeprom, as well 1-wire is multiplexed with application-specific user-defined code. Currently, we have a hack in place that reads SFP data, stores it in register and then fakes I2C slave that is read by WRPC.

The proposal is to have two signals: "select" and "ready". Before reading SFP (and potentially other peripherals), WRPC SW would first request access and then check whether it is granted. In most boards, "select" would be looped back to "ready". In VFC-HD (and any other where needed), the signals would be actually used.

This requires small changes in HDL and SW

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
1
Labels
feature
Assign labels
  • View project labels
Reference: project/wr-cores#81