• State Verified Answer
  • Replies 7 replies
  • Subscribers 73 subscribers
  • Views 6838 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 110373
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Sudden error with J-Link RTT Viewer: "WARNING: Sent 15 of 89 bytes

Elm

Hi,

I am developing a program on a Nordic nRF51 DK, using Eclipse/gcc, and am using J-Link RTT for a debug command line interface. This has worked very well for some time, but now I have a problem: When I type a command, the "Log" tab of the j-Link RTT Viewer opens and there is a message: "WARNING: Sent 15 of 89 bytes." The first number is always 15, and the second varies with the length of the command. Commands longer than 15 bytes gives this answer, commands shorter than 15 bytes seem to work.

I am totally at loss. I realize that my own program is the major suspect, maybe an astray pointer. Possibly, there is some error with the RTT code from Segger/Nordic. Another thing is that my program now is now close to 64kB, and it might be some 16/32-bit address error. I have not configured RTT in any way, just called SEGGER_RTT_Init().

I would like to know what causes this error in the RTT Viewer, so I can use this information to debug my code. Any help appreciated.

regards, //Elm

Parents
  • 0

    I had a similar problem a while back. Worse, in fact, as RTT viewer was covering the screen with overlapping error messages, and I had to physically disconnect the J-Link before I could shut RTT viewr down. I believe it was a problem with my code crashing, and get stuck in a tight loop in which a string was written to RTT. Once I fixed my code the problem went away, but I wasn't impressed by the behaviour of RTT viewer - not what I call failing gracefully...

Reply
  • 0

    I had a similar problem a while back. Worse, in fact, as RTT viewer was covering the screen with overlapping error messages, and I had to physically disconnect the J-Link before I could shut RTT viewr down. I believe it was a problem with my code crashing, and get stuck in a tight loop in which a string was written to RTT. Once I fixed my code the problem went away, but I wasn't impressed by the behaviour of RTT viewer - not what I call failing gracefully...

Children
No Data
Related
Terms of service