Author Topic: Is the code on an FPGA firmware?  (Read 7837 times)

0 Members and 1 Guest are viewing this topic.

Offline suicidaleggroll

  • Super Contributor
  • ***
  • Posts: 1453
  • Country: us
Re: Is the code on an FPGA firmware?
« Reply #25 on: September 20, 2017, 02:55:38 pm »
You write firmware.  After it's been synthesized, you load the bitstream onto the FPGA.  That's the syntax I use...the code itself is "firmware" or "HDL", the synthesized binary blob is the bitstream, though many people I work with still refer to that as the firmware, and nobody cares.
 

Offline jnz

  • Frequent Contributor
  • **
  • Posts: 593
Re: Is the code on an FPGA firmware?
« Reply #26 on: September 20, 2017, 08:43:14 pm »
I mean, I don't know the second thing about FPGA really, but it seems to me you're just defining a *configuration*.

In terms of the real world firmware seems about a million times clearer to a normal person than bitstream.
 

Offline ZaneKaminski

  • Contributor
  • Posts: 30
  • Country: us
Re: Is the code on an FPGA firmware?
« Reply #27 on: September 21, 2017, 02:42:27 pm »
Once it's on the FPGA, it is certainly not a bitstream. The bits all end up scattered around in different internal flipflops and SRAM blocks. There is no stream anymore. So it's a "configuration" now, not a bitstream. A bitstream is just that... a stream of bits. In this case, the bitstream encodes the FPGA configuration.

Firmware is a more abstract concept. Firmware is the stuff you have to apply to the device or it doesn't work. I hesitate to provide a more specific definition, since more specificity would undermine the usefulness of the term. Firmware doesn't have to be a single bitstream, though it often is. It could be multiple, or it could refer to some other way to structure the data. Consider multiple files in a typical computer filesystem. These files could, together, represent the firmware, but they have tree-type relationship and aren't just a single stream (a tree of streams, of course).

So if all a system needs to "work" (whatever that means) is an FPGA configuration bitstream, then it represents the entirety of the firmware. Otherwise there may be other files or bistreams or whatever you want to say, and those all together represent the firmware.

Addendum: it's worth noting that the firmware doesn't have to be compiled, whereas a bitstream (like the software  term, a "binary") always is compiled and ready to run or be applied to the device.
« Last Edit: September 21, 2017, 02:44:17 pm by ZaneKaminski »
 

Offline legacy

  • Super Contributor
  • ***
  • !
  • Posts: 4415
  • Country: ch
Re: Is the code on an FPGA firmware?
« Reply #28 on: September 21, 2017, 07:36:55 pm »
mr.brilliant: hey?
mr.sapiens: oh!
mr.brilliant: pip?
mr.sapiens: and dandy!
mr.brilliant: yeah! let's upload the firmware
mr.sapiens: yeah cool!!!!!!!!

5 sec later ... some neurons have a blast
 
mr.sapiens: ehm ... what? into what? we have two CPUs and four fpgas on the board
mr.brilliant: ye-e-ah, I meant the file-something for the chip-something
mr.sapiens: which one? the slave MPU? the ARM chip? do you mean loooooonnnniiiixxxxx?
mr.brilliant: it! (pointing the finger in the direction of the chip)
mr.sapiens: ah, that chip, that file!!! Alright!

---

The ape was a great big Hit!
The first time it said "banana",
pointing the finger in the direction
of a banana on a banana tree.

Nowadays problems with evolution
are greater still  :D

( kidding )
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf