Sign in

username:

password:



Not a member?

Search adsp



Search tips

Subscribe to adsp



adsp by Keywords

AD1819 | AD7332 | ADSP-2106 | ADSP-21060 | ADSP-21065L | ADSP-2116 | ADSP-21160M | ADSP-2181 | ADSP-218x | ADSP-219 | ADSP-2199 | ADSP219 | BF531 | BF532 | BF533 | BF535 | Blackfin | FFT | JTAG | LDF | SDRAM | SHARC | SPORT | UART | VDSP++ | VisualDSP

Discussion Groups

Discussion Groups | Analog Devices DSPs | Problem with multiple version of VisualDSP++

Technical discussions related to Analog Devices DSPs (including Blackfin, TigerSHARC, SHARC and ADSP-21xx DSPs).

  

Post a new Thread

Problem with multiple version of VisualDSP++ - Zlatko Petroff - Dec 5 11:32:00 2003



Dear Members,
recently I installed VisualDSP++ 3.0 for Blackfin and Sharc. Before I had only VisualDSP++ 3.0 for 21xx. I done the procedure according the guide of ADI, but now they do not work properly. The next which I tried was that I uninstalled everithing and I installed only VisualDSP++ 3.0 for ADSP21xx, but it does not work properly. How to solve the problem without format of my hard drive? Can someone to share your experience?
I am with WinXP Pro.
 
 
Sincerely,
Zlatko


(You need to be a member of adsp -- send a blank email to adsp-subscribe@yahoogroups.com )

Re: Problem with multiple version of VisualDSP++ - Kenneth Porter - Dec 6 6:16:00 2003

--On Friday, December 05, 2003 3:32 AM -0800 Zlatko Petroff
<> wrote:

> recently I installed VisualDSP++ 3.0 for Blackfin and Sharc. Before I had
> only VisualDSP++ 3.0 for 21xx. I done the procedure according the guide of
> ADI, but now they do not work properly. The next which I tried was that I
> uninstalled everithing and I installed only VisualDSP++ 3.0 for ADSP21xx,
> but it does not work properly. How to solve the problem without format of my
> hard drive? Can someone to share your experience?

The VDSP key in your user registry may be corrupt. This can happen if you run
a command line tool before the GUI after an installation. The GUI IDE is the
only tool that properly initializes the VDSP registry entry. If you run a
command line tool first, it only partially populates the registry, and nothing
else will correct it, as it believes the job is all done.

To fix this, use your favorite registry editor to navigate to
"HKEY_CURRENT_USER/Software/Analog Devices" and delete the VisualDSP
hierarchy. (The usual cautions about having a proper backup of your registry
apply.) Then run IDDE.EXE to repopulate that key.

Note that all of your IDE settings are stored in this key, as well as things
like projects, targets, and ICE settings.


(You need to be a member of adsp -- send a blank email to adsp-subscribe@yahoogroups.com )

Re: Problem with multiple version of VisualDSP++ - Jaime Andres Aranguren Cardona - Dec 6 22:26:00 2003

What Kenneth points out is right, but is not the only
cause for "improper" installation. Also important is
the order in which you install the tools.

I currently have VDSP++3.0 for 21xx, SHARC, TigerSHARC
and Blackfin (3.1 for this one).

I recommend you try to get from ADI knowledge base or
FTP site a document about how to properly uninstall
the tools. Do it, and then install everything again,
taking care of the order of installation. Of course,
install first what was released first.

Hope this helps,

JaaC --- Kenneth Porter <>
wrote:
> --On Friday, December 05, 2003 3:32 AM -0800 Zlatko
> Petroff
> <> wrote:
>
> > recently I installed VisualDSP++ 3.0 for Blackfin
> and Sharc. Before I had
> > only VisualDSP++ 3.0 for 21xx. I done the
> procedure according the guide of
> > ADI, but now they do not work properly. The next
> which I tried was that I
> > uninstalled everithing and I installed only
> VisualDSP++ 3.0 for ADSP21xx,
> > but it does not work properly. How to solve the
> problem without format of my
> > hard drive? Can someone to share your experience?
>
> The VDSP key in your user registry may be corrupt.
> This can happen if you run
> a command line tool before the GUI after an
> installation. The GUI IDE is the
> only tool that properly initializes the VDSP
> registry entry. If you run a
> command line tool first, it only partially populates
> the registry, and nothing
> else will correct it, as it believes the job is all
> done.
>
> To fix this, use your favorite registry editor to
> navigate to
> "HKEY_CURRENT_USER/Software/Analog Devices" and
> delete the VisualDSP
> hierarchy. (The usual cautions about having a proper
> backup of your registry
> apply.) Then run IDDE.EXE to repopulate that key.
>
> Note that all of your IDE settings are stored in
> this key, as well as things
> like projects, targets, and ICE settings.
>
> _____________________________________
> /groups.php3

__________________________________



(You need to be a member of adsp -- send a blank email to adsp-subscribe@yahoogroups.com )