Marantz SR7300 User Manual

0 (0)

SW-A0271-HSI-002 : Rev 02

Marantz

RS232C Control Specifica tion

for

SR7300/SR7300OSE

Number of Page :19

Category

Document Version

Date

: AV. Receiver

: 2.01

: 2003/07/01

Hardware Software Interface (HSI) Spec. Page: 2 / 19 SR7300/SR7300OSE Document Version [2.01]

Table of Contents

Introduc tio n.............................................. ........ ........ ...... ......... ........ ...... ........ ......... ............................................3

1-1. Purpose.................... ...... ........ ....... ........ ........ ...... ........ ......... ...... ........ ...... ......... ........ ... .................................3

1-2. Scope................. ...... ........ ...... ......... ........ ...... ........ ......... ...... ........ ...... ........ ......... ...... .. ...... ...... ........ ......... .....3

1-3. Abbreviatio ns................. ...... ........ ......... ...... ........ ........ ....... ........ ...... ........ ......... ...... ........................... ........ ...3

1-4. References........................ ........ ......... ...... ........ ........ ....... ........ ...... ........ ........ ....... ........ .. ...... ...... ......... ........ .3

2. Global Description............................................................................................................................................ .3

2-1. Overview.............. ........ ...... ........ ......... ...... ........ ........ ....... ........ ...... ........ ........ ....... .......................... ......... .....3

2-2. Block Diagra m........................................ .......... ........ ........... .......... ........ ........... .......... ...... .... ........ ......... ...... .3

2-3. Interface connecter specification of This Product........................................................................................3

2-4. Assumptions and Dependencies.................................................................................................................3

3. Detai led De scr ipti on...................................... ............ ........... ............ ............ ........... ........... ...............................4

3-1. Connection f or mat............................ .......... .......... ......... .......... ........ .......... ........... ........ ...... ...... ......... ........ ...4

3-1-1. Ph ysi cal conn ecti on...................................... ........... ............ .......... ............. ............ .......... ...... ....... .......4

3-1-1-1. Data tra nsmi ssio n se que nce fr om Ho st to Sla ve.............. ............ ........... ............ ............. .......... .4

3-1-1-2. Data tra nsmi ssio n se que nce fr om Sl ave to Ho st.............. ............ ........... ............ ............. .......... .4

3-2. Transmi ssio n d at a f orm at......................................... ........... ........ .......... ........... ........ .......... .... ......... ........ .....5

3-2-1. Transm is sion da ta fo rma t fr om H ost to Sla ve..................... .......... ........... ........ .......... .......... ......... ..... ..5

3-2-1-1. Form1: Co mma nd............................................. ........ .......... ........ ........... .......... ........ ........... .. .......5

3-2-1-2. Form2: Sta tus req ue st....................................... ........ .......... ........ ........... .......... ........ ........... .........5

3-2-2. Transm is sion da ta fo rma t fr om S la ve to Ho st....................... ........ ........... ........ .......... .......... ......... ..... ..5

3-2-2-1. Form1: AC K/NAK.............. .......................... ............................. ........................... ..................... .....5

3-2-2-2. Form2: Sta tus an swe r................. .......... ......... .......... .......... ........ ........... ........ .......... ........... ... ........5

3-3. The transact ion seq ue nces an d th e re gu lat ion s......................... ........ ........... .......... ........ .......... .......... ........6

3-3-1. T he tra nsa ctio n se quen ces.................. .......... ............. .......... ............ ............. .......... ............ ....... ...... ...6

3-3-2. T he tra nsa ctio n reg ula tion s.......................... ............. .......... ............ ........... ............ ............ .... ............. .6

3-3-3. Ex amp le of the tr an sacti on s..................... ............ ............. .......... ............. ............ .......... ......... ........ .....6

3-3-4. Ex am pl es of t he ha nd sh aki ng fl ow ch ar t................................. ...... ......... ........ ...... ........ ........ ....... ..... ....7

3-3-4-1. Example o f su cce ss ful han dsh aki ng..................... .......... .......... ......... .......... .......... ........ ........... ...7

3-3-4-2. Example o f er ro r ha nd sha ki ng................................ ........ ...... ........ ....... ........ ........ ...... ......... ....... ..7

3-4. Command list................... ........ ........... ........ .......... .......... ......... .......... .......... ......... .......... ..............................8

3-4-1. N or mal Co mm an d li st............................. ...... ......... ...... ........ ........ ...... ......... ........ ...... ........ ..... .... ........ ...8

3-5. Statu s r eq ue st an d Stat us an sw e r li st........................ ......... ...... ........ ........ ....... ........ ...... ........ ...... ..... ...... ...13

3-5-1. N orm al Sta tu s re qu est a nd Statu s an sw er list................................ ........... ........ .......... ........... ........ ...13

3-5-2. Speci al Statu s r equ est and Statu s a nsw er list...................................... ........... ........ .......... ......... ...... .18

4. Revision h ist ory............................ ............. .......... ............ ............. ............ .......... ............. ...... ...... ......... ........ ...19

Hardware Software Interface (HSI) Spec. Page: 3 / 19 SR7300/SR7300OSE Document Version [2.01]

1. Introduction

1-1. Purpose

This document was written in order to clarify specification for control this product by the host controller.

1-2. Scope

This document would be using by software or h ardware engineers for prod uction of this product. This product is [marantz SR7300/SR7300OSE]. (It’s refe r ed to a s “ Th is pr od u ct” a f ter th i s.)

1-3. Abbreviations

Abbreviation Description

1-4. References

2. Global Description

2-1. Overview

A Host controller can control or watch out this product as a Slave very easily via the communication cable.

2-2. Block Diagram

2-3. Interface connecter specification of This Product

Processor Interface Signal name Connection device D-Sub Pin Connecter

2-4. Assumptions and Dependencies

HOST

(Controller)

- N.C. - 1 TxD (output) 2 UART RxD (input)

- N.C. 4

- GND 5

- N.C. CTS (input) 7 GENERAL PORT RTS (output)

- N.C. - 9

RS232C ca ble ( str aig ht)

RS232C Level shift driver

(This product)

Connector D-SUB (9pin, male)

6 8

SLAVE

RS232C D-SUB

(9pin,male)

Hardware Software Interface (HSI) Spec. Page: 4 / 19 SR7300/SR7300OSE Document Version [2.01]

3. Detailed Description

The interface specification between this product and a Host controller is described below.

3-1. Connection format

3-1-1. Physical connection

Host (Controller) Slave (This product)

RTS

CTS

(Serial setting <RS232C basic>) Baud Rate : 9600bps

TxD

Data Bits : 8bit Parity : None

RxD

Stop bit : 1bit

Handshaking : (RTS/CTS)

3-1-1-1. Data transmission sequence from Host to Slave

Host (Controller) Slave (This product)

3-1-1-2. Data transmission sequence from Slave to Host

GND

RTS → CTS

CTS ← RTS

TxD → RxD

RxD ← TxD

1. The host checks that CTS is High, then starts a data transmission from TxD.

2. The host performs the data transmission of the number of required bytes, and ends a transmission. * The host can do RTS to Low during the transmission for disable dat a transmission from a slave.

Host (Controller) Slave (This product)

RTS → CTS

CTS ← RTS

TxD → RxD

RxD ← TxD

1. The slave checks that CTS is High, then starts a data transmission from TxD.

2. The slave performs the data transmission of the number of required bytes, and ends a transmission. * The slave can do RTS to Low during the transmission for disable data transmission from a host.

CTS

RTS

RxD

TxD

GND

Hardware Software Interface (HSI) Spec. Page: 5 / 19 SR7300/SR7300OSE Document Version [2.01]

3-2. Transmission data format

3-2-1. Transmission data format from Host to Slave

There are two kinds of transmission data form from Host shown below .

3-2-1-1. Form1: Command

Command is a data that requests some status change. Start chara cter : ’@’ ID : ‘0’ ~ ‘9’ (A Slave has ow n ID, A Host has to set the ID.) COMMAND : see “Command list”

End character : 0Dh

COM M ANDStart

‘@

’

3-2-1-2. Form2: Status request

Status request is a data that requests a answer of some status. Start chara cter : ’@’ ID : ‘0’ ~ ‘9’ (A Slave has ow n ID, A Host has to set the ID.) Request character : ‘?’ Request status : see “Status request list”

End character : 0Dh

S tart

‘@ ’

R equest status

‘?’

3-2-2. T ransmission dat a format from Slave to Host

There are two kinds of transmission data form from Slave shown below .

3-2-2-1. Form1: ACK/NAK

ACK is a reply data from Slave when Slave got an acceptable command data from Host.

ACK : 06h

ACK

06h

NAK is a reply data from Slave when Slave got an incorrect Command data, Status request data or

some other data from Host.

NAK : 15h

NAK

15h

3-2-2-2. Form2: Status answer

Status answers are reply dat a when Slave got an acceptable Re quest status data fro m Host. Start chara cter : ’@’ ID : ‘0’ ~ ‘9’ (A Slave will set own ID.) Answer cha racter : see “S t atu s an swer list”

End character : 0Dh

End

0D h

End

0D h

End

0D h

‘@ ’

Status answ erStart

Hardware Software Interface (HSI) Spec. Page: 6 / 19 SR7300/SR7300OSE Document Version [2.01]

3-3. The transaction sequences and the regulations

3-3-1. The transaction sequences

The transactions have two kinds of sequence.

*A transaction is a Command from Host then the Sla ve will be an answer by ACK or NAK.

*A transaction is a S t atus request fro m Host then the Slave will be an an swer by Status answer.

3-3-2. The transaction regulations

The transactions have some kinds of regulation.

* A Command or a Status request transmission by the Host has to finish within one second.

* An answer (ACK , NAK or Status answer) transmitt ion by the Slave ha s to finish withi n one second

when got a Command or a Status request from the Host.

* The Host must not transmit an another Command or Status request until "it receives a answer by a

previous Command or Status request" or "it passes one second from a finishing of previous transmission

of a Command or a Sta tus request ".

3-3-3. Example of the transactions

RTS CTS

CTS RTS

TxD RxD

RxD TxD

Command

max. 1sec

a transaction a transaction

max. 1sec

ACK/NAK

Example of the transactions

Status request

max. 1sec

Status answer

+ 13 hidden pages