• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 56 subscribers
  • Views 942 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.

CCS V5.2: Source Code step over does not work on __delay_cycles()

Guenther Klenner
Expert 1790 points


Hi TI-Team,

My congratulation to this new build. I like this transition from V4 to V5. To make it even better here a small bug:

When using function __delay_cycles(160); the MSP430 debugger does not step over on "Step over (F6)". It steps several times on the same line.

Regards
Guenther

PS: If there is a special board to note such bugs then let me know

  • 0
    TI__Guru**** 171309 points

    Guenther,

    I am glad you are liking v5 so far.

    Thanks for reporting this. I also see the same issue reported by you; the function is only left after executing "Step Over" several times. I will try to see if this was already reported and eventually file a bug.

    Cheers,

    Rafael

    P.S. This is the correct forum for CCS-related questions/bugs/etc.

  • 0 in reply to desouza
    Guru 92251 points

    desouza said:
    I will try to see if this was already reported and eventually file a bug.

    I previously reported this in CCS 5.1.1.00031 "Step Over" doesn't work for MSP430 __delay_cycles intrinsic

  • 0 in reply to desouza
    Prodigy 160 points

    Hi,TI team

    I'm using msp430 launch pad (g2553),and try to use CCS v5 to program the device. And I encountered the same problem as what they are talking about.It just doesn't step over when encountered the __delay_cycles function.

    And another problem is that after I write things into the UCB0TXBUF, it should be cleared and shifted into the shift register,right? But in my situation the things in the UCB0TXBUF never clear,though it doesn't influence the result,seems like it's also a bug or am I doing it wrong? If you need my code I can post it.

    The third problem is that when read only one byte from the UCN0RXBUF,the user guide said that the code should be like this:

    UCB0CTL1 &= ~UCTR ; // Clear I2C TX flag for receive
    UCB0CTL1 |= UCTXSTT; // I2C TX, start condition
    UCB0CTL1 |= UCTXSTP; // I2C stop conditiond

    data = UCB0RXBUF;

    but actually if I doing it like that,I can never get the data from the receive buffer,i can get data only if I doing it like this:

    UCB0CTL1 |= UCTXSTT; // I2C TX, start condition

    data = UCB0RXBUF;
    UCB0CTL1 |= UCTXSTP; // I2C stop conditiond

    So about this problem can you tell me what is going wrong here?

    Thank you for your help!