|
Just a quick "hi" to all.... I just joined this list and I know that there is very little traffic so far... maybe we can get more going... I am working on a proprietary dual-21065L system that we're using for those systems at the entranceway of store that go "whoop-whoop" when someone steals something. I am currently getting the 24-bit codec system up an going... so far, short of the little gotchas we've found along the way, we've been doing pretty well... I am using VisualDSP for development and simulation as well as the White Mountain SUMMIT-ICE for JTAG support. In reply to some of the questions: Michael: the linker is a pain, until you get the hang of it. The ldr files are a trip but I've gotten it working... contact me at and we can discuss what you're having problems with. Hari: re: Coding Standards, check out the "C Compiler Guide" book of the VisualDSP tools for info about mixed C/ASM code. I've found that, even when I wasn't in C all the time, obeying the standard gave me a lot more flexibility than setting up my own standards.... Hope to hear from others! Rachel |
|
|
Hello
Started by ●June 10, 1999
Reply by ●June 15, 19991999-06-15
|
Can anyone tell me which are the Hardware tools available for ADSP21060 processor for testing with and without target hardware. Regards Hari |
|
|
Reply by ●June 17, 19991999-06-17
|
Hello, On Tue, 15 Jun 1999, Hari Krishna wrote: > > Can anyone tell me which are the Hardware tools available for ADSP21060 > processor for testing with and without target hardware. Hardware tools for testing w/o hardware ? well, there is the EZ-ICE, an JTAG interface (from ADI) to look at the processor/download code/run code/look at the memory etc. there is another company "White Mountain" which sells (sold?) a multiprocessor-capable version of the EZ-ICE, they were bought by ADI some months ago. the JTAG interface can be found on most development boards and also on many target hardware platforms. to test w/o hardware i can only think of the simulator (also from ADI). from third-parties i have only seen RT-OS's, libs etc., but no testing tools. Michael -- Michael Haertl |
Reply by ●June 17, 19991999-06-17
|
<> wrote: Original Article: http://www.egroups.com/group/adsp/?start=4 > > I am working on a proprietary dual-21065L system that we're using for those > systems at the entranceway of store that go "whoop-whoop" when someone steals > something. What kind of boot architecture have you decided to go with? My own is probably going to use separate EPROMs for the two 65's. They'll share SDRAM and a serial Flash for the bulk of the code. Ken |
Reply by ●June 17, 19991999-06-17
|
On Thu, 10 Jun 1999, RACHEL ADAMEC wrote: > Just a quick "hi" to all.... hi, > [...] > the little gotchas we've found along the way, we've been doing pretty well... I > am using VisualDSP for development and simulation as well as the White Mountain > SUMMIT-ICE for JTAG support. I have some questions: -Which debugger do you use with the summit-ice (the VisualDSP debugger or the White Mountain Vista-ICE debugger) ? -How long does a single step take (e.g. if you press F11 in VisualDSP) ? -Can you set breakpoints in ext SDRAM (if you have code in ext SDRAM in bank 0) ? About the Summit-ICE: do you know if it is just a PCI-version of the Mountain-ICE/ISA ? The WM website does not mention 21065L-support for the Mountian-ICE (although i have used it with VisualDSP), but for the Summit-ICE. > In reply to some of the questions: > Michael: the linker is a pain, until you get the hang of it. The ldr files are a > trip but I've gotten it working... i guess you mean the LDF-files, yes i also think it could be managed a bit easier. but i have definitly a difference if i am using the linker via the GUI or on the command line in a DOS box. especially when it comes to large segments of code/data in ext. memory. The "PACKING"-command seems to be ignored by the GUI linker. Michael -- Michael Haertl |
