Using a segger's flasher 5 programmer in labview

Question

I want to use labview to send and receive commands to a Flasher 5 programmer made by Segger.  It comes with ASCII command sets, and I was unsucessful in getting the return information using the basic serial read and write, labview example, error states that is timeout on the read.  When you send a AUTO  command the programmer is suppose to erase, program and verify the microcontroller, in which it sends back response when it completes each step.  The port is setup correctly, because when the auto command is sent, the programmer lights blink, but having problems with the read.  Anyone familiar with this particular programmer and could give me some pointers, it would be much appreciated.
Solved!
Go to Solution.

Answer 1

I was using the basic serial read and write in the labview examples, so its a common VI, the issue was getting the response back from the programmer.  Listed below is the command set when using the programmer in serial mode.
 #AUTO
The Auto command behaves exactly as the start button or external remote control input.
·    Flasher starts clearing target, if “automatic clear before program“ option was set.
·    Flasher programs target CPU
·    Flasher verifies target CPU
·    Flasher verifies its internal CRC to validate the programming operation.
Finally, Flasher responds with
·    #OK if no error occurred
·    #ERRxxx if any error occurred during operation. xxx represents the errorcode, normally replied to Flasher PC program. The #ERRxxx message may be followed by an additional error text.
During execution of the AUTO command, Flasher automatically sends “status” messages via RS232 to reflect the state of execution. Typically during execution of #AUTO command, Flasher will reply the following sequence of messages:
#ACK
#STATUSTART CMD
#STATUS:CONNECTING
#STATUS:CLEARING
#STATUS:WRITING
#STATUS:VERIFYING
#STATUS:VERIFY FLASHER CRC
#OK
or no staus until end:
#AUTO NOINFO
This command may be used instead of AUTO, if no status messages from Flasher should be sent during execution.
The command ends with #OK or #ERRxxx 
EACH command sent ends in an ASCII 13 ("CR").
Labview is timing out before the response even if I increase the time.