FPGA Intellectual Property
PCI Express*, Networking and Connectivity, Memory Interfaces, DSP IP, and Video IP
6530 Discussions

DSP Builder Custom Boards

Altera_Forum
Honored Contributor II
‎08-20-2007 08:36 PM
1,695 Views

I have been working with DSP Builder 7.1 for a few months now at a lab at school. I was wondering if anybody could help me in creating a new board device to use. Currently, I am trying to use the Cyclone II EP2C50. I tried creating a .board file using another Cyclone II device as a template. However, even though I have changed all the pins to the correct pinouts, the old pinouts from the other Cyclone II device remain. I am not even sure if I am going about the right way of doing this. Please help!

0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎08-31-2007 10:52 AM
842 Views

Are you regenerating the board library after creating the .board file? The command alt_dspbuilder_createComponentLibrary may help here. The board and component files are cached once they're loaded - so you may have to restart MATLAB and then run the command without opening any designs or the library first.

0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎08-31-2007 01:17 PM
842 Views

Thanks so much for your help with that. That was definately my problem. Was there some documentation where this kind of stuff is written down? I couldn't really seem to find anything around. Thanks again for your time! 

 

David Tietz
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.