• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 894 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.

MSP430F67791A: EVM430-F6779 couldn't be connected to EMDC

Kien
Expert 3530 points
Part Number: MSP430F67791A
Other Parts Discussed in Thread: EVM430-F6779, ISO7421, MSP-ISO, MSP-FET

Hi team,

I am working on a demo with the EMDC and EVM430-F6779.

I follow the guidelines and were able to get the HID bridge which is the F5529LP connected to the GUI. However, the EVM didn't. I can only see the text "HID Connected" at the bottom left of the GUI. Compares to the guidelines, the only difference I made is the isolation board. I am waiting for the MSP-ISO board shipped. In the meantime, I created a simple circuit using ISO7421 as shown in the picture below.

On the SW side, I programmed the F6779 EVM with the image. I even tried to generate code from the example project (EVM430-F6779_CT_3V_3C_50Hz), import it to CCS, build and download to the board.

By using an oscilloscope I was able to see short pulses at RX_EN pin on the EVM, but there was nothing on the TX_EN.

What else should I check?

  • 0
    TI__Guru 60321 points

    Hi Kien,

    Let me check with the team that supports this.

  • 0 in reply to Dennis Lehman
    TI__Mastermind 49692 points

    Hi Kien,

    Thanks for your detailed post and for using EMDC!

    I think what's going on here is that the EVM may not be powered up or the UART connections from the HID Bridge (F5529 LP) to the EVM are on the wrong pins.

    First, without connecting the EVM to high voltage, make sure the jumper for DVCC (nearest the RS232 connector) is set to INTERNAL Then, try powering the EVM with the MSP-FET. See if the communication works now. In your diagram (thanks for sharing it by the way), it looks like there's only one phase connected. The onboard cap-drop supply selected with the other DVCC jumper set to VCC_PL gets power from all three phases and may not have enough power with a single phase. Also, the onboard AC/DC supply selected by setting DVCC to VCC_ISO gets its power from Phase C (Phase A is connected in your diagram). This could be causing the issue.

    Another thing that could be causing the issue is the wrong UART connections on the EVM. If I remember correctly, the pins on the left side of the TX_EN and RX_EN headers should be used. You're probably on the correct pins but I just wanted to mention that in case.

    If these things were done already, try unplugging the HID Bridge from your PC, closing/re-opening EMDC GUI on your PC, plugging HID Bridge back into your PC with everything else connected to the EVM (except high voltage), then click Connect in the EMDC GUI. It should work now.

    Please let me know if these tips don't help or if any did, let me know which one. Thanks.

    Regards,

    James

  • 0 in reply to James Evans
    TI__Expert 3530 points

    Hi James,

    Thanks a lot for a very detailed answer as usual.

    Yes, you were right. I corrected the connections to TX_EN and RX_EN.

    Fortunately, I was able to identify the cause: I was using an example project which used F6779 while the one on the EVM is F67791A. I am not sure why the example code didn't work after being generated by the EMDC and imported to CCS, changed the Part number in the Target configuration file.

    I tried to create a new EMDC project. And it worked with the EVM finally.

    Now, I am facing another issue with customer's board. They use UCA1 instead of UCA0. So I have to modify the generated source code to change to communication interface from UCA0 by default to UCA1. I have found only one statement in the "uart_defs.h" file to modify.

    From 

    #define UART__EUSCI_A_PERIPHERAL (EUSCI_A0_BASE)

    To

    #define UART__EUSCI_A_PERIPHERAL (EUSCI_A1_BASE)

    But it didn't help. Is there something else that I need to modify in the code?

  • 0 in reply to Kien
    TI__Expert 3530 points

    Hi team,

    Do you have any comment on this?

    I am still struggling with changing the communication interface from UCA0 (by default) to UCA1.

  • 0 in reply to Kien
    TI__Guru 60321 points

    Hi Kien,

    I believe you also need to configure the port pins P3.4, P3.5 for using the UCA1.  This is done in the hal_system_GPIOInit function.

    You can see here that default uses P3.0, P3.1 for UCA0.

  • 0 in reply to Dennis Lehman
    TI__Mastermind 49692 points

    Hi Kien,

    Another thing to check is the ISRs for the UART communication. If the UCA changes, then the ISR will too.

    Regards,

    James

  • 0 in reply to James Evans
    TI__Guru 60321 points

    Hi Kien,

    It's been a couple of days since I have heard from you so I will assume you have the problem working.

    If this isn’t the case, please click the "This did NOT resolve my issue" button and reply to this thread with more information.
    If this thread locks, please click the "Ask a related question" button and in the new thread describe the current status of your issue and any additional details you may have to assist us in helping to solve your issues.

  • 0 in reply to Dennis Lehman
    TI__Expert 3530 points

    James and Dennis,

    Sorry for my late confirmation.

    Those suggestions were successfully verified on the real board.

    Thanks a lot for your supports.

  • 0 in reply to Kien
    TI__Mastermind 49692 points

    Outstanding! Many thanks for letting us know, Kien.

    Regards,

    James

**Attention** This is a public forum