File information: | |
File name: | 321 TAP info.pdf [preview 321] |
Size: | 133 kB |
Extension: | |
Mfg: | Bose |
Model: | 321 🔎 |
Original: | |
Descr: | Bose 321 Serial Commands |
Group: | Electronics > Automobile > Car Audio |
Uploaded: | 02-01-2011 |
User: | Ghostlane |
Multipart: | No multipart |
Information about the files in archive: | ||
Decompress result: | OK | |
Extracted files: | 1 | |
File name 321 TAP info.pdf CLASS SR REV REVISIONS DESCRIPTION CHECK DWG NO. 266861 ENG DATE APPLICABLE DOCUMENTS: DOC LVL 3 2 1 DRAFTER M. HICKMAN CHECKER B. BITTER ENGINEER M. HICKMAN RLS TO PROD DATE 4/23/02 4/23/02 4/23/02 SIZE A FRAMINGHAM, MA 01701-9168 DESCRIPTION AV3·2·1 TEST AUTOMATION PROTOCOL FSCM 32108 CLASS SR DWG NO. REV. 266861 00 SHT 1 OF 14 1. INTRODUCTION This protocol describes the control of the 3·2·1 product via TAP (Test Access Port) for software V&V, manufacturing, and field service usage. 2. TAP USERS GUIDE Communications Link a) b) c) Three-wire TTL electrical interface. (Transmit Data, Receive Data, Ground) Logically inverted receive and transmit signals from RS-232 specification. Same asynchronous character/timing construction as RS-232 specification requires. The asynchronous protocol has the following specific configuration: a) b) c) d) e) f) Half-Duplex operation 9600 baud 8-bits / data character 1 Stop bit No Parity The console echoes all characters of the command, including the terminating carriage return There is no special action required to put the 3·2·1 product into TAP mode: when power is applied TAP control may be used. The connected console should not attempt to send a new character until the echo of the previous character is returned. The consequence of not waiting for the echo is the possibility of overrunning the previous character, thereby changing the command, or rendering it unrecognizable. 3·2·1 does not work with multiple commands simultaneously. The user must receive an acknowledgement prior to issuing the next TAP command. Framingham, MA 01701-9168 SIZE A FSCM 32108 CLASS DWG NO. SR 266861 SHEET 2 of 14 REV. 00 3. GENERAL MESSAGES FOR CONTROL OF HARDWARE SUBSYSTEMS OF 3·2·1 Conventions: 1. 2. 3. All transmitted or received characters are presented in bold, fixed-width font. String names are in fixed width font, not bold, and all caps. A named string represents the characters to be received. Each alternative response is enclosed in parentheses and the choices separated by the word "or." Both the parentheses and the word "or" do not count as part of the response. Repeated strings are surrounded by parentheses and followed by "*n", where n is the number of occurrences. White space between characters or string names (Item 3) represent the character 0x20. Responses represented using multiple lines imply the strings of each line are concatenated without any line termination characters or white space in between. Special Characters are represented by the following constructs: a. b. c. 8. \r \n · 0x0D 0x0A 0x20 Carriage Return Line feed (newline) Space (Used for leading or multiple spaces only) 4. 5. 6. 7. Response strings: String Name a. NEWLINE b. c. d. e. f. g. ACK NACK NACK> SACK SNACK NACK> BADLINE Transmitted characters \n\r (NEWLINE)*2 ·ACK> (NEWLINE)*2 NEWLINE ·ACK> NEWLINE \n\r\r where aaaa is the hex representation of the starting address of the data, and dd is the hex representation of the data v |
Date | User | Rating | Comment |