On Fri, 18 May 2001 23:41:32 -0000, Robert K Yu wrote: > Curious. What version number do you see when you > select Help->About? I see the following: > VisualDSP++ Debug Application > Version 4.0.1.0 > Aug 28 2000 > > I supposedly have the VisualDSP++ 1.0 tool set, > though nowhere in the various tool version numbers > does it actually say "1.0". Ok, I see what you mean. The individual tool versions are totally unrelated to the package version. I see 4.0.1.0 for the debugger. Other versions from the about box: ADSP-21xxx JTAG Emulator (Summit): 4.20.1 Symbol Manager: 3.1.7.1 Processor (ADSP-210xx) DLL: 2.1.3.1 Kenneth Porter Kensington Laboratories, Inc. mailto: http://www.kensingtonlabs.com |
|
Re: Tool Versions (Re: source code doesn't display in debugger)
Started by ●May 19, 2001
Reply by ●May 22, 20012001-05-22
On Mon, 21 May 2001 13:44:24 +0800, manjula ellepola wrote: > I have got a 218x emulator and some eval boards which use the > serial port of my desktop to communicate for debugging etc. > > I am intending to buy a laptop which only has USB. I can get a > USB to RS232 convertor to interface the ICE to the laptop. > > Can the emmulator software ( visual DSP 6.1 ) which searches for > com ports be made to work with the USB port? In other words the > visual DSP thinks it's working with a com port but in reality it is a > USB port. I think that should work, but check with ADI support to verify. VDSP should use regular comm port API's, so the only real question is whether it can use any unusual device name the driver comes up with. You don't say whether you're using Win9x or Win2k. I know they behave a little differently with comm port names. When opening a non-standard name (ie. not "com1" but something like "octalport-1-2") you might need to put "\\.\" in front of the device name. Please reply on the mailing list so others can benefit from any new info. Kenneth Porter Kensington Laboratories, Inc. mailto: http://www.kensingtonlabs.com |