From fe178520b884f60abe83dad45c4fef6ca501e942 Mon Sep 17 00:00:00 2001 From: TC Wan Date: Tue, 4 Jan 2011 16:41:58 +0800 Subject: fixed comment regarding header length for telegram size calculation --- Debugger/debug_comm.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Debugger') diff --git a/Debugger/debug_comm.S b/Debugger/debug_comm.S index 11cba1c..480b1bd 100644 --- a/Debugger/debug_comm.S +++ b/Debugger/debug_comm.S @@ -288,7 +288,7 @@ _exit_conv_ascii2byte: * =========== * Byte 0: Telegram Type Field (0x8d Direct Command, No response required) | USB Channel Header * Byte 1: Segment No (1-255, 0: Last Segment; limit is MSG_NUMSEGMENTS) | - * Byte 2: Telegram Size (Len of USB Buffer - 2, max is MSG_SEGMENTSIZE) | + * Byte 2: Telegram Size (Len of USB Buffer - 3, max is MSG_SEGMENTSIZE) | * Byte 3-N: Message data | GDB Command * * The GDB Command (of size M) has the following format: @@ -305,7 +305,7 @@ _exit_conv_ascii2byte: * ============ * Byte 0: Telegram Type Field (0x8d Direct Command, No response required) | USB Channel Header * Byte 1: Segment No (1-255, 0: Last Segment; limit is MSG_NUMSEGMENTS) | - * Byte 2: Telegram Size (Len of USB Buffer - 2, max is MSG_SEGMENTSIZE) | + * Byte 2: Telegram Size (Len of USB Buffer - 3, max is MSG_SEGMENTSIZE) | * Byte 3-N: Message data | GDB Response * * The GDB Response (of size M) has the following format: -- cgit v1.2.3