This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AIC3254 and GPIO



Hi,

I'm trying to make a Signal to the GPIO Pin. I used the Basic DSP GPIO Output Box, but when compiling Purepath means
Error: Cannot find the template file: Gpio_Output.asmx
What do I wrong?

Micky

  • Micky:

    In the following directory "C:\Program Files\Texas Instruments Inc\PurePath Studio Portable Audio\ComponentCache\Gpio_Output_TI_v1" there should be a file called Gpio_Output.asmx? If it does not exist you will get this error. Can you verify it exists in this directory?  What version of PPS are you using?  You can check using the Help/About menu.

    Brent

     

  • Hi Brent,

    i've checked this - the file is missing. I'm using version 4.10 build 2 revision 9285 as a "fresh" install.

    Micky

  • Hi Brent,

    can you please provide me the missing file?

    Thanks in advance.

    Micky

  • Micky:

    Send me your email address and I will forward this component to you.

    Brent

  • micky42@gmx.de

  • Hi Brent,

    Can you please send me the missing file too?

    I am using Version 4.10 build 2 revision 9120.

    My email address is hpcc@ust.hk

    Thanks

    Horace

  • I currently working with the GPIO and Purepath 4.80 build 1. 

    The GPIO is connected to a comparator as shown above. Principally this example works. When changing C_to_D_1 or C_to_D_2, the signal will toggle as expected. At least I can observe it with the Probe Point Tool of PPS.

    I'm facing two problems:

    1. But when I observe the real world GPIO Signal, I can see this Signal changing from high to low and vice a versa as expected. But when high, there will be a short low impulse every 460 Hz being low for 16.5µs.
    2. In my real world application C_to_D_2 is replaced by the SMDet (speech detector). This works at least when observing the Probe Points (means the signal GPIO_Probe alters from 0 to 1 if speech is detected), but the GPIO stays high all the time (with the exception, that there is a low impulse for 16.5µs  every 460Hz).

    What do I wrong here?

    Additionally, if I want to read the probe points by hand with the I2C Memory tool, I don't see them changing (The seem to stay at the initial value). How can I change this?

    Thanks in advance

    Micky

     

  • To answer the last question by myself: I found http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/70292/254785.aspx#254785.

    So now just point 1 and 2 are not clear.

    Micky

  • Mickey:

    I am not sure I follow what you are seeing at the GPIO pin.  Can you provide a graph from a scope or logic analyzer?  Note that the GPIO Out component directs an interrupt (1 or 2) to an output pin (GPIO, DOUT, MISO) and will always be a series of pulses.  From the Technical data sheet (SLAS549A–SEPTEMBER 2008–REVISED OCTOBER 2008): Section 5.22.2:

    These interrupt signals can either be configured as a single pulse or a series of pulses by programming Page 0, Register 48, D(0) and Page 0, Register 49, D(0). If the user configures the interrupts as a series of pulses, the events will trigger the start of pulses that will stop when the flag registers in Page 0, Register 42, 44 and 45 are read by the user to determine the cause of the interrupt.

     Page 0, Register 48, D(0):

    Page 0, Register 49, D(0):

    Each pulse should be 2 ms (i.e. 460Hz).  I am not sure if that is what you are seeing or not, but it sounds like it.  Please confirm.  Thanks!  I’m sorry I do not know the answer to your Probe Point question right now.  I will get back to you soon with an answer.

    Best Regards,

     

    Brent Karley

    Texas Instruments, Inc.

  • Hi Brent

    >Each pulse should be 2 ms (i.e. 460Hz)

    Oh, that is what I observe. Well I just used the GPIO Module and thought it was a "normal" GPIO. Perhaps, as the reading of the flags 42/44/45 is not done by my system, the GPIO stays at high output (with the exception of the event re-triggering).

    It would be great, if the input goes to high the output at the pin is high also and vice a versa just as a normal GPIO Pin of a processor.

    Micky.