• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 16 subscribers
  • Views 981 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.

Original question:

CCS/RF430FRL152H: CCS coding issue (Printf)

CCS/RF430FRL152H: UART issue

hyosung kim
Intellectual 550 points
Part Number: RF430FRL152H
Other Parts Discussed in Thread: MSP-EXP430G2ET, , , MATHLIB

Tool/software: Code Composer Studio

I want to connect MSP-EXP430G2ET and TRF7970ABP as a reader and read the ADC0 value of RF430FRL152H-Patch.
Because E2E community recommended a method called UART, I want to use it. Which of these codes do I need to read?

++Modified.

I downloaded anything, then imported.
And I ran it like a picture, and while it was being debugged, there was no output.
Is this normal?
I want the printed value. What should I do?

  • 0
    Intellectual 550 points

    + Additional questions
    What function must be entered to output the ADC0 value of RF430FRL152H?!

    And I'd like to print out the results of the ADC0 in the form that I made.
    Is that possible?

  • 0
    TI__Guru*** 135355 points
    Hello Hyosung,

    The simplest way would be to use the RF430FRL152HEVM EVM GUI with your kit. You can see how to do this outlined in Section 1.4 of our RF430FRL15xH FAQ Guide: www.ti.com/.../sloa247

    Alternatively if you are using the RF430 Temperature Sensing Patch, you can use a different LaunchPad to get the data on an LCD screen which you could instead send over UART as well: www.ti.com/.../sloa233
  • 0 in reply to Ralph Jacobi
    Intellectual 550 points
    Of course I've already done it in that way.
    But I need a different formula. This is because another sensor will be connected to ADC0.
  • 0 in reply to hyosung kim
    TI__Guru*** 135355 points
    Hello Hyosung,

    First off, that was not stated anywhere in your post so I had no idea.

    If that is your requirement, then first off, the MSP430 examples won't help much, they just show basic UART functionality.

    I can help you further now that I understand your requirement more, but you will need to do some leg work on your end as well.

    I have an example of SLOA233 ported to the MSP-EXP430G2ET that will let you get UART output of the Temperature Result, and I will provide that later today, I just want to validate it works correctly first.

    However, that still is based on our EVM's temperature sensor.

    What you need to do is adapt what I am providing to handle the calculation for your custom sensor, as that is not something we would do, since we cannot reasonably provide code for every sensor that exists. But with this project, you will have the building blocks you need to realize your application.

    Will that work for you?
  • 0 in reply to Ralph Jacobi
    Intellectual 550 points

    Thank you. If you could do that, it would be very meaningful.
    But I understand that temperature sensors affect ADC1 and ADC2, so can you tell me if they are related to light sensors?(which is related to ADC0)

    Of course, thank you very much for letting me know that it is related to the temperature sensor.

  • 0 in reply to hyosung kim
    Intellectual 550 points
    I also wonder if I can substitute ADC values for other functions to output results.
  • 0 in reply to hyosung kim
    TI__Guru*** 135355 points
    Hello Hyosung,

    I have been dealing with an issue trying to get the project running properly, so I will not be able to provide it today. Hopefully will have it resolved tomorrow.

    As far as the questions asked, first off the example I have is for reading a thermistor like on the RF430 Temperature Sensing Patch, not the full EVM. So if you are reading the ADC for something other than a thermistor, you'd need to configure it different.

    The ADC values you get are based on the sensor, so you'd need to make new functions to process the result. The result is just a raw ADC count number that corresponds to a voltage. What that number means is completely dependent on the sensor.

    As such, the temperature sensors on ADC1/ADC2 do not impact the light sensor on ADC0.
  • 0 in reply to Ralph Jacobi
    Intellectual 550 points

    Thank you. While I'm waiting, I'll find out about the code.

  • 0 in reply to hyosung kim
    TI__Guru*** 135355 points

    Hello Hyosung,

    Okay so I had some issues with the project and worked out most of them but the linking of files isn't the cleanest, so you'll have to deal with that a little.

    The project is attached here: TRF7970ABP_G2ET_FRL_Reader.zip

    To get it to compile, you will need to download and install IQmathLib as the files are linked to the install path for IQmathLib - I didn't have the time to figure out why the build was failing when I tried to pull the files into the project directly.

    You can get IQmathLib here: http://www.ti.com/tool/MSP-IQMATHLIB

  • 0 in reply to Ralph Jacobi
    Intellectual 550 points

    Thank you very much. I love you.
    I downloaded the link's material and I.Q.mathLib.

    However, when I attempt to open and run a project, the following error occurs:
    What's the problem?
    (The folder is located on the desktop.)

  • 0 in reply to hyosung kim
    Intellectual 550 points
    Description Resource Path Location Type
    This project was created using a version of compiler that is not currently installed - 16.9.7.LTS [MSP430]. Another version of the compiler will be used during build - 18.12.1.LTS. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'. TRF7970ABP_G2ET_FRL_Reader properties Problem





    This error is particularly suspicious.