• Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 541 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.

TAS1020B Firmware Compilation Using uVision4

Henry
Prodigy 50 points

Hi,

I have a question about the Firmware Development Kit available on TI's website.

http://focus.ti.com/docs/toolsw/folders/print/tas1020fdk.html

If I take that firmware, open it in uVision, and simply build it, should the output file, "app116.hex" match the one included in the development kit. I am using uVision4 and it seems like the firmware project was setup in uVision2.

Thanks

Harpreet

 

  • TI__Expert 4160 points

    Harpreet,

    The app116.bin in the FDK has size 5826 bytes.

    When I open the project in uVision3 and rebuild, the resulting app116.bin has size 5598 bytes.

    Someday I may have time to load the two images and see if their behavior is different, but not today!

    Frank

  • in reply to Frank Minich
    TI__Expert 4160 points

    In changing from c51/cx51 8.16->8.17, the Keil compiler changed so that, in the case of the v1.8 application, a succession of 'PUSH' instructions was inserted in devRcode.SRC before the 'ljmp' to the ROM interrupt service routine.  Since the ROM ISR returns via IRET, this results in an incorrect return address and the stack is left inconsistent.  You can modify devRcode.SRC to eliminate the PUSH and POP instructions, and then should be able to use version 8.17a or 8.18 (as I have verified).

    However, in the 8.18->9.0 transition, some additional changes appear to have been made.  I have not yet identified all of the ramifications.

    So, the current recommendation is to use the 8.16a version of the Keil tools.