Sign in

username:

password:



Not a member?

Search motoroladsp



Search tips

Subscribe to motoroladsp



motoroladsp by Keywords

56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Discussion Groups

Discussion Groups | Freescale DSPs | DSP56858EVM, CW6.0 & SDK2.0E

Technical discussions about Freescale (Motorola) DSPs (including the DSP56000, DSP56300, DSP56600, 56800 DSPs).

  

Post a new Thread

DSP56858EVM, CW6.0 & SDK2.0E - thisalfkatz - Mar 4 3:21:00 2004



Have just received my EVM, copy of CW6.0 (patched to 6.0.1) and
SDK2.0E. Following th instructions in the targetting manual, I get
to 1.2.4 Step 3 (execute a buildall on the SDK). Now I get loads of
errors (e.g. multiply defined symbols), and then the build grinds to
a halt compileing one of the security modules. The Motorola site
says I need CW2.0E, the FAE says that CW6.0 replaced that and I can't
get V2.0E anymore. Has anyone else experienced this problem? Is
there a workaround?

The tools work well isolated from the SDK, I got an application
running flashing some leds from interrupts and from a background task.

Any help in getting the SDK up and running would be appreciated.

Cheers,
Alf Katz





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

Re: DSP56858EVM, CW6.0 & SDK2.0E - Kenneth Ciszewski - Mar 5 2:52:00 2004

I tried to send a file "nos.zip" to m...@yahoogroups.com to help t...@yahoo.com  but that site would not accept it due to file size.  If any one else wants a copy, please let me know.

Kenneth Ciszewski <k...@swbell.net> wrote:
I had a similar problem trying to get the audio CODEC driver to work.  Attached are files I was sent to help this problem, along with instructions on where to install them in SDK.

thisalfkatz <t...@yahoo.com.au> wrote:
Have just received my EVM, copy of CW6.0 (patched to 6.0.1) and
SDK2.0E.  Following th instructions in the targetting manual, I get
to 1.2.4 Step 3 (execute a buildall on the SDK).  Now I get loads of
errors (e.g. multiply defined symbols), and then the build grinds to
a halt compileing one of the security modules.  The Motorola site
says I need CW2.0E, the FAE says that CW6.0 replaced that and I can't
get V2.0E anymore.  Has anyone else experienced this problem?  Is
there a workaround?

The tools work well isolated from the SDK, I got an application
running flashing some leds from interrupts and from a background task.

Any help in getting the SDK up and running would be appreciated.

Cheers,
Alf Katz


_____________________________________
/groups.php3








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