Skip to content

Suggestion for enhancement #22

@DanRoh

Description

@DanRoh

I like the idea to use the (cheap, small, ..) AVX edge connector as a debug interface. I also found the information on debug-edge.io very clearly structured and inspiring.. Thanks for this.

Recently I added the edge connector to one of my target boards and found it a bit confusing how exactly the pin assignment is meant. I guess the drawing on debug-edge.io is a "view towards the target board"?

I know I could find out by opening the KiCad files, but for us out there without KiCad it's a bit difficult..
May I suggest to place a small note on the drawing?

I also have a suggestion to extend the meaning/description of some pin assignments:

Vref: I think this normally is meant to be output from the target board and used as a reference voltage for the interface drivers on the interface side.
However, I often use this to power the target board during production programming and I think many developers do it this way.. What about naming this "Vref/Vcc"? This also would suggest that it is "bidirectional".

TRACE0/1: If I'm correct the signals TRACE_CLK, TRACE0, TRACE1 are normally output from the target to the host. You already specified that TRACE0 can also be used as RX, which is input to the target, i.e. TRACE0/RX is bidirectional.
I would like to suggest to change the specification for the TRACE signals like this:
TRACE_CLK/TX (no change)
TRACE0/RX/IO0 (added IO0, suggest use as general purpose bidirectional I/O)
TRACE1/IO1 (added IO1, suggest use as general purpose bidirectional I/O)

This would then look like this:
debugedge

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions