• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 33 subscribers
  • Views 712 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiling the TAS1020B sample code

Rich B
Prodigy 110 points

Other Parts Discussed in Thread: TLV320AIC33

Afternoon engineers

I'm working with a TAS1020B evaluation board. The board's really nice, I like it, it does some lovely things.

However my headaches begin with compiling and running the Firmware Development Kit sources, which are the basis for a TAS1020B project. Basically I cannot for the life of me get the code to run past the while loop at line 129 of device.c. So, for me, for some reason, the FDK sources arn't working. I've tried numerous compiler option changes (as well as compiling it straight from the zip file of course) all to no avail and more headaches.

I'm reaching out to someone out there (I know you're there somewhere) for a working base code setup that you've got of the TAS1020B example code, that you've seen working and then built on. Just something that I can then build my stuff on, and eventually work out why my vanilla sources arn't working.

The only thing that definitely works for me on my eval board is the firmware that shipped inside of it, and a firmware image from TI's consultants InDesign, which apparently is the shipped firmware. Which means that i'm struggling to evaluate the the actual chip!

Hope someone can help.

Many more details available on request. Please ask.

 

Rich

  • 0
    Prodigy 110 points

    Attached is my base source tree (completely unmodified sources from TI). What is modified is that the build output goes into the ./build directory, not the root.

    Only the app116 target is configured for this.

    Could someone try this code out, by unzipping it and opening with uVision3 with Keil compiler and giving it a whirl in the eval board. It ought to function exactly as the eval board does as shipped.

    Cheers

    Rich

  • 0 in reply to Rich B
    Prodigy 110 points

    We are having similar problems with a TAS1020B based product (in combination with the TLV320AIC33 codec).  The sample code that came wih the EVM runs fine if you use the precompiled binaries.  In fact, we can even take the pre-compiled hex files and run the hex2bin and header programs and get that to function beautifully.

     

    However, using the Keil compiler to generate the hex file leaves us unable to communicate via USB with the chip until we load the precompiled code again.

     

    After working some with the TI folks, we have compared Keil version numbers and we are using a more up-to-date version of the compiler (v3.4).  Other than that, we've compared project settings.  We're really stumped and would love it if someone could show us the path to getting this working.  Thanks.

     

    Eric Wachsmann

    FlexRadio Systems

  • 0 in reply to Eric W
    Prodigy 110 points

    Finally after 6+ weeks of trying to get this firmware up and moving, I have an answer to why it wasnt working for me.

    I downloaded the _only_ code that was available from the TI website. This happened to be version 1.8.

    After significant time spent with InDesign, who's final contribution was a codebase of the eval firmware that I could compile and run. The difference I found between the TI site version and theirs was some memory map things.

     

    Just gona ask the guy who gave me it if I can release it on here for the public at large to enjoy.

     

    Rich

  • 0
    TI__Expert 4160 points

    Rich,

    Sorry about not seeing your post till today.  Thought I was checking all the potential TAS1020B posting areas, but I guess not.

    Anyhow, could you please identify the loop that the code isn't getting past?  The source that I have from V1.8 of the FDK shows a blank line at line 129.

    This loop precedes it:  is it the one you are talking about?

    │        // wait till codec inited
    │    DevAmpCounter = 1500;
    │        while (AppDevice.configSetting == 0)
    │       devCheckReset();
    │    DevAmpCounter = 0;

    I unzipped the FDK, built, and the resulting bin did work, so I am also interested in whatever the difference is between the version I have and you have.

    Thanks,

    Frank

  • 0 in reply to Rich B
    Genius 3945 points

    "Just gona ask the guy who gave me it if I can release it on here for the public at large to enjoy."

    Any chance of this happening?