DSPRelated.com
Forums

configuring dip switch in dsk6713

Started by PVN May 5, 2008
Hey , we are a group of 4 ec students working on a project which deals
with creating delay based music effects using dsk 6713. We want to use
the dip switches for user interface (to decide which effect). But we
are having trouble coding the interface part. Can anyone give us an
idea about how we should go about coding  of the switch functions? Any
tutorial or help that can tell us how to code dip switch interface?

PVN wrote:
> Hey , we are a group of 4 ec students working on a project which deals > with creating delay based music effects using dsk 6713. We want to use > the dip switches for user interface (to decide which effect). But we > are having trouble coding the interface part. Can anyone give us an > idea about how we should go about coding of the switch functions? Any > tutorial or help that can tell us how to code dip switch interface?
Do you know how to read the switch settings? How many switches are there? How many effects do you want to choose among? (With 4 switches, you could encode up to 16 effects.) Jerry -- Engineering is the art of making what you want from things you can get. �����������������������������������������������������������������������
hi,

If your question is:
"Can anyone give us an
>idea about how we should go about coding of the switch functions?"
Coding of the switch functions, are you using CCS for your C6713 dsp? i have not worked on the 6713dsk, but if you have managed the hardware part which i suppose, would be using the gpio pins in the c6713? writing code for the gpio pins is not difficult as there are a lot of APIs which can be used straightaway in you c code... aps
>Hey , we are a group of 4 ec students working on a project which deals >with creating delay based music effects using dsk 6713. We want to use >the dip switches for user interface (to decide which effect). But we >are having trouble coding the interface part. Can anyone give us an >idea about how we should go about coding of the switch functions? Any >tutorial or help that can tell us how to code dip switch interface? > >
On May 5, 11:41 am, "aaac111" <aaac...@gmail.com> wrote:
> hi, > > If your question is: > "Can anyone give us an > > >idea about how we should go about coding of the switch functions?" > > Coding of the switch functions, are you using CCS for your C6713 dsp? i > have not worked on the 6713dsk, but if you have managed the hardware part > which i suppose, would be using the gpio pins in the c6713? writing code > for the gpio pins is not difficult as there are a lot of APIs which can be > used straightaway in you c code... > > aps > > >Hey , we are a group of 4 ec students working on a project which deals > >with creating delay based music effects using dsk 6713. We want to use > >the dip switches for user interface (to decide which effect). But we > >are having trouble coding the interface part. Can anyone give us an > >idea about how we should go about coding of the switch functions? Any > >tutorial or help that can tell us how to code dip switch interface?
well, where can we get those APIs? :)
On May 5, 11:00 am, Jerry Avins <j...@ieee.org> wrote:
> PVN wrote: > > Hey , we are a group of 4 ec students working on a project which deals > > with creating delay based music effects using dsk 6713. We want to use > > the dip switches for user interface (to decide which effect). But we > > are having trouble coding the interface part. Can anyone give us an > > idea about how we should go about coding of the switch functions? Any > > tutorial or help that can tell us how to code dip switch interface? > > Do you know how to read the switch settings? > > How many switches are there? > > How many effects do you want to choose among? (With 4 switches, you > could encode up to 16 effects.) > > Jerry > -- > Engineering is the art of making what you want from things you can get. > &#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;
4 switches are available in th kit.. we would like to encode min 4. but we are encountering some difficulties while trying to program 'em.
The switches and LEDs are mapped through the CPLD.  The CPLD is at
address 0x90080000.  The CPLD is defined with 4 - 8 bit registers at
offset 0,1,4, and 6.  The 0 offset register has the bits for the LED
and switches, the LEDs are the 4 lsb bits and the switches are the 4
msb bits.

Also there is a library with a bunch or hardware interface functions
(either installed with CCS or Spectrum Digital software).
DSK6713_DIP_get(switch_num)
DSK6713_LED_on(led_num)
DSK6713_LED_off(led_num)

Believe these functions are available in the dsk6713bsl.lib,

ya we knew abt the switches' functions as u mentioned. But we faced
sum problems. We planned on using the interrupts to configure the
switch positions instead of polling. Now when we use inerrupts a new
prob arise - we have to configure software interrupts.we havent yet
figured out how to configure the software interrupts. Now thats the
present position we are in. Any help with regard to configuring
software interrupts?

Thanks for letting us know abt th functions :)


On May 6, 7:14&#4294967295;am, PVN <vivaciousp...@gmail.com> wrote:
> ya we knew abt the switches' functions as u mentioned. But we faced > sum problems. We planned on using the interrupts to configure the > switch positions instead of polling. Now when we use inerrupts a new > prob arise - we have to configure software interrupts.we havent yet > figured out how to configure the software interrupts. Now thats the > present position we are in. Any help with regard to configuring > software interrupts? > > Thanks for letting us know abt th functions :)
Do you mean "We planned to read the switch positions from within an interrupt service routine"? Software interrupts are very easily configured using DSP/BIOS. If you are not already using it, it might be worth looking at.
PVN wrote:
> ya we knew abt the switches' functions as u mentioned. But we faced > sum problems. We planned on using the interrupts to configure the > switch positions instead of polling. Now when we use inerrupts a new > prob arise - we have to configure software interrupts.we havent yet > figured out how to configure the software interrupts. Now thats the > present position we are in. Any help with regard to configuring > software interrupts? > > Thanks for letting us know abt th functions :)
"we faced sum problems": Why do you need to add? Plan better. Software interrupts allow the running program to use the processor's interrupt mechanism to execute a jump. The program does software interrupts, not the switches. If something -- hardware interrupt, polling, black magic -- doesn't look at the switch, how will the program "know" to execute the the software interrupt? To quote our friend Vladimir, "muddle headed." Jerry -- Engineering is the art of making what you want from things you can get. &#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;&#4294967295;
hi,

>interrupts to configure the switch positions instead of polling
are you going to write the software interrupts to poll the switches? or to configure the switches? under what conditions will the interrupt routine be called? i suppose, that is not what we write interrupts for... what is ec? In other TI DSPs (i do not know about the 6713dsk) there are GPIO pins which can also be configured as external interrupt pins. but for that you need to put the hardware in order, so that the switch output is correctly given to the GPIO pins. aps
> >ya we knew abt the switches' functions as u mentioned. But we faced >sum problems. We planned on using the interrupts to configure the >switch positions instead of polling. Now when we use inerrupts a new >prob arise - we have to configure software interrupts.we havent yet >figured out how to configure the software interrupts. Now thats the >present position we are in. Any help with regard to configuring >software interrupts? > >Thanks for letting us know abt th functions :) > > >