• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 17 subscribers
  • Views 2047 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

RF430FRL152H Demo android

BAziliO BaziliO
Intellectual 340 points
Other Parts Discussed in Thread: RF430FRL152H

Hi, please tell me where I can get it open application code for android RF430FRL152H Demo, the current version, which implement a data read function with the sensors? In this post e2e.ti.com/.../1689969 old version of the application

  • 0
    TI__Guru*** 131520 points
    Hi Bazilio,

    I don't believe there is a newer version available but I will check with Eddie and find out.
  • 0 in reply to Ralph Jacobi
    Intellectual 340 points

    Thank you, when can I expect an answer, whether there is a new version of the app for Android?

  • 0 in reply to Ralph Jacobi
    Intellectual 340 points

    Any body here? RF430FRL152H android-demo

  • 0 in reply to BAziliO BaziliO
    TI__Expert 7820 points

    The Android APK that we provided does do temperature sensing and display of the RF430FRL152H.

    The source code also has the same functionality, that is configuring and reading out the temperature information.

    The file that is setting up the RF commands for temperature sensing is at this place: ti-sensor-app.git\app\src\main\java\com\ti\nfcdemo\activities\iso15693\Iso15693WriteTagActivity.java .


    Have you been able to compile the project and generate and run it on an Android handset?

  • 0 in reply to Alex K.
    Expert 1090 points

    In case it's helpful, with one Android device I ran across (Nexus 7 2013), the ISO15693 write single block commands using request flags of 0x42 cause the tag to disconnect rather than successfully complete the command. It seems the option flag set to 1 upsets it. Changing to 0x02 allows the writes to succeed.

    This is with the VERSION_4 Android Demo app for the EVM. 

    Out of curiosity, the 16 bit values written to FRAM appear to be stored LSB first. Is this simply how writing a u16 to FRAM works with these devices? 

    (Example: 0x00 4511 DF11 420B FFFF) Single log of temp/1 temp/2 and ADC0. 

    EDIT: Are the 16 bit writes atomic? 

    Thanks, 
    Karl

  • 0 in reply to forum_user
    TI__Expert 7820 points

    The option flag on writes is needed for devices with flash memory which need a longer time to write the data.  Since this device uses FRAM writes are as fast as RAM and have no delay.

    I think you know that the option flag needs an extra EOF frame sent when the tag has finished writing the data.  Since this is not need on the RF430FRL152H, it is not supported.  Therefore the handset has an issue with it. 

    The sent data is stored from LSB first and higher as it is sent in over RF.

    The writes are written into FRAM 8-bits at a time by the processor.

  • 0 in reply to Alex K.
    Expert 1090 points

    Alexander Kozitsky said:

    I think you know that the option flag needs an extra EOF frame sent when the tag has finished writing the data.  Since this is not need on the RF430FRL152H, it is not supported.  Therefore the handset has an issue with it. 

    Was unaware that this was actually unsupported by the device., so is helpful to know. Please note the Android demo app that was released on this forum has that option flag set for the write single block command, causing them to fail. Might be a good update. 

    Thanks, 
    Karl