Volatile memory, system-on-chip and electronic device

Abstract

The volatile memory device includes: a memory cell array including a plurality of memory cells for storing data; and a control logic that controls read and write operations of the plurality of memory cells. The control logic is configured to receive a command indicating a self-refresh operation from an external device, perform the self-refresh operation in response to the received command, request the external device to transfer data stored in the plurality of memory cells in response to an execution time of the self-refresh operation having passed a first threshold time, and perform the self-refresh operation. In response to receiving a notification of termination of the self-refresh operation and a read command from the external device, the read command received from the external device is monitored, and in response to not receiving the read command within a second threshold time, the power-off state is entered.

Description

[0001] Cross - reference to related applications

[0002] This application claims priority to Korean Patent Application No. 10 - 2024 - 0003344, filed on January 9, 2024, and Korean Patent Application No. 10 - 2024 - 0026623, filed on February 23, 2024, with the Korean Intellectual Property Office, the entire contents of which are incorporated herein by reference. Technical field

[0003] Various example embodiments relate to one or more of a volatile memory, a system - on - chip (SoC), and an electronic device including the volatile memory and the SoC. Background art

[0004] An electronic device may be installed in a vehicle to control and provide vehicle information. In an automotive system applied to a vehicle (such as a sedan, a truck, a sport utility vehicle, etc.), when the vehicle power is turned off, an ECU (electronic control unit) for controlling the vehicle also loses power. In this case, a volatile memory (such as DRAM (dynamic random access memory)) necessary for or used in the ECU operation performs a self - refresh operation to retain data stored in the volatile memory even when the ECU loses power. Since the current consumption of this self - refresh operation increases as the capacity of the volatile memory increases. Therefore, research is needed or desired to improve this problem. Summary of the invention

[0005] Various example embodiments may provide a volatile storage device, a system - on - chip (SoC), and / or an electronic device capable of reducing operating power.

[0006] According to some example embodiments, a volatile storage device is provided, including: a memory cell array including a plurality of memory cells configured to store data; and control logic configured to control read operations and write operations for the plurality of memory cells. The control logic is configured to receive a command indicating a self - refresh operation from an external device, perform the self - refresh operation in response to the received command, request the external device to transmit data stored in the plurality of memory cells in response to a first threshold time having elapsed since the execution time of the self - refresh operation, monitor a read command received from the external device in response to a notification of termination of the self - refresh operation and a read command received from the external device, and enter a power - off state in response to not receiving a read command within a second threshold time.

[0007] Alternatively or additionally, according to some example embodiments, there is provided a system-on-chip (SoC) including: a first interface configured to communicate with a volatile storage device; a second interface configured to communicate with a non-volatile storage device; and a controller configured to control the first interface and the second interface. The controller is configured to send a command indicating an auto-refresh operation to the volatile storage device, receive a request from the volatile storage device to transfer data stored in the volatile storage device to the non-volatile storage device, determine whether the volatile storage device has performed the auto-refresh operation in response to vehicle power-off, when determining that the volatile storage device has performed the auto-refresh operation in response to vehicle power-off, send a read command to the volatile storage device in response to the request, when determining that the volatile storage device has not performed the auto-refresh operation in response to vehicle power-off, send a command indicating the auto-refresh operation to the volatile storage device in response to the request, receive data corresponding to the read command from the volatile storage device, store the received data in the non-volatile storage device, receive a control signal from a sensor, and power on the volatile storage device in response to the control signal.

[0008] Alternatively or additionally, according to various example embodiments, there is provided an electronic device configured to be included in a vehicle, the electronic device including: a volatile storage device configured to store first data for vehicle operation; a non-volatile storage device configured to store second data for vehicle operation; a sensor configured to output a control signal in response to receiving a detection signal from at least one of a door, a seat, and a seat belt of the vehicle; and a system-on-chip (SoC) configured to power on the volatile storage device in response to a control signal received from the sensor and control the volatile storage device and the non-volatile storage device. The volatile storage device is configured to: receive a command indicating an auto-refresh operation from the SoC, perform the auto-refresh operation in response to the received command, and request the SoC to transfer data stored in the volatile storage device to the non-volatile storage device in response to a first threshold time having elapsed since the execution of the auto-refresh operation. The SoC is configured to: when determining that the volatile storage device has performed the auto-refresh operation in response to vehicle power-off, send a read command to the volatile storage device in response to the request, receive data corresponding to the read command from the volatile storage device, and store the received data in the non-volatile storage device, and when determining that the volatile storage device has not performed the auto-refresh operation in response to vehicle power-off, send a command indicating the auto-refresh operation to the volatile storage device in response to the request.

[0009] The technical objects of various embodiments are not limited to the above technical objects, and other technical objects not mentioned will be clearly understood by those of ordinary skill in the art from the following description. Description of the Drawings

[0010] Figure 1 FIG. is a diagram showing an electronic device according to some example embodiments.

[0011] Figure 2 is for explaining Figure 1 the sensor of.

[0012] Figure 3 is a diagram showing Figure 1 the ECU (electronic control unit) of.

[0013] Figure 4 is a diagram showing Figure 3 the volatile storage device of.

[0014] Figure 5A and Figure 5B is a diagram showing the power-off operation of an electronic device according to some example embodiments.

[0015] Figure 6 and Figure 7 is for explaining Figure 5A and Figure 5B the operation of.

[0016] Figure 8 is a diagram showing the power-on operation of an electronic device according to some example embodiments.

[0017] Figure 9 is a diagram for explaining the volatile storage device according to some example embodiments.

[0018] Figure 10 is a block diagram of an electronic device according to some example embodiments.

[0019] Figure 11 is a diagram of a vehicle including an electronic device according to some example embodiments. DETAILED DESCRIPTION

[0020] Hereinafter, various example embodiments will be described with reference to the drawings.

[0021] Figure 1 is a diagram showing an electronic device according to some example embodiments. Figure 2 is for explaining Figure 1 the sensor of. Figure 3 is a diagram showing Figure 1 the ECU (electronic control unit) of.

[0022] Referring to Figure 1 , the electronic device 1 may include an ECU (electronic control unit) 1000 and a sensor 2000.

[0023] In some example embodiments, the electronic device 1 may be installed in a vehicle (or may be configured to be installed in a vehicle). In some example embodiments, the electronic device 1 may form or be included in an automotive system for controlling a vehicle. Hereinafter, the electronic device 1 will be described as being installed in a vehicle, but the example embodiments are not limited thereto.

[0024] The ECU 1000 may control the vehicle and / or provide information about the vehicle to one or more users, for example.

[0025] Referring Figure 1 and Figure 2 to, the sensor 2000 may detect the movement of one or more of the vehicle's seat 3000, seat belt 3100, and door 4000, and may send a control signal to the ECU 1000 when the movement is detected.

[0026] For example, when the door 4000 is opened or closed, the sensor 2000 may detect such movement and send a control signal to the ECU 1000. Additionally or alternatively, the sensor 2000 may detect such movement when a person or animal is sitting on the seat 3000 and send a control signal to the ECU 1000. Alternatively or additionally, the sensor 2000 may detect such movement when a person pulls the seat belt 3100 and send a control signal to the ECU 1000. Alternatively or additionally, when a person couples the seat belt 3100 to the buckle, the sensor 2000 may detect such movement and send a control signal to the ECU 1000.

[0027] The ECU 1000 that receives the control signal from the sensor 2000 may recognize that the vehicle is about to be powered on and perform the operations required for powering on the vehicle. This will be described in more detail later.

[0028] Although Figure 2 shows four seats 3000, the example embodiments are not limited thereto. For example, there may be more than four seats or less than four seats. Additionally or alternatively, although Figure 2 shows four doors 4000, the example embodiments are not limited thereto. For example, there may be more than four doors 4000 or less than four doors 4000. Additionally or alternatively, although Figure 2 shows the driver's seat on the left side, the example embodiments are not limited thereto. For example, the driver's seat may be on the right side. Alternatively or additionally, the vehicle may not include a steering wheel (e.g., the vehicle may be an autonomous vehicle).

[0029] Referring Figure 3 to, the ECU 1000 may include a SoC (System on Chip) 100, a non-volatile storage device 200, and a volatile storage device 300.

[0030] The SoC 100 may include, for example, a microcontroller and may control the overall operation of the ECU 1000. For example, the SoC 100 may control the operations of the non-volatile storage device 200 and the volatile storage device 300.

[0031] The SoC 100 may include a controller 110 that controls the overall operation of the SoC 100, a first interface 112 that performs docking with the volatile storage device 300, and a second interface 114 that performs docking with the non-volatile storage device 200.

[0032] In some example embodiments, the protocols applied to the first interface 112 and the second interface 114 may be different. In some example embodiments, the first interface 112 and the second interface 114 may be implemented using various interface methods, such as one or more of ATA (Advanced Technology Attachment), SATA (Serial ATA), e-SATA (External SATA), SCSI (Small Computer System Interface), SAS (Serial Attached SCSI), PCI (Peripheral Component Interconnect), PCIe (PCI Express), NVMe, IEEE 1394, USB (Universal Serial Bus), SD (Secure Digital) card, MMC (MultiMediaCard), eMMC, UFS, eUFS (Embedded Universal Flash Storage), CF (CompactFlash) card interface, etc.

[0033] The non-volatile storage device 200 may store data necessary or used for vehicle operation. In some example embodiments, the non-volatile storage device 200 may include a flash memory device. In some example embodiments, the non-volatile storage device 200 may include a NAND flash memory device. However, the example embodiments are not limited thereto, and the non-volatile storage device 200 may include various other types of non-volatile storage devices. For example, the non-volatile storage device 200 may include one or more of MRAM (Magnetic RAM), spin-transfer torque MRAM, conductive-bridge RAM (CBRAM), FeRAM (Ferroelectric RAM), PRAM (Phase RAM), and resistive RAM devices.

[0034] The volatile storage device 300 may store data necessary or used for vehicle operation. In some example embodiments, the volatile storage device 300 may include DRAM (Dynamic Random Access Memory). For example, the volatile storage device 300 may include one or more of DDR SDRAM (Double Data Rate Synchronous DRAM), HBM (High Bandwidth Memory), HMC (Hybrid Memory Cube), DIMM (Dual In-line Memory Module), etc. In some example embodiments, the volatile storage device 300 may also (or alternatively) include SRAM.

[0035] The volatile memory device 300 may include control logic 310, a command timer 314, a time setting register 316, and a self - refresh timer 318.

[0036] The control logic 310 may control the operation of the volatile memory device 300. The control logic 310 may wake up the volatile memory device 300 or may put it into a sleep mode. In some example embodiments, the control logic 310 may power on or off the volatile memory device 300.

[0037] The time setting register 316 may store a first threshold time. In this embodiment, the first threshold time represents the maximum time for the volatile memory device 300 to perform a self - refresh operation to reduce power consumption caused by the self - refresh operation of the volatile memory device 300 when the vehicle is powered off. After the first threshold time has elapsed, the volatile memory device 300 may perform the operations required for power - off. This will be described in more detail later.

[0038] The self - refresh timer 318 may monitor whether the execution time of the self - refresh operation of the volatile memory device 300 has passed the first threshold time based on the first threshold time in the time setting register 316. Additionally or alternatively, if the execution time of the self - refresh operation of the volatile memory device 300 has passed the first threshold time, the self - refresh timer 318 may send a control signal to the control logic 310.

[0039] The command timer 314 may monitor read commands provided from the SoC 100 to the control logic 310. Additionally or alternatively, if no read command is received from the SoC 100 within a second threshold time, the command timer 314 may send a control signal to the control logic 310.

[0040] In various example embodiments, the second threshold time may be the time to confirm that all data stored in the volatile memory device 300 has been transferred to the non - volatile memory device 200. When transferring the data stored in the volatile memory device 300 to the non - volatile memory device 200, the SoC 100 may provide read commands to the volatile memory device 300 multiple times to transfer the data stored in the volatile memory device 300 to the non - volatile memory device 200. Once all data stored in the volatile memory device 300 has been transferred to the non - volatile memory device 200, the SoC 100 may no longer provide read commands to the volatile memory device 300. Therefore, if no read command is received from the SoC 100 before the second threshold time has passed, it can be determined that all data stored in the volatile memory device 300 has been transferred to the non - volatile memory device 200.

[0041] Thereafter, the control logic 310 may power down the volatile storage device 300. Alternatively, the SoC 100 may power down the volatile storage device 300.

[0042] In some example embodiments, a first threshold time for reducing current consumption caused by the self-refresh operation of the volatile storage device 300 when the vehicle is powered down and a second threshold time for confirming that all data stored in the volatile storage device 300 has been transferred to the non-volatile storage device 200 may be the same or different. In some example embodiments, the second threshold time may be shorter than the first threshold time, but the embodiments are not limited thereto.

[0043] In some example embodiments, the command timer 314, the time setting register 316, and the self-refresh timer 318 may be implemented as separate hardware different from the control logic 310. Additionally or alternatively, in some example embodiments, at least some of the command timer 314, the time setting register 316, and the self-refresh timer 318 may be implemented as components included in the control logic 310.

[0044] Figure 4 is a diagram showing Figure 3 the volatile storage device.

[0045] Referring to Figure 4 , the volatile storage device 300 may include control logic 310, an address register 320, bank control logic 330, a row address multiplexer 340, a refresh address generator 345, a column address latch 350, a row decoder 360, a column decoder 370, sense amplifiers 385, an input / output strobe circuit 390, a memory cell array MCA, an ECC engine EOE, and a data input / output buffer 395.

[0046] The memory cell array MCA may include a plurality of memory cells MC for storing data therein. For example, the memory cell array MCA may include a first bank array BA1 to an eighth bank array BA8. Each of the first to eighth bank arrays BA1 to BA8 may include a plurality of word lines WL, a plurality of bit lines BTL, and a plurality of memory cells MC respectively disposed at intersections of the word lines WL and the bit lines BTL.

[0047] The memory cell array MCA may include a first bank array BA1 to an eighth bank array BA8. Although Figure 4 the volatile storage device 300 shown includes eight bank arrays BA1 to BA8, the embodiments are not limited thereto, and the volatile storage device 300 may include any number of bank arrays.

[0048] The control logic 310 may control the operation of the volatile memory device 300. For example, the control logic 310 may generate control signals CTL1 and CTL2 such that the volatile memory device 300 performs an operation of writing data or reading data. The control logic 310 may include a command decoder 311 for decoding a command CMD received from the SoC 100, and a mode register 312 for setting an operation mode of the volatile memory device 300.

[0049] For example, the command decoder 311 may generate a control signal corresponding to the command CMD by decoding one or more of a write enable signal, a row address strobe signal, a column address strobe signal, and a chip select signal. The control logic 310 may receive a clock signal and a clock enable signal for driving the volatile memory device 300 in a synchronous manner.

[0050] Additionally or alternatively, the control logic 310 may control the refresh address generator 345 to generate a refresh row address REF_ADDR in response to a refresh command.

[0051] The address register 320 may receive an address ADDR from the SoC 100. For example, the address register 320 may receive an address ADDR including a bank address BANK_ADDR, a row address ROW_ADDR, and a column address COL_ADDR. The address register 320 may provide the received bank address BANK_ADDR to the bank control logic 330, provide the received row address ROW_ADDR to the row address multiplexer 340, and provide the received column address COL_ADDR to the column address latch 350.

[0052] The bank control logic 330 may generate bank control signals in response to the bank address BANK_ADDR received from the address register 320. In response to these bank control signals, a bank row decoder corresponding to the bank address BANK_ADDR among the first to eighth bank row decoders 360a to 360h may be activated, and a bank column decoder corresponding to the bank address BANK_ADDR among the first to eighth bank column decoders 370a to 370h may be activated.

[0053] The row address multiplexer 340 can receive a row address ROW_ADDR from the address register 320 and a refresh row address REF_ADDR from the refresh address generator 345. The row address multiplexer 340 can selectively output the row address ROW_ADDR received from the address register 320 or the refresh row address REF_ADDR received from the refresh address generator 345 as a row address RA. The row address RA output from the row address multiplexer 340 can be applied to the first bank row decoder 360a to the eighth bank row decoder 360h, respectively.

[0054] The refresh address generator 345 can generate a refresh row address REF_ADDR to refresh the memory cells. The refresh address generator 345 can provide the refresh row address REF_ADDR to the row address multiplexer 340. Accordingly, the memory cells provided in the word lines corresponding to the refresh row address REF_ADDR can be refreshed.

[0055] The column address latch 350 can receive a column address COL_ADDR from the address register 320 and can temporarily store the received column address COL_ADDR therein. In addition, the column address latch 350 can increment the received column address COL_ADDR step by step in a burst mode. The column address latch 350 can apply the temporarily stored or incremented column address COL_ADDR to each of the first bank column decoders 370a to the eighth bank column decoders 370h.

[0056] The row decoder 360 can include the first bank row decoder 360a to the eighth bank row decoder 360h respectively connected to the first bank array BA1 to the eighth bank array BA8. The column decoder 370 can include the first bank column decoder 370a to the eighth bank column decoder 370h respectively connected to the first bank array BA1 to the eighth bank array BA8. The sense amplifier 385 can include the first bank sense amplifier 385a to the eighth bank sense amplifier 385h respectively connected to the first bank array BA1 to the eighth bank array BA8.

[0057] The bank row decoder activated by the bank control logic 330 among the first bank row decoder 360a to the eighth bank row decoder 360h can decode the row address RA output from the row address multiplexer 340 to activate the word line corresponding to the row address RA. For example, the activated bank row decoder can apply a word line drive voltage to the word line corresponding to the row address RA.

[0058] Among the first to eighth bank column decoders 370a to 370h, the bank column decoder activated by the bank control logic 330 can activate the bank sense amplifiers 385a to 385h corresponding to the bank address BANK_ADDR and the column address COL_ADDR through the input / output strobe circuit 390.

[0059] The input / output strobe circuit 390 may include a circuit for strobing input / output data, input data mask logic, a read data latch for storing data output from the first to eighth bank arrays BA1 to BA8, and a write driver for writing data to the first to eighth bank arrays BA1 to BA8.

[0060] The codeword CW to be read from one of the first to eighth bank arrays BA1 to BA8 can be read by the bank sense amplifiers 385a to 385h corresponding to the one bank array and stored in the read data latch.

[0061] The ECC engine EOE can perform ECC decoding on the codeword CW stored in the read data latch. When an error is detected in the data of the codeword CW, the ECC engine EOE can provide a corrected data signal DQ to the external memory controller through the data input / output buffer 395.

[0062] The data signal DQ to be written to one of the first to eighth bank arrays BA1 to BA8 can be provided to the ECC engine EOE. The ECC engine EOE can generate parity bits based on the data signal DQ and provide the data signal DQ and the parity bits to the input / output strobe circuit 390. The input / output strobe circuit 390 can write the data signal DQ and the parity bits to a subpage of the one bank array through the write driver.

[0063] The data input / output buffer 395 can receive the data signal DQ and the data strobe signal DQS from an external device (e.g., the SoC 100). In some example embodiments, the data input / output buffer 395 may include a first data input / output buffer (e.g., a data buffer) for receiving the data signal DQ from an external device (e.g., the SoC 100) and a second data input / output buffer (e.g., a data strobe buffer) for receiving the data strobe signal DQS from an external device (e.g., the SoC 100).

[0064] During a write operation, the data input / output buffer 395 can buffer or drive a data signal DQ (e.g., write data), and can provide the data signal DQ to the ECC engine EOE. During a read operation, the data input / output buffer 395 can buffer or drive the data signal DQ (e.g., read data) provided from the ECC engine EOE, and can provide the data signal DQ to an external device (e.g., the SoC 100).

[0065] Figure 5A and Figure 5B FIG. is a diagram illustrating a power-off operation of an electronic device according to some example embodiments. Figure 6 and Figure 7 is for explaining Figure 5A and Figure 5B the operations of.

[0066] Referring Figure 5A to, when the volatile memory device 300 is initialized, the SoC 100 provides a first threshold time RTIME (S100) to the volatile memory device 300.

[0067] In the present embodiment, the first threshold time RTIME is the maximum time for the volatile memory device 300 to perform a self-refresh operation, in order to reduce the power consumption caused by the self-refresh operation of the volatile memory device 300 when the vehicle is powered off.

[0068] The first threshold time RTIME can be set to a sufficiently long time such that it is not applied to the instantaneous self-refresh operation of the volatile memory device 300 when the vehicle is not powered off.

[0069] For example, if the first threshold time RTIME is set too short, the volatile memory device 300 may unnecessarily need to perform a power-off preparation operation that will be described later. Therefore, in various example embodiments, the first threshold time RTIME can be set to be sufficiently long to prevent or reduce the possibility and / or impact of unnecessary subsequent operations.

[0070] The volatile memory device 300 that has been provided with the first threshold time RTIME can set the first threshold time RTIME as a self-refresh termination time (S105).

[0071] For example, referring Figure 3 to, the control logic 310 of the volatile memory device 300 can store the first threshold time RTIME provided by the SoC 100 in the time setting register 316.

[0072] Next, when the vehicle is powered off, the SoC 100 detects that the vehicle is powered off (S110). Even when the vehicle is powered off, it is necessary or desirable to retain the data stored in the volatile storage device 300 because this data may be reused soon. Therefore, the SoC 100 provides a command to instruct the volatile storage device 300 to perform a self-refresh operation (S115). In some example embodiments, thereafter, the SoC 100 may continue to maintain the self-refresh related control signals for the volatile storage device 300 such that the volatile storage device 300 remains in the self-refresh mode continuously.

[0073] The volatile storage device 300 that receives the command indicating the self-refresh operation from the SoC 100 performs the self-refresh operation (S120). According to performing such a self-refresh operation, the volatile storage device 300 may consume an operating current (e.g., IDD6).

[0074] Then, the method includes checking whether the execution time of the self-refresh operation of the volatile storage device 300 has passed a first threshold time RTIME, i.e., the self-refresh termination time (S125).

[0075] If the execution time of the self-refresh operation has not passed the first threshold time RTIME, i.e., the self-refresh termination time (S125-N), the self-refresh operation is continued (S120). However, if the execution time of the self-refresh operation has passed the first threshold time RTIME, i.e., the self-refresh termination time (S125-Y), the volatile storage device 300 requests the SoC 100 to transfer the data stored in the volatile storage device 300 (S130).

[0076] For example, referring to Figure 3 , the self-refresh timer 318 may monitor whether the execution time of the self-refresh operation of the volatile storage device 300 has passed the first threshold time (RTIME) based on the first threshold time (RTIME) of the time setting register 316. And, if the execution time of the self-refresh operation of the volatile storage device 300 has passed the first threshold time (RTIME), the self-refresh timer 318 may send a control signal to the control logic 310.

[0077] The control logic 310 that receives the control signal from the self-refresh timer 318 may send a request to the SoC 100 to transfer the data stored in the volatile storage device 300.

[0078] Referring to Figure 3 and Figure 6, in some example embodiments, the control logic 310 may switch the volatile memory device 300 to an active mode to send a request to the SoC 100 to transfer the data stored in the volatile memory device 300. Additionally, the control logic 310 may send a flag signal (FLAG) to the SoC 100 to request the SoC 100 to transfer the data stored in the volatile memory device 300.

[0079] For example, the control logic 310 may send a flag signal (FLAG) to the SoC 100 to request the transfer of the data stored in the volatile memory device 300 by holding one or more data port signals sent to the SoC 100. For example, the control logic 310 may send a flag signal (FLAG) to the SoC 100 to request the transfer of the data stored in the volatile memory device 300 by holding the DQ1 port signal sent to the SoC 100 at H (logical high) for 64BL (burst length).

[0080] Reference Figure 3 and 7 , in some example embodiments, the control logic 310 may store in the mode register 312 of the volatile memory device 300 information indicating that the execution time of the self-refresh operation has passed a first threshold time, so as to send a request to the SoC 100 to transfer the data stored in the volatile memory device 300. Subsequently, the SoC 100 may receive a transfer request for the data stored in the volatile memory device 300 by confirming the information stored in the mode register 312 (e.g., using an MRR command).

[0081] Reference Figure 5A , the SoC 100 that has received a request to transfer the data stored in the volatile memory device 300 determines whether the volatile memory device 300 has performed a self-refresh operation in response to vehicle power-off (S135).

[0082] If the SoC determines that the volatile memory device 300 has not performed a self-refresh operation in response to vehicle power-off (S135-N), the SoC 100 sends a command to instruct the volatile memory device 300 to perform a self-refresh operation (S140). Alternatively, the SoC 100 continues to hold the self-refresh related control signals for the volatile memory device 300 without change.

[0083] If the SoC determines that the volatile memory device 300 has performed a self-refresh operation in response to vehicle power-off (S135-Y), the SoC 100 sends a read command to the volatile memory device 300 to transfer the data stored in the volatile memory device 300 to the non-volatile memory device 200 (S145).

[0084] Transferring the data stored in the volatile memory device 300 to the non-volatile memory device 200 and then transferring the data stored in the non-volatile memory device 200 to the volatile memory device 300 may take a large amount of time and / or a large amount of resources. Sometimes, even when the vehicle is not powered off, the volatile memory device 300 may perform a self-refresh operation as needed or intended. In this case, the self-refresh operation mode of the volatile memory device 300 can be resolved in a relatively short time. Therefore, even in this case, transferring the data stored in the volatile memory device 300 to the non-volatile memory device 200 and then transferring the data stored in the non-volatile memory device 200 to the volatile memory device 300 may cause unnecessary waste of resources. Therefore, in various exemplary embodiments, the volatile memory device 300 performs a self-refresh operation in response to a vehicle power-off and transfers the data stored in the volatile memory device 300 to the non-volatile memory device 200 when a first threshold time has elapsed. This can reduce the use of unnecessary resources.

[0085] Next, the volatile memory device 300 determines whether it has received a notification of termination of the self-refresh operation and a read command from the SoC 100 (S150). In some exemplary embodiments, the notification of termination of the self-refresh operation from the SoC 100 may be, for example, a change in a self-refresh related control signal sent from the SoC 100.

[0086] If a notification of termination of the self-refresh operation and a read command are received from the SoC 100 (S150-Y), the volatile memory device 300 transfers the data corresponding to the read command to the SoC 100 (S155). Then, the SoC 100 stores the data received from the volatile memory device 300 in the non-volatile memory device 200 (S160).

[0087] If a notification of termination of the self-refresh operation is not received from the SoC 100 (S150-N), the volatile memory device 300 continues to perform the self-refresh operation.

[0088] Next, the volatile memory device 300 monitors the read command received from the SoC 100 (S165). If no read command is received from the SoC 100 within a certain period of time (S170-Y), the volatile memory device 300 is powered off (S175). And if the certain period of time has not elapsed (S170-N), the read command is continuously monitored (S165).

[0089] Reference Figure 3 , in order to transfer the data stored in the volatile memory device 300 to the non-volatile memory device 200, the SoC 100 may send multiple read commands to the volatile memory device 300.

[0090] In some example embodiments, the command timer 314 may monitor read commands provided from the SoC 100 to the control logic 310. And, if a read command is not received from the SoC 100 within a second threshold time, the command timer 314 may send a control signal to the control logic 310.

[0091] In some example embodiments, the second threshold time may be the time to confirm that all data stored in the volatile storage device 300 has been transferred to the non-volatile storage device 200. If all data stored in the volatile storage device 300 has been transferred to the non-volatile storage device 200, the SoC 100 will no longer provide a read command to the volatile storage device 300. Therefore, if no read command is received from the SoC 100 anymore before the second threshold time has passed, it can be determined that all data stored in the volatile storage device 300 has been transferred to the non-volatile storage device 200. In some examples, the volatile storage device 300 according to various example embodiments may be equipped with the command timer 314, which can improve the reliability of the operation of transferring data stored in the volatile storage device 300 to the non-volatile storage device 200.

[0092] The control logic 310 that receives the control signal from the command timer 314 may power off the volatile storage device 300. Alternatively or additionally, in some example embodiments, the SoC 100 may power off the volatile storage device 300.

[0093] Therefore, when the vehicle is powered off, all data stored in the volatile storage device 300 has been reliably transferred to the non-volatile storage device 200, and then the volatile storage device 300 is also powered off, thereby reducing the operating power of the electronic device 1.

[0094] Figure 8 is a diagram showing the power-on operation of an electronic device according to some example embodiments.

[0095] Refer to Figure 8 , the sensor 2000 may detect pre-start operations of the vehicle (S200). And, when a pre-start operation of the vehicle is detected, the sensor 2000 sends a control signal to the SoC 100 (S205).

[0096] Refer to Figure 1 and Figure 2, for example, the sensor 2000 can detect movements such as the opening or closing of a door 4000 and send a control signal to the SoC 100. Additionally or alternatively, when a person sits on the seat 3000, the sensor 2000 can detect such movement and send a control signal to the SoC 100. Additionally or alternatively, when a person pulls the seat belt 3100, the sensor 2000 can detect such movement and send a control signal to the SoC 100. Additionally or alternatively, when a person fastens the seat belt 3100 to the buckle, the sensor 2000 can detect the movement and send a control signal to the SoC 100.

[0097] The SoC 100 that receives these control signals from the sensor 2000 can recognize that the vehicle is about to be powered on and perform the operations necessary to power on the vehicle.

[0098] The SoC 100 powers on the powered-off volatile storage device 300 (S210). Then, the SoC 100 sends a read command to the non-volatile storage device 200 and receives the data transferred from the volatile storage device 300 to the non-volatile storage device 200 (S220). Subsequently, the SoC 100 stores the data received from the non-volatile storage device 200 in the volatile storage device 300 (S225). Thus, the data transferred to the non-volatile storage device 200 before the volatile storage device 300 was powered off can be restored to the volatile storage device 300.

[0099] In various example embodiments, the operation of restoring the data transferred to the non-volatile storage device 200 back to the volatile storage device 300 can even start before the actual vehicle is powered on. Thus, one or more users may not notice the delay caused by the data transfer, which can improve the operating performance of the electronic device 1.

[0100] Figure 9 is a diagram for explaining a volatile storage device according to some example embodiments. Figure 9 is shown above Figure 3 of the volatile storage device 300 in an embodiment.

[0101] Reference Figure 9 , the storage device 560 can include a stack of multiple storage layers 510, 520, 530, and 540. The storage device 560 can be embodied as, for example, an HBM (High Bandwidth Memory). The storage layers 510, 520, 530, and 540 can form multiple independent interfaces called channels.

[0102] Each of the storage layers 510, 520, 530, and 540 can include two channels 511 - 512, 521 - 522, 531 - 532, or 541 - 542. Figure 9An example is shown in which the memory device 560 includes a stack of four memory layers 510, 520, 530, and 540 to form (or be included in) eight channels. However, the example embodiment is not limited thereto. According to various embodiments, the memory device 560 may have a stack of 2 to 8 or more than 8 memory layers. The memory layers 510, 520, 530, and 540 may have the same or different electrical and / or physical characteristics; the example embodiment is not limited thereto.

[0103] Each of the channels 511, 512, 521, 522, 531, 532, 541, and 542 may include a memory cell array 543 that operates independently based on each channel, an input / output controller 544 for independently controlling the memory cell array 543 based on each channel, and a channel pad 545 that provides a channel for the memory cell array 543.

[0104] The memory cell array 543 may include memory cells connected to a plurality of word lines and a plurality of bit lines. The memory cells may be grouped into a plurality of banks and / or memory blocks. In the area of the memory cell array 543, one or more of a row decoder, a column decoder, a sense amplifier, etc. for accessing the memory cells may be provided.

[0105] The input / output control 544 may include RAS control logic, CAS control logic, etc. The channel pad 545 may include pads arranged in a matrix, including a plurality of rows and a plurality of columns. Each pad of the channel pad 545 may be connected to the electrode 548 and the through-silicon via (TSV) 570 using wiring for signal routing.

[0106] The memory device 560 may further include a memory buffer 550 provided below the stack of the memory layers 510, 520, 530, and 540. The memory buffer 550 may include an input buffer (or receiver) that receives commands, addresses, clocks, and data from the control logic, and may buffer and provide the received commands, addresses, clocks, and data to the channels 511, 512, 521, 522, 531, 532, 541, and 542.

[0107] The memory buffer 550 may include a data receiving device ( Figure 1 the RX in) as described above. The memory buffer 550 may perform a signal distribution function and a data input / output function for the channels 511, 512, 521, 522, 531, 532, 541, and 542 using the electrode 548 and the through-silicon via 570.

[0108] The memory buffer 550 may communicate with the control logic through a mechanism (e.g., bumps or solder balls) formed on the outer surface of the memory device 560 by a conductive bus.

[0109] Each of the storage layers 510, 520, 530, and 540 may include two channels 511, 512, 521, 522, 531, 532, 541, and 542. A single channel may be composed of two pseudo-channels.

[0110] Assume that the number of data input / output (DQ) pads included in the area of the channel pad 545 of each of the channels 511, 512, 521, 522, 531, 532, 541, and 542 is, for example, 128. Then, the 128 DQ pads of the channel pad 545 of each of the channels 511, 512, 521, 522, 531, 532, 541, and 542 can be divided into two groups of pseudo-channels 546 and 547, and the number of DQ pads of each of the pseudo-channels 546 and 547 can be 64. In this regard, each of the channels 511, 512, 521, 522, 531, 532, 541, and 542 can receive data through eight DQ pads.

[0111] Figure 10 is a block diagram of an electronic device according to some example embodiments. Figure 10 is a diagram illustrating an embodiment of the previously described electronic device 1.

[0112] Reference Figure 10 , the electronic device 601 in the network environment 600 may communicate with the electronic device 602, for example, through a first network 698 (e.g., a short-range wireless network), or may communicate with the electronic device 604 or the server 608, for example, through a second network 699 (e.g., a long-range wireless network). In some example embodiments, although such an electronic device 601 may be, for example, a laptop computer, a notebook computer, a portable mobile terminal, etc., the embodiments are not limited thereto.

[0113] The electronic device 601 may communicate with the electronic device 604 through the server 608. The electronic device 601 may include a processor 620, a memory 630, an input device 650, a sound output device 655, a display device 660, an audio module 670, a sensor module 676, an interface 677, a tactile module 679, a camera module 680, a power management module 688, a battery 689, a communication module 690, a subscriber identification module (SIM) 696, or an antenna module 697, etc.

[0114] In some example embodiments, for example, at least one component, such as the display device 660 or the camera module 680, may be omitted from the electronic device 601, or one or more other components may be added to the electronic device.

[0115] In some example embodiments, some components may be implemented as a single integrated circuit (IC). For example, the sensor module 676 (e.g., fingerprint sensor, iris sensor, or brightness sensor) may be embedded in an image display device (e.g., a display).

[0116] The processor 620 may execute software (e.g., the program 640) to control other components (e.g., hardware or software components connected to the processor 620) of at least one electronic device 601, thereby performing various data processing and calculations.

[0117] As at least part of the data processing or calculation, the processor 620 may load commands or data received from other components (e.g., the sensor module 676 or the communication module 690) into the volatile memory 632, process the commands or data stored in the volatile memory 632, and store the resulting data in the non-volatile memory 634.

[0118] The processor 620 may include, for example, a main processor 621 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 623 that is independent of or operates together with the main processor 621.

[0119] Such an auxiliary processor 623 may include, for example, a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP), etc.

[0120] In some example embodiments, the auxiliary processor 623 may be configured to consume less power or perform specific functions than the main processor 621. The auxiliary processor 623 may be implemented separately from the main processor 621, or may be implemented as part of the main processor 621.

[0121] The auxiliary processor 623 may, for example, represent the main processor 621 when the main processor 621 is in an inactive state, or may control at least some functions or states associated with at least one of the components of the electronic device 601 together with the main processor 621 when the main processor 621 is in an active state.

[0122] The memory 630 may store various types of data used in at least one component of the electronic device 601. The various types of data may include, for example, input data and / or output data for software such as the program 640, and commands associated therewith. The memory 630 may include a volatile memory 632 and a non-volatile memory 634. The non-volatile memory 634 may include an internal memory 636 and an external memory 638.

[0123] In some example embodiments, the non-volatile memory 634 may correspond to the non-volatile storage device described above (Figure 3 200) in, and the volatile memory 632 may correspond to the above-described volatile storage device ( Figure 3 300) in.

[0124] The program 640 may be stored in the memory 630 as software, and may include, for example, an operating system (OS) 642, middleware 644, or an application 646.

[0125] The input device 650 may receive a command or data to be used in other components of the electronic device 601 from the outside of the electronic device 601. The input device 650 may include, for example, one or more of a microphone, a mouse, or a keyboard.

[0126] The sound output device 655 may output a sound signal to the outside of the electronic device 601. The sound output device 655 may include, for example, a speaker. Multimedia data may be output through the speaker.

[0127] The display device 660 may provide information to the outside of the electronic device 601 visually. The display device may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the corresponding device in the display, the hologram device, or the projector.

[0128] In some example embodiments, the display device 660 may include a touch circuit configured to detect a touch, or a sensor circuit, such as a pressure sensor configured to measure the intensity of a force caused by the touch.

[0129] The audio module 670 may convert sound into an electrical signal or convert an electrical signal into sound. In some example embodiments, the audio module 670 may obtain sound through the input device 650, or may output sound through the sound output device 655 or headphones of an external electronic device 602 directly and / or wirelessly connected to the electronic device.

[0130] The sensor module 676 may detect an operating state of the electronic device 601 (e.g., power or temperature) or an external environmental state (e.g., a state of a user), and may generate an electrical signal or a data value corresponding to the detected state. The sensor module 676 may include, for example, one or more of a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0131] Interface 677 may support one or more specified protocols used by an electronic device 601 that is directly or wirelessly connected to an external electronic device 602. In some example embodiments, interface 677 may include, for example, one or more of a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0132] Connection terminal 678 may include a connector through which the electronic device 601 may be physically connected to the external electronic device 602. In some example embodiments, connection terminal 678 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector, etc.).

[0133] The haptic module 679 may convert an electrical signal into a mechanical stimulus, such as vibration or movement that a user may perceive through haptic perception or kinesthetic perception. In some example embodiments, the haptic module 679 may include, for example, one or more motors, piezoelectric elements, or electrostimulators.

[0134] The camera module 680 may capture still images or moving images. In some example embodiments, the camera module 680 may include one or more lenses, an image sensor, an image signal processor, a flash, etc.

[0135] The power management module 688 may manage the power to be provided to the electronic device 601. The power management module may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

[0136] The battery 689 may supply power to at least one component of the electronic device 601. According to various example embodiments, the battery 689 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0137] The communication module 690 may support establishing a direct communication channel or a wireless communication channel between the electronic device 601 and an external electronic device (e.g., the electronic device 602, the electronic device 604, or the server 608), and perform communication through the established communication channel.

[0138] The communication module 690 may include one or more communication processors that may operate independently of the processor 620 and support direct communication or wireless communication.

[0139] In some example embodiments, the communication module 690 may include a wireless communication module 692, such as one or more of a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module, or a wired communication module 694, such as a local area network (LAN) communication module or a power line communication module (PLC).

[0140] Among these communication modules, a corresponding communication module may communicate with an external electronic device via a first network 698, for example, one or more of Bluetooth™, Wi-Fi (Wireless Fidelity) Direct, or IrDA (Infrared Data Association standard), or may communicate with an external electronic device via a second network 699, for example, a cellular communication network, the Internet, or a long-distance communication network.

[0141] Various types of communication modules may be implemented as a single component, or may be implemented as multiple components separated from each other. The wireless communication module 692 may, for example, use user information (such as an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 696 to authenticate and verify an electronic device 601 within a communication network (such as the first network 698 or the second network 699).

[0142] The antenna module 697 may transmit signals or power to the outside of the electronic device 601 and receive signals or power from the outside of the electronic device 601. In some example embodiments, the antenna module 697 may include one or more antennas, and thus, the communication module 690 may select at least one antenna suitable for a communication scheme used in a communication network (such as the first network 698 or the second network 699). Then, signals or power may be transmitted or received between the communication module and the external electronic device via the at least one selected antenna.

[0143] At least some of the above components may be connected to each other to perform signal communication therebetween via an inter-peripheral communication scheme, for example, one or more of General-Purpose Input / Output (GPIO), Serial Peripheral Interface (SPI), or Mobile Industry Processor Interface (MIPI).

[0144] In some example embodiments, commands or data may be transmitted or received between the electronic device 601 and an external electronic device 606 via a server 608 connected to the second network 699. Each of the electronic devices 602 and 606 may be a device of the same type or a different type from the electronic device 601. All or some of the operations to be performed in the electronic device 601 may be performed in one or more external electronic devices 602, 606, or 608. For example, all or some of the operations to be performed in the electronic device 601 may be performed in one or more external electronic devices 602, 606, or 608.

[0145] For example, if the electronic device 601 needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device 601 that performs the function or service may request or may use one or more external electronic devices to perform at least part of the function or service on its behalf or additionally. One or more external electronic devices that receive the request may perform at least some of the requested function or service or additional functions or additional services associated with the request, and send the execution result to the electronic device 601. The electronic device 601 provides the result as at least part of the response to the request, with or without further processing of the result. For example, cloud computing, distributed computing, or client-server computing technologies may be used for this purpose.

[0146] Figure 11 is a diagram of a vehicle including an electronic device according to some example embodiments.

[0147] Reference Figure 11 , the vehicle 700 may include a plurality of electronic control units (ECUs) 710 and a storage device 720.

[0148] In some example embodiments, the electronic control unit 710 may correspond to the ECU ( Figure 1 in 1000) described above.

[0149] Each of the plurality of electronic control units 710 is electrically, mechanically, and communicatively connected to at least one of the plurality of devices provided in the vehicle 700, and may control the operation of at least one device based on a command for any one function.

[0150] Here, the plurality of devices may include: an acquisition device 730 that acquires an image required to perform at least one function; and a driving unit 740 that performs at least one function.

[0151] For example, the acquisition device 730 may include various detection units and an image acquisition unit, and the driving unit 740 may include a fan and a compressor of an air conditioner, a fan of a ventilation device, an engine and a motor of a power device, a motor of a steering device, a motor and a valve of a braking device, an opening / closing device of a door or a tailgate, etc.

[0152] The plurality of electronic control units 710 may communicate with the acquisition device 730 and the driving unit 740 using at least one of, for example, Ethernet, low-voltage differential signaling (LVDS) communication, and local interconnect network (LIN) communication.

[0153] A plurality of electronic control units 710 determine whether a function needs to be executed based on information acquired by an acquisition device 730. When it is determined that the function needs to be executed, the plurality of electronic control units 710 control the operation of a drive unit 740 that executes the function, and can control the operation amount based on the acquired information. At this time, the plurality of electronic control units 710 can store the acquired information in a storage device 720, or read and use the information stored in the storage device 720.

[0154] The plurality of electronic control units 710 are capable of controlling the operation of a drive unit 740 that executes a function according to a function execution command input through an input unit 750, and are capable of checking a set amount corresponding to the information input through the input unit 750, and controlling the operation of the drive unit 740 that executes the function according to the checked set amount.

[0155] Each electronic control unit 710 can independently control any one function, or can cooperate with other electronic control units to control any one function.

[0156] For example, when the distance to an obstacle detected by a distance detection unit is within a reference distance, the electronic control unit of an anti-collision device can output a warning sound of collision with the obstacle through a speaker.

[0157] The electronic control unit of an autonomous driving control device can cooperate with the electronic control unit of an in-vehicle terminal, the electronic control unit of an image acquisition unit, and the electronic control unit of an anti-collision device to receive navigation information, road image information, and distance information to an obstacle, and use the received information to control one or more of a power device, a braking device, and a steering device, thereby realizing autonomous driving.

[0158] A connection control unit (CCU) 760 is electrically connected, mechanically connected, and communicatively connected to each of the plurality of electronic control units 710, and communicates with each of the plurality of electronic control units 710.

[0159] In some examples, the connection control unit 760 is capable of directly communicating with a plurality of electronic control units 710 provided inside a vehicle, capable of communicating with an external server, and capable of communicating with an external terminal through an interface.

[0160] Here, the connection control unit 760 is capable of communicating with the plurality of electronic control units 710, and is capable of communicating with a server 810 using an antenna (not shown) and RF communication.

[0161] In some examples, the connection control unit 760 may communicate with the server 810 via wireless communication. At this time, the wireless communication between the connection control unit 760 and the server 810 may be performed by various wireless communication methods. For example, in addition to or instead of Wi-Fi and wireless broadband, one or more of GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), TDMA (Time Division Multiple Access), LTE (Long Term Evolution), and NR (New Radio).

[0162] Any of the elements and / or functional blocks disclosed above may be included or implemented in a processing circuit, such as hardware including logic circuits; a hardware / software combination such as a processor executing software; or a combination of both. For example, the processing circuit may more specifically include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a system on a chip (SoC), a programmable logic unit, a microprocessor, an application specific integrated circuit (ASIC), etc. The processing circuit may include at least one of electronic components such as transistors, resistors, capacitors, etc. The processing circuit may include at least one of electronic components such as logic gates, including AND gates, OR gates, NAND gates, NOT gates, etc.

[0163] Those skilled in the art will understand that many variations and modifications can be made to the preferred embodiments without substantially departing from the principles of the inventive concept. Therefore, the disclosed example embodiments are for general and descriptive purposes only and not for purposes of limitation. Additionally, the example embodiments are not necessarily mutually exclusive. For example, some example embodiments may include one or more features described with reference to one or more of the drawings and may also include one or more other features described with reference to one or more other drawings.

Claims

1. A volatile memory device, comprising: A memory cell array including a plurality of memory cells configured to store data; And Control logic configured to control read operations and write operations for the plurality of memory cells, Wherein the control logic is configured to: Receive a command indicating a self - refresh operation from an external device, Execute the self - refresh operation in response to the received command, Request the external device to transmit the data stored in the plurality of memory cells in response to the execution time of the self - refresh operation having passed a first threshold time, Monitor the read command received from the external device in response to receiving a notification of termination of the self - refresh operation and a read command from the external device, and Enter a power - down state in response to not receiving the read command within a second threshold time.

2. The volatile memory device according to claim 1, further comprising: A time - setting register configured to store the first threshold time; And A self - refresh timer configured to: Monitor whether the execution time of the self - refresh operation has passed the first threshold time based on the first threshold time in the time - setting register, and Provide a first control signal to the control logic in response to the execution time of the self - refresh operation having passed the first threshold time.

3. The volatile memory device according to claim 2, further comprising: A command timer configured to: Monitor the read command provided from the external device to the control logic, and Provide a second control signal to the control logic in response to not receiving the read command within the second threshold time.

4. The volatile memory device according to claim 3, Among them, The second threshold time is shorter than the first threshold time.

5. The volatile memory device according to claim 2, Among them, The first threshold time is provided from the external device during initialization of the volatile memory device.

6. The volatile memory device according to claim 1, Among them, The control logic is configured to request transmission of the data stored in the plurality of memory cells by sending a flag signal to the external device.

7. The volatile memory device according to claim 6, Among them, The control logic is configured to: Switch the volatile memory device to an active mode in response to the execution time of the self - refresh operation having passed the first threshold time, and Request transmission of the data stored in the plurality of memory cells by maintaining a first data port signal transmitted to the external device in a first logic state over a 64 - burst length.

8. The volatile memory device according to claim 1, Among them, The control logic is configured to: Store information indicating that the execution time of the self - refresh operation has passed the first threshold time in a mode register in response to the execution time of the self - refresh operation having passed the first threshold time, and Request transmission of the data stored in the plurality of memory cells by having the external device check the information stored in the mode register.

9. The volatile memory device according to claim 1, Among them, The control logic continues to perform the self - refresh operation in response to not receiving a notification of the termination of the self - refresh operation from the external device.

10. The volatile memory device according to claim 1, Among them, The volatile memory device includes a dynamic random access memory.

11. A system - on - chip (SoC) includes: A first interface configured to communicate with a volatile memory device; A second interface configured to communicate with a non - volatile memory device; And A controller configured to control the first interface and the second interface, wherein the controller is configured to: Send a command indicating to perform a self - refresh operation to the volatile memory device, Receive a request from the volatile memory device to transfer data stored in the volatile memory device to the non - volatile memory device, Determine whether the volatile memory device has performed the self - refresh operation in response to vehicle power - off, When it is determined that the volatile memory device has performed the self - refresh operation in response to vehicle power - off, send a read command to the volatile memory device in response to the request, When it is determined that the volatile memory device has not performed the self - refresh operation in response to vehicle power - off, send a command indicating the self - refresh operation to the volatile memory device in response to the request, The controller is further configured to: Receive data corresponding to the read command from the volatile memory device, Store the received data in the non - volatile memory device, Receive a control signal from a sensor, and Power on the volatile memory device in response to the control signal.

12. The SoC according to claim 11, Among them, The controller is further configured to: Send a first threshold time to the volatile memory device when the volatile memory device is initialized, and Receive the request from the volatile memory device after sending a command indicating the self - refresh operation to the volatile memory device and after the first threshold time has elapsed.

13. The SoC according to claim 11, Among them, The controller is configured to receive the control signal from the sensor before vehicle power - on.

14. The SoC according to claim 11, Among them, The controller is configured to receive the request from the volatile memory device via a flag signal.

15. The SoC according to claim 14, Among them, The flag signal includes the following signal: A first data port signal remains at a first logic level over a 64 - burst length.

16. The SoC according to claim 11, Among them, The controller is configured to receive the request by checking information stored in a mode register of the volatile memory device.

17. An electronic device configured to be included in a vehicle, the electronic device includes: A volatile memory device configured to store first data for vehicle operation; A non - volatile memory device configured to store second data for vehicle operation; A sensor configured to output a control signal in response to receiving a detection signal from at least one of a vehicle door, a seat, and a seat belt; And A system-on-chip (SoC) is configured to power on the volatile storage device in response to the control signal received from the sensor, and to control the volatile storage device and the non-volatile storage device. Wherein, the volatile storage device is configured to: Receive a command indicating a self-refresh operation from the SoC; Execute the self-refresh operation in response to the received command; Request the SoC to transfer the data stored in the volatile storage device to the non-volatile storage device in response to the first threshold time having elapsed since the execution time of the self-refresh operation; Wherein, the SoC is configured to: In response to the request when it is determined that the volatile storage device has executed the self-refresh operation in response to vehicle power-off, Send a read command to the volatile storage device; Receive data corresponding to the read command from the volatile storage device, and Store the received data in the non-volatile storage device; In response to the request when it is determined that the volatile storage device has not executed the self-refresh operation in response to vehicle power-off, Send a command indicating the self-refresh operation to the volatile storage device.

18. The electronic device according to claim 17, Among them, The volatile storage device includes: A time setting register configured to store the first threshold time; and A self-refresh timer configured to monitor whether the execution time of the self-refresh operation has elapsed the first threshold time based on the first threshold time in the time setting register.

19. The electronic device according to claim 18, Among them, The SoC is configured to provide the first threshold time to the volatile memory when the volatile storage device is initialized.

20. The electronic device according to claim 19, Among them, The volatile storage device further includes: a command timer configured to monitor the read command received from the SoC and to monitor whether the read command has not been received within a second threshold time.

Images