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.

  • TI Thinks Resolved

CCS/TMDX5535EZDSP: TMDX5535eZdsp

Part Number: TMDX5535EZDSP

Tool/software: Code Composer Studio

Hi,

I am trying to follow the step by step instruction on this document to build and test the speech recognition software but I get many errors.

Here is the link to the document:

http://www.ti.com/lit/ug/tidubj5a/tidubj5a.pdf

When I try to build the the TIESRdemoC55 then I get the following errors:

<Linking>
"../C5535.cmd", line 18: error #10263: MMR memory range has already been
specified
"../C5535.cmd", line 18: error #10264: MMR memory range overlaps existing
memory range MMR
"../C5535.cmd", line 19: error #10263: DARAM0 memory range has already been
specified
"../C5535.cmd", line 19: error #10264: DARAM0 memory range overlaps existing

Do you have any solution? What is the correct step?

  • In reply to Lalindra Jayatilleke:

    Hello Lali,

    Yes, all I am doing is capturing audio on the Bluegiga and passing it to the C5535 via I2S1 for the recognition. 

    Since Bluegiga clock is at 16 KHz then I thought to follow the steps in this Forums. I just wanted to make it to work with Codec I2S2 first before connecting the Bluegiga. 

    e2e.ti.com/.../1952595

    When I followed the steps except (changing the codec gain), the voice recognition doesn't work anymore. 

    Would you please let me know how to make the changes first that works with Codec at 16KHz?

    Thank you for your support. 

  • In reply to farzin dinyarian64:

    Farzin,

    Were you able to make any progress?
    Are you able to use 8KHz sampling on the Bluegiga instead of 16KHz?

    Lali
  • In reply to Lalindra Jayatilleke:

    Hello Lali,

    No, I didn't make any progress. 

    Our current setup with BlueGiga is at 16Khz, I can't do at 8 KHz. 

    Would you please just let me know if these changes work with current setup? I made the changes but it doesn't recognize anything. 

    e2e.ti.com/.../1952595

    Thank you.

  • In reply to farzin dinyarian64:

    Farzin,

    As mentioned earlier, I'm not sure how well TIesr would work at 16KHz since its not supported in the default demo.

    However, let me try to assist based on the Sensory (third party) demo that we typically recommend customers to build their voice trigger systems with. Attached is a .out file that you can run on the ezdsp5535 assuming you have the I2S1 lines connected to your secondary device that does the audio capture. This .out was tested on my end with a C5517 EVM  that has a linear microphone array connected. The audio captured on the C5517 is then be piped (via I2S) to the ezdsp5535 for the keyword recognition. In this case, the keyword is "Hello Blue Genie".

    The Sensory library is provided as a 30-day trial at http://software-dl.ti.com/dsps/dsps_public_sw/dsps_swops_houston/C55X/Sensory-THF/latest/index_FDS.html Contact Sensory if you need to use this library in your product and they can work with you on the licensing. http://www.sensory.com/

    Below is a diagram of the demo. A video is also attached. This will at least enable you to show-case the keyword recognition on the ezdsp5535 with audio coming from your BlueGiga device. Keep in mind that the audio will have to be presented to the ezdsp5535 as 16KHz sampling. I2S1 on the ezdsp5535 is SLAVE.

    In the video, you will see that the P3 header was used on the ezdsp5535 to connected the I2S1 lines. You can also use the edge connector P2. Note the way the ezdsp5535 is armed by pressing the SW2 button once the .out is loaded. Please excuse the untidy wiring of the HW pic, did not get a chance to clean it up.

    Please try this .out in your system.

     /cfs-file/__key/communityserver-discussions-components-files/109/SensoryDemoC55.out

    /cfs-file/__key/communityserver-discussions-components-files/109/demo_5F00_vid_5F00_HBG.mp4

    Lali

  • In reply to Lalindra Jayatilleke:

    Hello Lali,

    Thank you so much for your last update. I actually tested the Sensory code with my Setup BlueGiga connected to TI over I2S1 and it worked great. 

    I am just wondering if you could compare the sensory code with TI code and let me know what are the changes to make it working at 16KHz. I am not sure if we could use Sensory solution at this time but we are very interested in using TI solution if it supports 16KHz. The TI documentation suggests that it should support 16KHz but it doesn't work when I change the sampling rate. 

    I would really appreciate your support. It would be a great Holiday gift for me. 

    Thank you.

  • In reply to Lalindra Jayatilleke:

    Hi Lali,

    Thank you for sending the binary image of the Sensory implementation on the CC5535 EzDSP on the Speech Recognition EVK.  I have a few questions regarding the I2S waveforms.

    The waveform below is from the unmodified 8KHz implementation showing the I2S waveform between the Codec and CC5535 chip.

    As you can see, both left and right channels contain audio data.  If the audio stream is mono, why is there data in the Right channel?  Also, each channel contains 32 bit-clocks.  Is the audio data 8-bit or 16-bit?  Based on where I think the LSB is, to me it looks like 16-bit data?  Is this correct?  Where is the MSB?  Should it be the left-most bit, one-bit delayed after the falling-edge of Word-Select?

    The below waveform is from the modified 16-KHz implementation feeding the Sensor speech recognition engine in the CC5535.

    In this case, there is once again, audio data in both the Left and Right channels.  Also, there are 24 bit-clocks in each channel instead of 32 as in the previous example.  Once again, is the audio data 8-bit or 16-bit in this case?  If the MSB is one bit delayed from the falling-edge of Word-Select, then it appears there are 16-bits per audio sample.  Is this correct?

    Thanks for your help on this and Merry Xmas and Happy new year. 

  • In reply to farzin dinyarian64:

    Farzin,

    This is stereo data, so not sure why you were expecting mono.
    The far left most bit is the MSB, so the data is left adjusted 16-bit.

    Not sure why there is a delta between your bit clocks (32 vs 24). This is coming from the codec or whatever device is clocking your I2S, so perhaps you dont have something configured correctly.

    Lali
  • In reply to farzin dinyarian64:

    Hello,

    I have the same problem here. Here is the error that I am receiving.
    /usr/bin/ld: cannot find -lTIesrFA_ALSA
    The make file doesn't have any Linux env.
    # Specify use of windows Cygwin gcc tools if building for Windows
    $(WINCONFS) : WINTOOLS=CC=gcc.exe CCC=g++.exe CXX=g++.exe AS=as.exe CND_PLATFORM=Cygwin-Windows
    $(LINUXCONFS) : WINTOOLS=

    Would you please share your make file which has LinuxConfi?

    Would also share your path on your Linux box please?

    Thank you so much in advance for your support.
    Mahsa
  • In reply to Mahsa Sasani:

    Dear Sirs,

    Would you please attach your project that builds on your Linux Ubuntu system including the Make File? 

    Would you please also send me the PATH that needs to be included? 

    Thank you,

    Mahsa

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.