• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 477 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.

EVM430-FR6047: I2C communication protocol with an external processor issues

Suzzi Riccardo
Prodigy 40 points
Part Number: EVM430-FR6047


Hello,

I need to know the correct commands sequence (and if the commands are to be invoked in read or write mode) to read Dtof, absTofs, ADC data and debug data with an external processor, using i2c interface and the USS Design Centre protocol.

The hardware and the I2C driver I wrote are working fine because at the moment I'm already able to set up and read back all the configuration parameters, but not to read measurement data. Moreover, the help file in the USS Design Centre PC program illustrates only the command format butabsolutely not the way to use and combine them (also the necessary 0x55 and 0xAA Sync bytes were omitted) and I haven't time at this stage to make reverse enginering with protocol analyzer.

Hoping an a fast reply,

Best regards

riccardo Suzzi

  • 0
    TI__Guru 71216 points

    Hello Riccardo,

    Let me see if I can get that information for you.

  • 0 in reply to Dennis Lehman
    TI__Guru 71216 points

    Hello Suzzi,

    I'm being told that the commandIDs for those variables are documented in this file located in the installation for the USS sw version 2.40.00.00:  C:/ti/msp/USS_02_40_00_00/USS/docs/UserGuide/UserGuide/ch_protocol.html.

    The request needs to be sent out using Commands 0x97 & 0x98 as a Write. The data is returned by the SW running on MSP430FR604x via the below IDs:

    DToF: 0xB0

    AbsToF UPS: 0xB1

    AbsToF DNS: 0xB2

    VFR: 0xB3

    ADC UPS: 0xB4

    ADC DNS: 0xB5

    Debug: 0xB6

    Advanced Debug: 0xB7

     

    The above will be returned separately. These will also not be returned as soon as the external processor makes the request.

    • The ADC UPS/DNS are returned after the ADC obtains the captures. This is done inside HMI_PostMeasurement_Update().
    • The DToF & AbsToF are returned after the measurement results are computed.  This is done inside HMI_PostAlgorithm_Update().

     

    You can also look at hmi.c & ussDCCommandHandlers.c/h in the USS Water Demo project for the specifics if needed:

    #define COMMAND_HANDLER_PLOT_DTOF_ID                        0xB0

    #define COMMAND_HANDLER_PLOT_ABS_UPS_ID                     0xB1

    #define COMMAND_HANDLER_PLOT_ABS_DNS_ID                     0xB2

    #define COMMAND_HANDLER_PLOT_VOL_ID                         0xB3

    #define COMMAND_HANDLER_PLOT_ADC_UPS_STRT_STP_PACKS_ID      0xB4

    #define COMMAND_HANDLER_PLOT_ADC_DNS_STRT_STP_PACKS_ID      0xB5

    #define COMMAND_HANDLER_PLOT_GENERIC_PLOT_ID                0xB6

    #define COMMAND_HANDLER_PLOT_ADVANCED_GENERIC_PLOT_ID       0xB7

  • 0 in reply to Dennis Lehman
    Prodigy 40 points

    Dear Dennis,

    thanks a lot!

    All is clear now and my set is working fine.

    For the moment I'll continue my development using USS libray V2.30.00 because I've already deeply customize it for my specific app. (clamp-on liquid flowmeter).

    I've already considered to upgrade, but later.

    Best regards.

    Riccardo

**Attention** This is a public forum