01-27-2008 02:17 PM
01-28-2008
02:01 PM
- last edited on
01-24-2025
10:10 AM
by
Content Cleaner
04-08-2008 01:54 PM
I have the same problem. Does any part of the development environment for the single core processors produce useful code or other help in dealing with the 561? What about developing for one of the supported devices and porting the C over to one core of the 561...would that work? Can you ask Analog Devices about that with their Visual DSP++?
Thanks
Newbie
04-09-2008
11:36 AM
- last edited on
01-24-2025
10:10 AM
by
Content Cleaner
Hi Hummer1,
Unfortunately, it's not possible to target the BF 561 using the NI LabVIEW Embedded Module for ADI Blackfin Processors. This is not even possible if you generate the code using a different target and then porting it over to the 561. However, with the LabVIEW Microprocessor SDK, you can target any 32 bit platform. This would be the best option if you want to work with LabVIEW and the BF 561. Hope this helps.
04-09-2008 04:00 PM
06-06-2008 12:25 PM
I notice in the LV Blackfin developer suite that Visual DSP ++ is a part of hte system now. Visual DSP ++ supports the 561. I guess I need to ask again. Could you develop for the 537 say (a same speed target as the 561), take the resulting code, move it to Visual DSP++, and port the download to the 561 that way? If you are going to distribute Visual DSP++ with your system, could you please ask them if they could help with this? It's not my job to integrate your products for you.
Thanks.
Anxiously awaiting what I know will be an awsome combination tool from LV and VisualDSP++ for all the Analog Device products.
Just sitting here Humming while I wait.
06-09-2008 02:15 PM
Hi Hummer1,
I checked it up once again and presently it is not possible to port the code developed for BF537 (using LabVIEW) to a BF561. You did mention that they have similar speeds, however, there is a key difference; the BF561 is a multicore processor and hence it is a different type of product all together. There are many other differences between these two modules which prevent it from being ported.