TWI767997B - Communication device, communication method, program, and communication system - Google Patents

Communication device, communication method, program, and communication system Download PDF

Info

Publication number
TWI767997B
TWI767997B TW107106711A TW107106711A TWI767997B TW I767997 B TWI767997 B TW I767997B TW 107106711 A TW107106711 A TW 107106711A TW 107106711 A TW107106711 A TW 107106711A TW I767997 B TWI767997 B TW I767997B
Authority
TW
Taiwan
Prior art keywords
data
transmission
length
communication device
read
Prior art date
Application number
TW107106711A
Other languages
Chinese (zh)
Other versions
TW201837728A (en
Inventor
高橋宏雄
越坂直弘
Original Assignee
日商索尼半導體解決方案公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日商索尼半導體解決方案公司 filed Critical 日商索尼半導體解決方案公司
Publication of TW201837728A publication Critical patent/TW201837728A/en
Application granted granted Critical
Publication of TWI767997B publication Critical patent/TWI767997B/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
    • G06F13/4291—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus using a clocked protocol
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/28—Handling requests for interconnection or transfer for access to input/output bus using burst mode transfer, e.g. direct memory access DMA, cycle steal
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4004—Coupling between buses
    • G06F13/4009—Coupling between buses with data restructuring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40032—Details regarding a bus interface enhancer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/403—Bus networks with centralised control, e.g. polling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/1438—Negotiation of transmission parameters prior to communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/36—Handling requests for interconnection or transfer for access to common bus or bus system
    • G06F13/362—Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control
    • G06F13/364—Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control using independent requests or grants, e.g. using separated request and grant lines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F2213/0016—Inter-integrated circuit (I2C)
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • H04L1/0063—Single parity check
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40143—Bus networks involving priority mechanisms
    • H04L12/40156—Bus networks involving priority mechanisms by using dedicated slots associated with a priority level

Abstract

本揭示係關於一種可更確實地進行通信之通信裝置、通信方法、程式及通信系統。 I3C主控器自I3C受控器接收最大讀取長度及最大寫入長度。且，於對I3C受控器進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為最大讀取長度及最大寫入長度之方式控制資料之收發，且於對資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。本技術可應用於例如匯流排IF。The present disclosure relates to a communication device, a communication method, a program, and a communication system capable of more reliable communication. The I3C master receives the maximum read length and maximum write length from the I3C slave. In addition, when data transmission is performed to the I3C slave device, the data transmission and reception are controlled in such a way that the data length of the data transmitted in one data transmission is the maximum read length and the maximum write length, and the data is transmitted during data transmission. Previously, transmission length information was sent indicating the data length of the data to be transmitted. The present technology can be applied to, for example, a bus bar IF.

Description

通信裝置、通信方法、程式及通信系統Communication device, communication method, program, and communication system

本揭示係關於一種通信裝置、通信方法、程式及通信系統，尤其是關於一種可更確實地進行通信之通信裝置、通信方法、程式及通信系統。The present disclosure relates to a communication device, a communication method, a program, and a communication system, and more particularly, to a communication device, a communication method, a program, and a communication system that can communicate more reliably.

先前以來，作為用以控制各種器件之暫存器之匯流排IF(Interface：介面)，廣泛使用CCI(Camera Control Interface：相機控制介面)，於CCI中，對實體層採用I2C(Inter-Integrated Circuit：內部積體電路)規格。 例如，於CCI中，於開始資料傳輸時，自系統控制器對被控制器件預先通知成為進行資料之讀出或寫入對象的暫存器之開頭位址(Index：索引)。並且，系統控制器每當進行1位元組之資料傳輸時，判定是否已對暫存器進行所需資料量之讀出或寫入。且，於系統控制器判定為已對暫存器進行所需資料量之讀出或寫入之情形時，進行結束資料傳輸之控制。 例如，專利文獻1中，揭示一種藉由主器件向I2C匯流排串列地輸出從屬器件之位址、寫入指示、寫入對象之暫存器位址及寫入資料，而由從屬器件進行對暫存器之寫入之技術。 [先前技術文獻] [專利文獻] [專利文獻1]日本專利特開2016-018319號公報In the past, CCI (Camera Control Interface) has been widely used as a bus IF (Interface) for controlling registers of various devices. In CCI, I2C (Inter-Integrated Circuit) is used for the physical layer. : Internal integrated circuit) specifications. For example, in CCI, when starting data transfer, the system controller notifies the controlled device in advance of the head address (Index: index) of the register to be read or written to. In addition, the system controller determines whether the required amount of data has been read or written to the register every time a 1-byte data transmission is performed. In addition, when the system controller determines that the required amount of data has been read or written to the register, the control of ending the data transfer is performed. For example, Patent Document 1 discloses a method of serially outputting the address of the slave device, the write instruction, the register address of the write object, and the write data to the I2C bus from the master device, and the slave device performs The technique of writing to the scratchpad. [Prior Art Document] [Patent Document] [Patent Document 1] Japanese Patent Laid-Open No. 2016-018319

[發明所欲解決之問題] 如上所述，於CCI中對實體層採用I2C規格。因此，由於傳送速率為最大1 Mbps之低速，故要求實現更為高速化。因此，作為下一代之規格，策定了傳送速率為最大37.5 Mbps之高速之I3C(Improved Inter Integrated Circuit：經改良積體電路間)規格，且逐步推進其修訂。又，亦進行對實體層使用I3C之新穎之CCI之探討。 然而，於I3C之HDR模式中，當探討採用於資料傳輸中包含傳輸之資料之資料長度(位元組數)之訊框構成時，在新型之CCI與I3C之間會有發生衝突之疑慮，且有無法正常地進行通信之虞。 本揭示係鑑於此種狀況而完成者，可更確實地進行通信。 [解決問題之技術手段] 本揭示一態樣之通信裝置係經由匯流排進行通信者，且藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，上述第1通信裝置具備：取得部，其自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度；收發控制部，其於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發；及發送部，其對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。 本揭示一態樣之通信方法或程式係經由匯流排進行通信者，且藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，且該通信方法或程式包含以下步驟：上述第1通信裝置自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度，於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發，於對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。 本揭示一態樣之通信系統係經由匯流排，藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信者，且上述第1通信裝置具備：取得部，其自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度；收發控制部，其於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發；及發送部，其對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。 於本發明之一態樣中，自第2通信裝置取得表示第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度，與第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為最大傳輸長度以下之方式控制資料之收發，且於對該資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。 [發明之效果] 根據本揭示之一態樣，可更確實地進行通信。[Problems to be Solved by the Invention] As described above, the I2C specification is adopted for the physical layer in the CCI. Therefore, since the transfer rate is as low as 1 Mbps at the maximum, higher speed is required. Therefore, as a next-generation specification, the high-speed I3C (Improved Inter Integrated Circuit) specification with a maximum transfer rate of 37.5 Mbps has been established, and its revision has been gradually advanced. In addition, a novel CCI using I3C for the physical layer is also discussed. However, in the HDR mode of I3C, when discussing the frame structure used in data transmission including the data length (number of bytes) of the data to be transmitted, there is a fear of conflict between the new CCI and I3C. And there is a possibility that normal communication cannot be performed. The present disclosure has been made in view of such a situation, and communication can be performed more reliably. [Technical Means for Solving the Problem] A communication device of one aspect of the present disclosure communicates via a bus, and through a first communication device having communication mastery, and at least one communication device that communicates according to the control of the first communication device Communication is performed by two or more second communication devices, and the first communication device includes an acquisition unit that obtains, from the second communication device, a maximum value indicating the maximum transmission length that the second communication device can transmit in one data transmission. The transmission length; the transmission and reception control unit, which controls the transmission and reception of data in such a way that the data length of the data transmitted in one data transmission is equal to or less than the above maximum transmission length during data transmission with the above-mentioned second communication device; and the transmission unit, Before it performs data transmission on the above-mentioned data, it sends transmission length information indicating the data length of the data to be transmitted. The communication method or program of one aspect of the present disclosure is one that communicates through a bus, and through a first communication device having communication mastery, and at least one or more second communication devices that communicate under the control of the first communication device. The communication device communicates, and the communication method or program includes the following steps: the first communication device obtains, from the second communication device, a maximum transmission representing the maximum transmission length that the second communication device can transmit in one data transmission. Length, when data transmission is performed with the above-mentioned second communication device, the data transmission and reception are controlled in such a way that the data length of the data transmitted in one data transmission is less than the above-mentioned maximum transmission length, and before data transmission is performed on the above-mentioned data, send Transfer length information indicating the data length of the data to be transferred. The communication system of one aspect of the present disclosure communicates with at least one second communication device that communicates with at least one second communication device that communicates under the control of the first communication device through the bus bar, which has the communication mastery. Further, the first communication device includes: an obtaining unit that obtains, from the second communication device, a maximum transmission length representing the maximum transmission length that can be transmitted by the second communication device in one data transmission; When data transmission is performed with the above-mentioned second communication device, the data transmission and reception are controlled in such a way that the data length of the data transmitted in one data transmission is equal to or less than the above-mentioned maximum transmission length; Send transfer length information indicating the data length of the data to be transferred. In one aspect of the present invention, the maximum transmission length representing the maximum transmission length that can be transmitted by the second communication device in one data transmission is obtained from the second communication device, and when performing data transmission with the second communication device, use In one data transmission, the data length of the data to be transmitted is less than or equal to the maximum transmission length, and the transmission and reception of the data is controlled, and before the data is transmitted, the transmission length information indicating the data length of the data to be transmitted is sent. [Effects of the Invention] According to an aspect of the present disclosure, communication can be performed more reliably.

以下，對應用本技術之具體之實施形態一面參照圖式一面詳細地進行說明。 ＜匯流排IF之構成例＞ 圖1係顯示應用本技術之匯流排IF之一實施形態之構成例之方塊圖。 圖1所示之匯流排IF11構成為將I3C主控器12與3台I3C受控器13-1至13-3經由資料信號線14-1及時脈信號線14-2連接，且可進行依據I3C規格之通信。 I3C主控器12具有匯流排IF11之控制主導權，且可經由資料信號線14-1及時脈信號線14-2與I3C受控器13-1至13-3進行通信。 I3C受控器13-1至13-3可根據I3C主控器12之控制，經由資料信號線14-1及時脈信號線14-2與I3C主控器12進行通信。另，I3C受控器13-1至13-3各自同樣地構成，以下，於無須區分該等之情形時，簡稱為I3C受控器13，對於構成I3C受控器13之各區塊亦同。 資料信號線14-1及時脈信號線14-2用於在I3C主控器12與I3C受控器13之間傳送信號。例如，於匯流排IF11中，經由資料信號線14-1每1位元地逐次傳送串列資料(SDA：Serial Data)，經由時脈信號線14-2，傳送特定頻率之串列時脈(SCL：Serial Clock) I3C主控器12具備：資料發送部21、資料接收部22、指令發送部23、模式控制部24、及收發控制部25，該等各區塊由電路或模組等構成。 資料發送部21經由資料信號線14-1及時脈信號線14-2將資料發送至I3C受控器13。例如，資料發送部21根據藉由驅動時脈信號線14-2而發送之串列時脈之時序，進行對資料信號線14-1之驅動(將電位切換為H位準或L位準)，藉此可將資料發送至I3C受控器13。 資料接收部22經由資料信號線14-1及時脈信號線14-2接收自I3C受控器13傳來之資料。例如，資料接收部22按照時脈信號線14-2之串列時脈之時序，藉由I3C受控器13進行對資料信號線14-1之驅動，而可接收自I3C受控器13傳來之資料。 指令發送部23與資料發送部21同樣地，經由資料信號線14-1及時脈信號線14-2，對I3C受控器13發送如後述之各種指令。 模式控制部24根據來自上階層(例如後述之圖2之CCI層處理部42)之請求，選擇I3C規格所規定之複數種傳輸模式中之任一種，並且以依該選擇之傳輸模式進行通信之方式進行對收發控制部25之控制。 例如，於匯流排IF11中，根據資料之傳輸速率，規定有以通常之傳輸速率進行資料傳輸之SDR(Standard Data Rate：標準資料速率)模式、與以高於SDR模式之傳輸速率進行資料傳輸之HDR(High Data Rate：高資料速率)模式。又，於HDR模式中，根據規格定義有以下3種傳輸速率：DDR(Double Data Rate：雙倍資料速率)模式、TSP(Ternary Symbol Pure-Bus：三元符號純匯流排)模式、及TSL(Ternary Symbol Legacy-inclusive-Bus：三元符號舊版相容性匯流排)模式。 因此，模式控制部24選擇SDR模式、DDR模式、TSP模式、及TSL模式之任一者，並且以依該選擇之傳輸模式進行通信之方式進行對收發控制部25之控制。 收發控制部25以藉由模式控制部24選擇之傳輸模式，根據來自上階層之請求，控制資料發送部21及資料接收部22之資料之收發、及指令發送部23之指令之發送等。 如此構成I3C主控器12，且可根據需要切換傳輸模式，而例如藉由資料發送部21發送要寫入至暫存器之資料，或藉由資料接收部22接收自暫存器讀出之資料。 I3C受控器13具備：資料發送部31、資料接收部32、指令解譯部33、模式控制部34、及收發控制部35，且該等各區塊由電路或模組等構成。 資料發送部31經由資料信號線14-1及時脈信號線14-2將資料發送至I3C主控器12。例如，資料發送部31依照藉由I3C主控器12驅動之時脈信號線14-2之串列時脈之時序，對資料信號線14-1進行驅動，藉此可將資料發送至I3C主控器12。 資料接收部32經由資料信號線14-1及時脈信號線14-2接收自I3C主控器12傳來之資料。例如，資料接收部32依照時脈信號線14-2之串列時脈之時序，藉由I3C主控器12進行對資料信號線14-1之驅動，而可接收自I3C主控器12傳來之資料。 指令解譯部33接收自I3C主控器12之指令發送部23經由資料信號線14-1及時脈信號線14-2傳來之指令，解譯該指令，而進行基於指令之指示之各種處理。例如，指令解譯部33於接收到指示開始HDR模式之通信之指令之情形時，進行對模式控制部34通知開始HDR之通信之處理。又，指令解譯部33當接收到指示寫入資料之指令或指示讀出資料之指令之情形時，進行對收發控制部35通知進行資料寫入或讀出之處理。 模式控制部34根據指令解譯部33接收到之指令之指示，與I3C主控器12之模式控制部24同樣地，選擇SDR模式、DDR模式、TSP模式、及TSL模式之任一者。且，模式控制部34以依該選擇之傳輸模式進行通信之方式對收發控制部25進行控制。 收發控制部35以藉由模式控制部24選擇之傳輸模式，根據指令解譯部33接收到之指令，控制資料發送部31及資料接收部32之資料之收發。 如此構成I3C受控器13，且根據I3C主控器12之控制而切換傳輸模式，例如，可藉由資料發送部31發送自暫存器讀出之資料，或使資料接收部32接收要寫入至暫存器之資料。 如上所述般構成之I3C主控器12及I3C受控器13分別安裝於系統控制器及被控制器件，且可執行由該等進行之通信之實體層中之處理。 圖2係顯示安裝有圖1之I3C主控器12之系統控制器之構成例的方塊圖。 圖2所示之系統控制器41構成為除連接於資料信號線14-1及時脈信號線14-2之I3C主控器12外，並具備CCI層處理部42、CPU43、及內部匯流排44。又，如圖示般，I3C主控器12連接於進行較I3C主控器12為上階之處理的CCI層處理部42，CCI層處理部42經由內部匯流排44而連接於進行系統控制器41整體之控制的CPU43。 CCI層處理部42構成為具備：暫存器位址管理器51、傳輸長度資訊保持部52、寫入傳輸結束控制部53、無效資料處理部54、及傳輸長度資訊發送部55。 暫存器位址管理器51管理連接於圖1之匯流排IF11之各暫存器之位址。 傳輸長度資訊保持部52保持表示與I3C受控器13之間進行之資料傳輸中傳輸之資料之資料長度(位元組數)的傳輸長度資訊(Length)。 寫入傳輸結束控制部53進行結束將自I3C主控器12傳輸至I3C受控器13之資料寫入至暫存器之寫入傳輸時之控制。 無效資料處理部54例如進行以下處理：於將傳輸資料時之最低單位即1字元規定為2位元組(16位元)之HDR模式中，附加或刪除傳輸奇數位元組之資料時使用之虛設資料。 傳輸長度資訊發送部55將保持於傳輸長度資訊保持部52之傳輸長度資訊經由I3C主控器12發送至I3C受控器13。 圖3係顯示安裝有圖1之I3C受控器13之被控制器件之構成例的方塊圖。 圖3所示之被控制器件61構成為除連接於資料信號線14-1及時脈信號線14-2之I3C受控器13外，並具備CCI層處理部62、器件控制部63、及內部匯流排64。又，如圖示般，I3C受控器13連接於進行較I3C受控器13為上階之處理的CCI層處理部62，CCI層處理部62經由內部匯流排64而連接於進行被控制器件61整體之控制的器件控制部63。 CCI層處理部62構成為具備：暫存器位址管理部71、暫存器R/W(讀/寫)控制部72、讀取傳輸結束控制部73、無效資料處理部74、及傳輸長度資訊保持部75。 暫存器位址管理部71管理被控制器件61所具備之暫存器之位址。 暫存器R/W控制部72進行將自I3C主控器12傳輸至I3C受控器13之資料寫入至暫存器之控制、及為了自I3C受控器13發送至I3C主控器12而自暫存器讀出資料之控制。 讀取傳輸結束控制部73進行結束將自暫存器讀出之資料自I3C受控器13傳輸至I3C主控器12之讀取傳輸時之控制。 無效資料處理部74於HDR模式中，進行附加或刪除傳輸奇數位元組之資料時使用之無效資料之處理。 傳輸長度資訊保持部75於與I3C主控器12之間進行資料傳輸時，保持自I3C主控器12傳來之傳輸長度資訊(Length)。 且，器件控制部63例如根據CCI層處理部62之暫存器R/W控制部72之控制，進行將I3C受控器13接收到之資料向狀態暫存器寫入之控制。又，器件控制部63進行例如自狀態暫存器讀出藉由I3C受控器13發送之資料之控制，且根據CCI層處理部62之暫存器R/W控制部72之控制而發送該資料。 於如上所述般構成之系統控制器41及被控制器件61中，例如，可將向暫存器寫入之資料自系統控制器41向被控制器件61傳輸，或將自暫存器讀出之資料自被控制器件61向系統控制器41傳輸。 ＜資料傳輸之第1處理例＞ 參照圖4至圖6，對匯流排IF11中傳輸資料之第1資料傳輸處理之一例進行說明。 圖4係顯示傳輸模式為DDR模式之情形時，於I3C主控器12與I3C受控器13之間收發之信號之格式。於圖4之上側，顯示進行將自暫存器讀出之資料自I3C受控器13向I3C主控器12傳輸之讀取傳輸處理時之格式。於圖4之下側，顯示進行將要寫入至暫存器之資料自I3C主控器12向I3C受控器13傳輸之寫入傳輸處理時的格式。 於進行讀取傳輸處理之情形時，首先，I3C主控器12發送指示開始或重啟HDR模式之通信之指令(ENTHDR或HDR_Restart)。接著，I3C主控器12發送指示進行用以向I3C受控器13通知自暫存器讀出並傳輸之資料之資料長度之寫入的寫入指令(DDR_Cmd(W))。且，I3C主控器12接續寫入指令，發送通知開始讀出資料之開頭位址之索引(Index)、表示傳輸之資料之資料長度之傳輸長度資訊(Length)、及CRC(Cyclic Redundancy Check：循環冗餘檢查)字元。隨後，I3C主控器12發送指示重啟HDR模式之通信之指令(HDR_Restart)，並發送指示讀出資料之讀取指令(DDR_Cmd(R))。 據此，I3C受控器13自對應於索引之位址之開頭依序按DDR模式之每1字元(16位元)傳輸資料，並於對應於傳輸長度資訊之讀取位元組數之資料發送結束時，發送CRC字元。隨後，I3C主控器12發送指示重啟或結束HDR模式之通信之指令(HDR_Restart或HDR_Exit)。 於進行寫入傳輸處理之情形時，首先，I3C主控器12發送指示開始或重啟HDR模式之通信之指令(ENTHDR或HDR_Restart)。接著，I3C主控器12發送指示寫入資料之寫入指令(DDR_Cmd(W))、通知開始寫入資料之開頭位址之索引(Index)、及表示傳輸之資料之資料長度之傳輸長度資訊(Length)。且，I3C主控器12自對應於索引之位址之開頭依序按DDR模式之每1字元(16位元)傳輸資料，且於對應於傳輸長度資訊之寫入位元組數之資料發送結束時，發送CRC字元。隨後，I3C主控器12發送指示重啟或結束HDR模式之通信之指令(HDR_Restart或HDR_Exit)。 圖5係顯示於傳輸模式為TSL模式或TSP模式之情形時，於I3C主控器12與I3C受控器13之間收發之信號之格式。於圖5之上側，顯示進行將自暫存器讀出之資料自I3C受控器13向I3C主控器12傳輸之讀取傳輸處理時之格式。於圖5之下側，顯示進行將所要寫入至暫存器之資料自I3C主控器12向I3C受控器13傳輸之寫入傳輸處理時的格式。 此處，TSL模式或TSP模式為就不進行圖4所示之CRC字元之發送之點與DDR模式不同、其他點皆為共通之格式。 如此，於第1資料傳輸處理中，於傳輸資料時，自I3C受控器13向I3C主控器12發送傳輸長度資訊。且，該傳輸長度資訊於系統控制器41側被保持於CCI層處理部42之傳輸長度資訊保持部52，於被控制器件61側被保持於CCI層處理部62之傳輸長度資訊保持部75。 藉此，例如，於請求傳輸之資料的資料長度為奇數位元組之情形時，即使附加1位元組之虛設資料而傳輸，亦可基於傳輸長度資訊辨識該虛設資料並將其捨棄。藉此，即使於傳輸資料時之最低單位即1字元為2位元組(16位元)，亦可確實地進行奇數位元組之資料之傳輸。 然而，於I3C中，規定有每1次之讀取傳輸所能傳輸之位元組數之上限(以下稱為最大讀取長度(MRL：Max Read Length))。同樣地，於I3C中，規定有每1次之寫入傳輸所能傳輸之最大之位元組數之上限(以下稱為最大寫入長度(MWL：Max Write Length))。通常，最大讀取長度及最大寫入長度除了於設計時點根據被控制器件61各者之安裝上之情況而設為固定值以外，例如於與其他共享資源之情形等可設為可變。 例如，I3C主控器12於自CCI層處理部42請求資料傳輸之資料之資料長度長於最大讀取長度或最大寫入長度之情形時，進行以成為最大讀取長度或最大寫入長度以下之方式將資料分割並傳輸之控制。 圖6係對I3C主控器12中進行之處理進行說明之流程圖。 於步驟S11中，I3C主控器12對連接於匯流排IF11之各I3C受控器13發送指示發送各個I3C受控器13之最大讀取長度及最大寫入長度之指令(GETMWL/MRL)。且，I3C主控器12根據該指令，取得自各個I3C受控器13發送之最大讀取長度及最大寫入長度。 於步驟S12中，I3C主控器12判定是否需要調整步驟S11中取得之各I3C受控器13之最大讀取長度或最大寫入長度。例如，I3C主控器12比較設想自CCI層處理部42請求資料傳輸之資料的資料長度、與I3C受控器13之最大讀取長度及最大寫入長度各者。且，I3C主控器12於I3C受控器13之最大讀取長度及最大寫入長度之至少一者為設想之資料的資料長度以下之情形時，判定為需要調整設想之資料的資料長度以下之最大讀取長度或最大寫入長度。又，I3C主控器12例如亦可將I3C主控器12自身之最大讀取長度及最大寫入長度作為設想之資料之資料長度而進行比較。 於步驟S12中，若I3C主控器12判定為需要調整I3C受控器13之最大讀取長度或最大寫入長度，處理前進至步驟S13。 於步驟S13中，I3C主控器12調整判定為需要調整之I3C受控器13之最大讀取長度或最大寫入長度，且將設定調整後之最大讀取長度及最大寫入長度之指令(SETMWL/MRL)發送至I3C受控器13。例如，I3C主控器12將設想為自CCI層處理部42請求資料傳輸之資料的資料長度以下之I3C受控器13的最大讀取長度或最大寫入長度，調整為該設想之資料的資料長度。又，I3C主控器12例如亦可將I3C受控器13之最大讀取長度或最大寫入長度，調整為I3C主控器12自身之最大讀取長度及最大寫入長度。 於步驟S13之處理後，或步驟S12中判定為無須調整I3C受控器13之最大讀取長度或最大寫入長度之情形時，處理前進至步驟S14。 於步驟S14中，I3C主控器12等待自上階層的CCI層處理部42請求資料傳輸，當有資料傳輸之請求時接收該請求。 於步驟S15中，I3C主控器12判定步驟S14中自CCI層處理部42請求資料傳輸之資料之資料長度是否長於進行資料傳輸之對象之I3C受控器13之最大讀取長度或最大寫入長度。例如，於步驟S13中如已調整I3C受控器13之最大讀取長度或最大寫入長度之情形時，基於調整後之最大讀取長度或最大寫入長度進行判定。 於步驟S15中，若I3C主控器12判定為請求資料傳輸之資料的資料長度長於進行資料傳輸之對象之I3C受控器13之最大讀取長度或最大寫入長度，處理前進至步驟S16。於步驟S16中，I3C主控器12將請求資料傳輸之資料分割成進行資料傳輸之對象之I3C受控器13之最大讀取長度或最大寫入長度以下之長度，並進行讀取傳輸處理或寫入傳輸處理。 另一方面，於步驟S15中，若I3C主控器12判定為請求資料傳輸之資料的資料長度非長於進行資料傳輸之對象之I3C受控器13之最大讀取長度或最大寫入長度(最大讀取長度或最大寫入長度以下之長度)，處理前進至步驟S17。於步驟S17中，I3C主控器12不分割資料而進行通常之讀取傳輸處理或寫入傳輸處理。 步驟S16或S17之處理後，處理返回至步驟S14，I3C主控器12等待來自上階層的CCI層處理部42之資料傳輸請求，後續重複進行同樣之處理。 如此，I3C主控器12於請求長於I3C受控器13中設定之最大讀取長度或最大寫入長度之資料之資料傳輸之情形時，可將該資料分割並傳輸。 即，於系統控制器41中，I3C主控器12取得I3C受控器13之最大讀取長度及最大寫入長度，且於與I3C受控器13進行資料傳輸時，以1次之資料傳輸所能傳輸之資料之資料長度為最大讀取長度及最大寫入長度以下之方式，藉由收發控制部25控制資料之收發。且，於系統控制器41中，CCI層處理部42可對表示傳輸之資料的資料長度之傳輸長度資訊設定最大讀取長度及最大寫入長度以下之資料長度，且I3C主控器12於資料傳輸資料之前，將該傳輸長度資訊發送至I3C受控器13。 例如，於步驟S17中進行通常之讀取傳輸處理或寫入傳輸處理時，I3C受控器13進行於CCI層處理部42中以不超過最大讀取長度及最大寫入長度之方式設定之資料傳輸。 又，於步驟S16中分割成最大讀取長度或最大寫入長度以下之長度而進行讀取傳輸處理或寫入傳輸處理時，I3C受控器13以分成複數次發送資料之方式進行資料傳輸。此時，I3C受控器13例如可就每次之資料傳輸發送傳輸長度資訊。或者，如後述般，I3C受控器13於進行讀取傳輸處理時，可僅發送1次表示請求傳輸之資料整體之資料長度之傳輸長度資訊，藉此可降低處理負擔而避免傳輸效率降低。 然而，亦設想存在與指示發送最大讀取長度及最大寫入長度之指令(GETMRL,GETMWL)不對應之I3C受控器13。或者，亦設想I3C主控器12非有意地將超過最大讀取長度或最大寫入長度之長度設定為傳輸長度資訊之情形。 因此，於寫入較最大寫入長度為長之資料長度之資料時，會發生I3C受控器13側之FIFO(First In,First Out：先入先出)溢出之事態。 作為針對此種事態之第1對策，I3C受控器13於FIFO溢出為止正常地寫入資料，將FIFO溢出後之資料全部捨棄，建立表示發生FIFO溢出之錯誤之錯誤旗標(over MWL error)，且將錯誤旗標保持至清除為止。且，I3C受控器13於接收到下一個HDR結束指令或HDR重啟指令(HDR_Exit或HDR_Restart) 為止，忽略一切信號。 又，作為第2對策，I3C受控器13於達到最大寫入長度後，進行自I3C受控器13側中斷通信之處理(Slave Abort)。據此，I3C主控器12停止通信，並可藉由HDR結束指令(HDR_Exit)使其停止，或發佈HDR重啟指令(HDR_Restart)而繼續剩餘之資料之傳輸。 又，作為第3對策，由於I3C受控器13可於接收到傳輸長度資訊之時點辨識超過最大寫入長度，故隨後立即進行自I3C受控器13側中斷通信之處理(Slave Abort)。據此，I3C主控器12停止通信，可藉由HDR結束指令(HDR_Exit)使其停止，或發佈HDR重啟指令(HDR_Restart)而繼續剩餘之資料之傳輸。 再者，於讀出較最大讀取長度之資料長度為長之資料時亦需要採取對策。 例如，作為第1對策，因I3C受控器13難以將資料傳輸進行至最後，故於接收到讀取指令後立即回覆NACK而使通信結束。且，I3C受控器13建立表示因指示讀出較最大讀取長度為長之資料長度之資料而發生錯誤之錯誤旗標(over MRL error)，且將錯誤旗標保持至清除為止。 又，作為第2對策，I3C受控器13暫且將資料傳輸至I3C主控器12直至達到最大讀取長度之上限。且，於達到最大讀取長度之時點建立錯誤旗標(over MRL error)，於DDR模式之情形時將結束封包即CRC字元發送至I3C主控器12，於TSP/TSL模式之情形時，停止對資料信號線14-1及時脈信號線14-2之驅動，而釋放匯流排。 另一方面，於I3C主控器12側，於DDR模式之情形時，於達到傳輸長度資訊所示之資料長度為止，且在已受理CRC字元之階段，辨識為I3C受控器13發生錯誤(over MRL error)。而如未發生CRC錯誤，則I3C主控器12受理該時點為止之資料。 又，於I3C主控器12側，於TSL/TSP模式之情形時，於達到傳輸長度資訊所示之資料長度之前，且於檢測出未進行對資料信號線14-1及時脈信號線14-2之驅動(未觸發)之狀態之階段，辨識為I3C受控器13發生錯誤(over MRL error)。 且，無論為DDR模式及TSL/TSP模式之何者，I3C主控器12於辨識到I3C受控器13之錯誤(over MRL error)以後，皆以依不超過最大讀取長度之資料長度進行HDR讀取處理之方式進行資料之重新發送。 ＜資料傳輸之第2處理例＞ 參照圖7至圖25，對匯流排IF11中傳輸資料之第2資料傳輸處理進一步詳細地進行說明。 於圖7顯示於傳輸模式為DDR模式之情形時，進行將超過最大讀取長度之資料分割並傳輸，且自I3C受控器13向I3C主控器12讀出資料之讀取傳輸處理時的格式。另，於圖7中顯示於最大讀取長度為200位元組時，請求傳輸300位元組之資料時之例。 首先，I3C主控器12發送指示開始或重啟HDR模式之通信之指令(ENTHDR或HDR_Restart)。接著，I3C主控器12發送指示進行用以通知I3C受控器13自暫存器讀出並傳輸之資料之資料長度之寫入的寫入指令(DDR_Cmd(W))。 接著，I3C主控器12接續寫入指令，發送通知開始讀出資料之開頭位址之索引(Index)、表示傳輸之資料之資料長度之傳輸長度資訊(Length)、及CRC字元。隨後，I3C主控器12發送指示重啟HDR模式之通信之指令(HDR_Restart)，且發送指示讀出資料之讀取指令(DDR_Cmd(R))。於圖7所示之例中，將開始讀出資料之開頭位址設為0位址，將傳輸之資料之資料長度設為300位元組，且按最大讀取長度即每200位元組進行分割而傳輸資料。 據此，I3C受控器13根據索引，自0位址之位址起依序按DDR模式之每1字元(16位元)傳輸資料，且於成為最大讀取長度之200位元組之資料發送結束後，發送CRC字元。 隨後，I3C主控器12發送指示重啟HDR模式之通信之指令(HDR_Restart)，接著，發送指示資料之讀出之讀取指令((DDR_Cmd(R))。 此時，I3C受控器13根據已發送出傳輸長度資訊所示之300位元組中之200位元組之資料，而可辨識其後續之開頭位址為200位址，且需要發送剩餘之100位元組。因此，I3C受控器13自200位址之位址起依序按DDR模式之每1字元(16位元)傳輸資料，且於100位元組之資料發送結束時，發送CRC字元。 藉此，讀出請求傳輸之300位元組之資料，且I3C主控器12發送指示重啟或結束HDR模式之通信之指令(HDR_Restart或HDR_Exit)。 如上所述，I3C主控器12於進行讀取傳輸處理時，如參照上述之圖4說明般，於自I3C受控器13讀出資料之前，發送索引及傳輸長度資訊，藉此向I3C受控器13通知開始讀出資料之開頭位址及所要傳輸之資料的資料長度。此處，I3C主控器12例如於將超過最大讀取長度之資料分割並讀出之情形時，最先發送整體資料相關之索引及傳輸長度資訊。 因此，即使I3C主控器12不對連續讀出之每個資料發送索引及傳輸長度資訊，於I3C受控器13中，亦可藉由每當發送資料時更新發送剩餘量，而辨識連續讀出之資料之索引及資料長度。 藉此，可不對連續傳輸之每個資料發送索引及傳輸長度資訊，相應地可削減處理負擔，可提高資料之傳輸效率。 於圖8顯示傳輸模式為TSL模式或TSP模式之情形時，進行將超過最大讀取長度之資料分割並傳輸，且自I3C受控器13向I3C主控器12讀出資料之讀取傳輸處理時的格式。另，於圖8中與圖7同樣顯示於最大讀取長度為200位元組時，請求傳輸300位元組之資料之例。 此處，TSL模式或TSP模式為就不進行圖7所示之CRC字元之發送之點與DDR模式不同、其他點皆為共通之格式。即，於TSL模式或TSP模式中，與DDR模式同樣地，可提高資料之傳輸效率。 ＜系統控制器之資料傳輸處理＞ 參照圖9至圖17所示之流程圖，對系統控制器41中執行之資料傳輸處理進行說明。 於步驟S21中，I3C主控器12進行基於連接於匯流排IF11之各I3C受控器13之初始設定程序(例如，上述之圖6之步驟S11至S13之處理)。 於步驟S22中，CCI層處理部42等待來自上階層的CPU43之資料傳輸請求，當有資料傳輸之請求時接收該請求。 於步驟S23中，CCI層處理部42根據步驟S22中接收到之資料傳輸請求，判定在與被控制器件61間進行資料傳輸時之傳輸模式為DDR模式、TSL/TSP模式、及SDR模式之任一者。 於步驟S23中，若CCI層處理部42判定傳輸模式為DDR模式，處理前進至步驟S24，如參照圖10至圖13於後述般進行DDR模式之暫存器R/W傳輸處理。 另一方面，於步驟S23中，若CCI層處理部42判定傳輸模式為TSL/TSP模式，處理前進至步驟S25，如參照圖14至圖17於後述般進行TSL/TSP模式之暫存器R/W傳輸處理。 另一方面，於步驟S23中，若CCI層處理部42判定傳輸模式為SDR模式之情形時，處理前進至步驟S26，藉由SDR模式進行暫存器R/W傳輸。另，於藉由SDR模式進行暫存器R/W傳輸之情形時，無須收發如上所述之傳輸長度資訊。 於步驟S24、步驟S25、或步驟S26之處理後，處理返回至步驟S22，於系統控制器41中，後續重複進行同樣之處理。 接著，參照圖10至圖13，對系統控制器41執行之DDR模式之暫存器R/W傳輸處理(圖9之步驟S24)進行說明。 圖10係說明DDR模式之暫存器R/W傳輸處理之流程圖。 於步驟S31中，於I3C主控器12中，指令發送部23對連接於匯流排IF11之所有的I3C受控器13開始HDR模式之通信，且發送以DDR模式進行通信之HDR開始指令(ENTHDR0)。 於步驟S32中，CCI層處理部42將圖9之步驟S22中自上階層的CPU43請求資料傳輸之資料的資料長度，設定為表示與被控制器件61之間傳輸之資料之剩餘部分的傳輸剩餘量。 於步驟S33中，CCI層處理部42判定由CPU43請求之資料之傳輸方向為讀取傳輸及寫入傳輸之何者。 於步驟S33中，若CCI層處理部42判定資料之傳輸方向為讀取傳輸，處理前進至步驟S34，如參照圖11於後述般進行DDR讀取傳輸處理。 另一方面，於步驟S33中，若CCI層處理部42判定資料之傳輸方向為寫入傳輸，處理前進至步驟S35，如參照圖13於後述般進行DDR寫入傳輸處理。 於步驟S34之DDR讀取傳輸處理、或步驟S35之DDR寫入傳輸處理之處理後，處理前進至步驟S36。 於步驟S36中，CCI層處理部42判定是否自上階層的CPU43請求下一個HDR之資料傳輸。 於步驟S36中，若CCI層處理部42判定為請求下一個HDR之資料傳輸，處理前進至步驟S37。於步驟S37中，於I3C主控器12中，指令發送部23發送指示重啟HDR模式之通信之HDR重啟指令。隨後，處理返回至步驟S32，後續重複進行同樣之處理。 另一方面，於步驟S36中，若CCI層處理部42判定為未請求下一個HDR之資料傳輸，處理前進至步驟S38。 於步驟S38中，於I3C主控器12中，指令發送部23發送指示結束HDR模式之通信之指令後，DDR模式之暫存器R/W傳輸處理結束，且處理返回至圖9之步驟S22。 圖11係說明圖10之步驟S34中進行之DDR讀取傳輸處理之流程圖。 於步驟S41中，CCI層處理部42將圖10之步驟S32中設定之傳輸剩餘量，設定為表示發送至被控制器件61之資料之資料長度的傳輸長度資訊，且使其保持於傳輸長度資訊保持部52。 於步驟S42中，I3C主控器12為了向I3C受控器13通知自暫存器讀出並傳輸之資料之資料長度，進行將傳輸長度資訊發送至I3C受控器13之HDR寫入傳輸處理(參照圖12)。於該處理後，於I3C主控器12中，指令發送部23於步驟S43中發送HDR重啟指令，於步驟S44中，發送讀取指令。 於步驟S45中，I3C主控器12停止對資料信號線14-1之驅動，且當I3C受控器13進行對資料信號線14-1之驅動而傳來信號時，藉由資料收發部22開始信號之接收。 於步驟S46中，I3C主控器12進行基於自I3C受控器13傳來之信號之前導碼之判定。於步驟S46中，若I3C主控器12基於前導碼而判定為自I3C受控器13傳來資料之情形時，處理前進至步驟S47。 於步驟S47中，於I3C主控器12中，資料接收部22接收自I3C受控器13傳來之資料及同位碼。 於步驟S48中，I3C主控器12使用步驟S47中接收到之同位碼，判定步驟S47中接收到之資料是否發生錯誤。且，於I3C主控器12判定未發生同位碼錯誤之情形時，處理前進至步驟S49。 於步驟S49中，CCI層處理部42判定當前之傳輸剩餘量為2位元組以上、1位元組、及0位元組之何者。 於步驟S49中，若CCI層處理部42判定當前之傳輸剩餘量為2位元組以上，處理前進至步驟S50。於步驟S50中，CCI層處理部42取得自暫存器讀出且自I3C受控器13向I3C主控器12傳輸之2位元組之資料，且於步驟S51中，將傳輸剩餘量更新為往後推2位元組。 另一方面，於步驟S49中，若CCI層處理部42判定當前之傳輸剩餘量為1位元組，處理前進至步驟S52。於步驟S52中，於CCI層處理部42中，藉由無效資料處理部54將自I3C受控器13向I3C主控器12傳輸之資料之2位元組中之1位元組之虛設資料捨棄，取得自暫存器讀出之1位元組之資料。隨後，I3C主控器12於步驟S53中，將傳輸剩餘量更新為往後推1位元組。 另一方面，於步驟S49中，若CCI層處理部42判定當前之傳輸剩餘量為0位元組之情形時，處理前進至步驟S54。即，於該情形時，由於無自I3C受控器13傳來之資料(0位元組)，違反CCI協議，故CCI層處理部42將自I3C受控器13向I3C主控器12傳輸之2位元組皆捨棄。 於步驟S51、步驟S53、或步驟S54之處理後，處理前進至步驟S55，I3C主控器12進行基於自I3C受控器13發送之信號之前導碼之判定。 於步驟S55中，若I3C主控器12基於前導碼而判定自I3C受控器13傳來資料，處理返回至步驟S47，後續重複進行同樣之處理。 另一方面，於步驟S55中，若I3C主控器12基於前導碼而判定傳來CRC字元，處理前進至步驟S56，資料接收部22接收CRC字元。例如I3C受控器13於發送出請求資料傳輸之所有資料之情形、或發送出最大讀取長度之資料之情形時，發送CRC字元。 於步驟S57中，I3C主控器12判定步驟S56中資料接收部22接收到之CRC字元是否發生錯誤。 於步驟S57中，若I3C主控器12判定為CRC字元未發生錯誤，處理前進至步驟S58，重新開始對資料信號線14-1之驅動。 於步驟S59中，I3C主控器12例如於步驟S51或S53中更新傳輸剩餘量後，判定當前之傳輸剩餘量是否為0。例如，於發送出由傳輸長度資訊表示之資料長度之資料、即請求資料傳輸之所有資料之情形時，當前之傳輸剩餘量為0。對此，例如，若因由傳輸長度資訊表示之資料長度長於最大讀取長度，而將資料分割傳輸之情形時，有即使未發送請求資料傳輸之所有資料但仍發送CRC字元之情形，於該情形時，當前之傳輸剩餘量不為0。 於步驟S59中，若I3C主控器12判定為當前之傳輸剩餘量不為0，處理返回至步驟S43，自發送HDR重啟指令起繼續進行處理。 另一方面，於步驟S46中，若I3C主控器12基於前導碼而判定為例如傳來表示I3C受控器13未能正常地接收資料或指令等之NACK回應，或檢測出發生訊框錯誤(Framing Error)之情形時，處理前進至步驟S60。同樣地，當I3C主控器12判定步驟S48中發生同位碼錯誤之情形、於步驟S55中檢測出訊框錯誤之情形、於步驟S57中判定為CRC字元發生錯誤之情形時，處理前進至步驟S60。 於步驟S60中，I3C主控器12對I3C受控器13發送19次串列時脈。 且，於步驟S61中，I3C主控器12對CCI層處理部42通知錯誤，於步驟S62中，CCI層處理部42對上階層的CPU43通知錯誤。 於步驟S62之處理後、或於步驟S59中判定當前之傳輸剩餘量為0之情形時，DDR讀取傳輸處理結束，處理進行至圖10之步驟S36。 圖12係說明圖11之步驟S42中進行之HDR寫入傳輸處理之流程圖。 於步驟S71中，指令發送部23將寫入指令發送至I3C受控器13，於步驟S72中，資料發送部21將索引發送至I3C受控器13。 於步驟S73中，資料發送部21將對應於圖9之步驟S22中接收到之資料傳輸請求之傳輸長度資訊發送至I3C受控器13。於步驟S74中，於資料發送部21發送出CRC字元後，HDR寫入傳輸處理結束，處理進行至圖11之步驟S43。 圖13係對圖10之步驟S35中進行之DDR寫入傳輸處理進行說明之流程圖。 於步驟S81中，系統控制器41之CCI層處理部42判定圖10之步驟S32中設定之傳輸剩餘量之資料長度是否長於1次傳輸所能發送之資料長度。此處，1次傳輸所能發送之資料長度為自成為寫入端之I3C受控器13之最大寫入長度減去通知開始寫入資料之開頭位址之索引、及傳輸之資料的資料長度之值(=MWL-Index-Length)。 於步驟S81中，若CCI層處理部42判定傳輸剩餘量之資料長度長於1次傳輸所能發送之資料長度之情形時，處理前進至步驟S82。於步驟S82中，CCI層處理部42將1次傳輸所能發送之資料長度設定為傳輸長度資訊並使其保持於傳輸長度資訊保持部52，且處理前進至步驟S84。 另一方面，於步驟S81中，若CCI層處理部42判定傳輸剩餘量之資料長度非長於(短於)1次傳輸所能發送之資料長度之情形時，處理前進至步驟S83。於步驟S83中，CCI層處理部42將傳輸剩餘量設定為傳輸長度資訊並使其保持於傳輸長度資訊保持部52，且處理前進至步驟S84。 於步驟S84中，指令發送部23將寫入指令發送至I3C受控器13，於步驟S85中，資料發送部21將索引發送至I3C受控器13。隨後，於步驟S86中，傳輸長度資訊發送部55將保持於傳輸長度資訊保持部52之傳輸長度資訊藉由資料發送部21發送至I3C受控器13。 於步驟S87中，CCI層處理部42將當前時點保持於傳輸長度資訊保持部52之傳輸長度資訊設定為要進行寫入至暫存器之剩餘之資料之資料長度。 於步驟S88中，CCI層處理部42判定當前之剩餘資料長度為2位元組以上、1位元組、及0位元組之任一者。 於步驟S88中，若CCI層處理部42判定當前之剩餘資料長度為2位元組以上，處理前進至步驟S89。於步驟S89中，CCI層處理部42將自I3C主控器12向I3C受控器13傳輸並寫入至暫存器之2位元組之資料供給至I3C主控器12，於步驟S90中，將剩餘之資料長度更新為往後推2位元組。 另一方面，於步驟S88中，若CCI層處理部42判定當前之剩餘資料長度為1位元組，處理前進至步驟S91。於步驟S91中，於CCI層處理部42中，將自I3C主控器12向I3C受控器13傳輸並寫入至暫存器之1位元組之資料供給至I3C主控器12，且藉由無效資料處理部54附加1位元組之虛設資料。且，CCI層處理部42於步驟S92中，將剩餘之資料長度更新為往後推1位元組。 於步驟S90或S92之處理後，處理前進至步驟S93。I3C主控器12將步驟S89或S91中自CCI層處理部42供給之資料藉由資料發送部21發送至I3C受控器13，且處理返回至步驟S88。 另一方面，於步驟S88中，若CCI層處理部42判定當前之剩餘資料長度為0位元組，處理前進至步驟S94。即，於該情形時，對應於圖9之步驟S22中接收到資料傳輸處理請求之所有資料之傳輸完成，於步驟S94中，I3C主控器12發送CRC字元。 於步驟S95中，CCI層處理部42自當前之傳輸剩餘量減去傳輸長度資訊而更新傳輸剩餘量(=輸剩餘量-Length)。 於步驟S96中，CCI層處理部42判定更新後之傳輸剩餘量是否為0。 於步驟S96中，若CCI層處理部42判定更新後之傳輸剩餘量非為0，處理前進至步驟S97。於步驟S97中，於I3C主控器12發送出指示重啟HDR模式之通信之指令後，處理返回至步驟S81，後續重複同樣之處理。 另一方面，於步驟S96中，若CCI層處理部42判定更新後之傳輸剩餘量為0，DDR寫入傳輸處理結束，處理進行至圖10之步驟S36。 如參照圖10至圖13說明般，系統控制器41可進行DDR模式之暫存器R/W傳輸處理。 接著，參照圖14至圖17，對TSL/TSP模式之暫存器R/W傳輸處理(圖9之步驟S25)進行說明。 圖14係說明TSL/TSP模式之暫存器R/W傳輸處理之流程圖。 於步驟S101中，I3C主控器12對連接於匯流排IF11之所有I3C受控器13，開始HDR模式之通信，並發送以TSL/TSP模式進行通信之HDR開始指令(ENTHDR1/2)。 於步驟S102中，CCI處理部42將圖9之步驟S22中來自上階層的CPU43之資料傳輸請求之資料的資料長度設定為表示與被控制器件61之間傳輸之資料之剩餘之傳輸剩餘量。 於步驟S103中，CCI處理部42判定由CPU43請求之資料之傳輸方向為讀取傳輸及寫入傳輸之何者。 於步驟S103中，若CCI處理部42判定資料之傳輸方向為讀取傳輸，處理前進至步驟S104，如參照圖15於後述般進行TSL/TSP讀取傳輸處理。 另一方面，於步驟S103中，若CCI處理部42判定資料之傳輸方向為寫入傳輸，處理前進至步驟S105，如參照圖17於後述般進行TSL/TSP寫入傳輸處理。 於步驟S104之TSL/TSP讀取傳輸處理之處理後、或步驟S105之TSL/TSP寫入傳輸處理之處理後，處理前進至步驟S106。且，於步驟S106至S108中，進行與圖10之步驟S36至S38同樣之處理，隨後，TSL/TSP模式之暫存器R/W傳輸處理結束，處理返回至圖9之步驟S22。 圖15係說明圖14之步驟S104中進行之TSL/TSP讀取傳輸處理的流程圖。 於步驟S111至S114中，進行與圖11之步驟S41至S44同樣之處理。接著，於步驟S115中，I3C主控器12停止對資料信號線14-1及時脈信號線14-2之驅動。另，於TSL/TSP模式中，周轉(Turnaround)之次序與DDR模式不同。 於步驟S116中，I3C主控器12判定是否接收到自I3C受控器13傳來之資料。另，於TSL/TSP模式中，與DDR模式不同，不進行前導碼之發送。 於步驟S116中，若判定為接收到自I3C受控器13傳來之資料，處理前進至步驟S117，資料接收部22接收自I3C受控器13傳來之資料及同位碼。 於步驟S118中，I3C主控器12判定步驟S117中資料接收部22接收到之資料是否包含錯誤，若判定為不包含錯誤，處理前進至步驟S119。 於步驟S119至S124中，CCI層處理部42進行與圖11之步驟S49至S54同樣之處理。 於步驟S125中，I3C主控器12判定是否接收到自I3C受控器13傳來之資料，若判定為接收到資料，處理返回至步驟S117，後續重複進行同樣之處理。 另一方面，於步驟S125，若判定為未接收到資料，處理前進至步驟S126，I3C主控器12重新開始對資料信號線14-1及時脈信號線14-2之驅動。另，於TSL/TSP模式中不進行CRC字元之發送，且周轉之次序與DDR模式不同。 另一方面，於步驟S118中，若I3C主控器12判定為步驟S117中資料接收部22接收到之資料包含錯誤，處理前進至步驟S128。另，於TSL/TSP模式中，錯誤檢測條件與DDR模式不同，例如，若檢測出同位碼錯誤、或於資料字元之界限以外接收到符號2×2以上之情形時，判定為資料包含錯誤。 於步驟S128中，I3C主控器12等待信號之變化停止，且當信號之變化停止時，處理前進至步驟S129。即，於TSL/TSP模式中，錯誤復原之次序與DDR模式不同。 又，於步驟S116中，若判定為未接收到自I3C受控器13傳來之資料，例如於接收到NACK回應(符號2×3次)之情形時，處理前進至步驟S129。 於步驟S129中，I3C主控器12對CCI層處理部42通知錯誤，於步驟S130中，CCI層處理部42對上階層的CPU43通知錯誤。 於步驟S130之處理後、或步驟S127中判定當前之傳輸剩餘量為0之情形時，TSL/TSP讀取傳輸處理結束，處理進行至圖14之步驟S106。 圖16係說明圖15之步驟S112中進行之HDR寫入傳輸處理之流程圖。 於步驟S141至S143中，進行與圖12之步驟S71至S73同樣之處理，於發送寫入指令、索引、及傳輸長度資訊且HDR寫入傳輸處理結束後，處理進行至圖15之步驟S113。即，圖16所示之TSL/TSP讀取傳輸處理之HDR寫入傳輸處理不發送CRC字元，此點與參照圖12於上文所述之DDR讀取傳輸處理之HDR寫入傳輸處理不同。 圖17係對圖14之步驟S105中進行之TSL/TSP寫入傳輸處理進行說明之流程圖。 於步驟S151至S163中，進行與圖13之步驟S81至S93同樣之處理。且，於步驟S158中，若判定當前剩餘之資料長度為0位元組，即，當對應於圖9之步驟S22中接收到之資料傳輸請求之所有資料之傳輸完成時，處理前進至步驟S164。 於步驟S164至S166中，進行與圖13之步驟S95至S97同樣之處理，隨後，TSL/TSP寫入傳輸處理結束，且處理進行至圖14之步驟S106。即，圖17所示之TSL/TSP寫入傳輸處理不發送CRC字元，此點與參照圖13於上文所述之DDR寫入傳輸處理不同。 如參照圖14至圖17說明般，系統控制器41可進行TSL/TSP模式之暫存器R/W傳輸處理。 ＜被控制器件之資料傳輸處理＞ 參照圖18至圖25，對被控制器件61中執行之資料傳輸處理進行說明。 圖18係說明系統控制器41對應於參照圖10於上文所述之DDR模式之暫存器R/W傳輸處理之執行而於被控制器件61中進行之資料傳輸處理的流程圖。 例如，I3C受控器13當接收到自I3C主控器12傳來之以DDR模式進行通知之HDR開始指令(ENTHDR0)時，開始處理。接著，於步驟S171中，I3C受控器13進行基於由I3C主控器12接續HDR開始指令傳來之信號之前導碼之判定。於步驟S171中，若I3C受控器13基於前導碼而判定為自I3C主控器12傳來指令，處理前進至步驟S172。 於步驟S172中，於I3C受控器13中，指令解譯部33接收自I3C主控器12傳來之指令及同位碼。 於步驟S173中，指令解譯部33使用步驟S172中接收到之同位碼，判定步驟S172中接收到之指令是否發生錯誤。且，若指令解譯部33判定為未發生同位碼錯誤，處理前進至步驟S174。 於步驟S174中，指令解譯部33判定步驟S172中接收到之指令之指令碼為讀取指令及寫入指令之何者。 於步驟S174中，若指令解譯部33判定指令碼為讀取指令，處理前進至步驟S175，且如參照圖19於後述般進行DDR讀取傳輸處理。 另一方面，於步驟S174中，若指令解譯部33判定指令碼為寫入指令，處理前進至步驟S176，且如參照圖20於後述般進行DDR寫入傳輸處理。 於步驟S175之DDR讀取傳輸處理、或步驟S176之DDR寫入傳輸處理之處理後，處理前進至步驟S179。 另一方面，於步驟S171中，若基於前導碼檢測出發生訊框錯誤，或於步驟S173中判定為發生同位碼錯誤之情形時，處理前進至步驟S177。 於步驟S177中，I3C受控器13對CCI層處理部62通知錯誤，於步驟S178中，CCI層處理部62將傳輸剩餘量設定為0後，處理前進至步驟S179。 於步驟S179中，I3C受控器13判定指令解譯部33接收到指示重啟HDR模式之通信之指令、及指示結束HDR模式之通信之指令之何者。 於步驟S179中，若判定指令解譯部33接收到指示重啟HDR模式之通信之指令，處理返回至步驟S171，後續重複進行同樣之處理。 另一方面，於步驟S179，若判定指令解譯部33判定為接收到指示結束HDR模式之通信之指令，被控制器件61之資料傳輸處理結束。 圖19係說明圖18之步驟S175中進行之DDR讀取傳輸處理之流程圖。 於步驟S181中，CCI層處理部62判定當前之傳輸剩餘量為大於0位元組且未達最大讀取長度、最大讀取長度以上、及0位元組之何者。 於步驟S181中，若CCI層處理部62判定當前之傳輸剩餘量為大於0位元組且未達最大讀取長度之情形時，處理前進至步驟S182。於步驟S182中，CCI層處理部62將當前之傳輸剩餘量設定為當前之根據讀取指令發送之資料之發送剩餘量。 另一方面，於步驟S181中，若CCI層處理部62判定當前之傳輸剩餘量為最大讀取長度以上，處理前進至步驟S183。於步驟S183中，CCI層處理部62將最大讀取長度設定為當前之根據讀取指令發送之資料之發送剩餘量。 於步驟S182或S183之處理後，處理前進至步驟S184，I3C受控器13開始對資料信號線14-1之驅動。 於步驟S185中，CCI層處理部62判定當前之根據讀取指令發送之發送剩餘量為2位元組以上、1位元組、及0位元組之何者。 於步驟S185中，若CCI層處理部62判定當前之根據讀取指令發送之資料之發送剩餘量為2位元組以上，處理前進至步驟S186。 於步驟S186中，CCI層處理部62自暫存器讀出2位元組之資料。接著，CCI層處理部62於步驟S187中，將步驟S186中讀出之2位元組之資料供給至I3C受控器13。於步驟S188中，CCI層處理部62進行將索引往前移2位元組，將當前之根據指令發送之資料之發送剩餘量往後推2位元組，且將傳輸剩餘量往後推2位元組之更新。 另一方面，於步驟S185中，若CCI層處理部62判定當前之根據讀取指令發送之資料之發送剩餘量為1位元組之情形時，處理前進至步驟S189。 於步驟S189中，CCI層處理部62自暫存器讀出1位元組之資料。接著，CCI層處理部62於步驟S190中，對步驟S189中讀出之1位元組之資料附加1位元組之虛設資料並供給至I3C受控器13。於步驟S191中，CCI層處理部62進行將索引往前移1位元組、將當前之根據指令發送之資料之發送剩餘量往後推1位元組、將傳輸剩餘量往後推1位元組之更新。 於步驟S188或S191之處理後，處理前進至步驟S192，I3C受控器13將步驟S187或S190中自CCI層處理部62供給之資料藉由資料發送部31發送至I3C主控器12。 於步驟S193中，I3C受控器13判定是否進行指示藉由I3C主控器12中途阻斷通信之主控器中止。 於步驟S193中，若I3C受控器13判定為未進行主控器中止，處理返回至步驟S185，後續重複同樣之處理。另一方面，於步驟S193中，若I3C受控器13判定為已進行主控器中止，處理前進至步驟S195。 另一方面，於步驟S185中，若CCI層處理部62判定當前之根據讀取指令發送之發送剩餘量為0位元組，處理前進至步驟S194。於步驟S194中，I3C受控器13發送CRC字元，且處理前進至步驟S195。 於步驟S195中，I3C受控器13停止對資料信號線14-1之驅動。 另一方面，於步驟S181中，若判定當前之傳輸剩餘量為0位元組，處理前進至步驟S196。即，於該情形時，由於違反CCI協議，故於步驟S196中，I3C受控器13將NACK發送至I3C主控器12。 於步驟S195或S196之處理後，DDR讀取傳輸處理結束，處理進行至圖18至步驟S179。 圖20係說明圖18之步驟S176中進行之DDR寫入傳輸處理之流程圖。 於步驟S201中，I3C受控器13進行基於自I3C主控器12傳來之信號之前導碼之判定。 於步驟S201中，若I3C受控器13基於前導碼而判定自I3C主控器12傳來資料，處理前進至步驟S202。 於步驟S202中，於I3C受控器13中，資料接收部32接收自I3C主控器12傳來之資料及同位碼。 於步驟S203中，I3C受控器13使用步驟S202中接收到之同位碼，判定步驟S202中接收到之資料是否發生錯誤。且，若I3C受控器13判定為未發生同位碼錯誤，處理前進至步驟S204。 於步驟S204中，CCI層處理部62取得步驟S202中資料接收部32接收到之資料，即I3C主控器12發送出之索引。 於步驟S205中，I3C受控器13基於自I3C主控器12傳來之信號之前導碼，判定為傳來資料、傳來CRC字元、或是發生錯誤之任一者。 於步驟S205中，若I3C受控器13判定為傳來資料，處理前進至步驟S206。 於步驟S206中，於I3C受控器13中，資料接收部32接收自I3C主控器12傳來之資料及同位碼。 於步驟S207中，I3C受控器13使用步驟S206中接收到之同位碼，判定步驟S206中接收到之資料是否發生錯誤。且，若I3C受控器13判定為未發生同位碼錯誤，處理前進至步驟S208。 於步驟S208中，CCI層處理部62取得步驟S206中資料接收部32接收到之資料、即I3C主控器12發送出之傳輸長度資訊，作為傳輸剩餘量。 於步驟S209中，I3C受控器13基於自I3C主控器12傳來之信號之前導碼，判定為傳來資料、傳來CRC字元、或是發生錯誤之任一者。 於步驟S209中，若I3C受控器13判定為傳來資料，處理前進至步驟S210並進行寫入處理(圖21)。 另一方面，於步驟S209中，若I3C受控器13判定為傳來CRC字元，處理前進至步驟S211，資料接收部32接收CRC字元。 於步驟S212中，I3C受控器13判定步驟S211中資料接收部32接收到之CRC字元是否發生錯誤。於步驟S212中，若判定為CRC字元未發生錯誤，處理前進至步驟S213，I3C受控器13判斷為隨機讀取。 另一方面，於步驟S205中，若I3C受控器13判定為傳來CRC字元，處理前進至步驟S214，資料接收部32接收CRC字元。 於步驟S215中，I3C受控器13判定步驟S214中資料接收部32接收到之CRC字元是否發生錯誤。於步驟S215中，若I3C受控器13判定CRC字元未發生錯誤，處理前進至步驟S216。即，於該情形時，由於違反CCI協議，故於步驟S216中，CCI層處理部62將傳輸剩餘量設定為0。 另一方面，於步驟S201、步驟S205、或步驟S209中，若基於前導碼而檢測出發生訊框錯誤，處理前進至步驟S217。同樣地，於步驟S203及S207中，若判定為發生同位碼錯誤，處理前進至步驟S217。再者，於步驟S212或S215中，若判定為發生CRC錯誤，處理前進至步驟S217。 於步驟S217中，I3C受控器13對CCI層處理部62通知錯誤，於步驟S218中，CCI層處理部62將傳輸剩餘量設定為0。 且，於步驟S210、步驟S213、步驟S216、或步驟S218之處理後，DDR寫入傳輸處理結束，處理進行至圖18之步驟S179。 圖21係說明圖20之步驟S210中進行之寫入處理之流程圖。 於步驟S221中，於I3C受控器13中，資料接收部32接收自I3C主控器12傳來之資料及同位碼。 於步驟S222中，I3C受控器13使用步驟S221中接收到之同位碼，判定步驟S221中接收到之資料是否發生錯誤。且，若I3C受控器13判定未發生同位碼錯誤，處理前進至步驟S223，且由於可正常地接收資料故CCI層處理部62判斷為開始寫入傳輸。 於步驟S224中，CCI層處理部62判定傳輸剩餘量為2位元組以上、1位元組、及0位元組之何者。 於步驟S224中，若判定傳輸剩餘量為2位元組以上，處理前進至步驟S225，CCI層處理部62取得I3C受控器13接收到之2位元組之資料，作為要寫入至暫存器之資料。接著，CCI層處理部62於步驟S226中，進行該2位元組之資料之暫存器寫入處理，於步驟S227中，進行將索引往前移2位元組、將傳輸剩餘量往後推2位元組之更新。 另一方面，於步驟S224中，若判定傳輸剩餘量為1位元組，處理前進至步驟S228。於步驟S228中，於CCI層處理部62中，藉由無效資料處理部74將I3C受控器13接收到之2位元組資料中之虛設資料之1位元組捨棄，並取得剩餘之1位元組作為要寫入至暫存器之資料。且，CCI層處理部62於步驟S229中，進行該1位元組之資料之暫存器寫入處理，於步驟S230中，進行將索引往前移1位元組、將傳輸剩餘量往後推1位元組之更新。 另一方面，於步驟S224中，若判定傳輸剩餘量為0位元組，則處理前進至步驟S231。即，於該情形時，由於違反CCI協議，故於步驟S231中，CCI層處理部62將I3C受控器13接收到之資料之2位元組均捨棄。 於步驟S227、步驟S230、或步驟S231之處理後，處理前進至步驟S232。於步驟S232中，I3C受控器13基於自I3C主控器12傳來之信號之前導碼，判定為傳來資料、傳來CRC字元、或是發生錯誤之任一者。 於步驟S232中，若I3C受控器13判定為傳來資料，則處理返回至步驟S221，後續重複進行同樣之處理。 另一方面，於步驟S232中，若I3C受控器13判定為傳來CRC字元，則處理前進至步驟S233，資料接收部32接收CRC字元。 於步驟S234中，I3C受控器13判定步驟S233中資料接收部32接收到之CRC字元是否發生錯誤。於步驟S234中，若判定為CRC字元未發生錯誤，處理前進至步驟S235。即，於該情形時，由於可正常地接收CRC字元，故CCI層處理部62於步驟S235中判斷為結束寫入傳輸，且於步驟S236中，將傳輸剩餘量設定為0。 另一方面，若於步驟S222中判定為發生同位碼錯誤、於步驟S232中基於前導碼判定為發生訊框錯誤、或於步驟S234中判定為發生CRC錯誤，處理前進至步驟S237。 於步驟S237中，I3C受控器13對CCI層處理部62通知錯誤，於步驟S238中，CCI層處理部62將傳輸剩餘量設定為0。 接著，於步驟S236或S238之處理後，寫入處理結束，處理進行至圖18之步驟S179。 如參照圖18至圖21說明般，被控制器件61可進行DDR模式之暫存器R/W傳輸處理。 圖22係說明系統控制器41對應於參照圖14於上文所述之TSL/TSP模式之暫存器R/W傳輸處理之執行而於被控制器件61中進行之資料傳輸處理的流程圖。 例如，I3C受控器13當接收到自I3C主控器12傳來之以DDR模式進行通信之HDR開始指令(ENTHDR1/2)時開始處理。接著，於步驟S241中，於I3C受控器13中，指令解譯部33接收自I3C主控器12傳來之指令及同位碼。另，於TSL/TSP模式中，與DDR模式不同，不進行前導碼之發送。 於步驟S242中，指令解譯部33判定步驟S172中接收到之指令是否發生錯誤。另，於TSL/TSP模式中，錯誤檢測條件與DDR模式不同，例如，於檢測出同位碼錯誤之情形，或於資料字元之界限以外接收到符號2×2以上之情形時，判定為資料發生錯誤。 於步驟S242中，若指令解譯部33判定為未發生錯誤，處理前進至步驟S243。 於步驟S243中，指令解譯部33判定步驟S242中接收到之指令之指令碼為讀取指令及寫入指令之何者。 於步驟S243中，若指令解譯部33判定指令碼為讀取指令，處理前進至步驟S244，且如參照圖23後述般進行TSL/TSP讀取傳輸處理。 另一方面，於步驟S243中，若指令解譯部33判定指令碼為寫入指令，處理前進至步驟S245，且如參照圖24後述般進行TSL/TSP寫入傳輸處理。 於步驟S244之TSL/TSP讀取傳輸處理、或步驟S245之TSL/TSP寫入傳輸處理之處理後，處理前進至步驟S248。 另一方面，於步驟S242中，若指令解譯部33判定為發生錯誤，處理前進至步驟S246。於步驟S246之S248中，進行與圖18之步驟S177至S179同樣之處理。 圖23係說明圖22之步驟S244中進行之TSL/TSP讀取傳輸處理之流程圖。 於步驟S251至S253中，進行與圖19之步驟S181至S183同樣之處理。接著，於步驟S252或S253之處理後，於步驟S254中，I3C受控器13開始對資料信號線14-1及時脈信號線14-2之驅動。 隨後，於步驟S255至S262中，進行與圖19之步驟S185至S192同樣之處理，且重複進行處理直到於步驟S255中判定當前之根據讀取指令發送之資料之發送剩餘量為0位元組為止。另，於TSL/TSP模式中，與DDR模式不同，不進行主控器中止。 於步驟S255中，若判定發送剩餘量為0位元組，處理前進至步驟S263，I3C受控器13發送表示傳輸結束之信號(符號2×3次)。另，於TSL/TSP模式中，與DDR模式不同，不進行CRC字元之發送。 另一方面，於步驟S251中，若判定當前之傳輸剩餘量為0位元組，處理前進至步驟S264。即，於該情形時，由於違反CCI協議，故I3C受控器13於步驟S264中開始對資料信號線14-1及時脈信號線14-2之驅動，於步驟S265中，發送NACK(符號2×3次)。另，於TSL/TSP模式中，NACK之形式與DDR模式不同。 於步驟S263或S265之處理後，處理前進至步驟S266。於步驟S266中，I3C受控器13停止對資料信號線14-1及時脈信號線14-2之驅動後，TSL/TSP讀取傳輸處理結束，處理進行至圖22之步驟S248。另，於TSL/TSP模式中，周轉之次序與DDR模式不同。 圖24係說明圖22之步驟S245中進行之TSL/TSP寫入傳輸處理之流程圖。 於步驟S271中，於I3C受控器13中，資料接收部32接收自I3C主控器12傳來之資料及同位碼。另，於TSL/TSP模式中，與DDR模式不同，不進行前導碼之發送。 於步驟S272中，I3C受控器13判定步驟S271中接收到之資料是否發生錯誤。另，於TSL/TSP模式中，錯誤檢測條件與DDR模式不同，例如，若檢測出同位碼錯誤，或於資料字元之界限以外接收到符號2×2以上，判定為資料發生錯誤。 於步驟S272中，若判定為資料未發生錯誤，處理前進至步驟S273，CCI層處理部62取得步驟S271中資料接收部32接收到之資料，即I3C主控器12發送之索引。 於步驟S274中，I3C受控器13判定是否接收到自I3C主控器12傳來之資料。 於步驟S274中，若判定接收到自I3C主控器12傳來之資料，處理前進至步驟S275，資料接收部32接收自I3C主控器12傳來之資料及同位碼。 於步驟S276中，I3C受控器13與步驟S272同樣地，判定步驟S275中接收到之資料是否發生錯誤，若判定為未發生錯誤，處理前進至步驟S277。 於步驟S277中，CCI層處理部62取得步驟S275中資料接收部32接收到之資料、即I3C主控器12發送之傳輸長度資訊，作為傳輸剩餘量。 於步驟278中，I3C受控器13判定是否接收到自I3C主控器12傳來之資料。另，於TSL/TSP模式中，與DDR模式不同，不進行前導碼之發送。 於步驟S278中，若I3C受控器13判定為接收到資料，處理前進至步驟S279並進行寫入處理(圖25)。 另一方面，於步驟S278中，若判定為未接收到資料，處理前進至步驟S280，且I3C受控器13判斷為隨機讀取。 另一方面，於步驟S274中，若判定未接收到自I3C主控器12傳來之資料，處理前進至步驟S281。即，於該情形時，由於違反CCI協議，故於步驟S281中，CCI層處理部62將傳輸剩餘量設定為0。另，於TSL/TSP模式中，與DDR模式不同，不進行CRC字元之發送。 另一方面，於步驟S272或S276中，若判定接收到之資料發生錯誤，處理前進至步驟S282。於步驟S282中，I3C受控器13對CCI層處理部62通知錯誤，於步驟S283中，若CCI層處理部62將傳輸剩餘量設定為0。 且，於步驟S279、步驟S280、步驟S281、或步驟S283之處理後，TSL/TSP寫入傳輸處理結束，且處理進行至圖22之步驟S248。 圖25係說明圖24之步驟S279中進行之寫入處理之流程圖。 於步驟S291中，於I3C受控器13中，資料接收部32接收自I3C主控器12傳來之資料及同位碼。 於步驟S292中，I3C受控器13判定步驟S291中接收到之資料是否發生錯誤。另，於TSL/TSP模式中，錯誤檢測條件與DDR模式不同，例如，若檢測出同位碼錯誤，或於資料字元之界限以外接收到符號2×2以上，判定為資發生錯誤。 於步驟S292中，若I3C受控器13判定資料未發生錯誤，處理前進至步驟S293，且由於可正常地接收資料，故CCI層處理部62判斷為開始寫入傳輸。 於步驟S294至S301中，進行與圖21之步驟S224至S231同樣之處理後，於步驟S302中，I3C受控器13判定是否接收到自I3C主控器12傳來之資料。另，於TSL/TSP模式中，與DDR模式不同，不進行前導碼之發送。 於步驟S302中，若I3C受控器13判定接收到資料，處理返回至步驟S291，後續重複進行同樣之處理。 另一方面，於步驟S302中，若I3C受控器13判定未接收到資料，處理返回至步驟S303。且，CCI層處理部62因無資料傳來，故於步驟S303中判定為寫入傳輸結束，且於步驟S304中，將傳輸剩餘量設定為0。 另一方面，於步驟S292中，若I3C受控器13判定資料未發生錯誤，處理前進至步驟S305。於步驟S305中，I3C受控器13對CCI層處理部62通知錯誤，於步驟S306中，CCI層處理部62將傳輸剩餘量設定為0。 接著，於步驟S304或S306之處理後，寫入處理結束，處理進行至圖22之步驟S248。 如參照圖22至圖25說明般，被控制器件61可進行TSL/TSP模式之暫存器R/W傳輸處理。 ＜I3C受控器及CCI層處理部之錯誤對策＞ 參照圖26，對I3C受控器及CCI層處理部之錯誤對策進行說明。於圖26顯示於TSL/TSP模式之讀取傳輸處理中連續讀出資料時發生錯誤時之處理之一例。 例如，於HDR模式(TSP/TSL/DDR)中，規定為於I3C受控器13檢測出任何錯誤時，I3C受控器13於接收到HDR結束指令(HDR_Exit)或HDR重啟(HDR_Restart)之前，忽略一切通信，且當檢測出任一者時恢復通信。 此處，如圖26所示，對例如自接收到位址設定用之寫入指令(TSL/TSP_Cmd(W))起至接收到讀取指令(TSL/TSP_Cmd(R))之緊接在前之HDR重啟指令為止之期間發生錯誤時的處理進行說明。即，若於該時序發生錯誤，則I3C受控器13停止自檢測出錯誤至接收到HDR重啟指令為止之期間(忽略區間)之處理。因此，於該情形時，不向CCI層處理部62通知索引(Index)及傳輸長度資訊(Length)。 且，其後，I3C受控器13藉由接收HDR重啟指令而恢復通信，且將接續HDR重啟指令發送之讀取指令向CCI層處理部62傳輸。然而，由於CCI層處理部62未掌握索引及傳輸長度資訊，因而發生無從得知應自何處讀出資料之狀態。 因此，本實施形態之I3C受控器13規定為於檢測出錯誤之情形時，向CCI層處理部62通知該錯誤之檢測(例如，圖20之步驟S217或圖24之步驟S282等)。且，規定為根據該錯誤之通知，CCI層處理部62將傳輸剩餘量設定為0(例如圖20之步驟S218或圖24之步驟S283等)。 藉此，即使CCI層處理部62例如於因發生錯誤而無法辨識索引及傳輸長度資訊之情形時接收到讀取指令，仍判定傳輸剩餘量為0，於是違反CCI協議。因此，CCI層處理部62可於I3C受控器13檢測出錯誤後至接收到HDR重啟指令及寫入指令之組合(HDR_Restart＋TSL/TSP_Cmd(W))為止、或接收到HDR結束指令為止，忽略一切通信。 如此，可避免發生CCI層處理部62無從得知應自何處讀出資料之狀態，而進行與I3C受控器13之規定同樣之動作。因此，可避免對應I3C受控器13與CCI層處理部62之錯誤而發生偏差，而確實地執行讀取處理。 因此，被控制器件61可避免將有可能錯誤之資料寫入至暫存器，或將有可能錯誤之資料自暫存器讀出，且不會因此種錯誤而導致通信不穩定，可更確實地進行通信。 另，參照上述流程圖說明之各處理無須完全依照作為流程圖記載之順序按時間序列地進行處理，亦可為包含並行地或個別地執行之處理(例如，並行處理或基於目標之處理)者。又，程式可為藉由1個CPU處理者，亦可為藉由複數個CPU分散處理者。 又，上述之一連串之處理(通信方法)可藉由硬體執行，亦可藉由軟體執行。於藉由軟體執行一連串之處理之情形時，將構成該軟體之程式自記錄有程式之程式記錄媒體安裝於組入於專用硬體之電腦、或藉由安裝各種程式而可執行各種功能之例如泛用之個人電腦等。 圖27係顯示藉由程式執行上述之一連串處理之電腦之硬體之構成例的方塊圖。 於電腦中，CPU(Central Processing Unit)101、ROM(Read Only Memory：唯讀記憶體)102、RAM(Random Access Memory：隨機存取記憶體)103、及EEPROM(Electronically Erasable and Programmable Read Only Memory：電子可抹除可程式化唯讀記憶體)104藉由匯流排105相互連接。於匯流排105進而連接有輸入輸出介面106，且輸入輸出介面106連接於外部。 於如以上般構成之電腦中，CPU101例如將記憶於ROM102及EEPROM104之程式經由匯流排105下載至RAM103並執行，藉此進行上述之一連串之處理。又，電腦(CPU101)所執行之程式除預先寫入ROM102外，亦可經由輸入輸出介面106自外部安裝於EEPROM104或加以更新。 ＜構成之組合例＞ 另，本技術亦可採取如下之構成。 (1) 一種通信裝置，其係經由匯流排進行通信者， 藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，且 上述第1通信裝置具備： 取得部，其自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度； 收發控制部，其於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發；及 發送部，其對上述資料進行之前，發送表示要傳輸之資料的資料長度之傳輸長度資訊。 (2) 如上述(1)之通信裝置，其中 於經請求傳輸上述最大傳輸長度以上之長度之資料長度的資料之情形時，上述收發控制部將該請求傳輸之資料分割成上述最大傳輸長度以下而進行資料傳輸， 上述發送部發送表示經上述收發控制部分割之資料之資料長度之上述傳輸長度資訊。 (3) 如上述(1)或(2)之通信裝置，其中 於進行傳輸要寫入至上述第2通信裝置之資料之寫入傳輸時， 上述取得部取得上述第2通信裝置之寫入傳輸中之上述最大傳輸長度即最大寫入長度， 於經請求傳輸上述最大寫入長度以上之長度之資料長度的資料之情形時，上述收發控制部以將該請求傳輸之資料分割成上述最大寫入長度以下而分成複數次發送資料之方式進行資料傳輸， 上述發送部於每次傳輸上述資料時，發送表示經上述收發控制部分割之資料之資料長度的上述傳輸長度資訊。 (4) 如上述(1)至(3)中任一項之通信裝置，其中 於進行傳輸自上述第2通信裝置讀出之資料之讀取傳輸時， 上述取得部取得上述第2通信裝置之讀取傳輸中之上述最大傳輸長度即最大讀取長度， 於經請求傳輸上述最大讀取長度以上之長度之資料長度的資料之情形時，上述收發控制部以將該請求傳輸之資料分割成上述最大讀取長度以下而分成複數次發送資料之方式進行資料傳輸， 上述發送部於每次傳輸上述資料時，發送表示經上述收發控制部分割之資料之資料長度的上述傳輸長度資訊。 (5) 如上述(1)至(3)中任一項之通信裝置，其中 於進行傳輸自上述第2通信裝置讀出之資料之讀取傳輸時， 上述取得部取得上述第2通信裝置之讀取傳輸中之上述最大傳輸長度即最大讀取長度， 於經請求傳輸上述最大讀取長度以上之長度之資料長度的資料之情形時，上述收發控制部以將該請求傳輸之資料分割成上述最大讀取長度以下而分成複數次發送資料之方式進行資料傳輸， 上述發送部僅發送1次表示請求傳輸之資料整體之資料長度之上述傳輸長度資訊。 (6) 如上述(1)至(5)中任一項之通信裝置，其中 上述第2通信裝置具備： 錯誤通知部，其於至少檢測出發生無法正常地接收上述傳輸長度資訊之錯誤之情形時，向在上階層中進行處理之處理部通知該錯誤之發生； 於該上階層中，於接收到指示重啟通信之指令與指示寫入上述資料之指令之組合為止，或接收到指示通信結束之指令為止，忽略一切通信。 (7) 一種通信方法，其係經由匯流排進行通信者，且 藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，且該通信處理包含以下步驟： 上述第1通信裝置 自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度， 於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發，且 於資料傳輸上述資料之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。 (8) 一種使電腦執行通信處理之程式，其係使經由匯流排進行通信之通信裝置之電腦執行者，且 藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，且該通信處理包含以下步驟： 上述第1通信裝置 自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度， 於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發，且 於對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。 (9) 一種通信系統，其係經由匯流排，藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信者，且 上述第1通信裝置具備： 取得部，其自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度； 收發控制部，其於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發；及 發送部，其於對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊。 另，本實施形態並非限定於上述之實施形態者，於不脫離本發明主旨範圍內得進行各種變更。 Hereinafter, a specific embodiment to which the present technology is applied will be described in detail with reference to the drawings. <Configuration example of bus bar IF> FIG. 1 is a block diagram showing a configuration example of an embodiment of a bus bar IF to which the present technology is applied. The bus IF11 shown in FIG. 1 is configured to connect the I3C master 12 and the three I3C slaves 13-1 to 13-3 via the data signal line 14-1 and the clock signal line 14-2, and can be based on Communication of the I3C standard. The I3C master 12 has control over the bus IF11, and can communicate with the I3C slaves 13-1 to 13-3 via the data signal line 14-1 and the clock signal line 14-2. The I3C slaves 13-1 to 13-3 can communicate with the I3C master 12 via the data signal line 14-1 and the clock signal line 14-2 according to the control of the I3C master 12. In addition, each of the I3C slave devices 13-1 to 13-3 is constructed in the same way. Hereinafter, when there is no need to distinguish these cases, it is simply referred to as the I3C slave device 13, and the same applies to each block constituting the I3C slave device 13. . The data signal line 14 - 1 and the clock signal line 14 - 2 are used to transmit signals between the I3C master 12 and the I3C slave 13 . For example, in the bus IF11, serial data (SDA: Serial Data) is transmitted one by one through the data signal line 14-1, and serial clock (SDA: Serial Data) of a specific frequency is transmitted through the clock signal line 14-2. SCL: Serial Clock) The I3C master 12 includes a data transmission unit 21 , a data reception unit 22 , a command transmission unit 23 , a mode control unit 24 , and a transmission/reception control unit 25 , and each of these blocks is composed of circuits or modules. . The data sending unit 21 sends data to the I3C slave 13 via the data signal line 14-1 and the clock signal line 14-2. For example, the data transmission unit 21 drives the data signal line 14-1 according to the timing of the serial clock transmitted by driving the clock signal line 14-2 (switches the potential to the H level or the L level). , so that data can be sent to the I3C slave 13 . The data receiving unit 22 receives data from the I3C slave 13 via the data signal line 14-1 and the clock signal line 14-2. For example, the data receiving unit 22 drives the data signal line 14-1 by the I3C slave 13 according to the serial clock timing of the clock signal line 14-2, and can receive the data from the I3C slave 13. information to come. The command transmission unit 23 transmits various commands, which will be described later, to the I3C slave 13 via the data signal line 14-1 and the clock signal line 14-2, similarly to the data transmission unit 21. The mode control unit 24 selects any one of a plurality of transmission modes specified by the I3C standard according to a request from an upper layer (for example, the CCI layer processing unit 42 of FIG. 2 described later), and performs communication in accordance with the selected transmission mode. The control of the transmission/reception control unit 25 is performed in a manner. For example, in the bus IF11, according to the data transmission rate, there is an SDR (Standard Data Rate) mode for data transmission at a normal transmission rate and a data transmission mode for data transmission at a transmission rate higher than the SDR mode. HDR (High Data Rate: High Data Rate) mode. In the HDR mode, the following three transmission rates are defined according to the specifications: DDR (Double Data Rate: Double Data Rate) mode, TSP (Ternary Symbol Pure-Bus: Ternary Symbol Pure-Bus) mode, and TSL ( Ternary Symbol Legacy-inclusive-Bus: Ternary Symbol Legacy-inclusive-Bus) mode. Therefore, the mode control unit 24 selects any one of the SDR mode, the DDR mode, the TSP mode, and the TSL mode, and controls the transmission/reception control unit 25 so as to communicate in accordance with the selected transmission mode. The transmission and reception control unit 25 controls the transmission and reception of data by the data transmission unit 21 and the data reception unit 22, and the transmission of commands by the command transmission unit 23, according to the request from the upper layer, according to the transmission mode selected by the mode control unit 24. The I3C master 12 is thus constituted, and the transmission mode can be switched as required, for example, the data to be written into the temporary register is sent by the data sending part 21 , or the data read from the temporary register is received by the data receiving part 22 . material. The I3C slave 13 includes a data transmission unit 31 , a data reception unit 32 , a command interpretation unit 33 , a mode control unit 34 , and a transmission/reception control unit 35 , and each of these blocks is constituted by circuits or modules. The data sending unit 31 sends data to the I3C master 12 via the data signal line 14-1 and the clock signal line 14-2. For example, the data transmission unit 31 drives the data signal line 14-1 according to the sequence of the serial clock of the clock signal line 14-2 driven by the I3C master 12, thereby sending data to the I3C master controller 12. The data receiving unit 32 receives data from the I3C master 12 via the data signal line 14-1 and the clock signal line 14-2. For example, the data receiving unit 32 drives the data signal line 14-1 by the I3C master 12 according to the serial clock timing of the clock signal line 14-2, and can receive the data from the I3C master 12. information to come. The command interpreting unit 33 receives the command from the command sending unit 23 of the I3C master 12 via the data signal line 14-1 and the clock signal line 14-2, interprets the command, and performs various processing based on the command's command. . For example, the command interpretation unit 33 performs a process of notifying the mode control unit 34 to start the HDR communication when receiving the command instructing to start the communication in the HDR mode. In addition, the command interpretation unit 33 performs a process of notifying the transmission/reception control unit 35 to perform data writing or reading when receiving a command for writing data or a command for reading data. The mode control unit 34 selects any one of the SDR mode, DDR mode, TSP mode, and TSL mode similarly to the mode control unit 24 of the I3C master 12 according to the instruction of the command received by the command interpretation unit 33 . Then, the mode control unit 34 controls the transmission/reception control unit 25 so as to communicate according to the selected transmission mode. The transmission/reception control unit 35 controls the transmission and reception of data by the data transmission unit 31 and the data reception unit 32 according to the command received by the command interpretation unit 33 in the transmission mode selected by the mode control unit 24 . The I3C slave 13 is constructed in this way, and the transmission mode is switched according to the control of the I3C master 12. For example, the data read from the register can be sent by the data sending part 31, or the data receiving part 32 can be used to receive the data to be written. Data entered into the scratchpad. The I3C master 12 and the I3C slave 13 constructed as described above are installed in the system controller and the controlled device, respectively, and can perform processing in the physical layer of the communication performed by them. FIG. 2 is a block diagram showing a configuration example of a system controller in which the I3C master 12 of FIG. 1 is installed. The system controller 41 shown in FIG. 2 is configured to include a CCI layer processing unit 42, a CPU 43, and an internal bus 44 in addition to the I3C master 12 connected to the data signal line 14-1 and the clock signal line 14-2. . Also, as shown in the figure, the I3C master 12 is connected to a CCI layer processing unit 42 that performs processing higher than the I3C master 12 , and the CCI layer processing unit 42 is connected to a system controller via an internal bus 44 41 The CPU 43 for overall control. The CCI layer processing unit 42 includes a scratchpad address manager 51 , a transfer length information holding unit 52 , a write transfer completion control unit 53 , an invalid data processing unit 54 , and a transfer length information transmitting unit 55 . The register address manager 51 manages the addresses of the registers connected to the bus IF11 of FIG. 1 . The transfer length information holding unit 52 holds transfer length information (Length) indicating the data length (number of bytes) of the data transferred in the data transfer with the I3C slave 13 . The write transfer end control section 53 performs control at the time of ending the write transfer for writing the data transferred from the I3C master 12 to the I3C slave 13 to the register. For example, the invalid data processing unit 54 performs the following processing: in the HDR mode in which 1 character, which is the lowest unit of data transmission, is specified as 2 bytes (16 bits), it is used when adding or deleting data of odd-numbered bytes to be transmitted. fictitious information. The transmission length information sending unit 55 sends the transmission length information held in the transmission length information holding unit 52 to the I3C slave 13 via the I3C master 12 . FIG. 3 is a block diagram showing a configuration example of a controlled device to which the I3C slave 13 of FIG. 1 is mounted. The controlled device 61 shown in FIG. 3 is configured to include a CCI layer processing unit 62 , a device control unit 63 , and an internal bus bar 64 . Also, as shown in the figure, the I3C slave 13 is connected to a CCI layer processing unit 62 that performs processing at a higher level than the I3C slave 13, and the CCI layer processing unit 62 is connected to a controlled device via an internal bus 64. 61 The device control unit 63 for overall control. The CCI layer processing unit 62 is configured to include a scratchpad address management unit 71, a scratchpad R/W (read/write) control unit 72, a read transfer completion control unit 73, an invalid data processing unit 74, and a transfer length Information holding unit 75 . The temporary register address management unit 71 manages the addresses of the temporary registers included in the controlled device 61 . The register R/W control section 72 performs control of writing data transmitted from the I3C master 12 to the I3C slave 13 to the register, and for sending from the I3C slave 13 to the I3C master 12 The control of reading data from the register. The read transfer end control unit 73 controls when the read transfer of the data read out from the register is ended from the I3C slave 13 to the I3C master 12 . In the HDR mode, the invalid data processing unit 74 performs processing of adding or deleting invalid data used when transmitting data of odd-numbered bytes. The transmission length information holding unit 75 holds the transmission length information (Length) transmitted from the I3C master 12 during data transmission with the I3C master 12 . In addition, the device control unit 63 controls, for example, to write the data received by the I3C slave 13 into the status register according to the control of the register R/W control unit 72 of the CCI layer processing unit 62 . Also, the device control section 63 performs control such as reading data sent from the status register by the I3C slave 13, and sends the data according to the control of the register R/W control section 72 of the CCI layer processing section 62. material. In the system controller 41 and the controlled device 61 constructed as described above, for example, the data written to the register can be transferred from the system controller 41 to the controlled device 61, or read from the register. The data is transmitted from the controlled device 61 to the system controller 41 . <The 1st example of data transmission process> With reference to FIGS. 4-6, an example of the 1st data transmission process of the data transmission in the bus bar IF11 is demonstrated. FIG. 4 shows the format of signals sent and received between the I3C master 12 and the I3C slave 13 when the transmission mode is the DDR mode. On the upper side of FIG. 4 , the format of the read transfer process for transferring the data read from the register from the I3C slave 13 to the I3C master 12 is shown. On the lower side of FIG. 4 , the format of the write transfer process for transferring the data to be written to the register from the I3C master 12 to the I3C slave 13 is shown. In the case of the read transmission process, first, the I3C master 12 sends a command (ENTHDR or HDR_Restart) instructing to start or restart the communication in the HDR mode. Next, the I3C master 12 sends a write command (DDR_Cmd(W)) to instruct the I3C slave 13 to write the data length of the data read and transmitted from the register. In addition, the I3C master 12 continues the write command, and sends a notification to start reading the index of the start address of the data (Index), the transmission length information (Length) indicating the data length of the transmitted data, and the CRC (Cyclic Redundancy Check: cyclic redundancy check) character. Subsequently, the I3C master 12 sends a command (HDR_Restart) instructing to restart the communication in the HDR mode, and sends a read command (DDR_Cmd(R)) instructing to read data. Accordingly, the I3C slave 13 sequentially transmits data every 1 character (16 bits) of the DDR mode from the beginning of the address corresponding to the index, and transmits data corresponding to the number of read bytes of the transmission length information. At the end of data transmission, a CRC character is sent. Subsequently, the I3C master 12 sends a command (HDR_Restart or HDR_Exit) indicating to restart or end the communication in the HDR mode. In the case of the write transfer process, first, the I3C master 12 sends a command (ENTHDR or HDR_Restart) instructing to start or restart the communication in the HDR mode. Next, the I3C master 12 sends a write command (DDR_Cmd(W)) for instructing data to be written, an index (Index) for informing the start address of the data to be written, and transfer length information for indicating the data length of the transferred data (Length). And, the I3C master 12 sequentially transmits data every 1 character (16 bits) of the DDR mode from the beginning of the address corresponding to the index, and the data corresponding to the number of written bytes of the transmission length information At the end of transmission, the CRC character is sent. Subsequently, the I3C master 12 sends a command (HDR_Restart or HDR_Exit) indicating to restart or end the communication in the HDR mode. FIG. 5 shows the format of signals sent and received between the I3C master 12 and the I3C slave 13 when the transmission mode is the TSL mode or the TSP mode. On the upper side of FIG. 5 , the format of the read transfer process for transferring the data read from the register from the I3C slave 13 to the I3C master 12 is shown. The lower side of FIG. 5 shows the format of the write transfer process for transferring the data to be written to the register from the I3C master 12 to the I3C slave 13 . Here, the TSL mode or the TSP mode is a format that is different from the DDR mode in that the transmission of CRC characters shown in FIG. 4 is not performed, and other points are common. In this way, in the first data transmission process, the transmission length information is sent from the I3C slave 13 to the I3C master 12 during data transmission. The transfer length information is held in the transfer length information holding unit 52 of the CCI layer processing unit 42 on the system controller 41 side, and in the transfer length information holding unit 75 of the CCI layer processing unit 62 on the controlled device 61 side. Thereby, for example, when the data length of the data requested to be transmitted is an odd number of bytes, even if dummy data of 1 byte is attached and transmitted, the dummy data can be identified and discarded based on the transmission length information. Therefore, even if the lowest unit of data transmission, ie, 1 character, is 2 bytes (16 bits), data transmission of odd-numbered bytes can be performed reliably. However, in I3C, the upper limit of the number of bytes that can be transmitted per one read transfer (hereinafter referred to as the maximum read length (MRL: Max Read Length)) is stipulated. Similarly, in I3C, the upper limit of the maximum number of bytes that can be transferred per one write transfer (hereinafter referred to as the maximum write length (MWL: Max Write Length)) is stipulated. Generally, the maximum read length and the maximum write length can be set as fixed values at design time according to the installation conditions of each of the controlled devices 61 , and can be set to be variable, for example, when sharing resources with other devices. For example, when the data length of the data requested for data transmission from the CCI layer processing unit 42 is longer than the maximum read length or the maximum write length, the I3C master 12 performs the process to become the maximum read length or less than the maximum write length. Controls how data is divided and transmitted. FIG. 6 is a flowchart illustrating the processing performed in the I3C master 12. As shown in FIG. In step S11 , the I3C master 12 sends commands (GETMWL/MRL) instructing to transmit the maximum read length and maximum write length of each I3C slave 13 to each I3C slave 13 connected to the bus IF11 . Furthermore, the I3C master 12 obtains the maximum read length and the maximum write length sent from each I3C slave 13 according to the command. In step S12, the I3C master 12 determines whether the maximum read length or the maximum write length of each I3C slave 13 obtained in step S11 needs to be adjusted. For example, the I3C master 12 compares the data length of the data assumed to be requested for data transfer from the CCI layer processing unit 42 with the maximum read length and the maximum write length of the I3C slave 13 . In addition, when at least one of the maximum read length and the maximum write length of the I3C slave 13 is less than or equal to the data length of the expected data, the I3C master 12 determines that the data length of the expected data needs to be adjusted. Maximum read length or maximum write length. In addition, the I3C master 12 may compare, for example, the maximum read length and the maximum write length of the I3C master 12 itself as the data length of the assumed data. In step S12, if the I3C master 12 determines that the maximum read length or the maximum write length of the I3C slave 13 needs to be adjusted, the process proceeds to step S13. In step S13, the I3C master 12 adjusts the maximum read length or the maximum write length of the I3C slave 13 that needs to be adjusted, and will set the adjusted maximum read length and the maximum write length of the command ( SETMWL/MRL) to the I3C slave 13. For example, the I3C master 12 adjusts the maximum read length or the maximum write length of the I3C slave 13, which is assumed to be the data length of the data requested from the CCI layer processing unit 42 for data transmission, to the data of the assumed data. length. In addition, the I3C master 12 can also adjust the maximum read length or the maximum write length of the I3C slave 13 to the maximum read length and the maximum write length of the I3C master 12 itself, for example. After the process of step S13, or when it is determined in step S12 that it is not necessary to adjust the maximum read length or the maximum write length of the I3C slave 13, the process proceeds to step S14. In step S14, the I3C master 12 waits for a data transmission request from the upper-level CCI layer processing unit 42, and receives the request when there is a data transmission request. In step S15, the I3C master 12 determines whether the data length of the data requested for data transmission from the CCI layer processing unit 42 in step S14 is longer than the maximum read length or the maximum write length of the I3C slave 13 that is the object of data transmission. length. For example, when the maximum read length or the maximum write length of the I3C slave 13 has been adjusted in step S13, the determination is made based on the adjusted maximum read length or the maximum write length. In step S15, if the I3C master 12 determines that the data length of the data requesting data transfer is longer than the maximum read length or the maximum write length of the I3C slave 13 to which the data transfer is performed, the process proceeds to step S16. In step S16, the I3C master 12 divides the data requested for data transmission into a length less than the maximum read length or the maximum write length of the I3C slave 13 of the object of data transmission, and performs read transmission processing or Write transfer processing. On the other hand, in step S15, if the I3C master 12 determines that the data length of the data requested for data transmission is not longer than the maximum read length or the maximum write length (maximum read length or the length less than or equal to the maximum write length), the process proceeds to step S17. In step S17, the I3C master 12 performs the normal read transfer process or write transfer process without dividing the data. After the process of step S16 or S17, the process returns to step S14, and the I3C master 12 waits for a data transfer request from the upper-level CCI layer processing unit 42, and then repeats the same process. In this way, when the I3C master 12 requests data transmission of data longer than the maximum read length or the maximum write length set in the I3C slave 13, the data can be divided and transmitted. That is, in the system controller 41, the I3C master 12 obtains the maximum read length and the maximum write length of the I3C slave 13, and when performing data transmission with the I3C slave 13, the data transfer is performed once. When the data length of the data that can be transmitted is less than the maximum read length and the maximum write length, the sending and receiving of the data is controlled by the sending and receiving control unit 25 . Furthermore, in the system controller 41, the CCI layer processing section 42 can set the maximum read length and the data length below the maximum write length for the transfer length information indicating the data length of the data to be transferred, and the I3C master 12 stores the data in the data length. The transmission length information is sent to the I3C slave 13 before the data is transmitted. For example, when performing the normal read transfer process or write transfer process in step S17, the I3C slave 13 performs the data set in the CCI layer processing unit 42 in such a way as to not exceed the maximum read length and the maximum write length transmission. In addition, in step S16 , when the read transfer process or the write transfer process is performed by dividing the length into the maximum read length or the length less than the maximum write length, the I3C slave 13 transmits the data by dividing the data into a plurality of times. At this time, the I3C slave 13 may, for example, send transmission length information for each data transmission. Alternatively, as will be described later, when the I3C slave 13 performs the read transmission process, the transmission length information representing the data length of the entire data requested to be transmitted may be sent only once, thereby reducing the processing burden and avoiding the reduction of transmission efficiency. However, it is also envisaged that there are I3C slaves 13 that do not correspond to the commands (GETMRL, GETMWL) indicating to send the maximum read length and maximum write length. Alternatively, it is also envisaged that the I3C master 12 unintentionally sets the length exceeding the maximum read length or the maximum write length as the transfer length information. Therefore, when writing data whose data length is longer than the maximum write length, the FIFO (First In, First Out: First In, First Out) overflow on the side of the I3C controller 13 will occur. As a first countermeasure against such a situation, the I3C slave 13 normally writes data until the FIFO overflows, discards all the data after the FIFO overflows, and sets up an error flag (over MWL error) indicating that a FIFO overflow occurs. , and hold the error flag until cleared. Moreover, the I3C slave 13 ignores all signals until the next HDR end command or HDR restart command (HDR_Exit or HDR_Restart) is received. In addition, as a second measure, the I3C slave 13 performs a process of interrupting communication from the I3C slave 13 side (Slave Abort) after reaching the maximum write length. Accordingly, the I3C master 12 stops communication, and can stop the communication through the HDR end command (HDR_Exit), or issue the HDR restart command (HDR_Restart) to continue the transmission of the remaining data. In addition, as a third measure, since the I3C slave 13 can recognize that the maximum write length is exceeded at the time when the transfer length information is received, the processing (Slave Abort) of interrupting the communication from the I3C slave 13 side is immediately performed. Accordingly, the I3C master 12 stops communication, and can stop the communication through the HDR end command (HDR_Exit), or issue the HDR restart command (HDR_Restart) to continue the transmission of the remaining data. Furthermore, it is also necessary to take countermeasures when reading data whose data length is longer than the maximum read length. For example, as a first measure, since it is difficult for the I3C slave 13 to transfer data to the end, it immediately returns NACK after receiving the read command to terminate the communication. In addition, the I3C slave 13 sets up an error flag (over MRL error) indicating that an error occurs due to instructing to read data with a data length longer than the maximum read length, and keeps the error flag until cleared. Also, as a second measure, the I3C slave 13 temporarily transmits data to the I3C master 12 until the upper limit of the maximum read length is reached. In addition, an error flag (over MRL error) is set up when the maximum read length is reached, and in the case of the DDR mode, the end packet, that is, the CRC character, is sent to the I3C master 12, and in the case of the TSP/TSL mode, The driving of the data signal line 14-1 and the clock signal line 14-2 is stopped, and the bus bar is released. On the other hand, on the side of the I3C master controller 12, in the case of DDR mode, until the data length indicated by the transmission length information is reached, and at the stage that the CRC character has been received, it is recognized that the I3C slave device 13 has an error (over MRL error). If no CRC error occurs, the I3C master 12 accepts the data up to that point in time. In addition, on the I3C master 12 side, in the case of TSL/TSP mode, before reaching the data length indicated by the transmission length information, and before detecting that the data signal line 14-1 and the clock signal line 14- The stage of the drive (not triggered) state of 2 is identified as an over MRL error of the I3C slave 13 . In addition, no matter which is the DDR mode and the TSL/TSP mode, after the I3C master 12 recognizes the error (over MRL error) of the I3C slave 13, it will perform HDR according to the data length not exceeding the maximum read length. The data is resent in the way of read processing. <Second Processing Example of Data Transfer> Referring to FIGS. 7 to 25 , the second data transfer processing of transferring data in the bus IF11 will be described in further detail. As shown in FIG. 7 , when the transmission mode is the DDR mode, the data that exceeds the maximum read length is divided and transmitted, and the read transmission process of reading data from the I3C slave 13 to the I3C master 12 is performed. Format. In addition, FIG. 7 shows an example of requesting data transmission of 300 bytes when the maximum read length is 200 bytes. First, the I3C master 12 sends a command (ENTHDR or HDR_Restart) instructing to start or restart communication in the HDR mode. Next, the I3C master 12 sends a write command (DDR_Cmd(W)) for instructing the I3C slave 13 to write the data length of the data read and transmitted from the register. Next, the I3C master 12 continues the write command, and sends an index (Index) to notify the start address of the data to be read, transmission length information (Length) indicating the data length of the data to be transmitted, and a CRC character. Subsequently, the I3C master 12 sends a command (HDR_Restart) instructing to restart communication in the HDR mode, and sends a read command (DDR_Cmd(R)) instructing to read out data. In the example shown in Figure 7, the start address of the data to be read is set to 0 address, the data length of the transmitted data is set to 300 bytes, and the maximum read length is set to every 200 bytes. Data is split and transmitted. Accordingly, according to the index, the I3C slave 13 transmits data sequentially from the address of the 0 address in every 1 character (16-bit) of the DDR mode, and at the end of the 200-byte byte which becomes the maximum read length After the data is sent, the CRC character is sent. Subsequently, the I3C master 12 sends an instruction (HDR_Restart) indicating the restart of the communication in the HDR mode, and then sends a read instruction ((DDR_Cmd(R)) indicating the readout of the data. At this time, the I3C slave 13 The data of 200 bytes in the 300 bytes shown in the transmission length information is sent out, and the subsequent start address can be identified as the 200 address, and the remaining 100 bytes need to be sent. Therefore, I3C is controlled The device 13 transmits data sequentially from the address of the 200-bit address in every 1 character (16-bit) of the DDR mode, and when the data transmission of the 100-byte group ends, sends a CRC character. The data of the 300-byte data requested to be transmitted, and the I3C master 12 sends an instruction (HDR_Restart or HDR_Exit) indicating the communication of restarting or ending the HDR mode. As described above, when the I3C master 12 performs the read transmission process, As described above with reference to FIG. 4 , before the data is read from the I3C slave device 13 , the index and transmission length information are sent, thereby informing the I3C slave device 13 of the start address of the data read and the data to be transmitted. Here, the I3C master 12, for example, when dividing and reading the data exceeding the maximum read length, first sends the index and transmission length information related to the overall data. Therefore, even if the I3C master 12. The index and transmission length information are not sent for each data continuously read. In the I3C slave 13, the index and data length of the continuously read data can also be identified by updating the sending remaining amount every time the data is sent. Thereby, the index and transmission length information can not be sent for each data of continuous transmission, correspondingly, the processing burden can be reduced, and the transmission efficiency of the data can be improved. When the transmission mode is shown in FIG. 8 as the TSL mode or the TSP mode, carry out Divide and transmit the data that exceeds the maximum read length, and read the data from the I3C slave 13 to the I3C master 12. The format of the read and transfer process. In addition, in Fig. 8 and Fig. 7, it is shown in the maximum When the read length is 200 bytes, an example of requesting data transmission of 300 bytes. Here, the TSL mode or the TSP mode is the point that the transmission of the CRC characters shown in Fig. 7 is not performed, which is different from the DDR mode. The other points are all common formats. That is, in TSL mode or TSP mode, the same as DDR mode, the data transmission efficiency can be improved. <Data transmission processing by the system controller> Refer to the flowcharts shown in Fig. 9 to Fig. 17 Fig. 1 illustrates the data transfer process performed in the system controller 41. In step S21, the I3C master 12 performs an initial setting procedure based on each of the I3C slaves 13 connected to the bus IF11 (for example, the above figure The processing of steps S11 to S13 of 6). In step S22, the CCI layer processing section 42 waits for the data transmission request from the upper-level CPU 43, and receives the request when there is a request for data transmission. In step S23, the CCI layer processes 42 roots According to the data transmission request received in step S22, it is determined that the transmission mode during data transmission with the controlled device 61 is any one of the DDR mode, the TSL/TSP mode, and the SDR mode. In step S23, if the CCI layer processing unit 42 determines that the transfer mode is the DDR mode, the process proceeds to step S24, and the register R/W transfer process in the DDR mode is performed as described later with reference to FIGS. 10 to 13 . On the other hand, in step S23, if the CCI layer processing unit 42 determines that the transmission mode is the TSL/TSP mode, the process proceeds to step S25, and the register R of the TSL/TSP mode is performed as described later with reference to FIGS. 14 to 17 . /W transfer processing. On the other hand, in step S23, when the CCI layer processing unit 42 determines that the transmission mode is the SDR mode, the process proceeds to step S26, and the buffer R/W transmission is performed in the SDR mode. In addition, in the case of register R/W transmission in the SDR mode, there is no need to send and receive the transmission length information as described above. After the process of step S24, step S25, or step S26, the process returns to step S22, and the system controller 41 repeats the same process subsequently. Next, referring to FIGS. 10 to 13 , the register R/W transfer process in the DDR mode executed by the system controller 41 (step S24 in FIG. 9 ) will be described. FIG. 10 is a flowchart illustrating the register R/W transfer process in DDR mode. In step S31, in the I3C master 12, the command sending part 23 starts the communication in the HDR mode to all the I3C slaves 13 connected to the bus IF11, and sends the HDR start command (ENTHDR0) that communicates in the DDR mode. ). In step S32, the CCI layer processing unit 42 sets the data length of the data requested for data transmission from the upper-level CPU 43 in step S22 of FIG. quantity. In step S33, the CCI layer processing unit 42 determines whether the transfer direction of the data requested by the CPU 43 is the read transfer or the write transfer. In step S33, if the CCI layer processing unit 42 determines that the data transfer direction is read transfer, the process proceeds to step S34, and DDR read transfer processing is performed as described later with reference to FIG. 11 . On the other hand, in step S33, if the CCI layer processing unit 42 determines that the data transfer direction is write transfer, the process proceeds to step S35, and DDR write transfer processing is performed as described later with reference to FIG. 13 . After the DDR read transfer process in step S34 or the DDR write transfer process in step S35, the process proceeds to step S36. In step S36, the CCI layer processing unit 42 determines whether the next HDR data transmission is requested from the upper-level CPU 43. In step S36, if the CCI layer processing unit 42 determines that data transmission of the next HDR is requested, the process proceeds to step S37. In step S37, in the I3C master 12, the command sending unit 23 sends an HDR restart command instructing to restart the communication in the HDR mode. Then, the process returns to step S32, and the same process is repeated thereafter. On the other hand, in step S36, if the CCI layer processing unit 42 determines that the data transfer of the next HDR is not requested, the process proceeds to step S38. In step S38, in the I3C master 12, after the command sending section 23 sends a command to instruct to end the communication in the HDR mode, the register R/W transfer process in the DDR mode ends, and the process returns to step S22 in FIG. 9 . . FIG. 11 is a flowchart illustrating the DDR read transfer process performed in step S34 of FIG. 10 . In step S41, the CCI layer processing unit 42 sets the transfer remaining amount set in step S32 of FIG. 10 as the transfer length information indicating the data length of the data sent to the controlled device 61, and keeps it in the transfer length information. holding part 52 . In step S42, in order to notify the I3C slave 13 of the data length of the data read and transmitted from the register, the I3C master 12 performs the HDR write transmission process of sending the transmission length information to the I3C slave 13 (refer to Fig. 12). After this process, in the I3C master 12, the command sending unit 23 sends an HDR restart command in step S43, and sends a read command in step S44. In step S45, the I3C master 12 stops driving the data signal line 14-1, and when the I3C slave 13 drives the data signal line 14-1 to transmit a signal, the data transceiver 22 sends a signal. Start signal reception. In step S46 , the I3C master 12 performs a determination based on the preamble of the signal transmitted from the I3C slave 13 . In step S46, if the I3C master 12 determines that data is transmitted from the I3C slave 13 based on the preamble, the process proceeds to step S47. In step S47 , in the I3C master 12 , the data receiving unit 22 receives the data and the parity code transmitted from the I3C slave 13 . In step S48, the I3C master 12 uses the parity code received in step S47 to determine whether there is an error in the data received in step S47. Furthermore, when the I3C master 12 determines that no parity error has occurred, the process proceeds to step S49. In step S49, the CCI layer processing unit 42 determines whether the current transmission remaining amount is 2 bytes or more, 1 byte, and 0 bytes. In step S49, if the CCI layer processing unit 42 determines that the current transmission remaining amount is 2 bytes or more, the process proceeds to step S50. In step S50, the CCI layer processing unit 42 obtains the 2-byte data read out from the register and transmitted from the I3C slave 13 to the I3C master 12, and in step S51, updates the remaining amount of transmission to push back 2 bytes. On the other hand, in step S49, if the CCI layer processing unit 42 determines that the current transmission remaining amount is 1 byte, the process proceeds to step S52. In step S52, in the CCI layer processing unit 42, the dummy data of 1 byte in the 2 bytes of the data transmitted from the I3C slave 13 to the I3C master 12 is processed by the invalid data processing unit 54. Discard to obtain 1-byte data read from the register. Subsequently, in step S53, the I3C master 12 updates the transmission remaining amount to be pushed back by 1 byte. On the other hand, in step S49, if the CCI layer processing unit 42 determines that the current transmission remaining amount is 0 bytes, the process proceeds to step S54. That is, in this case, since there is no data (0 bytes) transmitted from the I3C slave 13, which violates the CCI protocol, the CCI layer processing unit 42 will transmit the data from the I3C slave 13 to the I3C master 12. 2 bytes are discarded. After the processing of step S51 , step S53 , or step S54 , the processing proceeds to step S55 , and the I3C master 12 performs determination based on the preamble of the signal sent from the I3C slave 13 . In step S55, if the I3C master 12 determines that data is transmitted from the I3C slave 13 based on the preamble, the process returns to step S47, and the same process is repeated subsequently. On the other hand, in step S55, if the I3C master 12 determines that the CRC character is transmitted based on the preamble, the process proceeds to step S56, and the data receiving unit 22 receives the CRC character. For example, the I3C slave 13 sends a CRC character when sending all the data requested for data transmission, or sending the data with the maximum read length. In step S57, the I3C master 12 determines whether an error occurs in the CRC character received by the data receiving unit 22 in step S56. In step S57, if the I3C master 12 determines that there is no error in the CRC character, the process proceeds to step S58 to restart the driving of the data signal line 14-1. In step S59, the I3C master 12, for example, after updating the transmission remaining amount in step S51 or S53, determines whether the current transmission remaining amount is 0. For example, in the case where the data of the data length indicated by the transfer length information, that is, all the data for which data transfer is requested, is sent, the current transfer remaining amount is 0. In this regard, for example, if the data length indicated by the transmission length information is longer than the maximum read length, and the data is divided and transmitted, there is a case in which the CRC character is sent even though all the data requested for data transmission is not sent. In this case, the current transmission remaining amount is not 0. In step S59, if the I3C master 12 determines that the current transmission remaining amount is not 0, the process returns to step S43, and the process continues after sending the HDR restart command. On the other hand, in step S46 , if the I3C master 12 determines based on the preamble that, for example, a NACK response is sent indicating that the I3C slave 13 cannot receive data or commands normally, or a frame error is detected (Framing Error), the process proceeds to step S60. Likewise, when the I3C master 12 determines that a parity error has occurred in step S48, that a frame error has been detected in step S55, and that that a CRC character error has occurred in step S57, the process proceeds to Step S60. In step S60 , the I3C master 12 sends serial clocks to the I3C slave 13 19 times. Then, in step S61, the I3C master 12 notifies the CCI layer processing unit 42 of the error, and in step S62, the CCI layer processing unit 42 notifies the upper-layer CPU 43 of the error. After the process of step S62, or when it is determined in step S59 that the current transfer remaining amount is 0, the DDR read transfer process ends, and the process proceeds to step S36 in FIG. 10 . FIG. 12 is a flowchart illustrating the HDR write transfer process performed in step S42 of FIG. 11 . In step S71 , the command sending part 23 sends a write command to the I3C slave 13 , and in step S72 , the data sending part 21 sends the index to the I3C slave 13 . In step S73 , the data sending unit 21 sends the transfer length information corresponding to the data transfer request received in step S22 of FIG. 9 to the I3C slave 13 . In step S74, after the data transmission unit 21 transmits the CRC character, the HDR writing transmission process ends, and the process proceeds to step S43 in FIG. 11 . FIG. 13 is a flowchart illustrating the DDR write transfer process performed in step S35 of FIG. 10 . In step S81, the CCI layer processing unit 42 of the system controller 41 determines whether the data length of the transmission remaining amount set in step S32 of FIG. 10 is longer than the data length that can be sent in one transmission. Here, the data length that can be sent in one transmission is the maximum write length of the I3C slave 13 that becomes the write end minus the index of the start address of the notification to start writing the data, and the data length of the transmitted data value (=MWL-Index-Length). In step S81, if the CCI layer processing unit 42 determines that the data length of the transmission remaining amount is longer than the data length that can be sent in one transmission, the process proceeds to step S82. In step S82, the CCI layer processing unit 42 sets the data length that can be sent in one transmission as the transmission length information and holds it in the transmission length information holding unit 52, and the process proceeds to step S84. On the other hand, in step S81, if the CCI layer processing unit 42 determines that the data length of the transmission remaining amount is not longer (shorter) than the data length that can be sent in one transmission, the process proceeds to step S83. In step S83, the CCI layer processing unit 42 sets the transmission remaining amount as transmission length information and holds it in the transmission length information holding unit 52, and the process proceeds to step S84. In step S84 , the command sending part 23 sends the write command to the I3C slave 13 , and in step S85 , the data sending part 21 sends the index to the I3C slave 13 . Subsequently, in step S86 , the transmission length information sending unit 55 sends the transmission length information held in the transmission length information holding unit 52 to the I3C slave 13 through the data sending unit 21 . In step S87, the CCI layer processing unit 42 sets the transmission length information held in the transmission length information holding unit 52 at the current time point as the data length of the remaining data to be written into the register. In step S88, the CCI layer processing unit 42 determines that the current remaining data length is any one of 2 bytes or more, 1 byte, and 0 bytes. In step S88, if the CCI layer processing unit 42 determines that the current remaining data length is 2 bytes or more, the process proceeds to step S89. In step S89, the CCI layer processing unit 42 supplies the 2-byte data transmitted from the I3C master 12 to the I3C slave 13 and written into the register to the I3C master 12, and in step S90 , update the remaining data length to 2 bytes backward. On the other hand, in step S88, if the CCI layer processing unit 42 determines that the current remaining data length is 1 byte, the process proceeds to step S91. In step S91, in the CCI layer processing unit 42, the 1-byte data transmitted from the I3C master 12 to the I3C slave 13 and written into the register is supplied to the I3C master 12, and The dummy data of 1 byte is added by the invalid data processing unit 54 . In addition, in step S92, the CCI layer processing unit 42 updates the remaining data length to be one byte backward. After the process of step S90 or S92, the process proceeds to step S93. The I3C master 12 transmits the data supplied from the CCI layer processing unit 42 in step S89 or S91 to the I3C slave 13 through the data transmission unit 21, and the process returns to step S88. On the other hand, in step S88, if the CCI layer processing unit 42 determines that the current remaining data length is 0 bytes, the process proceeds to step S94. That is, in this case, the transmission of all data corresponding to the data transmission processing request received in step S22 of FIG. 9 is completed, and in step S94, the I3C master 12 sends the CRC character. In step S95 , the CCI layer processing unit 42 subtracts the transmission length information from the current transmission remainder to update the transmission remainder (=transmission remainder−Length). In step S96, the CCI layer processing unit 42 determines whether or not the transmission remaining amount after the update is 0. In step S96, if the CCI layer processing unit 42 determines that the transmission remaining amount after the update is not 0, the process proceeds to step S97. In step S97, after the I3C master 12 sends an instruction instructing to restart the communication in the HDR mode, the process returns to step S81, and the same process is repeated subsequently. On the other hand, in step S96 , if the CCI layer processing unit 42 determines that the transfer remaining amount after the update is 0, the DDR write transfer process ends, and the process proceeds to step S36 in FIG. 10 . As described with reference to FIGS. 10 to 13 , the system controller 41 can perform the register R/W transfer process in the DDR mode. Next, referring to FIGS. 14 to 17 , the buffer R/W transfer process (step S25 in FIG. 9 ) in the TSL/TSP mode will be described. FIG. 14 is a flowchart illustrating the register R/W transfer process in TSL/TSP mode. In step S101, the I3C master 12 starts communication in the HDR mode to all the I3C slaves 13 connected to the bus IF11, and sends an HDR start command (ENTHDR1/2) for communication in the TSL/TSP mode. In step S102, the CCI processing unit 42 sets the data length of the data of the data transfer request from the upper-layer CPU 43 in step S22 of FIG. In step S103, the CCI processing unit 42 determines whether the transfer direction of the data requested by the CPU 43 is the read transfer or the write transfer. In step S103, if the CCI processing unit 42 determines that the data transfer direction is read transfer, the process proceeds to step S104, and TSL/TSP read transfer processing is performed as described later with reference to FIG. 15 . On the other hand, in step S103, if the CCI processing unit 42 determines that the data transfer direction is write transfer, the process proceeds to step S105, and TSL/TSP write transfer processing is performed as described later with reference to FIG. 17 . After the processing of the TSL/TSP read transfer processing of step S104 or the processing of the TSL/TSP write transfer processing of step S105, the processing proceeds to step S106. Then, in steps S106 to S108, the same processes as those of steps S36 to S38 in FIG. 10 are performed, then, the register R/W transfer process in TSL/TSP mode ends, and the process returns to step S22 in FIG. 9 . FIG. 15 is a flowchart illustrating the TSL/TSP read transfer process performed in step S104 of FIG. 14 . In steps S111 to S114, the same processes as those of steps S41 to S44 in FIG. 11 are performed. Next, in step S115, the I3C master 12 stops driving the data signal line 14-1 and the clock signal line 14-2. In addition, in the TSL/TSP mode, the turnaround order is different from that in the DDR mode. In step S116 , the I3C master 12 determines whether the data transmitted from the I3C slave 13 is received. In addition, in the TSL/TSP mode, unlike the DDR mode, no preamble transmission is performed. In step S116 , if it is determined that the data transmitted from the I3C slave 13 is received, the process proceeds to step S117 , and the data receiving unit 22 receives the data and the parity code transmitted from the I3C slave 13 . In step S118, the I3C master 12 determines whether the data received by the data receiving unit 22 in step S117 contains errors, and if it is determined that no errors are included, the process proceeds to step S119. In steps S119 to S124, the CCI layer processing unit 42 performs the same processing as steps S49 to S54 in FIG. 11 . In step S125, the I3C master 12 determines whether the data transmitted from the I3C slave 13 is received. If it is determined that the data is received, the process returns to step S117, and the same process is repeated subsequently. On the other hand, in step S125, if it is determined that no data has been received, the process proceeds to step S126, and the I3C master 12 restarts driving the data signal line 14-1 and the clock signal line 14-2. In addition, in TSL/TSP mode, CRC characters are not sent, and the turnaround order is different from that in DDR mode. On the other hand, in step S118, if the I3C master 12 determines that the data received by the data receiving unit 22 in step S117 contains an error, the process proceeds to step S128. In addition, in TSL/TSP mode, the error detection conditions are different from those in DDR mode. For example, if a parity error is detected, or if more than 2×2 symbols are received outside the data character limit, it is determined that the data contains errors . In step S128, the I3C master 12 waits for the change of the signal to stop, and when the change of the signal stops, the process proceeds to step S129. That is, in TSL/TSP mode, the order of error recovery is different from that in DDR mode. Furthermore, in step S116, if it is determined that the data transmitted from the I3C slave 13 has not been received, eg, when a NACK response (symbol 2×3 times) is received, the process proceeds to step S129. In step S129, the I3C master 12 notifies the CCI layer processing unit 42 of the error, and in step S130, the CCI layer processing unit 42 notifies the upper CPU 43 of the error. After the processing in step S130 or when it is determined in step S127 that the current transfer remaining amount is 0, the TSL/TSP read transfer processing ends, and the processing proceeds to step S106 in FIG. 14 . FIG. 16 is a flowchart illustrating the HDR write transfer process performed in step S112 of FIG. 15 . In steps S141 to S143, the same processes as those of steps S71 to S73 in FIG. 12 are performed. After the write command, index, and transfer length information are sent and the HDR write transfer process ends, the process proceeds to step S113 in FIG. 15 . That is, the HDR write transfer process of the TSL/TSP read transfer process shown in FIG. 16 does not send CRC characters, which is different from the HDR write transfer process of the DDR read transfer process described above with reference to FIG. 12 . FIG. 17 is a flowchart illustrating the TSL/TSP write transfer process performed in step S105 of FIG. 14 . In steps S151 to S163, the same processes as those of steps S81 to S93 in FIG. 13 are performed. And, in step S158, if it is determined that the current remaining data length is 0 bytes, that is, when the transmission of all data corresponding to the data transmission request received in step S22 of FIG. 9 is completed, the process proceeds to step S164 . In steps S164 to S166, the same processes as those of steps S95 to S97 of FIG. 13 are performed, then, the TSL/TSP write transfer process ends, and the process proceeds to step S106 of FIG. 14 . That is, the TSL/TSP write transfer process shown in FIG. 17 does not send CRC characters, which is different from the DDR write transfer process described above with reference to FIG. 13 . As described with reference to FIGS. 14 to 17 , the system controller 41 can perform the register R/W transfer processing in TSL/TSP mode. <Data transfer processing of controlled device> Referring to FIGS. 18 to 25 , the data transfer processing executed in the controlled device 61 will be described. 18 is a flowchart illustrating the data transfer process performed by the system controller 41 in the controlled device 61 corresponding to the execution of the register R/W transfer process in the DDR mode described above with reference to FIG. 10 . For example, the I3C slave 13 starts processing when it receives the HDR start command (ENTHDR0) transmitted from the I3C master 12 for notification in the DDR mode. Next, in step S171 , the I3C slave 13 performs a determination based on the preamble of the signal transmitted from the I3C master 12 following the HDR start command. In step S171, if the I3C slave 13 determines that the command is transmitted from the I3C master 12 based on the preamble, the process proceeds to step S172. In step S172 , in the I3C slave 13 , the command interpretation unit 33 receives the command and the parity code transmitted from the I3C master 12 . In step S173, the command interpretation unit 33 uses the parity code received in step S172 to determine whether an error occurs in the command received in step S172. Then, if the command interpretation unit 33 determines that no parity error has occurred, the process proceeds to step S174. In step S174, the command interpretation unit 33 determines whether the command code of the command received in step S172 is a read command or a write command. In step S174 , if the command interpretation unit 33 determines that the command code is a read command, the process proceeds to step S175 , and DDR read transfer processing is performed as described later with reference to FIG. 19 . On the other hand, in step S174 , if the command decoding unit 33 determines that the command code is a write command, the process proceeds to step S176 , and DDR write transfer processing is performed as described later with reference to FIG. 20 . After the DDR read transfer process of step S175 or the process of the DDR write transfer process of step S176, the process proceeds to step S179. On the other hand, in step S171, if a frame error is detected based on the preamble, or if it is determined in step S173 that a parity error has occurred, the process proceeds to step S177. In step S177, the I3C slave 13 notifies the CCI layer processing unit 62 of an error, and in step S178, after the CCI layer processing unit 62 sets the transmission remaining amount to 0, the process proceeds to step S179. In step S179 , the I3C slave 13 determines whether the command interpreter 33 has received a command instructing to restart the communication in the HDR mode and a command instructing to terminate the communication in the HDR mode. In step S179, if it is determined that the command interpretation unit 33 has received the command to instruct to restart the communication in the HDR mode, the process returns to step S171, and the same process is repeated thereafter. On the other hand, in step S179, if it is determined that the command interpretation unit 33 has received a command instructing to terminate the communication in the HDR mode, the data transmission process of the controlled device 61 is terminated. FIG. 19 is a flowchart illustrating the DDR read transfer process performed in step S175 of FIG. 18 . In step S181, the CCI layer processing unit 62 determines whether the current transfer remaining amount is greater than 0 bytes and less than the maximum read length, more than the maximum read length, and 0 bytes. In step S181, if the CCI layer processing unit 62 determines that the current transmission remaining amount is larger than 0 bytes and does not reach the maximum read length, the process proceeds to step S182. In step S182, the CCI layer processing unit 62 sets the current transmission remaining amount as the current transmission remaining amount of the data sent according to the read command. On the other hand, in step S181, if the CCI layer processing unit 62 determines that the current transfer remaining amount is equal to or larger than the maximum read length, the process proceeds to step S183. In step S183, the CCI layer processing unit 62 sets the maximum read length as the current remaining amount of data sent according to the read command. After the process of step S182 or S183, the process proceeds to step S184, and the I3C slave 13 starts driving the data signal line 14-1. In step S185, the CCI layer processing unit 62 determines whether the current transmission remaining amount sent according to the read command is 2 bytes or more, 1 byte, and 0 bytes. In step S185, if the CCI layer processing unit 62 determines that the current transmission remaining amount of the data transmitted according to the read command is 2 bytes or more, the process proceeds to step S186. In step S186, the CCI layer processing unit 62 reads the 2-byte data from the register. Next, in step S187 , the CCI layer processing unit 62 supplies the 2-byte data read out in step S186 to the I3C slave 13 . In step S188, the CCI layer processing unit 62 moves the index forward by 2 bytes, pushes the current transmission remaining amount of the data sent according to the command backward by 2 bytes, and pushes the transmission remaining amount backward by 2 bytes. Byte update. On the other hand, in step S185, if the CCI layer processing unit 62 determines that the current transmission remaining amount of the data transmitted according to the read command is 1 byte, the process proceeds to step S189. In step S189, the CCI layer processing unit 62 reads out 1-byte data from the register. Next, in step S190 , the CCI layer processing unit 62 adds 1-byte dummy data to the 1-byte data read in step S189 and supplies it to the I3C slave 13 . In step S191, the CCI layer processing unit 62 moves the index forward by 1 byte, pushes the current transmission residual amount of the data sent according to the command backward by 1 byte, and pushes the transmission residual amount backward by 1 bit Tuple update. After the processing in step S188 or S191, the process proceeds to step S192, and the I3C slave 13 sends the data supplied from the CCI layer processing unit 62 in step S187 or S190 to the I3C master 12 through the data sending unit 31. In step S193, the I3C slave 13 determines whether or not the master instructing the I3C master 12 to interrupt the communication midway is terminated. In step S193, if the I3C slave 13 determines that the master stop is not performed, the process returns to step S185, and the same process is repeated subsequently. On the other hand, in step S193, if the I3C slave 13 determines that the master abort has been performed, the process proceeds to step S195. On the other hand, in step S185, if the CCI layer processing unit 62 determines that the current remaining amount of transmission according to the read command is 0 bytes, the process proceeds to step S194. In step S194, the I3C slave 13 transmits the CRC character, and the process proceeds to step S195. In step S195, the I3C slave 13 stops driving the data signal line 14-1. On the other hand, in step S181, if it is determined that the current transmission remaining amount is 0 bytes, the process proceeds to step S196. That is, in this case, since the CCI protocol is violated, in step S196 , the I3C slave 13 sends a NACK to the I3C master 12 . After the process of step S195 or S196, the DDR read transfer process ends, and the process proceeds to FIG. 18 to step S179. FIG. 20 is a flowchart illustrating the DDR write transfer process performed in step S176 of FIG. 18 . In step S201 , the I3C slave 13 performs a determination based on the preamble of the signal transmitted from the I3C master 12 . In step S201, if the I3C slave 13 determines that data is transmitted from the I3C master 12 based on the preamble, the process proceeds to step S202. In step S202 , in the I3C slave 13 , the data receiving unit 32 receives the data and the parity code transmitted from the I3C master 12 . In step S203, the I3C slave 13 uses the parity code received in step S202 to determine whether there is an error in the data received in step S202. Then, if the I3C slave 13 determines that no parity error has occurred, the process proceeds to step S204. In step S204 , the CCI layer processing unit 62 obtains the data received by the data receiving unit 32 in step S202 , that is, the index sent by the I3C master 12 . In step S205 , the I3C slave 13 determines, based on the preamble of the signal transmitted from the I3C master 12 , whether the data is transmitted, the CRC character is transmitted, or an error has occurred. In step S205, if the I3C slave 13 determines that the data is transmitted, the process proceeds to step S206. In step S206 , in the I3C slave 13 , the data receiving unit 32 receives the data and the parity code transmitted from the I3C master 12 . In step S207, the I3C slave 13 uses the parity code received in step S206 to determine whether there is an error in the data received in step S206. Then, if the I3C slave 13 determines that no parity error has occurred, the process proceeds to step S208. In step S208, the CCI layer processing unit 62 obtains the data received by the data receiving unit 32 in step S206, that is, the transmission length information sent by the I3C master 12, as the transmission remaining amount. In step S209 , the I3C slave 13 determines, based on the preamble of the signal transmitted from the I3C master 12 , whether the data is transmitted, the CRC character is transmitted, or an error has occurred. In step S209, if the I3C slave 13 determines that the data is transmitted, the process proceeds to step S210 and the writing process is performed (FIG. 21). On the other hand, in step S209, if the I3C slave 13 determines that the CRC character is transmitted, the process proceeds to step S211, and the data receiving unit 32 receives the CRC character. In step S212, the I3C slave 13 determines whether an error occurs in the CRC character received by the data receiving unit 32 in step S211. In step S212, if it is determined that there is no error in the CRC character, the process proceeds to step S213, and the I3C slave 13 determines that the read is random. On the other hand, in step S205, if the I3C slave 13 determines that the CRC character is transmitted, the process proceeds to step S214, and the data receiving unit 32 receives the CRC character. In step S215, the I3C slave 13 determines whether an error occurs in the CRC character received by the data receiving unit 32 in step S214. In step S215, if the I3C slave 13 determines that no error has occurred in the CRC character, the process proceeds to step S216. That is, in this case, since the CCI protocol is violated, the CCI layer processing unit 62 sets the transmission remaining amount to 0 in step S216. On the other hand, in step S201, step S205, or step S209, if a frame error is detected based on the preamble, the process proceeds to step S217. Similarly, in steps S203 and S207, if it is determined that a parity error has occurred, the process proceeds to step S217. Furthermore, in step S212 or S215, if it is determined that a CRC error has occurred, the process proceeds to step S217. In step S217, the I3C slave 13 notifies the CCI layer processing unit 62 of the error, and in step S218, the CCI layer processing unit 62 sets the transmission remaining amount to 0. And, after the processing of step S210, step S213, step S216, or step S218, the DDR write transfer processing ends, and the processing proceeds to step S179 in FIG. 18 . FIG. 21 is a flowchart illustrating the writing process performed in step S210 of FIG. 20 . In step S221 , in the I3C slave 13 , the data receiving unit 32 receives the data and the parity code transmitted from the I3C master 12 . In step S222, the I3C slave 13 uses the parity code received in step S221 to determine whether there is an error in the data received in step S221. Furthermore, if the I3C slave 13 determines that no parity error has occurred, the process proceeds to step S223, and the CCI layer processing unit 62 determines that the write transfer is started because the data can be received normally. In step S224, the CCI layer processing unit 62 determines whether the transmission remaining amount is 2 bytes or more, 1 byte, and 0 bytes. In step S224, if it is determined that the transmission remaining amount is more than 2 bytes, the process proceeds to step S225, and the CCI layer processing unit 62 obtains the data of 2 bytes received by the I3C slave 13 as the data to be written temporarily. data in the storage. Next, in step S226, the CCI layer processing unit 62 performs the register writing process of the 2-byte data, and in step S227, moves the index forward by 2 bytes, and transfers the remaining amount of transmission backward. Push 2-byte update. On the other hand, in step S224, if it is determined that the transmission remaining amount is 1 byte, the process proceeds to step S228. In step S228, in the CCI layer processing unit 62, the invalid data processing unit 74 discards 1 byte of dummy data in the 2-byte data received by the I3C slave 13, and obtains the remaining 1 byte Bytes are the data to be written to the register. In addition, in step S229, the CCI layer processing unit 62 performs the register writing process of the 1-byte data, and in step S230, moves the index forward by 1 byte and forwards the transmission remaining amount. Push 1 byte update. On the other hand, in step S224, if it is determined that the transmission remaining amount is 0 bytes, the process proceeds to step S231. That is, in this case, since the CCI protocol is violated, in step S231, the CCI layer processing unit 62 discards all 2 bytes of the data received by the I3C slave 13. After the process of step S227, step S230, or step S231, the process proceeds to step S232. In step S232 , the I3C slave 13 determines, based on the preamble of the signal transmitted from the I3C master 12 , whether the data is transmitted, the CRC character is transmitted, or an error has occurred. In step S232, if the I3C slave 13 determines that the data is transmitted, the process returns to step S221, and the same process is repeated subsequently. On the other hand, in step S232, if the I3C slave 13 determines that the CRC character is transmitted, the process proceeds to step S233, and the data receiving unit 32 receives the CRC character. In step S234, the I3C slave 13 determines whether an error occurs in the CRC character received by the data receiving unit 32 in step S233. In step S234, if it is determined that no error has occurred in the CRC character, the process proceeds to step S235. That is, in this case, since the CRC character can be normally received, the CCI layer processing unit 62 determines in step S235 that the write transfer is terminated, and in step S236 sets the transfer remaining amount to 0. On the other hand, if it is determined that a parity error has occurred in step S222, that a frame error has occurred based on the preamble in step S232, or that a CRC error has occurred in step S234, the process proceeds to step S237. In step S237, the I3C slave 13 notifies the CCI layer processing unit 62 of the error, and in step S238, the CCI layer processing unit 62 sets the transmission remaining amount to 0. Next, after the process of step S236 or S238, the writing process ends, and the process proceeds to step S179 in FIG. 18 . As described with reference to FIGS. 18 to 21 , the controlled device 61 can perform the register R/W transfer process in the DDR mode. FIG. 22 is a flowchart illustrating the data transfer process performed by the system controller 41 in the controlled device 61 corresponding to the execution of the register R/W transfer process in the TSL/TSP mode described above with reference to FIG. 14 . For example, the I3C slave 13 starts processing when it receives the HDR start command (ENTHDR1/2) transmitted from the I3C master 12 to communicate in the DDR mode. Next, in step S241 , in the I3C slave 13 , the instruction interpretation unit 33 receives the instruction and the parity code transmitted from the I3C master 12 . In addition, in the TSL/TSP mode, unlike the DDR mode, no preamble transmission is performed. In step S242, the command interpretation unit 33 determines whether an error occurs in the command received in step S172. In addition, in TSL/TSP mode, the error detection conditions are different from those in DDR mode. For example, when a parity error is detected, or when more than 2 × 2 symbols are received outside the limit of data characters, it is determined as data. An error occurred. In step S242, if the command interpretation unit 33 determines that no error has occurred, the process proceeds to step S243. In step S243, the command interpretation unit 33 determines whether the command code of the command received in step S242 is a read command or a write command. In step S243, if the command interpretation unit 33 determines that the command code is a read command, the process proceeds to step S244, and TSL/TSP read transfer processing is performed as described later with reference to FIG. 23 . On the other hand, in step S243, if the command decoding unit 33 determines that the command code is a write command, the process proceeds to step S245, and TSL/TSP write transfer processing is performed as described later with reference to FIG. 24 . After the TSL/TSP read transfer processing of step S244 or the TSL/TSP write transfer processing of step S245, the processing proceeds to step S248. On the other hand, in step S242, if the command interpretation unit 33 determines that an error has occurred, the process proceeds to step S246. In S248 of step S246, the same processing as steps S177 to S179 of FIG. 18 is performed. FIG. 23 is a flowchart illustrating the TSL/TSP read transfer process performed in step S244 of FIG. 22 . In steps S251 to S253, the same processes as those of steps S181 to S183 in FIG. 19 are performed. Next, after the processing of step S252 or S253, in step S254, the I3C slave 13 starts to drive the data signal line 14-1 and the clock signal line 14-2. Subsequently, in steps S255 to S262, the same processing as in steps S185 to S192 of FIG. 19 is performed, and the processing is repeated until it is determined in step S255 that the current transmission remaining amount of the data sent according to the read command is 0 bytes until. Also, in the TSL/TSP mode, unlike the DDR mode, the master stop is not performed. In step S255, if it is determined that the transmission remaining amount is 0 bytes, the process proceeds to step S263, and the I3C slave 13 transmits a signal indicating the end of transmission (symbol 2×3 times). In addition, in the TSL/TSP mode, unlike the DDR mode, no CRC characters are sent. On the other hand, in step S251, if it is determined that the current transmission remaining amount is 0 bytes, the process proceeds to step S264. That is, in this case, since the CCI protocol is violated, the I3C controller 13 starts to drive the data signal line 14-1 and the clock signal line 14-2 in step S264, and in step S265, sends NACK (symbol 2 ×3 times). In addition, in TSL/TSP mode, the form of NACK is different from that in DDR mode. After the process of step S263 or S265, the process proceeds to step S266. In step S266, after the I3C slave 13 stops driving the data signal line 14-1 and the clock signal line 14-2, the TSL/TSP read transmission process ends, and the process proceeds to step S248 in FIG. 22 . In addition, in TSL/TSP mode, the turnaround order is different from that in DDR mode. FIG. 24 is a flowchart illustrating the TSL/TSP write transfer process performed in step S245 of FIG. 22 . In step S271 , in the I3C slave 13 , the data receiving unit 32 receives the data and the parity code transmitted from the I3C master 12 . In addition, in the TSL/TSP mode, unlike the DDR mode, no preamble transmission is performed. In step S272, the I3C slave 13 determines whether there is an error in the data received in step S271. In addition, in TSL/TSP mode, the error detection conditions are different from those in DDR mode. For example, if a parity error is detected, or if more than 2×2 symbols are received outside the data character limit, it is determined that a data error has occurred. In step S272, if it is determined that there is no error in the data, the process proceeds to step S273, and the CCI layer processing unit 62 obtains the data received by the data receiving unit 32 in step S271, that is, the index sent by the I3C master 12. In step S274 , the I3C slave 13 determines whether the data transmitted from the I3C master 12 is received. In step S274 , if it is determined that the data transmitted from the I3C master 12 is received, the process proceeds to step S275 , and the data receiving unit 32 receives the data and the parity code from the I3C master 12 . In step S276, as in step S272, the I3C slave 13 determines whether or not an error has occurred in the data received in step S275, and if it is determined that no error has occurred, the process proceeds to step S277. In step S277, the CCI layer processing unit 62 obtains the data received by the data receiving unit 32 in step S275, that is, the transmission length information sent by the I3C master 12, as the transmission remaining amount. In step 278 , the I3C slave 13 determines whether the data transmitted from the I3C master 12 is received. In addition, in the TSL/TSP mode, unlike the DDR mode, no preamble transmission is performed. In step S278, if the I3C slave 13 determines that the data has been received, the process proceeds to step S279 and the writing process is performed (FIG. 25). On the other hand, in step S278, if it is determined that no data has been received, the process proceeds to step S280, and the I3C slave 13 determines that it is random reading. On the other hand, in step S274, if it is determined that the data transmitted from the I3C master 12 has not been received, the process proceeds to step S281. That is, in this case, since the CCI protocol is violated, the CCI layer processing unit 62 sets the transmission remaining amount to 0 in step S281. In addition, in the TSL/TSP mode, unlike the DDR mode, no CRC characters are sent. On the other hand, in step S272 or S276, if it is determined that the received data has an error, the process proceeds to step S282. In step S282, the I3C slave 13 notifies the CCI layer processing unit 62 of an error, and in step S283, if the CCI layer processing unit 62 sets the transmission remaining amount to 0. And, after the process of step S279, step S280, step S281, or step S283, the TSL/TSP write transfer process ends, and the process proceeds to step S248 in FIG. 22 . FIG. 25 is a flowchart illustrating the writing process performed in step S279 of FIG. 24 . In step S291 , in the I3C slave 13 , the data receiving unit 32 receives the data and the parity code transmitted from the I3C master 12 . In step S292, the I3C slave 13 determines whether there is an error in the data received in step S291. In the TSL/TSP mode, the error detection conditions are different from those in the DDR mode. For example, if a parity error is detected, or if more than 2×2 symbols are received outside the data character limit, it is determined that an error has occurred. In step S292, if the I3C slave 13 determines that there is no error in the data, the process proceeds to step S293, and since the data can be received normally, the CCI layer processing unit 62 determines to start the write transfer. In steps S294 to S301 , after performing the same processing as steps S224 to S231 in FIG. 21 , in step S302 , the I3C slave 13 determines whether the data transmitted from the I3C master 12 is received. In addition, in the TSL/TSP mode, unlike the DDR mode, no preamble transmission is performed. In step S302, if the I3C slave 13 determines that the data has been received, the process returns to step S291, and the same process is repeated subsequently. On the other hand, in step S302, if the I3C slave 13 determines that no data has been received, the process returns to step S303. In addition, the CCI layer processing unit 62 determines that the write transfer is completed in step S303 because no data is transmitted, and sets the transfer remaining amount to 0 in step S304. On the other hand, in step S292, if the I3C slave 13 determines that there is no error in the data, the process proceeds to step S305. In step S305, the I3C slave 13 notifies the CCI layer processing unit 62 of the error, and in step S306, the CCI layer processing unit 62 sets the transmission remaining amount to 0. Next, after the process of step S304 or S306, the writing process ends, and the process proceeds to step S248 of FIG. 22 . As described with reference to FIGS. 22 to 25 , the controlled device 61 can perform the register R/W transfer processing in TSL/TSP mode. <Error Countermeasures of the I3C Slave and CCI Layer Processing Unit> Referring to FIG. 26 , the error countermeasures of the I3C controller and the CCI layer processing unit will be described. FIG. 26 shows an example of processing when an error occurs when data is continuously read out in the read transfer processing in the TSL/TSP mode. For example, in the HDR mode (TSP/TSL/DDR), it is stipulated that when the I3C slave 13 detects any error, before the I3C slave 13 receives the HDR end command (HDR_Exit) or the HDR restart (HDR_Restart), All communications are ignored and resumed when either is detected. Here, as shown in FIG. 26, for example, from the reception of the write command for address setting (TSL/TSP_Cmd(W)) to the time immediately before the reception of the read command (TSL/TSP_Cmd(R)). The processing when an error occurs before the HDR restart command will be explained. That is, if an error occurs at this timing, the I3C slave 13 stops the processing from the detection of the error until the HDR restart command is received (ignored interval). Therefore, in this case, the index (Index) and transmission length information (Length) are not notified to the CCI layer processing unit 62 . And, after that, the I3C slave 13 resumes communication by receiving the HDR restart command, and transmits the read command sent following the HDR restart command to the CCI layer processing unit 62 . However, since the CCI layer processing unit 62 does not grasp the index and transfer length information, there is a state in which it cannot know where to read the data. Therefore, when an error is detected, the I3C slave 13 of the present embodiment is defined to notify the CCI layer processing unit 62 of the detection of the error (eg, step S217 in FIG. 20 or step S282 in FIG. 24 , etc.). Furthermore, it is prescribed that the CCI layer processing unit 62 sets the transmission remaining amount to 0 according to the notification of the error (for example, step S218 in FIG. 20 or step S283 in FIG. 24 , etc.). Thereby, even if the CCI layer processing unit 62 receives a read command when the index and transmission length information cannot be recognized due to an error, for example, it still determines that the transmission remaining amount is 0, thus violating the CCI protocol. Therefore, the CCI layer processing unit 62 can ignore everything after the I3C slave 13 detects an error until it receives the combination of the HDR restart command and the write command (HDR_Restart+TSL/TSP_Cmd(W)), or until it receives the HDR end command. communication. In this way, the CCI layer processing unit 62 can avoid a state where the CCI layer processing unit 62 does not know where to read the data, and performs the same operation as the I3C slave 13 stipulates. Therefore, it is possible to avoid a deviation in response to the error of the I3C slave 13 and the CCI layer processing unit 62, and to execute the read process surely. Therefore, the controlled device 61 can avoid writing possibly erroneous data into the temporary register, or reading possibly erroneous data from the temporary register, and will not cause unstable communication due to such errors, which can be more reliable. to communicate. In addition, each process described with reference to the above-mentioned flowcharts does not need to be processed in time series in accordance with the order described in the flowcharts, and may include processes performed in parallel or individually (for example, parallel processing or target-based processing). . In addition, the program may be processed by one CPU, or may be processed in a distributed manner by a plurality of CPUs. In addition, one of the above-mentioned series of processing (communication method) can be executed by hardware or software. In the case of executing a series of processing by software, a program constituting the software is installed from a program recording medium on which the program is recorded into a computer incorporated in dedicated hardware, or various functions can be performed by installing various programs, such as General-purpose personal computers, etc. FIG. 27 is a block diagram showing an example of the hardware configuration of a computer that executes one of the above-mentioned series of processing by a program. In a computer, a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory: random access memory) 103, and an EEPROM (Electronically Erasable and Programmable Read Only Memory): The electronically erasable programmable read-only memory) 104 are connected to each other by a bus bar 105. An input/output interface 106 is further connected to the bus bar 105, and the input/output interface 106 is connected to the outside. In the computer configured as above, for example, the CPU 101 downloads the program stored in the ROM 102 and the EEPROM 104 to the RAM 103 via the bus 105 and executes it, thereby performing one of the above-mentioned series of processing. In addition, the program executed by the computer (CPU 101 ) is not only written in the ROM 102 in advance, but also can be externally installed in the EEPROM 104 through the input/output interface 106 or updated. <Example of Combination of Configurations> In addition, the present technology may take the following configurations. (1) A communication device, which communicates via a bus, by means of a first communication device having communication leadership, and at least one or more second communication devices that communicate under the control of the first communication device. communication, and the first communication device includes: an acquisition unit that acquires, from the second communication device, a maximum transmission length representing a maximum transmission length that the second communication device can transmit in one data transmission; a transmission and reception control unit, When performing data transmission with the above-mentioned second communication device, it controls the transmission and reception of data in such a way that the data length of the data transmitted in one data transmission is equal to or less than the above-mentioned maximum transmission length; Send transfer length information indicating the data length of the data to be transferred. (2) The communication device according to (1) above, wherein, when a request is made to transmit data with a data length of a length greater than or equal to the maximum transmission length, the transmission/reception control unit divides the data requested to be transmitted into a data length less than or equal to the maximum transmission length. For data transmission, the transmission unit transmits the transmission length information indicating the data length of the data divided by the transmission/reception control unit. (3) The communication device according to (1) or (2) above, wherein, when performing a write transmission to transmit data to be written to the second communication device, the acquisition unit acquires the write transmission of the second communication device The above-mentioned maximum transmission length is the maximum write-in length. In the case of requesting to transmit data with a data length longer than the above-mentioned maximum write-in length, the above-mentioned transmission/reception control unit divides the requested data into the above-mentioned maximum write-in length. The data is transmitted by dividing the data into a plurality of times below the length, and each time the transmitting section transmits the data, the transmitting section transmits the transmission length information indicating the data length of the data divided by the transmitting and receiving control section. (4) The communication device according to any one of (1) to (3) above, wherein when performing read transmission of data read out from the second communication device, the obtaining unit obtains the data of the second communication device. The above-mentioned maximum transmission length in the read transmission is the maximum read length. In the case of requesting to transmit data with a data length longer than the above-mentioned maximum read length, the above-mentioned transmission/reception control unit divides the requested data into the above-mentioned data. The data transmission is performed by dividing the data into a plurality of times below the maximum read length, and the transmitting unit transmits the transmission length information indicating the data length of the data divided by the sending and receiving control unit each time the data is transmitted. (5) The communication device according to any one of (1) to (3) above, wherein, when performing read transmission of data read out from the second communication device, the obtaining unit obtains the data of the second communication device. The above-mentioned maximum transmission length in the read transmission is the maximum read length. In the case of requesting to transmit data with a data length longer than the above-mentioned maximum read length, the above-mentioned transmission/reception control unit divides the requested data into the above-mentioned data. The data transmission is performed by dividing the data into a plurality of times to transmit the data below the maximum read length, and the above-mentioned transmission unit transmits the above-mentioned transmission length information indicating the data length of the entire data requested to be transmitted only once. (6) The communication device according to any one of (1) to (5) above, wherein the second communication device includes: an error notification unit that detects at least the occurrence of an error in which the transmission length information cannot be normally received When the error occurs, the processing unit in the upper layer is notified of the occurrence of the error; in the upper layer, the combination of the command to restart the communication and the command to write the above data is received, or the end of the communication is received. All communication is ignored until the command is given. (7) A communication method that communicates via a bus, and through a first communication device having communication mastery, and at least one or more second communication devices that communicate under the control of the first communication device Communication is performed, and the communication process includes the following steps: the first communication device obtains, from the second communication device, a maximum transmission length representing the maximum transmission length that the second communication device can transmit in one data transmission, and When the above-mentioned second communication device performs data transmission, the data transmission and reception shall be controlled in such a way that the data length of the data transmitted in one data transmission is less than the above-mentioned maximum transmission length, and the data indicated to be transmitted shall be sent before the data transmission. The transfer length information of the data length. (8) A program for causing a computer to execute a communication process, which is a computer executor of a communication device that communicates via a bus, and is executed by a first communication device having communication mastery and control according to the above-mentioned first communication device At least one or more second communication devices in communication communicate, and the communication process includes the following steps: The first communication device obtains from the second communication device, indicating that the second communication device can perform data transmission in one time. The maximum transmission length of the transmission is the maximum transmission length. When data transmission is performed with the above-mentioned second communication device, the data transmission and reception are controlled in such a way that the data length of the data transmitted in one data transmission is less than the above-mentioned maximum transmission length, and in Before data transmission for the above data, transmission length information indicating the data length of the data to be transmitted is sent. (9) A communication system that communicates via a bus by a first communication device having communication leadership and at least one or more second communication devices communicating under the control of the first communication device, Furthermore, the first communication device includes: an acquisition unit that acquires, from the second communication device, a maximum transmission length representing a maximum transmission length that can be transmitted by the second communication device in one data transmission; When data transmission is performed with the above-mentioned second communication device, the data transmission and reception are controlled in such a way that the data length of the data transmitted in one data transmission is equal to or less than the above-mentioned maximum transmission length; , which sends transfer length information indicating the data length of the data to be transferred. In addition, this embodiment is not limited to the above-mentioned embodiment, Various changes are possible in the range which does not deviate from the summary of this invention.

11‧‧‧匯流排IF12‧‧‧I3C主控器13‧‧‧I3C受控器13-1‧‧‧I3C受控器13-2‧‧‧I3C受控器13-3‧‧‧I3C受控器14-1‧‧‧資料信號線14-2‧‧‧時脈信號線21‧‧‧資料發送部22‧‧‧資料接收部23‧‧‧指令發送部24‧‧‧模式控制部25‧‧‧收發控制部31‧‧‧資料發送部31-1‧‧‧資料發送部31-2‧‧‧資料發送部31-3‧‧‧資料發送部32‧‧‧資料接收部32-1‧‧‧資料接收部32-2‧‧‧資料接收部32-3‧‧‧資料接收部33‧‧‧指令解譯部33-1‧‧‧指令解譯部33-2‧‧‧指令解譯部33-3‧‧‧指令解譯部34‧‧‧模式控制部34-1‧‧‧模式控制部34-2‧‧‧模式控制部34-3‧‧‧模式控制部35‧‧‧接收控制部35-1‧‧‧接收控制部35-2‧‧‧接收控制部35-3‧‧‧接收控制部41‧‧‧系統控制器42‧‧‧CCI層處理部43‧‧‧CPU44‧‧‧內部匯流排51‧‧‧暫存器位址管理部52‧‧‧傳輸長度資訊保持部53‧‧‧寫入傳輸結束控制部54‧‧‧無效資料處理部55‧‧‧傳輸長度資訊發送部61‧‧‧被控制器件62‧‧‧CCI層處理部63‧‧‧器件控制部64‧‧‧內部匯流排71‧‧‧暫存器位址管理部72‧‧‧暫存器R/W控制部73‧‧‧讀取傳輸結束控制部74‧‧‧無效資料處理部75‧‧‧傳輸長度資訊保持部101‧‧‧CPU102‧‧‧ROM103‧‧‧RAM104‧‧‧EEPROM105‧‧‧匯流排106‧‧‧輸入輸出介面CRC‧‧‧CRCDDR‧‧‧模式DDR_Cmd(R)‧‧‧指令DDR_Cmd(W)‧‧‧指令ENTHDR‧‧‧指令HDR_Exit‧‧‧指令HDR_Restart‧‧‧指令SCL‧‧‧串列時脈SDA‧‧‧串列資料SDR‧‧‧模式S11～S17‧‧‧步驟S21～S26‧‧‧步驟S31～S37‧‧‧步驟S41～S62‧‧‧步驟S71～S74‧‧‧步驟S81～S97‧‧‧步驟S101～S108‧‧‧步驟S111～S130‧‧‧步驟S141～S143‧‧‧步驟S151～S166‧‧‧步驟S171～S179‧‧‧步驟S181～S196‧‧‧步驟S201～S218‧‧‧步驟S221～S238‧‧‧步驟S241～S248‧‧‧步驟S251～S266‧‧‧步驟S271～S280‧‧‧步驟S291～S306‧‧‧步驟TSL/TSP‧‧‧模式TSL/TSP‧‧‧Cmd(R)指令‧‧‧TSL/TSPCmd(W)‧‧‧指令11‧‧‧Bus IF12‧‧‧I3C master 13‧‧‧I3C slave 13-1‧‧‧I3C slave 13-2‧‧‧I3C slave 13-3‧‧‧I3C slave Controller 14-1‧‧‧Data Signal Line 14-2‧‧‧Clock Signal Line 21‧‧‧Data Transmitter 22‧‧‧Data Receiver 23‧‧‧Command Transmitter 24‧‧‧Mode Control Section 25 ‧‧‧Transmission control part 31‧‧‧Data transmission part 31-1‧‧‧Data transmission part 31-2‧‧‧Data transmission part 31-3‧‧‧Data transmission part 32‧‧‧Data receiving part 32-1 ‧‧‧Data Receiver 32-2‧‧‧Data Receiver 32-3‧‧‧Data Receiver 33‧‧‧Command Interpreter 33-1‧‧‧Command Interpreter 33-2‧‧‧Command Interpreter Interpreter Section 33-3‧‧‧Command Interpreting Section 34‧‧‧Mode Control Section 34-1‧‧‧Mode Control Section 34-2‧‧‧Mode Control Section 34-3‧‧‧Mode Control Section 35‧‧‧ Receive control unit 35-1‧‧‧Receive control unit 35-2‧‧‧Receive control unit 35-3‧‧‧Receive control unit 41‧‧‧System controller 42‧‧‧CCI layer processing unit 43‧‧‧CPU44 ‧‧‧Internal bus 51‧‧‧Register address management part 52‧‧‧Transfer length information holding part 53‧‧‧Write transfer completion control part 54‧‧‧Invalid data processing part 55‧‧‧Transfer length Information Transmission Section 61‧‧‧Controlled Device 62‧‧‧CCI Layer Processing Section 63‧‧‧Device Control Section 64‧‧‧Internal Bus 71‧‧‧Register Address Management Section 72‧‧‧Register R/W control section 73‧‧‧read transfer completion control section 74‧‧‧invalid data processing section 75‧‧‧transfer length information holding section 101‧‧‧CPU102‧‧‧ROM103‧‧‧RAM104‧‧‧EEPROM105‧ ‧‧Bus 106‧‧‧I/O interface CRC‧‧‧CRCDDR‧‧‧Mode DDR_Cmd(R)‧‧‧Command DDR_Cmd(W)‧‧‧Command ENTHDR‧‧‧Command HDR_Exit‧‧‧Command HDR_Restart‧‧‧ Command SCL‧‧‧Serial Clock SDA‧‧‧Serial Data SDR‧‧‧Mode S11～S17‧‧‧Step S21～S26‧‧‧Step S31～S37‧‧‧Step S41～S62‧‧‧Step S71 ～S74‧‧‧Step S81～S97‧‧‧Step S101～S108‧‧‧Step S111～S130‧‧‧Step S141～S143‧‧‧Step S151～S166‧‧‧Step S171～S179‧‧‧Step S181～ S196‧‧‧Step S201～S218‧‧‧Step S221～S238‧‧‧Step S241～S248‧‧‧Step S251～S266‧‧‧Step S271～S280‧‧‧Step S291～S30 6‧‧‧Step TSL/TSP‧‧‧Mode TSL/TSP‧‧‧Cmd(R) command‧‧‧TSL/TSPCmd(W)‧‧‧command

圖1係顯示應用本技術之匯流排IF之一實施形態之構成例的方塊圖。 圖2係顯示安裝有I3C主控器之系統控制器之構成例之方塊圖。 圖3係顯示安裝有I3C受控器之被控制器件之構成例的方塊圖。 圖4係顯示DDR模式之格式之圖。 圖5係顯示TSL/TSP模式之格式之圖。 圖6係說明於I3C主控器中進行之處理之流程圖。 圖7係顯示DDR模式中分割資料並傳輸之讀取傳輸處理之格式的圖。 圖8係顯示TSL/TSP模式中分割資料並傳輸之讀取傳輸處理之格式的圖。 圖9係說明系統控制器中執行之資料傳輸處理之流程圖。 圖10係說明DDR模式之暫存器R/W傳輸處理之流程圖。 圖11係說明DDR讀取傳輸處理之流程圖。 圖12係說明DDR模式中之HDR寫入傳輸處理之流程圖。 圖13係說明DDR寫入傳輸處理之流程圖。 圖14係說明TSL/TSP模式之暫存器R/W傳輸處理之流程圖。 圖15係說明TSL/TSP讀取傳輸處理之流程圖。 圖16係說明TSL/TSP讀取之HDR寫入傳輸處理之流程圖。 圖17係對TSL/TSP寫入傳輸處理進行說明之流程圖。 圖18係說明DDR模式時於被控制器件中執行之資料傳輸處理之流程圖。 圖19係說明DDR讀取傳輸處理之流程圖。 圖20係說明DDR寫入傳輸處理之流程圖。 圖21係說明寫入處理之流程圖。 圖22係說明TSL/TSP模式時於被控制器件中執行之資料傳輸處理之流程圖。 圖23係說明TSL/TSP讀取傳輸處理之流程圖。 圖24係說明TSL/TSP寫入傳輸處理之流程圖。 圖25係說明寫入處理之流程圖。 圖26係對I3C受控器及CCI層處理部之錯誤對策進行說明之圖。 圖27係顯示應用本技術之電腦之一實施形態之構成例的方塊圖。FIG. 1 is a block diagram showing a configuration example of an embodiment of a bus bar IF to which the present technology is applied. FIG. 2 is a block diagram showing a configuration example of a system controller with an I3C master mounted thereon. FIG. 3 is a block diagram showing a configuration example of a controlled device to which an I3C slave is mounted. FIG. 4 is a diagram showing the format of the DDR mode. FIG. 5 is a diagram showing the format of the TSL/TSP mode. Figure 6 is a flow chart illustrating the processing performed in the I3C master. FIG. 7 is a diagram showing the format of the read transfer process in which data is divided and transferred in the DDR mode. FIG. 8 is a diagram showing the format of the read transmission process of dividing data and transmitting in the TSL/TSP mode. FIG. 9 is a flowchart illustrating the data transfer process performed in the system controller. FIG. 10 is a flowchart illustrating the register R/W transfer process in DDR mode. FIG. 11 is a flowchart illustrating the DDR read transfer process. 12 is a flowchart illustrating the HDR write transfer process in DDR mode. FIG. 13 is a flowchart illustrating the DDR write transfer process. FIG. 14 is a flowchart illustrating the register R/W transfer process in TSL/TSP mode. FIG. 15 is a flowchart illustrating the TSL/TSP read transfer process. FIG. 16 is a flowchart illustrating the HDR write transfer process for TSL/TSP read. FIG. 17 is a flowchart illustrating the TSL/TSP write transfer process. FIG. 18 is a flowchart illustrating the data transfer process performed in the controlled device in DDR mode. FIG. 19 is a flowchart illustrating the DDR read transfer process. FIG. 20 is a flowchart illustrating the DDR write transfer process. FIG. 21 is a flowchart illustrating the write process. FIG. 22 is a flowchart illustrating the data transfer process performed in the controlled device in TSL/TSP mode. FIG. 23 is a flowchart illustrating the TSL/TSP read transfer process. FIG. 24 is a flowchart illustrating the TSL/TSP write transfer process. FIG. 25 is a flowchart illustrating the write process. FIG. 26 is a diagram for explaining error countermeasures of the I3C slave and the CCI layer processing unit. FIG. 27 is a block diagram showing a configuration example of an embodiment of a computer to which the present technology is applied.

S11~S17‧‧‧步驟 Steps S11~S17‧‧‧

Claims (8)

一種通信裝置，其係經由匯流排進行通信者，且藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，上述第1通信裝置具備：取得部，其自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度；收發控制部，其於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發；及發送部，其於對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊；且於進行傳輸自上述第2通信裝置讀出之資料之讀取傳輸時，上述取得部取得上述第2通信裝置之讀取傳輸中之上述最大傳輸長度即最大讀取長度，於經請求傳輸上述最大讀取長度以上之長度之資料長度的資料之情形時，上述收發控制部以將該請求傳輸之資料分割成上述最大讀取長度以下而分成複數次發送資料之方式進行資料傳輸，上述發送部僅發送1次表示請求傳輸之資料整體之資料長度之上述傳輸長度資訊。 A communication device that communicates via a bus, and communicates via a first communication device having communication mastership and at least one second communication device that communicates under the control of the first communication device, The first communication device includes: an acquisition unit that acquires, from the second communication device, a maximum transmission length indicating a maximum transmission length that can be transmitted by the second communication device in one data transmission; When the above-mentioned second communication device performs data transmission, the data transmission and reception are controlled in such a way that the data length of the data transmitted in one data transmission is equal to or less than the above-mentioned maximum transmission length; The transmission length information indicating the data length of the data to be transmitted is sent; and when the read transmission of the data read from the second communication device is performed, the acquisition unit acquires the above-mentioned data in the read transmission of the second communication device. The maximum transmission length is the maximum read length. In the case of requesting to transmit data with a data length longer than the above-mentioned maximum read length, the above-mentioned transmission/reception control unit divides the requested data into sections below the above-mentioned maximum read length. The data transmission is performed by dividing the data into a plurality of times, and the above-mentioned transmitting section only transmits the above-mentioned transmission length information indicating the data length of the entire data requested to be transmitted once. 如請求項1之通信裝置，其中 於經請求傳輸上述最大傳輸長度以上之長度的資料長度之資料之情形時，上述收發控制部將該請求傳輸之資料分割成上述最大傳輸長度以下而進行資料傳輸，上述發送部發送表示經上述收發控制部分割之資料之資料長度之上述傳輸長度資訊。 The communication device of claim 1, wherein In the case of requesting to transmit data with a data length longer than the above-mentioned maximum transmission length, the above-mentioned transmission/reception control section divides the requested data into sections below the above-mentioned maximum transmission length for data transmission, and the above-mentioned transmission section indicates that the above-mentioned transmission/reception has been carried out. The above transmission length information of the data length of the data divided by the control part. 如請求項1之通信裝置，其中於進行傳輸要寫入至上述第2通信裝置之資料之寫入傳輸時，上述取得部取得上述第2通信裝置之寫入傳輸中之上述最大傳輸長度即最大寫入長度，於經請求傳輸上述最大寫入長度以上之長度之資料長度的資料之情形時，上述收發控制部以將該請求傳輸之資料分割成上述最大寫入長度以下而分成複數次發送資料之方式進行資料傳輸，上述發送部於每次傳輸上述資料時，發送表示經上述收發控制部分割之資料之資料長度的上述傳輸長度資訊。 The communication device according to claim 1, wherein when performing the write transmission for transmitting the data to be written to the second communication device, the acquisition unit obtains the maximum transmission length in the write transmission of the second communication device, that is, the maximum transmission length Write length, when a request is made to transmit data with a data length longer than the maximum write length, the transmission/reception control unit divides the requested data into sections below the maximum write length and sends the data in multiple times. The data transmission is carried out in the manner in which the transmission unit transmits the transmission length information indicating the data length of the data divided by the transmission and reception control unit each time the transmission unit transmits the data. 如請求項1之通信裝置，其中於進行傳輸自上述第2通信裝置讀出之資料之讀取傳輸時，上述取得部取得上述第2通信裝置之讀取傳輸中之上述最大傳輸長度即最大讀取長度，於經請求傳輸上述最大讀取長度以上之長度之資料長度之資料之情形時，上述收發控制部以將該請求傳輸之資料分割成上述最大讀取長度以下而分成複數次發送資料之方式進行資料傳輸， 上述發送部於每次傳輸上述資料時，發送表示經上述收發控制部分割之資料之資料長度的上述傳輸長度資訊。 The communication device according to claim 1, wherein when performing read transmission of the data read from the second communication device, the acquisition unit obtains the maximum transmission length in the read transmission of the second communication device, that is, the maximum read transmission length. Take the length, in the case of requesting to transmit data with a data length longer than the above-mentioned maximum read length, the above-mentioned sending and receiving control unit divides the data requested to be transmitted into a number below the above-mentioned maximum read length and divides the data into a plurality of times to send the data. way of data transmission, The transmission unit transmits the transmission length information indicating the data length of the data divided by the transmission/reception control unit each time the data is transmitted. 如請求項1之通信裝置，其中上述第2通信裝置具備：錯誤通知部，其於至少檢測出發生無法正常地接收上述傳輸長度資訊之錯誤之情形時，向在上階層中進行處理之處理部通知該錯誤之發生；於該上階層中，於接收到指示重啟通信之指令與指示寫入上述資料之指令之組合為止，或接收到指示通信結束之指令為止，忽略一切通信。 The communication device of claim 1, wherein the second communication device includes an error notification unit that, when at least detecting that an error that the transmission length information cannot be received normally occurs, reports to a processing unit that performs processing in an upper layer Notify the occurrence of the error; in the upper layer, ignore all communication until a combination of an instruction to restart communication and an instruction to write the above data is received, or an instruction to end communication is received. 一種通信方法，其係經由匯流排進行通信者，且藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，且該通信方法包含以下步驟：上述第1通信裝置自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸所能傳輸之最大傳輸長度的最大傳輸長度，於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發，且於資料傳輸上述資料之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊；且於進行傳輸自上述第2通信裝置讀出之資料之讀取傳輸時，取得上述第2通信裝置之讀取傳輸中之上述最大傳輸長度即最大讀取 長度，於經請求傳輸上述最大讀取長度以上之長度之資料長度的資料之情形時，以將該請求傳輸之資料分割成上述最大讀取長度以下而分成複數次發送資料之方式進行資料傳輸，僅發送1次表示請求傳輸之資料整體之資料長度之上述傳輸長度資訊。 A communication method in which a communication device communicates via a bus, and communicates with a first communication device having communication mastership and at least one or more second communication devices that communicate under the control of the first communication device, And the communication method includes the following steps: the first communication device obtains, from the second communication device, a maximum transmission length representing the maximum transmission length that the second communication device can transmit in one data transmission, and then communicates with the second communication device. When the device performs data transmission, the data transmission and reception shall be controlled in such a way that the data length of the data transmitted in one data transmission is less than the above-mentioned maximum transmission length, and before the above-mentioned data is transmitted, a message indicating the data length of the data to be transmitted shall be sent. Transmission length information; and when the read transmission of the data read from the second communication device is performed, the maximum transmission length in the read transmission of the second communication device is obtained, that is, the maximum read Length, in the case of requesting to transmit data with a data length longer than the above-mentioned maximum read length, the data transmission is performed by dividing the requested data into below the above-mentioned maximum read length and dividing the data into a plurality of times to send the data, The above transmission length information indicating the data length of the entire data requested to be transmitted is sent only once. 一種使電腦執行通信處理之程式，其係使經由匯流排進行通信之通信裝置之電腦執行者，且藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信，且該通信處理包含以下步驟：上述第1通信裝置自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度，於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發，且於對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊；且於進行傳輸自上述第2通信裝置讀出之資料之讀取傳輸時，取得上述第2通信裝置之讀取傳輸中之上述最大傳輸長度即最大讀取長度，於經請求傳輸上述最大讀取長度以上之長度之資料長度的資料之情 形時，以將該請求傳輸之資料分割成上述最大讀取長度以下而分成複數次發送資料之方式進行資料傳輸，僅發送1次表示請求傳輸之資料整體之資料長度之上述傳輸長度資訊。 A program that causes a computer to execute communication processing, which is a computer executor of a communication device that communicates via a bus, and that communicates with a first communication device that has communication mastery and that communicates under the control of the first communication device. At least one or more second communication devices communicate, and the communication process includes the following steps: the first communication device obtains from the second communication device the maximum value that the second communication device can transmit in one data transmission. The maximum transmission length of the transmission length, when data transmission is performed with the above-mentioned second communication device, the data transmission and reception are controlled in such a way that the data length of the data transmitted in one data transmission is less than or equal to the above-mentioned maximum transmission length, and when the above-mentioned data is transmitted and received Before performing data transmission, send transmission length information indicating the data length of the data to be transmitted; and when performing read transmission of the data read from the above-mentioned second communication device, obtain the read transmission of the above-mentioned second communication device. The above-mentioned maximum transmission length is the maximum read length, when the data of the data length longer than the above-mentioned maximum read length is requested to be transmitted In the case of data transmission, the data transmission is performed by dividing the data requested to be transmitted into below the maximum read length and dividing the data into multiple transmissions, and the above transmission length information indicating the data length of the entire data requested to be transmitted is transmitted only once. 一種通信系統，其係經由匯流排，藉由具有通信主導權之第1通信裝置、與根據上述第1通信裝置之控制進行通信之至少1台以上之第2通信裝置進行通信者，且上述第1通信裝置具備：取得部，其自上述第2通信裝置取得表示上述第2通信裝置於1次之資料傳輸中所能傳輸之最大傳輸長度的最大傳輸長度；收發控制部，其於與上述第2通信裝置進行資料傳輸時，以1次之資料傳輸中傳輸之資料的資料長度為上述最大傳輸長度以下之方式控制資料之收發；及發送部，其於對上述資料進行資料傳輸之前，發送表示要傳輸之資料之資料長度的傳輸長度資訊；且於進行傳輸自上述第2通信裝置讀出之資料之讀取傳輸時，上述取得部取得上述第2通信裝置之讀取傳輸中之上述最大傳輸長度即最大讀取長度，於經請求傳輸上述最大讀取長度以上之長度之資料長度的資料之情形時，上述收發控制部以將該請求傳輸之資料分割成上述最大讀取長度以下而分成複數次發送資料之方式進行資料傳輸，上述發送部僅發送1次表示請求傳輸之資料整體之資料長度之上述傳輸長度資訊。 A communication system that communicates via a bus by a first communication device having communication leadership, and at least one or more second communication devices communicating under the control of the first communication device, and wherein the first communication device communicates with the first communication device. 1. The communication device includes: an obtaining unit that obtains, from the second communication device, a maximum transmission length representing the maximum transmission length that the second communication device can transmit in one data transmission; 2 When data transmission is performed by the communication device, the data transmission and reception shall be controlled in such a way that the data length of the data transmitted in one data transmission is equal to or less than the above-mentioned maximum transmission length; The transmission length information of the data length of the data to be transmitted; and when the read transmission of the data read from the above-mentioned second communication device is performed, the above-mentioned acquisition section acquires the above-mentioned maximum transmission among the above-mentioned read transmissions of the above-mentioned second communication device The length is the maximum read length. When a request is made to transmit data with a data length longer than the above-mentioned maximum read length, the above-mentioned transmission/reception control unit divides the requested data into a plurality of numbers below the above-mentioned maximum read length. The data transmission is performed by sending the data at one time, and the above-mentioned sending unit sends the above-mentioned transmission length information, which represents the data length of the entire data requested to be transmitted, only once.
TW107106711A 2017-03-23 2018-03-01 Communication device, communication method, program, and communication system TWI767997B (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017-058247 2017-03-23
JP2017058247 2017-03-23

Publications (2)

Publication Number Publication Date
TW201837728A TW201837728A (en) 2018-10-16
TWI767997B true TWI767997B (en) 2022-06-21

Family

ID=63585444

Family Applications (1)

Application Number Title Priority Date Filing Date
TW107106711A TWI767997B (en) 2017-03-23 2018-03-01 Communication device, communication method, program, and communication system

Country Status (8)

Country Link
US (2) US11010328B2 (en)
EP (1) EP3605348B1 (en)
JP (1) JP7123905B2 (en)
KR (1) KR102515186B1 (en)
CN (1) CN110447020B (en)
SG (1) SG11201906694SA (en)
TW (1) TWI767997B (en)
WO (1) WO2018173796A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI767997B (en) * 2017-03-23 2022-06-21 日商索尼半導體解決方案公司 Communication device, communication method, program, and communication system
US11030142B2 (en) * 2017-06-28 2021-06-08 Intel Corporation Method, apparatus and system for dynamic control of clock signaling on a bus
JP2023089317A (en) * 2020-05-11 2023-06-28 ソニーセミコンダクタソリューションズ株式会社 Communication device and communication system
CN113031486B (en) * 2021-03-18 2022-12-02 深圳市度信科技有限公司 FPGA-based I3C logic controller implementation method, I3C read-write test device and system
CN117435518B (en) * 2023-12-21 2024-03-22 沐曦集成电路(上海)有限公司 Protection method for master-slave read-write data

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030172201A1 (en) * 1998-02-24 2003-09-11 Shinichi Hatae Data communication system, data communication method, and data communication apparatus
TW201116112A (en) * 2009-03-13 2011-05-01 Qualcomm Inc Method and apparatus for sequencing and correlating a positioning reference signal
TW201119480A (en) * 2009-08-12 2011-06-01 Qualcomm Inc Method and apparatus for relay backhaul design in a wireless communication system

Family Cites Families (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS582496B2 (en) * 1978-04-28 1983-01-17 日本電信電話株式会社 Data transfer method
JPH01258525A (en) 1988-04-08 1989-10-16 Hitachi Ltd Data transfer system
JPH0522345A (en) * 1991-07-12 1993-01-29 Hitachi Ltd Optimum management decision system for maximum transfer unit
JPH07160628A (en) * 1993-12-09 1995-06-23 Fujitsu Ltd Parallel transfer system for data
JP4046846B2 (en) * 1998-04-28 2008-02-13 キヤノン株式会社 Data communication system and data communication apparatus
US6711178B1 (en) * 1998-09-08 2004-03-23 Cisco Technology, Inc. Enhanced claw packing protocol
JP3557998B2 (en) * 2000-04-28 2004-08-25 日本電気株式会社 Fragmentation processing device and fragmentation processing apparatus using the same
JP2002290459A (en) * 2001-03-27 2002-10-04 Nec Corp Device for transferring packets and method for the same
US7236501B1 (en) * 2002-03-22 2007-06-26 Juniper Networks, Inc. Systems and methods for handling packet fragmentation
US7382788B2 (en) * 2002-12-24 2008-06-03 Applied Micro Circuit Corporation Method and apparatus for implementing a data frame processing model
US8090801B1 (en) * 2003-10-07 2012-01-03 Oracle America, Inc. Methods and apparatus for performing remote access commands between nodes
US7359405B2 (en) * 2003-10-17 2008-04-15 Asix Electronics Corporation Ltd. Burst transfer mechanism of network packets having MAC frames over USB bus
TW200622810A (en) * 2004-12-29 2006-07-01 Pixart Imaging Inc Method for communicating a usb device with a host
US20080034147A1 (en) * 2006-08-01 2008-02-07 Robert Stubbs Method and system for transferring packets between devices connected to a PCI-Express bus
JP4356765B2 (en) * 2007-04-20 2009-11-04 ソニー株式会社 Information processing apparatus and method, and program
JP5057833B2 (en) * 2007-04-24 2012-10-24 株式会社日立製作所 Transfer system, initiator device, and data transfer method
US7653773B2 (en) * 2007-10-03 2010-01-26 International Business Machines Corporation Dynamically balancing bus bandwidth
US8400942B2 (en) * 2008-11-12 2013-03-19 Emulex Design & Manufacturing Corporation Large frame path MTU discovery and communication for FCoE devices
US20100262726A1 (en) * 2009-01-13 2010-10-14 Tauscher Brian E Method and apparatus for implementing a limited functionality embedded universal serial (USB) host controller on a fully functional downstream USB port
US8352600B2 (en) * 2009-04-21 2013-01-08 Alcatel Lucent System and method for determining a maximum packet data unit (PDU) payload transmission size for communicating in a managed computer network system
US8402180B2 (en) * 2010-03-26 2013-03-19 Atmel Corporation Autonomous multi-packet transfer for universal serial bus
JP5533252B2 (en) * 2010-05-21 2014-06-25 富士通株式会社 Disk array device and disk array device control method
JP2012133643A (en) 2010-12-22 2012-07-12 Sony Corp Information processing apparatus, information processing system, information processing method, and program
CN103124275B (en) * 2011-11-18 2016-01-20 腾讯科技（深圳）有限公司 A kind of method and apparatus obtaining file
JP5932571B2 (en) 2012-08-28 2016-06-08 ルネサスエレクトロニクス株式会社 Transfer control device, transfer control method, and transfer control program
US9182996B2 (en) * 2013-03-12 2015-11-10 Midnight Mosaic Llc Methods and apparatus for USB tunneling through USB printer device class
US8989328B2 (en) * 2013-03-14 2015-03-24 Qualcomm Incorporated Systems and methods for serial communication
US9471521B2 (en) * 2013-05-15 2016-10-18 Stmicroelectronics S.R.L. Communication system for interfacing a plurality of transmission circuits with an interconnection network, and corresponding integrated circuit
JP2015014951A (en) 2013-07-05 2015-01-22 株式会社日立製作所 Data transfer system, computer system, and program
US9785595B2 (en) * 2013-09-09 2017-10-10 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Multi-channel universal serial bus (USB) to subrate channel systems
JP2015153279A (en) 2014-02-18 2015-08-24 三菱電機株式会社 plant control device
JP6340962B2 (en) 2014-07-07 2018-06-13 富士通株式会社 Bus control device, data transfer system, and bus control method
CN104216840B (en) * 2014-09-11 2018-03-23 青岛海信移动通信技术股份有限公司 The method and device that a kind of USB sets and operated to external equipment
JP5921734B2 (en) 2015-02-16 2016-05-24 株式会社日立製作所 Storage system, storage system management method, and computer system
US9755821B2 (en) * 2015-04-02 2017-09-05 Samsung Electronics Co., Ltd. Device including single wire interface and data processing system including the same
EP3268865B1 (en) * 2015-06-26 2021-08-04 Hewlett Packard Enterprise Development LP Self-tune controller
US9960981B2 (en) * 2015-10-08 2018-05-01 Sony Corporation Communication device, communication method, program, and communication system
US9973564B2 (en) * 2015-10-30 2018-05-15 Hewlett Packard Enterprise Development Lp Determining variable chunk size for transfer of a file
US10263830B2 (en) * 2017-01-23 2019-04-16 Wyse Technology L.L.C. Optimized data transfer for redirected UASP devices
TWI767997B (en) * 2017-03-23 2022-06-21 日商索尼半導體解決方案公司 Communication device, communication method, program, and communication system
WO2019016911A1 (en) * 2017-07-20 2019-01-24 株式会社日立製作所 Distributed storage system and distributed storage control method
US10761775B2 (en) * 2018-02-09 2020-09-01 Samsung Electronics Co., Ltd. System and method for NVMe inter command association in SSD storage using a bridge device
US10558367B2 (en) * 2018-03-08 2020-02-11 Western Digital Technologies, Inc. Adaptive transaction layer packet for latency balancing

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030172201A1 (en) * 1998-02-24 2003-09-11 Shinichi Hatae Data communication system, data communication method, and data communication apparatus
TW201116112A (en) * 2009-03-13 2011-05-01 Qualcomm Inc Method and apparatus for sequencing and correlating a positioning reference signal
TW201119480A (en) * 2009-08-12 2011-06-01 Qualcomm Inc Method and apparatus for relay backhaul design in a wireless communication system

Also Published As

Publication number Publication date
KR102515186B1 (en) 2023-03-29
US11010328B2 (en) 2021-05-18
CN110447020B (en) 2024-03-26
EP3605348A1 (en) 2020-02-05
KR20190131016A (en) 2019-11-25
JP7123905B2 (en) 2022-08-23
US11714778B2 (en) 2023-08-01
EP3605348A4 (en) 2020-03-11
TW201837728A (en) 2018-10-16
US20220058156A1 (en) 2022-02-24
SG11201906694SA (en) 2019-08-27
JPWO2018173796A1 (en) 2020-01-23
EP3605348B1 (en) 2023-06-28
CN110447020A (en) 2019-11-12
WO2018173796A1 (en) 2018-09-27
US20200012615A1 (en) 2020-01-09

Similar Documents

Publication Publication Date Title
TWI767997B (en) Communication device, communication method, program, and communication system
TWI610179B (en) Host device and methods for controlling a data transfer speed
CN108170370B (en) Data storage device and data transmission rate control method
JPWO2007125670A1 (en) Signal transmission method, transmission / reception apparatus, and communication system
CN110221842B (en) Data flashing method, device and equipment and computer readable storage medium
CN110945491B (en) Communication device, communication method, program, and communication system
JP6971538B2 (en) Communication equipment, communication methods, programs, and communication systems
JP2006285378A (en) Data transfer device
TWI758517B (en) Communication apparatus, communication method, program, and communication system
US20220066702A1 (en) Electronic device for communicating with host and operating method of the electronic device
JP6903645B2 (en) Communication devices, communication methods, programs, and communication systems
JP6185371B2 (en) Sub-microcomputer program rewriting method
TWI773969B (en) Method of testing slave device of inter-integrated circuit bus
JP5102300B2 (en) Data transmission block transmission method, data transmission block transmission method, and system for transmitting data transmission block
JPWO2010064293A1 (en) Data processing device, system thereof, method thereof, program thereof, recording medium recording the program, data transfer device, method thereof, program thereof, and recording medium recording the program
JP2005228222A (en) Serial data transfer method and device
CN110990313A (en) Method, equipment and storage medium for processing clock stretching of I3C bus
US20180076933A1 (en) Usb device, data transfer system and data transfer method
US20190163407A1 (en) Storage device and storage system
WO2021203227A1 (en) Data transmission method and data transmission apparatus based on inter-integrated circuit protocol
CN109213436B (en) Method and apparatus for reducing errors in data transmission and reception in flash memory interface
CN114817100A (en) Data reading method and device for single board
JP4269911B2 (en) Message exchange management method, network system, its master node, node, program
JP2011015037A (en) Communication system
JP2006319505A (en) Ieee1394 master/slave communication method, communication system, master device, slave device and ic chip