• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 709 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.

Build TAS1020B_Firmware_v1.8 Application with uVision4

yhf
Prodigy 95 points
Other Parts Discussed in Thread: TLV320AIC3254

Hello,

I'm evaluating the TAS1020B processor with that EVM and uVision4.

On that evaluation, the EVM did not work with the binary that I built from TAS1020BEVM_Firmware_V1.8 on uVision4.

It seems that the situation was caused by the board did not answer the HOST's GET_DESCRIPTOR request.

 

Is there something tips for work with uVision4?

And I attached the .M51 file for the information. If you find the point that something wrong, please advice me.

5556.app116_uV4.zip

  • 0
    TI__Genius 14545 points

    Hibino, 

     

    yo hibino said:
    On that evaluation, the EVM did not work with the binary that I built from TAS1020BEVM_Firmware_V1.8 on uVision4.

         I have not used uVision4, I was able to get APP116 and APP124 working just fine (but I have uVision3).

         One thing to note, is that when I compile the source code with uVision3, I receive a different binary size than what is included in the FDK - however the result works.

     

         Have you tried loading the included APP116 binary in the FDK to verify that the board is working correctly? If not, I would recommend trying this first.

     

  • 0 in reply to dabuan
    Prodigy 95 points

    Drew,

    Thank you for your advice and sorry for late my reply.

     

    Finally I've got to resolve the problem.

    The problem caused by that the "DevRCode.c" file and "DevRCode.SRC" file are existing on the project.

    The binay got to work fine when I remove the "DevRCode.c" file from the project.

     

    I'm not sure why the two files are existing one project, but there are assigned on the project defaultly when open the FDK with uVision4.

  • 0 in reply to yhf
    Prodigy 160 points

    Hi Yo Hobino,

    I am facing the same problem.

    I am have my own designed hardware containing TAS1020B and TLV320AIC3254 chips. I am also using uVision4 and working on FDK v1.8.

    I tried using the original/default binary APP116.bin in the FDK directory with my hardware and it works i.e my gets enumerated as USB composite Device.

    But when I use the compiled binary instead of APP116.bin, I don't see any enumeration happening with my hardware.

    I have tried removing the 'DevRCode.c' as suggeted above, but still no luck with enumeration :(

    Can you please let me know the detail settings done by you for uVision4 and FDK v1.8 compilation.

    Regards,

    Brontok

     

     

  • 0 in reply to Shriyash Chougule
    TI__Expert 4160 points

    Brontok,

    Just to make sure:  you have made _no_ changes to _any_ files, and yet cannot build a working app116.bin from the FDK?

    You get no warning messages as you build?

    What is your build platform's OS?

    That you can't build a working version of app116 nor try6 could indicate a uVision4 problem (which I am pursuing) or something else (of which I have no idea as of now).

    Regards,

    Frank 

  • 0 in reply to Shriyash Chougule
    Prodigy 95 points

    Hi Brontok

    I've already forgotten the detail about that problem... But, I attach the uvproj and uvopt file that I used.

    It might be work just only add to the original FDK v1.8 project. Please try this, and compare with your project.

    4377.App.zip 

     

  • 0 in reply to Frank Minich
    Prodigy 160 points

    Frank,

    Frank Minich said:
    Just to make sure:  you have made _no_ changes to _any_ files, and yet cannot build a working app116.bin from the FDK?

    True, no changes made to any files and yet I cannot build a working app116.bin nor a working try6.bin

    Frank Minich said:
    You get no warning messages as you build?

    1512.build_window_output.txt

    I do get warnings as I build but _no_ errors. I have attached the 'build window output' I get while compiling using uVision 4, I don't find these warnings critical.

    Frank Minich said:
    What is your build platform's OS?

    It is Windows XP SP3, 32 bit OS.

    Frank Minich said:
    That you can't build a working version of app116 nor try6 could indicate a uVision4 problem (which I am pursuing) or something else (of which I have no idea as of now).

    However, I tried compiling using uVision3 and the binaries generated out of it i.e. app116 and try6, worked fine. So, it seems to me that there is compatibilty issue between uVision4 and its predecessors. 

    Regards, Brontok.

     

     

  • 0 in reply to Shriyash Chougule
    TI__Expert 4160 points

    Brontok,

    Thanks much for this additional information. 

    Until I can get a legal version of uVision4 working here, I'm stalled on this thread.  For some reason even though the PSN was successfully used to install uVision3 on this PC, trying to license the same PSN on this (same) PC for uVision4 fails, indicating that the license is already installed on a different PC.  I've sent an email to Keil Support asking for assistance.

    Regards,

    Frank

  • 0 in reply to Frank Minich
    TI__Expert 4160 points

    Brontok,

    I have been able to build the app116 application successfully using c51/cx51 up to and including version 8.16a.

    Starting with 8.17, Keil made a slight change to the compiler, so that the devRCode.c file is compiled incorrectly.  You can see what's going on if you look at devRCode.SRC - a context save is performed before the long jump is performed (and that doesn't work because the code to which the long jump redirects ends with a RETI).

    I suggest using Keil tools version 8.16a or earlier.

    Regards,

    Frank