L
Lasse Langwadt Christensen
Guest
søndag den 30. august 2020 kl. 07.23.33 UTC+2 skrev Ricketty C:
I\'m not taking a few leds, think graphical UI, icons, graphs, text formatting
because an FPGA with the same amount of available memory is going to be
much more expensive
sure if you have only an FPGA you try to put it in the FPGA, if you have an MCU you try yo put it in the MCU, if you have both you put it where it makes the most sense, keeping in mind that a lot more people can write code than HDL and the turn around for code it a lot shorter than HDL
you don\'t have to convert me, I have used FPGAs for 20+ years, but just because you have a hammer not everything is a nail, sometimes a screw is better
On Saturday, August 29, 2020 at 10:25:18 PM UTC-4, Lasse Langwadt Christensen wrote:
søndag den 30. august 2020 kl. 01.58.15 UTC+2 skrev Ricketty C:
On Saturday, August 29, 2020 at 6:50:46 PM UTC-4, Lasse Langwadt Christensen wrote:
søndag den 30. august 2020 kl. 00.39.05 UTC+2 skrev boB:
On Sat, 29 Aug 2020 14:27:20 -0700 (PDT), Lasse Langwadt Christensen
langwadt@fonz.dk> wrote:
lørdag den 29. august 2020 kl. 23.13.05 UTC+2 skrev Ricketty C:
On Saturday, August 29, 2020 at 4:44:24 PM UTC-4, Lasse Langwadt Christensen wrote:
lørdag den 29. august 2020 kl. 21.57.41 UTC+2 skrev jla....@highlandsniptechnology.com:
On Sat, 29 Aug 2020 20:38:31 +0200, Piotr Wyderski
peter.pan@neverland.mil> wrote:
jlarkin@highlandsniptechnology.com wrote:
There have been many programmable mixed-type (analog+digital) chips
over the years, but they don\'t seem to survive. Probably because they
don\'t do analog or digital very well.
Some of them are very interesting, e.g. the PSOC5LP family.
Unfortunately, its maximum IO frequency is 33MHz and it has only one PLL.
A small ARM with a bunch of *good* analog i/o might be interesting.
The ARM would need to host some programmable hardware LUTs to compete
with even this small mixed-type device. It escapes me why the MCUs with
even ~100 LUTs either do not exist at all at the lower end or are as
huge as Cyclone V/ZYNQ. If the signal frequency is ~50MHz, the MCU has
simply no chance to react. One needs to deploy an FPGA, which bumps up
the overengineering factor by two orders of magnitude. I see a lot of
applications for a mix of an ARM and a 1kLUT MACHXO3 device.
Best regards, Piotr
I think there are some SOCs (modest FPGA plus a small ARM) in the $20
range now.
We\'ll be seeing smallish FPGAs with a soft RISC-V core soon too. Soft
cores have been pretty bad up to now. Program space will still be a
restriction, but maybe a small FPGA with a megabyte of RAM or flash
and soft RISC-V would be a good product.
I believe Xilinx has a soft cortex M0/M3 that is free to use in their FPGAs
I\'ve seen several MB RAM in an SO8 package with a 133MHz QSPI interface,
that might be fast enough for some code
M1 perhaps? That\'s the core from ARM that is intended for such uses. Looks like they also have M3 for FPGAs as well, they even mention using them for \"free\" which I assume means evaluation.
yes M1 is M0 optimized for FPGA
as far as I can tell it is really free for use in Xilinx FPGAs
\"
Free to use on FPGA
Free use on FPGA for Cortex-M1 and Cortex-M3
For prototyping, research and commercial use
\"
https://www.xilinx.com/publications/events/developer-forum/2018-frankfurt/bringing-the-benefits-of-cortex-m-processors-to-fpga.pdf
How fast will that FPGA programmed as an ARM Cortex M3 run and how
much will it cost ? Seems to me that a 20,000+ LUT FPGA is not
going to be cheap ? Compared to just buying an ARM processor of the
same complexity at least.
yeh you have to have some special need to put it in the fpga when you
can buy an MCU with more memory and preformance for a fraction of the price
I don\'t know why people get this backwards so often. You must have a special need to want a processor when you have a perfectly good FPGA.
and vice versa
Actually, an FPGA contains many, many tiny multiplexers connecting many, many tiny bits of RAM in contrast to a processor which has the power of the humongous multiplexer manipulating very large blocks of RAM and Flash. So the processor has to run very, very fast to create virtual connections between the many portions of memory. The FPGA in contrast has wires connected by routing FETs that can be used to connect the tiny multiplexers and bits of RAM as selected by the multiplexers.
While the processor can do many slow tasks by switching between them with its humongous multiplexer selecting which task to emulate now, the FPGA is actually processing each task in parallel using much simpler resources for each task, fast or slow, it doesn\'t care.
sure, but do you want to write something like a UI or a language interpreter
in rtl?
In this vent device the alarms are based on UI settings. To be able to say this is all hardware the UI will be controlled by the FPGA. So yes, an HDL UI is no big deal.
What are you thinking of that would be a big deal in HDL?
I\'m not taking a few leds, think graphical UI, icons, graphs, text formatting
and if you need memory it is going to be much cheaper in an MCU
All memory in a device is free once the device is selected. Why would it be more expensive in an FPGA???
because an FPGA with the same amount of available memory is going to be
much more expensive
Which is better...? usually the one we are more familiar with. People often talk as if it is silly to design something in an FPGA that doesn\'t require high speed or some other feature that makes it impossible to do in an MCU. I look at problems from the other perspective, I only put in an MCU the parts that are awkward to do in an FPGA.
sure if you have only an FPGA you try to put it in the FPGA, if you have an MCU you try yo put it in the MCU, if you have both you put it where it makes the most sense, keeping in mind that a lot more people can write code than HDL and the turn around for code it a lot shorter than HDL
In the board I sell by the thousands (making lots of money in the process) there was nothing that could not be done in the FPGA, so no MCU needed. Of course it is a daughter board in a bigger system with lots of processors running operating systems virtualizing other operating systems... and then they have bigger FPGAs than mine to do the real work.
I don\'t know what your board does, maybe an FPGA is the perfect fit
It was absolutely. But you fail to understand my point. Many, many designs can be done in FPGAs with no more trouble than in processors. But people who use processors are used to thinking in the messy, complex techniques of making a sequentially executing machine appear to execute many processes at the same time.
This is a bias based on familiarity. I would have though the same way 20 years ago. Now that I have done some more complex designs in FPGAs I realize it really isn\'t harder necessarily and can be easier since FPGA tools are optimized for simulation. Working in simulation allows so much to be verified without turning on power to a board. I think people underestimate that as well.
I realize now I\'m not going to win any converts by talking about it. People will keep using the tools they were taught. Now that they know the complex rules of making processors appear to process in parallel, there is little incentive to change their thinking. So they will continue to fight the same fights over and over.
you don\'t have to convert me, I have used FPGAs for 20+ years, but just because you have a hammer not everything is a nail, sometimes a screw is better