• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 1562 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:

PGA900EVM: PGA900EVM / Generic Firmware: How to send example commands?

PGA900EVM: USB2ANY SDK and Labview Example

Mario Schirmer
Intellectual 370 points
Part Number: PGA900EVM
Other Parts Discussed in Thread: USB2ANY, PGA900

Hi,

I have got some questions about the usb2any SDK and the labview examples from Scott.

1. I tried to write in the Data Ram of the PGA900 with the PGA900_OWI_Communication.vi. The IC excutes an OWI interrupt but doesn´t write any data in the RAM Cell 0x20000000.

The OWI_ERROR_STATUS_LO = 0x00 and OWI_ERROR_STATUS_HI = 0x00.

Is the vi correct configurated?  Do I have set some additonals bits in the sample firmware?

I using the following Setup:

2. The SDK provides some additional OWI - functions. I created an own C# programm based on the VI to generate an OWI activation impulse. The VI uses only the UART functions not the OWI functions. Is it
recommendable to use the OWI functions or should i only use uart functions?

Regards ,

Mario

  • 0
    TI__Mastermind 31655 points

    Hi Mario,

    Are you able to write and read other registers, for example in the control and status registers instead of the data RAM? Or is there no OWI communication happening with any register through the VI?

    As far as the activation goes, this is purely user preference. If you have access to the UART  of the device in a manufacturing environment, then I would recommend using that as an activation, but most of the time when only OWI is used for communication there is no access to the UART pins and OWI activation must occur through the OWI line. Either method is effective, but the UART can be a bit more reliable if you have access to it.

    Regards,

  • 0 in reply to Scott Cummins
    Intellectual 370 points

    Hi Scott,

    i can´t read any register. The vi responses always "0x00".

    Is it nescesarry to set the mirco_reset in the sample firmware?

    Regards,

    Mario

  • 0 in reply to Mario Schirmer
    TI__Mastermind 31655 points

    Hi Mario,

    Yes, in order to read or write any registers (other than the COMBUF registers or the MICRO_IF_CTRL register) you will need to place the microcontroller in reset. You don't need to do this in firmware, you can just write to the MICRO_IF_CTRL register first, and then you should be able to access the rest of the register space through the digital interfaces.


    Regards,

  • 0 in reply to Scott Cummins
    Intellectual 370 points

    Hi Scott,

    thanks for the fast response!

    If I want to do some owi communication I have set first the mirco_reset bit in the MICRO_INTERFACE_CONTROL register during the owi interrupt. Right?

    e.g. MICRO_INTERFACE_CONTROL = (DIGITAL_IF_SELECT | MICRO_RESET);

    I tried this during a debugging session but the ccs debuger crashs all the time at this point. Is that normal?


    Regards,

    Mario

  • 0 in reply to Mario Schirmer
    TI__Mastermind 31655 points

    Hi Mario,

    Yes, to be able to access most of the control and status registers, the microcontroller will have to be placed in reset.

    In what way is it crashing? Does it have an error code? When you place the micro in reset, the debugger will not be able to connect anymore.

    Regards,

  • 0 in reply to Scott Cummins
    Intellectual 370 points

    Hi Mario,

    crash means:  the dedugger loses the connecting.

    I Think this was the problem.

    Regards

    Mario