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

MSP430FR50431: MSP430FR50431 - Reading registers

ido amgar
Intellectual 440 points
Part Number: MSP430FR50431
Other Parts Discussed in Thread: MSP430FR6043, MSP-FET,

Hi!

I am trying to burn the demo code provided for MSP430FR6043 onto my custom board, which contains the MSP43050431. I followed the instructions and adjusted the values as suggested to adapt the code for MSP43050431 (as discussed in this [link](e2e.ti.com/.../msp430fr5043-msp430fr5043-custom-ultrasonic-board-software-issues)).

I connected the MSP-FET (which I bought from TI) to the jumpers on my board as shown in the figure. However, I connected only the following pins: 1, 3, 5, 7, 11,  and 2,4 (VCC, GND).

:

After completing these steps, I tried to burn the code using CCS, but I encountered the following

Could you please help me? Is the problem that I haven't connected all the pins between the MSP-FET and my custom board? Is the code not suitable for the MSP43050431 device, and can it only be burned onto the MSP430FR6043? Or could there be something else that I am missing in my process?

Thanks!

  • 0
    TI__Genius 12335 points

    Hi ido,

    Yes, the code for each device is not just the same, so to implement the code need do modification according to the device details hardware. However, this always not make the imapct on the connection with the board.

    On the other hand,  you should change the device linker file and the maybe the header file for your project. I recommend you use a example project and download it to yout customer board, and if it works then there is no hardare issue on the board, and then you can change the project setting according to your reference project.

    As for MSP FET connection, you can refer to below:https://www.ti.com/lit/ug/slau278ah/slau278ah.pdf?ts=1709293407423&ref_url=https%253A%252F%252Fwww.ti.com%252Ftool%252FMSP-FET 

    B.R.

    Sal

  • 0 in reply to Sal Ye
    Intellectual 440 points

    But I use MSP430FR50431 and it doesn't have a demo code,
    So I tried to burn the MSP430FR6043 demo code to it and it didn't work as I mentioned above.
    Do you have a demo code of 50431?

    Are you saying that the demo code should burn properly on my custom board?
    And if not, are these probably hardware problems?

  • 0 in reply to ido amgar
    Guru 91060 points

    You need to connect either VCC_TOOL or VCC_TARGET [See "Important to Connect" top-left in Sal's diagram above]. The MSP-FET needs to know the target VCC so it can drive the pins.

  • 0 in reply to ido amgar
    Intellectual 440 points

    I want to update
    If I click ignore
    It burns nonetheless, is it a normal burn? Or will information be lost there?

  • +1 in reply to ido amgar
    Guru 91060 points

    I don't know the differences between the FR6043 and the FR5043, so I don't know whether it will work (run properly) or not.

    What I would do next is go to "Build Settings->General->Variant" and change the selection to MSP430FR50431. I can't promise it will build (without errors), but that's how to change the "target setup".

    [Edit: While you're there, make sure the "Manage the target-configuration automatically" box is checked. It normally is.]

  • +1 in reply to ido amgar
    TI__Genius 12335 points

    Hi IDO,

    Bruce is correct, you should firstly change the device selection for the project, which will automatically change the linker file (cmd), some macro define and include file (.h file) to adapt to new device. After this, the code should download to device normally if your debug interface is all right.

    Note: it might be some error after change the variant whcih means you should do code migration. I suggest you can use the an empty project to verify the debug interface if you can not pass the compiler.

    Demo project for 6043:

    Change it to 5043:

    For the second parts, the demo code is for MSP430FR6043, I think there is no reference code for FR50431, you should do code migration for your own board. I recommend you use the TI EVM board to get good practise experience of USS, and then do migration.

    B.R.

    Sal

**Attention** This is a public forum