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.

MSP430FR6045:Contact USS Tool Connect

Part Number: MSP430FR6045
Other Parts Discussed in Thread: MSP430FR6047

MSP430FR6045 custom board is being produced and developed.
When PC, Cativate, Custom Board are connected and USS Tool is connected, the message “HID Bridge Connected -- waiting for device” appears on the bottom bar of the program as shown in Figure 1 below and the next step does not proceed.
Also, the Request Update button is not activated either.
However, it was confirmed that the Waveforms function of the USS Tool and the ADC Capture function work.

Figure 1

When debugging, if __delay_cycles was used before in the Comm_writeBuffer() function of the comm.c file as shown in Figure 2 below, it was confirmed that the connection at the bottom of the USS Tool was established as shown in Figure 3 below.

Figure 2

Figure 3

In order to test the MSP430FR6047 EVM board in the same environment as above, the HID Bridge of the EVM board was removed and Cativate was connected.
After connecting to PC, when connecting the USS Tool, it worked normally without modification of the code.

Please tell me why it is so different and how to solve it.

  • Hi,

    So, the custom board with FR6045 have issues connecting to the GUI. And the EVM-FR6047 board works fine. 

    Have you correctly connected the COMM_SDA, COMM_SCL and COMM_IRQ pins for the GUI communication? And it needs pull-up resistance to VCC on the COMM_SDA and COMM_SCL pins. 

    One more thing, have you change the Option->Meter option to custom board with FR6045 on the GUI when you connecting to your own board?

    Best regards,

    Cash Hao

  • Hi,

    As described above, all pins are correctly aligned.
    A pull-up resistor was also attached, and the Meter Option was also set to Custom-PCB with FR6045.

    Again, when __delay_cycles is inserted in the Comm_writeBuffer() function, it works normally.
    Only when there is no __delay_cycles, "HID Bridge Connected -- waiting for device" is maintained on the bottom bar of the USS program, and the "Request Update" button is not activated.

    Please read the article carefully.

    Best regatds, 

    Jayden

  • hello!
    Of course the pull-ups depend. (20K)
    All other actions in the above question are said to be fine.
    The board options have also been changed to Custom 6045.
    Please read the above question again carefully.
    When delay is added to the original source, it becomes like 6047 evm.
    The delay is not a problem here, but why the 6045 and 6047 have different FRAMs, but they behave differently.
    I also barely managed to get parts for the 6045 ($35 each), but not the 6047.
    thank you.

  • Hi,

    The IRQ should not be pulled-up to the VCC.

    Best regards,

    Cash Hao

  • As you said, I removed the pullup resistor and tested it.

    If there is no delay, the same operation as before is not possible.

    Are you a TI employee?

  • Hi,

    Yes, I am a TI employee. When you removed the pullup resistor on the IRQ pin. Is the connection to the GUI good now?

    Best regards,

    Cash Hao

  • Even removing the pull-up does not work.
    Same as above.
    It works when delay is included.

    thank you.

  • Hi,

    I am not sure why the delay helps here. If the hardware connection is correct, the FR6045 custom board and EVM-FR6047 should behave same. 

    It might related to the pullup resistor value, you are using 20k and we recommend to use 3.3k. Which cause an additional delay on the communication. 

    Best regards,

    Cash Hao

  • Hi,
    I solved the problem.

    I changed the pull-up resistor value as per your advice and it worked fine even without __delay_cycles.

    Thank you very much.

**Attention** This is a public forum