• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 652 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.

CCS/PGA900: PGA900 DEBUG ERR

chennangan
Intellectual 750 points
Part Number: PGA900

Tool/software: Code Composer Studio

Simulation with  PGA900 by XDS200, program execution, PC did not step by step, not by c language

WHY?

When i build  project ,such warning appear.

  • 0
    TI__Guru**** 249420 points

    I can only help with the warnings you see when building the project.  To explain what I happened, I need to reproduce it.  To help with both of those warnings, I need the CCS project.  Please zip up the project according to the directions in the article Sharing Projects, then attach that zip file to your next post.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 750 points

    PGA900FirmwareGeneric-1p5.rarI use the TI example project ( PGA900FirmwareGeneric-1p5.rar).

    I am using PGA900EMV development board and Code Composer Studio v7.3.0.00019. I want to use XDS200 USB JTAG emulator to program PGA900.

     PGA900 Software Quick Start Guide (SLDU015A) suggest me use Code Composer Studio v5.5.0.00077

  • 0
    TI__Guru**** 249420 points

    Unfortunately, I am unable to reproduce the errors.  I can give you a general explanation of these errors, but not a specific recommendation for a fix.

    Regarding the first warning about the variable i ...  That is saying you have a source line similar to ...

        int i;

    But the rest of the function never uses the variable i.  To avoid the warning, remove the declaration of i.

    Regarding the second warning about section was padded by 2 ... This comes from the hex utility.  The text section must be of size 2518 bytes, which is not a multiple of 4.  So 2 bytes of padding are added to the end.  One way to avoid this warning is to apply the palign directive to the section text in the linker command file.  Read more about palign in the ARM assembly tools manual.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 750 points

    hello George。

    I find the error,

    It cause by code composer studio→Optimization.

    When I turn off optimization level and Speed vs. size trade-offs to 0,it work well.

    Then  I  have another question .

    How to  get EEPROM_Default_Tcoeff(EEPROM_H0_Integer  to EEPROM_N2_Integer) with  

    Data as following.

    　Pressure/temperature
    		0(MPA) 10(MPA) 20(MPA) 30(MPA) 40(MPA) 50(MPA)
    3478 18.08.30        27.5℃ 0.440mv(output) 6.675mv 12.903 19.122 25.333 　
    0.430 6.656 12.870 19.072 25.269 31.457
    0.429 6.652 12.865 19.072 25.268 　
    0.418 6.620 12.812 18.994 25.168 31.289
    0.419 6.629 12.829 19.019 25.203 　
    0.417 6.611 12.794 18.968 25.133 31.289
    18.08.30        100℃ 0.417 6.608 12.791 18.965 25.132 　
    0.414 6.589 12.755 18.910 25.057 31.196
    0.416 6.599 12.773 18.938 25.095 31.196
    18.08.30        110℃ 0.414 6.585 12.752 18.910 25.053 　
    0.413 6.569 12.714 18.849 24.975 31.092
    　 　 　 　 　 　
    18.08.30        120℃ 0.410 6.565 12.710 18.846 24.973 　
    0.410 6.567 12.713 18.847 24.973 31.091
    0.410 6.566 12.712 18.847 24.973 31.091
    18.08.30        130℃ 0.411 6.563 12.707 18.845 24.972 　
    0.412 6.566 12.708 18.847 24.972 31.09
    0.412 6.565 12.708 18.846 24.972 31.09
    18.08.30        140℃ 0.411 6.562 12.707 18.843 24.970 　
    0.403 6.538 12.662 18.774 24.880 30.974
    0.407 6.550 12.685 18.809 24.925 30.974
    18.08.30        150℃ 0.398 6.530 12.654 18.771 24.876 　
    0.373 6.484 12.586 18.679 24.759 30.830
    0.367 6.473 12.576 18.669 24.753 　
    0.370 6.479 12.581 18.674 24.756 30.83
    　 　 　 　 　 　
    　 　 　 　 　 　
    18.08.30        160℃ 　 　 　 　 　 　
    　 　 　 　 　 　
    18.08.30        170℃ 　 　 　 　 　 　
    　 　 　 　 　 　
  • 0 in reply to chennangan
    TI__Guru**** 249420 points

    user4677916 said:
    When I turn off optimization level and Speed vs. size trade-offs to 0,it work well.

    It is likely this change only masks the problem.  Now the size of the code is a multiple of 4 bytes.  This happens by chance, and not by design.  I suspect the problem could return at any time.

    user4677916 said:
    How to  get EEPROM_Default_Tcoeff(EEPROM_H0_Integer  to EEPROM_N2_Integer) with  curve fitting 

    I'm sorry, but I know so little of what you mean, I am unable to refer you to the correct expert.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 750 points

    I mean How to obtain parameter（h0,h1,h2;g0,h1,g2;n0,n1,n2）of the second-order TC compensation on the file pga900_app.c;
    Such parameter is present in EEPROM_Default_Tcoeff just as an example routine,
    In the sample compensation algorithm in practical application,I need calculate those parameter by curve fitting ;
    How to curve fitting In the table above?

  • 0 in reply to chennangan
    TI__Guru**** 249420 points

    user4677916 said:
    How to curve fitting In the table above?

    I'm sorry, but I don't know.  I recommend you begin a new thread in the sensors forum.

    Thanks and regards,

    -George