Forums

ADSP-212xxx: Problem with VisualDSP++ 4.0

Started by rob.hutchins May 2, 2005
Hello list,

First off:  I apologize if this is not a list to which I should post
questions about the ADSP-212xx EZ-KIT lite and its IDDE - VisualDSP++.
I couldn't find an active Analog Devices related board and this seemed
to be the place I could get help at.

I had to uninstall VisualDSP++ 3.5 this morning as it would not open a
debug session, and I installed VisualDSP++ 4.0 which I downloaded from
the Analog Devices site.

I'm trying to build a project that worked just fine on Friday evening
but is now giving me the following error:

----------------Configuration: *ProjectName* - Debug----------------
.\ADSP-21262_CPP.LDF

[Warning li2060]  The following input section(s) that contain program
code
        and/or data have not been placed into the executable for
processor 'p0'
        as there are no relevant commands specified in the LDF:

        libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_vtbl)


[Error li1060]  The following symbols are referenced, but not mapped:
        '___vtbl__9bad_alloc' referenced from
libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco)
        '___vtbl__9exception' referenced from
libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco)

Linker finished with 1 error and 1 warning
cc3089: fatal error: Link failed
Tool failed with exit/exception code: 1.
Build was unsuccessful.

----------------------------------------------------------------------------
I looked up the help file to see what exactly the error is and what
remedial action is suggested.

This is what it says about fixing li1060:

How to Fix
Add an LDF command to map the necessary section.

How do I go about this in Expert Linker?

My system:
Windows 2000 Pro; VisualDSP++ Release 4.0 + Update; Target ADSP-21262.

"rob.hutchins" <rob.hutchins@gmail.com> wrote in message
news:1115075812.745018.112490@z14g2000cwz.googlegroups.com...
> Hello list, > > First off: I apologize if this is not a list to which I should post > questions about the ADSP-212xx EZ-KIT lite and its IDDE - VisualDSP++. > I couldn't find an active Analog Devices related board and this seemed > to be the place I could get help at. > > I had to uninstall VisualDSP++ 3.5 this morning as it would not open a > debug session, and I installed VisualDSP++ 4.0 which I downloaded from > the Analog Devices site. > > I'm trying to build a project that worked just fine on Friday evening > but is now giving me the following error: > > ----------------Configuration: *ProjectName* - Debug---------------- > .\ADSP-21262_CPP.LDF > > [Warning li2060] The following input section(s) that contain program > code > and/or data have not been placed into the executable for > processor 'p0' > as there are no relevant commands specified in the LDF: > > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_vtbl) > > > [Error li1060] The following symbols are referenced, but not mapped: > '___vtbl__9bad_alloc' referenced from > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco) > '___vtbl__9exception' referenced from > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco) > > Linker finished with 1 error and 1 warning > cc3089: fatal error: Link failed > Tool failed with exit/exception code: 1. > Build was unsuccessful. > > --------------------------------------------------------------------------
--
> I looked up the help file to see what exactly the error is and what > remedial action is suggested. > > This is what it says about fixing li1060: > > How to Fix > Add an LDF command to map the necessary section. > > How do I go about this in Expert Linker?
Hi Rob I can make a quick suggestion but don't guarantee that it will end your troubles. In the past, when I've made updates to VDSP, I've typically had to replace my .ldf file from my old project with a new one. Assuming you just use the default ldf for your processor, copy the new default ldf for your processor from the installation and overwrite the ldf in your project. It's quite likely that this will solve your problem. Search for "ADSP-21262_CPP.LDF" under your VDSP 4.0 installation. If you've made custom modifications to your ldf, then the process is a little more painful - backup your current ldf, overwrite with the default ldf from the install and redo the custom changes. Cheers Bhaskar
Bhaskar,

I hadn't thought of that.  I'll give it a whirl and let you know if it
works.

I hope it does!



Bhaskar Thiagarajan wrote:
> > Hi Rob > > I can make a quick suggestion but don't guarantee that it will end
your
> troubles. > In the past, when I've made updates to VDSP, I've typically had to
replace
> my .ldf file from my old project with a new one. Assuming you just
use the
> default ldf for your processor, copy the new default ldf for your
processor
> from the installation and overwrite the ldf in your project. It's
quite
> likely that this will solve your problem. > Search for "ADSP-21262_CPP.LDF" under your VDSP 4.0 installation. > > If you've made custom modifications to your ldf, then the process is
a
> little more painful - backup your current ldf, overwrite with the
default
> ldf from the install and redo the custom changes. > > Cheers > Bhaskar
Hi,

Besides Bhaskar's suggestion (which is a really good one), I'd recommend you 
to cross post your ADSP related questions to the mailing list 
adsp@yahoogroups.com

Maybe you need to join first, go to http://groups.yahoo.com/group/adsp/ or 
to http://www.dsprelated.com/groups/adsp/1.php

Regards

-- 
------------------------------
Jaime Andr&#2013265929;s Aranguren Cardona
jaac@sanjaac.com
SanJaaC Electronics
Soluciones en DSP
www.sanjaac.com

"rob.hutchins" <rob.hutchins@gmail.com> escribi&#2013265923; en el mensaje 
news:1115085000.038259.52450@z14g2000cwz.googlegroups.com...
> Bhaskar, > > I hadn't thought of that. I'll give it a whirl and let you know if it > works. > > I hope it does!
Bhaskar,

Just wanted to let you know that what you suggested worked.  I added a
new copy of the ADSP-21262_CPP.LDF file to my project and made the
custom changes to it, and used "Rebuild All".

Guess this is one of those things where you learn from experience :)

Thanks!
Rob.


Bhaskar Thiagarajan wrote:
> "rob.hutchins" <rob.hutchins@gmail.com> wrote in message > news:1115075812.745018.112490@z14g2000cwz.googlegroups.com... > > Hello list, > > > > First off: I apologize if this is not a list to which I should
post
> > questions about the ADSP-212xx EZ-KIT lite and its IDDE -
VisualDSP++.
> > I couldn't find an active Analog Devices related board and this
seemed
> > to be the place I could get help at. > > > > I had to uninstall VisualDSP++ 3.5 this morning as it would not
open a
> > debug session, and I installed VisualDSP++ 4.0 which I downloaded
from
> > the Analog Devices site. > > > > I'm trying to build a project that worked just fine on Friday
evening
> > but is now giving me the following error: > > > > ----------------Configuration: *ProjectName* -
Debug----------------
> > .\ADSP-21262_CPP.LDF > > > > [Warning li2060] The following input section(s) that contain
program
> > code > > and/or data have not been placed into the executable for > > processor 'p0' > > as there are no relevant commands specified in the LDF: > > > > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_vtbl) > > > > > > [Error li1060] The following symbols are referenced, but not
mapped:
> > '___vtbl__9bad_alloc' referenced from > > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco) > > '___vtbl__9exception' referenced from > > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco) > > > > Linker finished with 1 error and 1 warning > > cc3089: fatal error: Link failed > > Tool failed with exit/exception code: 1. > > Build was unsuccessful. > > > >
--------------------------------------------------------------------------
> -- > > I looked up the help file to see what exactly the error is and what > > remedial action is suggested. > > > > This is what it says about fixing li1060: > > > > How to Fix > > Add an LDF command to map the necessary section. > > > > How do I go about this in Expert Linker? > > Hi Rob > > I can make a quick suggestion but don't guarantee that it will end
your
> troubles. > In the past, when I've made updates to VDSP, I've typically had to
replace
> my .ldf file from my old project with a new one. Assuming you just
use the
> default ldf for your processor, copy the new default ldf for your
processor
> from the installation and overwrite the ldf in your project. It's
quite
> likely that this will solve your problem. > Search for "ADSP-21262_CPP.LDF" under your VDSP 4.0 installation. > > If you've made custom modifications to your ldf, then the process is
a
> little more painful - backup your current ldf, overwrite with the
default
> ldf from the install and redo the custom changes. > > Cheers > Bhaskar
"rob.hutchins" <rob.hutchins@gmail.com> wrote in message
news:1115179966.979513.298310@f14g2000cwb.googlegroups.com...
> Bhaskar, > > Just wanted to let you know that what you suggested worked. I added a > new copy of the ADSP-21262_CPP.LDF file to my project and made the > custom changes to it, and used "Rebuild All".
Mui Bien!! I'm glad it saved you some trouble and time. Cheers Bhaskar
> > Guess this is one of those things where you learn from experience :) > > Thanks! > Rob. > > > Bhaskar Thiagarajan wrote: > > "rob.hutchins" <rob.hutchins@gmail.com> wrote in message > > news:1115075812.745018.112490@z14g2000cwz.googlegroups.com... > > > Hello list, > > > > > > First off: I apologize if this is not a list to which I should > post > > > questions about the ADSP-212xx EZ-KIT lite and its IDDE - > VisualDSP++. > > > I couldn't find an active Analog Devices related board and this > seemed > > > to be the place I could get help at. > > > > > > I had to uninstall VisualDSP++ 3.5 this morning as it would not > open a > > > debug session, and I installed VisualDSP++ 4.0 which I downloaded > from > > > the Analog Devices site. > > > > > > I'm trying to build a project that worked just fine on Friday > evening > > > but is now giving me the following error: > > > > > > ----------------Configuration: *ProjectName* - > Debug---------------- > > > .\ADSP-21262_CPP.LDF > > > > > > [Warning li2060] The following input section(s) that contain > program > > > code > > > and/or data have not been placed into the executable for > > > processor 'p0' > > > as there are no relevant commands specified in the LDF: > > > > > > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_vtbl) > > > > > > > > > [Error li1060] The following symbols are referenced, but not > mapped: > > > '___vtbl__9bad_alloc' referenced from > > > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco) > > > '___vtbl__9exception' referenced from > > > libcpp.dlb[nomemory2126x_rev_0.0.doj](seg_pmco) > > > > > > Linker finished with 1 error and 1 warning > > > cc3089: fatal error: Link failed > > > Tool failed with exit/exception code: 1. > > > Build was unsuccessful. > > > > > > > -------------------------------------------------------------------------- > > -- > > > I looked up the help file to see what exactly the error is and what > > > remedial action is suggested. > > > > > > This is what it says about fixing li1060: > > > > > > How to Fix > > > Add an LDF command to map the necessary section. > > > > > > How do I go about this in Expert Linker? > > > > Hi Rob > > > > I can make a quick suggestion but don't guarantee that it will end > your > > troubles. > > In the past, when I've made updates to VDSP, I've typically had to > replace > > my .ldf file from my old project with a new one. Assuming you just > use the > > default ldf for your processor, copy the new default ldf for your > processor > > from the installation and overwrite the ldf in your project. It's > quite > > likely that this will solve your problem. > > Search for "ADSP-21262_CPP.LDF" under your VDSP 4.0 installation. > > > > If you've made custom modifications to your ldf, then the process is > a > > little more painful - backup your current ldf, overwrite with the > default > > ldf from the install and redo the custom changes. > > > > Cheers > > Bhaskar >
"rob.hutchins" <rob.hutchins@gmail.com> wrote in
news:1115179966.979513.298310@f14g2000cwb.googlegroups.com: 

> Bhaskar, > > Just wanted to let you know that what you suggested worked. I added a > new copy of the ADSP-21262_CPP.LDF file to my project and made the > custom changes to it, and used "Rebuild All". > > Guess this is one of those things where you learn from experience :) > > Thanks! > Rob.
This is not entirely unusually with new releases. I have done this many times before. Just one additional comment. There is already an update for VDSP 4.0 on the ADI web site. -- Al Clark Danville Signal Processing, Inc. -------------------------------------------------------------------- Purveyors of Fine DSP Hardware and other Cool Stuff Available at http://www.danvillesignal.com