• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 526 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.

FFT document SPRABB6 missing information

Ed Bryant
Prodigy 190 points

Just to let you guys at TI know there is some missing information in SPRABB6 section 4.5, the example to add lines to the CMD file for HWAFFT use is missing.  Could you post the missing information on the forum for us.

Ed

  • 0
    TI__Mastermind 30380 points

    Hi Ed,

    Thanks for pointing out this omission in the HWAFFT Appnote (SPRABB6). Here's the missing information from Section 4.5: Project Configuration for Calling Functions from ROM:


    Add the following lines to the bottom of the project’s linker CMD file and remove the hwafft.asm file from the project (or exclude it from the build). When the project is rebuilt, the HWAFFT functions will reference the ROM locations. The HWAFFT ROM locations are different between VC5505 (PG1.4) and C5505/C5515 (PG2.0). ROM locations for both device families are shown below:

    /*  VC5505 (PG1.4)  */
        _hwafft_br            = 0x00ff7342;                            
        _hwafft_8pts        = 0x00ff7356;                            
        _hwafft_16pts        = 0x00ff7445;                            
        _hwafft_32pts        = 0x00ff759b;                           
        _hwafft_64pts        = 0x00ff78a4;                            
        _hwafft_128pts        = 0x00ff7a39;                            
        _hwafft_256pts        = 0x00ff7c4a;                            
        _hwafft_512pts        = 0x00ff7e48;                            
        _hwafft_1024pts        = 0x00ff80c2;                            
               
    /*  C5505/C5515 (PG2.0)  */

        _hwafft_br            = 0x00ff6cbe
        _hwafft_8pts        = 0x00ff6cd2
        _hwafft_16pts        = 0x00ff6dc1
        _hwafft_32pts        = 0x00ff6f17
        _hwafft_64pts        = 0x00ff7220
        _hwafft_128pts        = 0x00ff73b5
        _hwafft_256pts        = 0x00ff75c6
        _hwafft_512pts        = 0x00ff77c4
        _hwafft_1024pts        = 0x00ff7a3e

    [EDIT - REPLACED INCORRECT PG2.0 ROM ADDRESSES WITH CORRECTED ADDRESSES]

    /*  C5505/C5515 (PG2.0)  */

        _hwafft_br = 0x00ff6cd6;
        _hwafft_8pts = 0x00ff6cea;
        _hwafft_16pts = 0x00ff6dd9;
        _hwafft_32pts = 0x00ff6f2f;
        _hwafft_64pts = 0x00ff7238;
        _hwafft_128pts = 0x00ff73cd;
            _hwafft_256pts = 0x00ff75de;
            _hwafft_512pts = 0x00ff77dc;
            _hwafft_1024pts = 0x00ff7a56;


    We'll put this material back into the HWAFFT Appnote in the next revision.

    Thanks,
    Mark

  • 0 in reply to Mark M
    TI__Mastermind 30380 points

    Hi Ed,

    In another post, it was revealed that the C5505/C5515 (PG2.0) ROM addresses are incorrect both in my previous post above and in the SPRABB6 HWAFFT App Report.

    The corrected Addresses are listed below:

    /*  VC5505 (PG1.4)  */

        _hwafft_br = 0x00ff7342;                           
        _hwafft_8pts = 0x00ff7356;                           
        _hwafft_16pts = 0x00ff7445;                           
        _hwafft_32pts = 0x00ff759b;                          
        _hwafft_64pts = 0x00ff78a4;                           
        _hwafft_128pts = 0x00ff7a39;                           
        _hwafft_256pts = 0x00ff7c4a;                           
        _hwafft_512pts = 0x00ff7e48;                           
        _hwafft_1024pts = 0x00ff80c2;    

    /*  C5505/C5515 (PG2.0)  */

        _hwafft_br = 0x00ff6cd6;
            _hwafft_8pts = 0x00ff6cea;
            _hwafft_16pts = 0x00ff6dd9;
            _hwafft_32pts = 0x00ff6f2f;
            _hwafft_64pts = 0x00ff7238;
            _hwafft_128pts = 0x00ff73cd;
            _hwafft_256pts = 0x00ff75de;
            _hwafft_512pts = 0x00ff77dc;
            _hwafft_1024pts = 0x00ff7a56;

    I apologize if these erroneous addresses caused you (or anybody) significant frustration. I am in the process of updating that app report.


    Thanks,
    Mark