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.

MSP430F5529: 5529LP can't support the online debug with my MSP4305529 device

Part Number: MSP430F5529
Other Parts Discussed in Thread: MSP-EXP430F5529LP

Hi,

step as below:

1. connect the MSP-EXP430F5529LP with my MSP430F5529(solder in my design board) chip, I can normally download the firmware into this chip, and after disconnect the MSP-EXP430F5529LP with my MSP430F5529, my MSP430F5529 can work normally as my expecting

2. connect the MSP-EXP430F5529LP with my MSP430F5529(solder in my design board) chip, I can normally download the firmware into this chip, and then I want to debug online that connect the MSP-EXP430F5529LP with my MSP430F5529, in my IAR window, I can't monitor the register on real time.

can you help us check it reason? TKS

and

  • Hello,

    So you are using the eZ-FET lite from the LaunchPad to program your MSP430F5529 device on a custom PC board? And even though you are able to program the device you cannot debug properly in IAR? What symptoms are shown to indicate that the debugger is not working as expected? Are you able to program and debug the F5529 device that is soldered on the LaunchPad?

    Regards,
    Ryan
  • Yes, I am using the eZ-FET lite from the LP to program my MSP430f5529 device on a custom PC board.

    when I debug this program as below, when the program exectue to  " UCSCTL4 |= SELS_5 + SELM_5;         ", I check the status of the P2DIR, P2SEL, P7DIR, P7SEL, I find they are "0x00".

     P2DIR |= BIT2;                            // SMCLK set out to pins
      P2SEL |= BIT2;                           
      P7DIR |= BIT7;                            // MCLK set out to pins
      P7SEL |= BIT7;
     
      P5SEL |= BIT2+BIT3;                       // Port select XT2

      UCSCTL6 &= ~XT2OFF;                       // Enable XT2
      UCSCTL6 &= 0xfff3;                        // Internal load cap
      UCSCTL3 |= SELREF_2;                      // FLLref = REFO
                                                // Since LFXT1 is not used,
                                                // sourcing FLL with LFXT1 can cause
                                                // XT1OFFG flag to set
      UCSCTL4 |= SELA_2;                        // ACLK=REFO,SMCLK=DCO,MCLK=DCO

      // Loop until XT1,XT2 & DCO stabilizes - in this case loop until XT2 settles
      do
      {
        UCSCTL7 &= ~(XT2OFFG + XT1LFOFFG + DCOFFG);
                                                // Clear XT2,XT1,DCO fault flags
        SFRIFG1 &= ~OFIFG;                      // Clear fault flags
      }while (SFRIFG1&OFIFG);                   // Test oscillator fault flag

      UCSCTL6 &= ~XT2DRIVE0;                    // Decrease XT2 Drive according to
                                                // expected frequency
      UCSCTL4 |= SELS_5 + SELM_5;               // SMCLK=MCLK=XT2

    About " Are you able to program and debug the F5529 device that is soldered on the LaunchPad?", you are right. TKS

  • Are you sure that FET Debugger is selected under the Debugger category of Project Options as compared to the Simulator driver? The eZ-FET lite's SBW is used to program the device as well as communicate with the debugger so it does not make sense for you to be able to accomplish one function but not the other. By demonstrating proper operation with the on-board F5529 we know that the eZ-FET lite is still functional. Make sure that the wires connecting the eZ-FET lite to the target board are as short as possible, and possibly provide a schematic if the issue persists.

    Regards,
    Ryan
  • Yes, I am sure.

  • A schematic of the custom board would be helpful, you should also test if the same symptoms can be observed in CCS as this may be an issue with the IAR debugger.

    Regards,
    Ryan

**Attention** This is a public forum