1.4 THE FLOW: METHODOLOGY AND TOOL ISSUES

The goal of this section is to put together all topics relevant to methodology and tools

The proposed M2IMPIR flow

M2IMPIR (Matlab2Implementation) quick description 

1. Matlab BB (Building Blocks)
1. Develop specific BBs. 
2. Reuse BBs, out of one of the several thousands of Toolboxes and librairies.
3. Build AS-DSP and simulate it.
2. 2 Map to Ideal Platform (BB to BB)
3. IMPlementation with Ideal Resources
1. Run and verify 
2. Iterate 

M2IMPIR issues

• There are 3 types of issues: Matlab, Mapping, Implementation platform. 

1. Matlab: Here the problem is "Matlab BBs". 
1. Because, more often than none, a Matlab BB ends up as a FPGA IP, i.e hdl code, i.e concurency. And Matlab is everything but concurent. 
2. The other issues have to do with the language. Going through all of them is outside this section just say the number is large and many are not obvious.    
2. Mapping:  Mapping has a few pitfalls but they are well known. 
3. Implementation platform:
1. My current methodology is to use a platform with ideal resources (which is not the same as infinite resources). That's all. 
2. Even an ideal platform has some issues 
1. but at least the flow is managable. 
3. For those  interested in implementation platforms and architecture, I propose to start with  Andre Dehon web site (at Uni Penn) , read all papers and go from there.

Further Topics

1. My early life: looking for an oxymoron: the descriptive Language
2. The NPU lessons
1. The thesis of Norwich Rich. 
3. Retargetable compiler: from bit slice to Archelon.
4. Meet the infinite loop: simulation and profiling on RC platforms (reconfigurable computing).