• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 3645 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.

Sending data to MSP430F5529

Prad
Expert 1125 points
Other Parts Discussed in Thread: MSP430F5529

Hi all,

 

I need to send a specific sequence of hex bytes like 0x00,0x80,0x8F etc using 

MSP430F5529 USB CDC example 3(echo).

Since hyperterminal apllication cannot be used for this purpose I am using RealTerm free software.

 

All other values works fine(i.e echo) but problem occurs with 0x00,

whenever I send 0x00 I dont see any display on the terminal,I have also checked the 

MSP430 buffer memory and nothing is written.

 

Thankyou in advance,

  • 0
    Guru 227245 points

    Are you sure you send 0x00 at all? Many programs do a check like if(x) to test whether there's something to do. And in case of 0x00, this results in no. This includes e.g. the windows standard input handlers, which refuse to accept an ALT-0 sequence as a character.

    You can use hyper term (I recommend downloading the newer version from the net, the one that comes with windows is stone old and buggy) for sending data sequences by defining macros. Works fine. Even for 0x00.

  • 0 in reply to Jens-Michael Gross
    Expert 1125 points

    Yes I am sending 0x00 through RealTerm, I think RealTerm is better than windows hyperterminal in this case.

  • 0 in reply to Prad
    Guru 227245 points

    Prad said:
    Yes I am sending 0x00


    How do you know if you don't see it arrive at the MSP or echoed?

    Prad said:
    I think RealTerm is better than windows hyperterminal in this case.


    maybe, I don't have this kind of problems with HyperTerm, but then, I don't use the centuries-old version that still comes with Windows. The 'brand new' 2002 version does not have this kind of problems. After all, HyperTerm is not from Microsoft.

  • 0 in reply to Jens-Michael Gross
    Expert 1125 points

     

    Hi,

     

    thankyou for the reply,

     

    I am not having problem with printable digit character '0'(whose ASCII value is 48),but with 0x00 or 0,

    I think you cannot use HyperTerm for that,

    if possible try with RealTerm.

     

     

  • 0 in reply to Prad
    TI__Expert 6280 points

    I actually tried using the H-term PC tool to transmit and receive hex/binary values (0x00h, 0x80h and 0xFFh) and was able to do so. Screen shot below:

    I downloaded the RealTerm PC application, but the tool did not show any COM ports beyond Port 22 (the MSP430 CDC device came up on COM 94 on my PC) and so was not able to check the same.

    Regards,

    Bhargavi

  • 0 in reply to Prad
    Guru 227245 points

    Prad said:
    I am not having problem with printable digit character '0'(whose ASCII value is 48),but with 0x00 or 0,

    That's what I was talking about. The macro function of the newest (2002) HyperTerm accepts ALT-0 (CTRL-@) as value and sends it properly.

    I'm sorry, but I cannot easily install new software here, including RealTerm. So I cannot test whether RealTerm does send a 0x00 at all. Well, it should. So back to the question why you're not receiving anything. With the given information: I don't know.

  • 0 in reply to Jens-Michael Gross
    Expert 1125 points

    Hi,

     

    Thankyou,

     

    I was able to transmit and receive the data,

    but in case of Example 1,if the first byte is "00" nothing is trasmitted or received.

  • 0 in reply to Prad
    Guru 227245 points

    Out of curiosity, I tried to send a zero value with HyperTerm to my 'Debug interface' (actually an RS232 to RS485 converter with integrated message decoder), which is based on MSP1611. And I observed som strange things. The problem is that my implementation of getchar() returns 0 if there is a serial timeout. And the main loop, which was intended to forward the data bytes to the RS485, didn't check for the EOF flag. I quickly rewrote it and all bytes I send to the RS232 now from hyperterm are properly forwarded (and echoed back), now including a zero value. YOu cannot, however, send a 0 by typing ALT-0 (ALT-1 works for sending a binary 1). If put into a Macro (represented as <CTRL-@>), it works perfectly, alone, first of several bytes or in the middle of a sequence.

    My guess is that the function that pulls the data from USB on the MSP (if any) or the function that groups and pushes an output sequence to the virtual serial port to the USB has a similar '0 = nothing to do' bug. So the problem could be the virtual com port driver.

**Attention** This is a public forum