this thread is for working out/sorting info. It can be skipped as a digression by those pressed for time. I have added this link to my favorites...and am reading there today. http://iotdesign.embedded-computing.com/search/#quicklogic the web page title? iotdesign.embedded I will track items along and see if QUIK eFPGA material starts to show up there. http://embedded-computing.com/pdfs/Altera.Fall03.pdf Code profiling can help identify the functions that consume the majority of the MIPS and can provide options, for example, such as accelerating the code by use of a hardware coprocessor. Not all functions are appropriate for off-loading to a coprocessor. First, the goal is to identify a group of algorithms that together occupy more than half of the processing load. Second, the identified group of algorithms should be clustered together so that once data reaches the coprocessor, there is no processor dependency in the calculation until the processing is complete and the coprocessor can return the result to the DSP. A third criterion is that the processing be straightforward to implement in hardware. A simple definition is that the algorithm be heavily looped, thus implying a very repetitive computational structure. So consider that while QUIK is at the other end of it all the process should be the same..One other thing...I had not considered a BIG DSP maker may have motivation to put an FPGA in to offload the DSP?While much of the items that might get placed here are for the cloud end, as we go forward look for key tidbits that say they want the same thing on the device....Facebook is exploring that already and says so loud and clear.Consider discarding the nagging thoughts that QUIK don't have FPGA IP worth a dime.Worth more each day that links FPGA to AI. There will be no fire sale.
No comments:
Post a Comment