RF430FRL152HEVM: MSP-FET430UIF

Hello Cherry,

what does the customer want to do? If he is using the MSP-FET430 then does he develop FW code, which shall read from the temperature sensor? Or does he want to use the ROM firmware to control the measurements? Which temperature sensor is the customer referring to, the chip internal temperature sensor or the external Thermistor, located on the EVM board?

Best regards,

Andreas.

Hello Andreas,

Thanks for your help.

The customer want to get the data of the internal temperature sensor, they have a mobile phone apk, and hope to be able to collect the temperature value, first they need to store the data, and then use the phone nfc to read out those values, now they do not know how to store these values, is it required to use the official firmware library? How to modify it? 

Thanks and regards,

Cherry

Hello Cherry,

now I got it.

I think this is a simple task, which can be done with the default firmware of the RF430FRL152HEVM. All the customers mobile phone apk needs to support is ISO15693 standard commands "Write Single Block" and "Read Single Block".

The virtual registers, which control the RF430FRL152HEVM firmware can be written with the "Write Single Block" command and the sensor results can be read back with "Read Single Block".

A typical command sequence can be found in chapter 3.6 of the FAQ document (https://www.ti.com/lit/pdf/sloa247). This example is for the light sensor, so the customer would just have to adapt the settings for the Internal Sensor. I think the default register values are a good start, the only register, which needs a modification is the Sensor Control Register Block 0 Byte 2), to select the Internal Sensor (write 0x08 instead of 0x04).

Best regards,

Andreas.

Hello Andreas,

Thanks. They also would like to know are these examples written in ccs? They don't have TRF7970AEVM, do they just need to burn the basic firmware plus what is written in www.ti.com/.../sloa247 in ccs?

Thanks and regards,

Cherry

Hello Cherry,

as far as I know, the RF430FRL152HEVM is coming with the SensorHub Project code programmed on it. So there should be no need to program any firmware for getting started. Even the plain ROM firmware (erased FRAM) would support the internal temperature sensor measurement via virtual registers.

Yes the example firmware consists of several CCS projects, one for every example and for every applicable device spin. If the customer wants to evaluate one of these projects then it would be required to open a project with CCS and download it to the RF430FRL152HEVM via MSP-FET430.

Alternatively the provided code image (.txt file) could be loaded per Over the Air programming if the DLP-7970ABP BoosterPack plug-in module and MSP-EXP430G2ET LaunchPad development kit would be available (see chapter 7 in http://www.ti.com/lit/pdf/slau607). In this case no CCS would be required.

Best regards,

Andreas.

Hello Andreas,

The customer now have two devices (MSP-FET430 and EVM) and they want to read the temperature inside the EVM.  They want to confirm whether ccs is required.  What software should the "block 3" and "block 0" in the manual and the acceptance "block 9" be configured on?

Thanks and regards,

Cherry

Hello Cherry,

if the customer has not modified the existing firmware on the RF430FRL152HEVM, then no CCS and no MSP-FET430 is required, because the RF430FRL152HEVM should already contain a functional firmware, which supports internal temperature-sensor measurements. CCS and MSP-FET430 are only required if the customer wants to develop and download a customized firmware to the RF430FRL152HEVM.

The firmware registers can be written via ISO15693 command "Write Single Block".

For the internal temperature sensor measurement, the following register configuration would be required:

Block3 contains all 0xFF by default, which can stay unchanged.

Block9 will contain the measurement result after completion, so it will be anyway overwritten with a new result and its initialization is not necessary. It would be only for better readability if all block 9 memory is initialized to 0xFF before the measurement, then you can better identify the result value.

Block 2 should be written with

Block 0 should be written at the end, because it triggers the measurement.

Best regards,

Andreas.

Hello Andreas,

Thanks for your detailed response.

Please let me clarify,  the customer indeed don't know where to put these blocks, i.e. they don't know what software to set it up on, the data sheet says that it can be set using the GUI, but they don't have TRF7970EVM, so they don't know where these "blocks" are configured.

Thanks and regards,

Cherry