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.

How could I download the sample code for the RF430FRL152H EVM?

Other Parts Discussed in Thread: RF430FRL152H, RF430FRL152HEVM

I want to modified the code for RF430FRL152H EVM, but I cannot download the sample code for this EVM board. I have no idea how to start with this EVM board.

  • The main setting with the RF430FRL152HEVM when connecting with JTAG is that switch labeled "S6" needs to be in the "Supply" setting.  Once that is set, programming is possible.

    The "Battery" setting is only used when you would like the EVM to be powered by the RF field.  

  • Thank you for your reply! But my problem is that I don't have source code for RF430FRL152H EVM. And I want it to help me understand how this EVM work. I don't know how to use the EVM board communicate with other sensor via I2C in passive mode (battery free).
  • Nick,

    We currently are not releasing the ROM code for the RF430FRL15xH.

    However if you visit the RF430FRL152H ti.com website (http://www.ti.com/product/RF430FRL152H/toolssoftware and see the software section) there is some example code provided.  The example code provided:

    1. Default Project:  This has no code but sets up the RF430 for full ROM code operation
    2. NFC Only Projects: Use only the ISO/IEC 15693 RF stack from the ROM code, the rest of the code can be developed by you and it will be in the FRAM
    3. SensorHub Project:  This is more of what you need.  This has example code for interfacing the RF430 to external digital I2C sensors.  It is also using the full ROM code.

    External digital sensors can be powered either from the VDD2X pin or VDDH pin.

  • Alexander,

    Thank you very much! Your suggestion is very helpful, but I still have a question. After receiving the data from external I2C sensor, I should put them as ISO 15693 RF stack(NFC projects)? And I can obtain the values from a smartphone APP?
  • If you look at the SensorHub project, there are several functions that are drivers, that is they are code to take one sample from the I2C digital sensor.

    The ROM code calls this driver code in FRAM (it has to be custom made for each I2C sensor) and it takes one sample, that sample is then put in the mailbox where the ROM code will process and store it in FRAM.

    Then an App can be used to read out what is in the FRAM, the logged data.

    I would recommend that you start with the SensorHub example project and develop driver code to read one sample from your I2C sensor and then return it to the mailbox.  The ROM code is configured through the virtual registers and its scheduler determines when the I2C driver is called.

    I would recommend you have an LSA to debug your I2C bus for quick debugging, unless you have example code.

    The "NFC only project" includes the ROM RF stack, but does not include the ROM code for taking sensor measurements and storing.  You would have to develop code in FRAM that would take a sample from the I2C sensor.  You would then have to store it somewhere in FRAM.   The app can be then programmed to read that result.  But this is possible.

  • Thank you for the good advice. It is really helpful. It is able to modify the 16bit value to mailbox to bigger data size(Such as 24bit or 32bits) in the SensorHub project?
  • The way that the ROM code is structured, it is set to 16 bits. However, if you use one sensor but configure to use two sensors, you can store a 32 bit value by storing 16 bits for each sensor call.
  • OK, it's a good idea. If I read data from external sensor through I2C and I return it to the mailbox. Should I modified the virtual register to make it work or just follow the sensorhub virtual register settings?
  • SensorHub uses three digital sensors.

    It is a good starting point and I would recommend to use it.  You will have to modify the I2C drivers, you need to create an I2C driver that initializes the digital sensor and then can collect one sample every time the ROM scheduler calls the driver.  Then return the sample through the mailbox.

    Once you have the driver code written you can test the results using the RF430FRL GUI and see if you are getting the correct results.

  • Alexander,

    Thank you my problem is solved. Thanks for your help!