Un bel giorno John Larkin digit�:> We're planning a new universal boot loader for a family of ST > processors. The uP would host the loader in a bit of local flash and > read an outboard serial flash to get the specific application code and > one or more FPGA configurations. > > So, how many config bits might there be for a modern mid-range FPGA > doing a moderately complex application? > > I think we could enable compression too. > > Please consider this a PHB type question. I don't do FPGA development > myself, past whiteboarding.My PHB answer would be 32 Mbit. However, "mid-range" FPGA is a very broad definition. These days I would call mid-range something like the Spartan 7 family, but probably someone could argue that it is already low-range. So you could choose 32 Mbit (which is the maximum bitstream size required for the Spartan-7 and for a mid-range Artix 7) or go a little further to accomodate also the mid-range Kintex-7. See table 1-1: https://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf -- Fletto i muscoli e sono nel vuoto.
FPGA config sizes
Started by ●November 8, 2019
Reply by ●November 10, 20192019-11-10
Reply by ●November 11, 20192019-11-11
On 09/11/2019 00:12, Rick C wrote:> On Friday, November 8, 2019 at 5:48:04 PM UTC-5, Stef wrote: >> On 2019-11-08 Rick C wrote in comp.arch.fpga: >>> On Friday, November 8, 2019 at 2:09:04 PM UTC-5, John Larkin wrote: >>>> >>>> Please consider this a PHB type question. I don't do FPGA development >>>> myself, past whiteboarding. >>> >>> Anyone know what a "PHB type question" is? >> >> https://dilbert.com/search_results?terms=phb > > Yeah, someone explained in the other group. A bit obscure, methinks. >Nah. I get suspicious of any engineer who doesn't know the term PHB! It's like not understanding the term SEP.
Reply by ●November 11, 20192019-11-11
In article <qqb5mf$e1f$1@dont-email.me>, David Brown <david.brown@hesbynett.no> wrote:>On 09/11/2019 00:12, Rick C wrote: >> On Friday, November 8, 2019 at 5:48:04 PM UTC-5, Stef wrote: >>> On 2019-11-08 Rick C wrote in comp.arch.fpga: >>>> On Friday, November 8, 2019 at 2:09:04 PM UTC-5, John Larkin wrote: >>>>> >>>>> Please consider this a PHB type question. I don't do FPGA development >>>>> myself, past whiteboarding. >>>> >>>> Anyone know what a "PHB type question" is? >>> >>> https://dilbert.com/search_results?terms=phb >> >> Yeah, someone explained in the other group. A bit obscure, methinks. >> > >Nah. I get suspicious of any engineer who doesn't know the term PHB! > >It's like not understanding the term SEP.I had to think a bit to come up with PHB, but I got it. I've no idea what SEP is. But then I'm acronymn dumb (and too lazy to try and google it right now.) (I've got a feeling a "whoosh" at my expense is incoming...) --Mark
Reply by ●November 11, 20192019-11-11
On 11/11/2019 17:33, gtwrek wrote:> In article <qqb5mf$e1f$1@dont-email.me>, > David Brown <david.brown@hesbynett.no> wrote: >> On 09/11/2019 00:12, Rick C wrote: >>> On Friday, November 8, 2019 at 5:48:04 PM UTC-5, Stef wrote: >>>> On 2019-11-08 Rick C wrote in comp.arch.fpga: >>>>> On Friday, November 8, 2019 at 2:09:04 PM UTC-5, John Larkin wrote: >>>>>> >>>>>> Please consider this a PHB type question. I don't do FPGA development >>>>>> myself, past whiteboarding. >>>>> >>>>> Anyone know what a "PHB type question" is? >>>> >>>> https://dilbert.com/search_results?terms=phb >>> >>> Yeah, someone explained in the other group. A bit obscure, methinks. >>> >> >> Nah. I get suspicious of any engineer who doesn't know the term PHB! >> >> It's like not understanding the term SEP. > > I had to think a bit to come up with PHB, but I got it. I've no idea > what SEP is."Somebody else's problem". It's a term from Douglas Adams: """ An SEP is something we can't see, or don't see, or our brain doesn't let us see, because we think that it's somebody else's problem. That’s what SEP means. Somebody Else’s Problem. The brain just edits it out, it's like a blind spot. """ <https://en.wikipedia.org/wiki/Somebody_else's_problem> It is very useful in all kinds of engineering, for helping focus on the task /you/ have to do instead of everyone else's tasks.> > But then I'm acronymn dumb (and too lazy to try and google it right > now.)You need to swat up on your TLA's :-)> > (I've got a feeling a "whoosh" at my expense is incoming...) > > --Mark > > > >
