drivig1977,
On 12/14/07, d...@yahoo.es wrote:
>
> Hi.
>
> I'm trying to connect my dsk6713 to a THS1206EVM through a 5-6k board.
> I've followed the slaa210a.pdf document but I couldn't get anything.
The
> jumpers of the boards are in their default position except for the one of
> the 5-6k board that chooses timer 1 for the conversion clock.
>
> The data converter plug-in settings are:
>
> -DSP settings tab:
>
> DSP: TMS320C6713BGDP
> CLOCK: 225(MHz)
> No Dispatcher
>
> -THS1206 settings tab:
>
> Address: 0xA0000000
> Shift:0
> DSP interrupt: EXT_INT_5
> Clock Source: Timer1
> Channel Select: Autoscan 2 single ended
> Trigger Level: 12
>
> -DSP/BIOS settings:
>
> HWI_INT5: _DMAISR
> HWI_INT8:_DCPDISP_dispatchEdmaIsr
>
> The main.c file is the same as the one in the getting started with data
> converter plug-in document. The program fails when it tries to configure
the
> A/D converter.
>
> If someone could tell me what I'm doing wrong or give some code running
I
> would thank it a lot.
I suggest using your debugger [CCS] to see what is going on.
Your A/D is supposed to be at address 0xA0000000. Try reading and writing
some of the registers.
Also check the 'CE2/3' routing on the adapter board with the 6713
daughtercard pinout. It has been a long time since I used the adapter, but I
think that there was a jumper relating to that. If someone else is running
that configuration, maybe they will respond.
Anytime that I add new hardware to a configuration, I prefer to [1]crawl,
[2] walk, then [3] run.
1. crawl - verify that the CPU can 'see' the new device. This can be
done by
using the CCS edit memory function to read write/write the hardware
addresses.
2. walk - write a simple program that performs very basic I/O using polling.
You just write the simplest program to exercise the peripheral. Once this
works, you can expand the program to do something with the data [I would
call this a fast walk].
3. run - now that the hardware is known to work and you know how it works,
you can expand it to perform its intended purpose. This is the point where
you start using interrupts and getting your app working. It seems that this
is where you are trying to start - and when it doesn't work you have too
many unknowns to know where to look for a solution.
mikedunn
Thanks in advance.
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
