• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 16 subscribers
  • Views 278 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/RF430FRL152HEVM: Errors: Could not read from device

CCS/RF430FRL152HEVM: RF430FRL152HEVM seems to have stopped transmitting

Adam Collins1
Prodigy 60 points
Part Number: RF430FRL152HEVM
Other Parts Discussed in Thread: MSP-EXP430G2ET, RF430FRL152H

Tool/software: Code Composer Studio

Hi All,

Apologies if this has been asked before I did do some searching on the forum.

I'm using the RF430FRL152HEVM to communicate with the MSP-EXP430G2ET plus the TRF7970ABP using the windows GUI.

I followed the setup guide for the RF430FRL152HEVM and got everything connected and reading ok. I could also get my smart phone to read the board using the RF430FRL152H demo app for android.

I was looking at the 'view sensor data' tab when an option came up about changing the block size from 8 bytes to 4 bytes (tbh I didn't read it fully) and I pressed ok. It seems ever since this point I have been unable to communicate with the RF430FRL152HEVM. The MSP-EXP430G2ET plus the TRF7970ABP are connecting ok with the software as before but I am getting a 'could not read from device' and 'could not write to device' error. My smart phone will no longer read it as it had before. 

The switches (S3, S4, S5, S6) are all in the correct positions. Anything else I can do to isolate the problem? Is it possible to do a factory reset on the RF430FRL152HEVM using a USB to laptop connection?

Appreciate any help.

Thanks,

Adam.

  • 0
    TI__Mastermind 18265 points

    Hello Adam,

    I have tried that with my RF430FRL152H EVM board and changed the block size to 4 byte. This alone will not "brick" the board. When trying to read or write with the GUI, it reports the wrong block size and ask if it should be changed.

    There must be something else went wrong with your device. The critical part in the memory is the interrupt table which is located  from 0xFFE0 to 0xFFFF. If the IRQ vector for the RF interface is overwritten, no RF communication is possible.

    Not sure what happened in your case, but if the board gets inaccessible via RF, the only way to recover it will be the use of the JTAG interface to reprogram it. For this the USB JTAG interface will be needed:

    https://www.ti.com/tool/MSP-FET

    If available, also the older MSP-FET430UIF (grey case) can be used.

    Best Regards,

    Helfried

  • 0 in reply to Helfried Vollbrecht
    Prodigy 60 points

    Hi Helfired,

    Thanks for the response.

    It is a strange issue. I must have corrupted it somehow.

    I think I will order another unit as it is only 18€ vs 96€ for the JTAG USB device, I will be more attentive this time when making readings.

    One quick related question: is it possible to purchase an off-the-shelf version of the 'Battery-Less NFC/RFID Temperature Sensing Patch'? Or can you reccomend an integrator who can produce trhe device from the designs (preferably in Europe)?

    Thanks again for the help,

    Adam.

  • 0 in reply to Adam Collins1
    TI__Mastermind 18265 points

    Hello Adam,

    I understand that this will be the cheaper way. Hopefully it will not happen again.

    I am sorry, but the Temperature Sensing Patch is not available for sale. It is only a reference design and TI provides the design data.

    A recommendation for a company, that can produce that patch, cannot be given. Depends also on the quantity needed.

    Best Regards,

    Helfried