SpinalHDL / SpinalHDL

Scala based HDL
Other
1.66k stars 331 forks source link

Cross platform toplevel pin mapping definition #8

Open Dolu1990 opened 8 years ago

Dolu1990 commented 8 years ago

For exemple, Xilinx and Altera have their own file format to specify mapping between design pins and package pins (+ specify pin technologies, current, terminaison, ...)

It could be great to have a scala DSL to specify them without having to worry about the specific syntax of the target EDA.

pmudry commented 8 years ago

I agree, would be a great feature ! :+1:

numero-744 commented 2 years ago

Do you have a plan for this? A design idea? Do you want to add this in the io bundle or externally? I think the second would be clearer/cleaner and easier to implement.

What about a class to express constraints in general?

Here is a draft:

val constraints = new Constraints(new myTop) {
    // The clocking constraint would be inferred from the clock domain if it specifies a frequency

    // Default voltage first
    voltage(myTop.io).set50
    // Specific voltage, erasing the previous one just for one pin
    voltage(myTop.io.myPin).set33
}
Dolu1990 commented 2 years ago

I'm thinking more about adding the information to the io signals via the SpinalTag utilities. Then we could analyse all the io of a given toplevel to generate the proper constraint file.

A bit like the qsysify tool does.

Readon commented 2 years ago

I'm thinking more about adding the information to the io signals via the SpinalTag utilities. Then we could analyse all the io of a given toplevel to generate the proper constraint file.

A bit like the qsysify tool does.

How about IP-XACT support mentioned #621?

Dolu1990 commented 2 years ago

Hmm, IP-XACT would be a good thing in itself, but it isn't related right ? i mean, this issue is more about the pin mapping of the FPGA i think.

Dolu1990 commented 2 years ago

While IP-XACT is more about interface definition ?

Readon commented 2 years ago

yes, in my opinion, if the names can be mapped to unified standards by IP-XACT, then it's not necessary to map again through other mechanism.

---Original--- From: @.> Date: Fri, Jun 10, 2022 16:18 PM To: @.>; Cc: @.**@.>; Subject: Re: [SpinalHDL/SpinalHDL] Cross platform toplevel pin mapping definition (#8)

While IP-XACT is more about interface definition ?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>