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 | 56303EVM connection help

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

  

Post a new Thread

56303EVM connection help - ezeckner - Mar 18 8:34:46 2007



I bought a 56303evm for my senior design and have been having trouble
getting my pc running Suite56 to find the device. I'm used to using
our schools 56311s with Boxview usb.

I have a a 56303evm, a parallel wiggler, and suite56.

I go to the command converter server and select LPT1, listen port
41475(the default). After that I open GDS56300 and I get a "unable to
communicate with default device". I've read through the manuals for
Suite56 and the EVM and have found little to steer me in the right
direction.

I perfectly understand writing and assembling code I'm just having
trouble getting Suite56 to communicate with the hardware.

Any help would be greatly appreciated I'm shooting in the dark right now.

Thanks,
Eric



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

Re: 56303EVM connection help - palm...@hotmail.com - Mar 20 9:32:18 2007

(Sorry, I'm learning english)

Hi Eric,
Is possible GDS56300 doesn't support parallel port driving.
Did you try to use that program under W98?
I use the 56303EVM with EVM30XW debbuger of Domain Technologies using the serial port but under
W98 and it works.

Regards,
Pablo

I bought a 56303evm for my senior design and have been having trouble
>getting my pc running Suite56 to find the device. I'm used to using
>our schools 56311s with Boxview usb.
>
>I have a a 56303evm, a parallel wiggler, and suite56.
>
>I go to the command converter server and select LPT1, listen port
>41475(the default). After that I open GDS56300 and I get a "unable to
>communicate with default device". I've read through the manuals for
>Suite56 and the EVM and have found little to steer me in the right
>direction.
>
>I perfectly understand writing and assembling code I'm just having
>trouble getting Suite56 to communicate with the hardware.
>
>Any help would be greatly appreciated I'm shooting in the dark right now.
>
>Thanks,
>Eric



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

Re: 56303EVM connection help - clan...@gmx.de - Mar 22 7:40:17 2007

Dear Eric,

there may be different reasons why the parallel wiggler doesn't work with your DSP56303EVM
board:

1.) Activate the OnCE/JTAG connection on the EVM board by removing all jumpers populating J4.
This is the External/On Chip Command Converter (OnCE) Select. 

If J4 is populated the DSP56002 and the serial interface is used as command converter. Refer to
page A-6 in the DSP56303EVM User's Manual for the schematic and p. 4-14 (last paragraph) for
the description of the ONCE/JTAG command converter interface. The wiggler can be connnected to
J5. The weird thing is the permanently halfly illuminated 'Debug' LED that is normal since it
is controlled by the DSP56002 that is disconnected now. By the way: if you look to p. A6 again
you may note _how_ this LED is controlled (I never have seen such a bad circuit design
before...).

2.) You must start the Command Converter Server (ccs.exe) before to connect the Suite56
debugger to the target. Otherwise the program will remind you with an error massage or may
simply not start at all.

3.) You must select the proper parallel port for the wiggler using the CCS. Double click on the
icon and use the menu 'file'->'configure' and select 'Parallel' and the correct LPT.

4.) If it does not work so far you have to select the proper memory resources for the parallel
interface. Please refer to the Suite56™ Command Converter Server User’s Guide p. 18 (4.0
Troubleshooting) to configure this resources (the table below is taken from this page):

Table 1. Parallel Port Configuration
LPT Number     Parallel Port
LPT1           0x378
LPT2           0x278
LPT3           0x3BC

Using Windows XP take the 'Device manager', select the parallel port: Right clicking on this
opens a context menue. Select 'Properties' the tab 'Resources' and disable any 'Automatic
Configuration'. Now you can select different resource configurations that start with the proper
address for the selected LPT. But lookout: selecting a configuration that causes an address
conflict may crash your OS :-(. So please look careful for the proper resource addresses before
hitting 'OK'.

Now the whole thing sshould work...

Good luck!

Christian

>I bought a 56303evm for my senior design and have been having trouble
>getting my pc running Suite56 to find the device. I'm used to using
>our schools 56311s with Boxview usb.
>
>I have a a 56303evm, a parallel wiggler, and suite56.
>
>I go to the command converter server and select LPT1, listen port
>41475(the default). After that I open GDS56300 and I get a "unable to
>communicate with default device". I've read through the manuals for
>Suite56 and the EVM and have found little to steer me in the right
>direction.
>
>I perfectly understand writing and assembling code I'm just having
>trouble getting Suite56 to communicate with the hardware.
>
>Any help would be greatly appreciated I'm shooting in the dark right now.
>
>Thanks,
>Eric



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