M58BW032DB60ZA6T

M58BW032BT STMICROELECTRONICS | Alldatasheet

Document overview

• Manufacturer or author: Provided By ALLDATASHEET.COM(FREE DATASHEET DOWNLOAD SITE)
• PDF pages: 60

Technical content

This is preliminary information on a new product now in development or undergoing evaluation. Details are subject to change without notice.

32 Mbit (1Mb x32, Boot Block, Burst)

Figure 1. Packages

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB SUMMARY DESCRIPTION The M58BW032B/D is a 32Mbit non-volatile Flash memory that can be erased electrically at the block level and programmed in-system on a Double- Word basis using a 3.0V to 3.6V VDD supply for the circuit and a VDDQ supply down to 1.6V for the In- put and Output buffers. The devices support Asynchronous (Latch Con- trolled and Page Read) and Synchronous Bus op- erations. The Synchronous Burst Read Interface allows a high data transfer rate controlled by the Burst Clock, K, signal. It is capable of bursting fixed or unlimited lengths of data. The burst type, latency and length are configurable and can be easily adapted to a large variety of system clock frequencies and microprocessors. All Writes are Asynchronous. On power-up the memory defaults to Read mode with an Asynchronous Bus. The device features an asymmetrical block archi- tecture. The M58BW032B/D has an array of 62 main blocks of 512 Kbits each, plus 4 large param- eter blocks of 128Kbits each and 8 small parame- ter blocks of 64 Kbits each. The large and small parameter blocks are located either at the top (M58BW032BT, M58BW032DT) or at the bottom (M58BW032BB, M58BW032DB) of the address space. The first large parameter block is referred to as Boot Block and can be used either to store a boot code or parameters. The memory array orga- nization is detailed in Tables 2, Top Boot Block Ad- dresses and 3, Bottom Boot Block Addresses. Program and Erase commands are written to the Command Interface of the memory. An on-chip Program/Erase Controller simplifies the process of programming or erasing the memory by taking care of all of the special operations that are re- quired to update the memory contents. The end of a Program or Erase operation can be detected and any error conditions identified in the Status Regis- ter. The command set required to control the memory is consistent with JEDEC standards. Erase can be suspended in order to perform either Read or Program in any other block and then re- sumed. Program can be suspended to Read data in any other block and then resumed. Each block can be programmed and erased over 100,000 cy- cles. All blocks are protected during power-up. The M58BW032B features four different levels of hard- ware and software block protection to avoid un- wanted program/erase operations: ■ Write/Protect Enable input, WP , provides a hardware protection of a combination of blocks from program or erase operations. The Block Protection configuration can be defined individually by issuing a Set Block Protection Configuration Register or Clear Block Protection Configuration Register commands. ■ All Program or Erase operations are blocked when Reset, RP, is held low. ■ A Program/Erase Enable input, VPEN , is used to protect all blocks, preventing Program and Erase operations from affecting their data. ■ The Program and Erase commands can be password protected by the Tuning Protection command. The M58BW032D offers the same protection fea- tures with the exception of the Tuning Block Pro- tection which is disabled in the factory. A Reset/Power-down mode is entered when the RP input is Low. In this mode the power consump- tion is reduced to the standby level, the device is write protected and both the Status and Burst Con- figuration Registers are cleared. A recovery time is required when the RP input goes High. A manufacturer and device code are available. They can be read from the memory allowing pro- gramming equipment or applications to automati- cally match their interface to the characteristics of the memory. Finally, the M58BW032B/D features a Unique De- vice Identifier (UID) which is programmed by ST. It is unique for each die and can be used to imple- ment cryptographic algorithms to improve securi- ty. The memory is offered in PQFP80 (14 x 20mm) and LBGA80 (1.0mm pitch) packages and it is supplied with all the bits erased (set to ’1’).

Figure 2. Logic Diagram Table 1. Signal Names

Figure 3. LBGA Connections (Top view through package)

Figure 4. PQFP Connections (Top view through package)

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB Block Protection The M58BW032B features four different levels of block protection. The M58BW032D has the same block protection with the exception of the Tuning Block Protection, which is disabled in the factory. ■ Write Protect Pin, WP, - When WP is Low, VIL, the protection status that has been configured in the Block Protection Configuration Register is activated. The Block Protection Configuration Register is volatile. Any combination of blocks is possible. Any attempt to program or erase a protected block will be ignored and will return an error in the Status Register (see Table 11., Status Register Bits). ■ Reset/Power-Down Pin, RP, - If the device is held in reset mode (RP at VIL), no program or erase operations can be performed on any block. ■ Program/Erase Enable, VPEN , - VPEN protects all blocks preventing Program and Erase operations from affecting their data. Program/Erase Enable must be kept High (VIH) during all Program/Erase Controller operations, otherwise the operations is not guaranteed to succeed and data may become corrupt. ■ Tuning Block Protection - M58BW032B features a 64 bit password protection for program and erase operations for a fixed number of blocks After power-up or reset the device is tuning protected. An Unlock command is provided to allow program or erase operations in all the blocks. After a device reset the first two kinds of block pro- tection (WP, RP) can be combined to give a flexi- ble block protection. They do not affect the Tuning Block Protection. When the two protections are disabled, WP and RP at VIH, the blocks locked by the Tuning Block Protection cannot be modified. All blocks are protected at power-up. Tuning Block Protection The Tuning Block Protection is a software feature to protect blocks from program or erase opera- tions. It allows the user to lock program and erase operations with a user definable 64 bit code. It is only available on the M58BW032B version. The code is written once in the Tuning Protection Register and cannot be erased. When shipped the flash memory will have the Tuning Protection Code bits set to ‘1'. The user can program a ‘0’ in any of the 64 positions. Once programmed it is not possible to reset a bit to ‘1’ as the cells cannot be erased. The Tuning Protection Register can be programmed at any moment (after providing the correct code), however once all bits are set to ‘0’ the Tuning Protection Code can no longer be al- tered. The Tuning Protection Code locks the program and erase operations of all the blocks except for blocks 12 and 13 for the bottom configuration, and blocks 60 and 61 for the top configuration. The tuning blocks are "locked" if the tuning protec- tion code has not been provided, and “unlocked" once the correct code has been provided. The tun- ing blocks are locked after reset or power-up. The tuning protection status can be monitored in the Status Register. Refer to the Status Register sec- tion. Refer to the Command Interface section for the Tuning Protection Block Unlock and Tuning Pro- tection Program commands. See Appendix A, Fig- ure 24, 25 and 26 for suggested flowcharts for using the Tuning Block Protection commands.

Table 2. Top Boot Block Addresses, Note: 1. Addresses are indicated in 32-bit addressing.

1. TP = Tuning Protected Block, only available for the

Table 3. Bottom Boot Block Addresses, Note: 1. Addresses are indicated in 32-bit Word addressing.

1. TP = Tuning Protected Block, only available for the

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB SIGNAL DESCRIPTIONS See Figure 2., Logic Diagram and Table 1., Signal Names , for a brief overview of the signals connect- ed to this device. Address Inputs (A0-A19).The Address Inputs are used to select the cells to access in the mem- ory array during Bus Read operations either to read or to program data to. During Bus Write oper- ations they control the commands sent to the Command Interface of the internal state machine. Chip Enable must be Low when selecting the ad- dresses. The address inputs are latched on the rising edge of Latch Enable L or Burst Clock K, whichever oc- curs first, in a read operation.The address inputs are latched on the rising edge of Chip Enable, Write Enable or Latch Enable, whichever occurs first in a Write operation. The address latch is transparent when Latch Enable is Low, VIL. The address is internally latched in an Erase or Pro- gram operation. Data Inputs/Outputs (DQ0-DQ31).The Data In- puts/Outputs output the data stored at the selected address during a Bus Read operation, or are used to input the data during a program operation. Dur- ing Bus Write operations they represent the com- mands sent to the Command Interface of the internal state machine. When used to input data or Write commands they are latched on the rising edge of Write Enable or Chip Enable, whichever occurs first. When Chip Enable and Output Enable are both Low, VIL, and Output Disable is at VIH, the data bus outputs data from the memory array, the Elec- tronic Signature, the Block Protection Configura- tion Register, the CFI Information or the contents of Burst Configuration Register or Status Register. The data bus is high impedance when the device is deselected with Chip Enable at VIH, Output En- able at VIH, Output Disable at VIL or Reset/Power- Down at VIL. The Status Register content is output on DQ0-DQ7 and DQ8-DQ31 are at VIL. Chip Enable (E).The Chip Enable, E, input acti- vates the memory control logic, input buffers, de- coders and sense amplifiers. Chip Enable, E, at VIH deselects the memory and reduces the power consumption to the Standby level. Output Enable (G).The Output Enable, G, gates the outputs through the data output buffers during a read operation, when Output Disable GD is at VIH. When Output Enable G is at VIH, the outputs are high impedance independently of Output Dis- able. Output Disable (GD).The Output Disable, GD, deactivates the data output buffers. When Output Disable, GD , is at VIH, the outputs are driven by the Output Enable. When Output Disable, GD, is at VIL, the outputs are high impedance indepen- dently of Output Enable. The Output Disable pin must be connected to an external pull-up resistor as there is no internal pull-up resistor to drive the pin. Write Enable (W).The Write Enable, W, input controls writing to the Command Interface, Input Address and Data latches. Both addresses and data can be latched on the rising edge of Write En- able (also see Latch Enable, L). Reset/Power-Down (RP).The Reset/Power- Down, RP, is used to apply a hardware reset to the memory. A hardware reset is achieved by holding Reset/Power-Down Low, VIL, for at least tPLPH . Writing is inhibited to protect data, the Command Interface and the Program/Erase Controller are re- set. The Status Register information is cleared and power consumption is reduced to the standby level (IDD1 ). The device acts as deselected, that is the data outputs are high impedance. After Reset/Power-Down goes High, VIH, the memory will be ready for Bus Read operations af- ter a delay of tPHEL or Bus Write operations after tPHWL . If Reset/Power-Down goes Low, VIL, during a Block Erase, a Program or a Tuning Protection Program the operation is aborted, in a time of tPL- RH maximum, and data is altered and may be cor- rupted. During Power-up power should be applied simulta- neously to VDD and VDDQ(IN) with RP held at VIL. When the supplies are stable RP is taken to VIH. Output Enable, G, Chip Enable, E, and Write En- able, W, should be held at VIH during power-up. In an application, it is recommended to associate Reset/Power-Down pin, RP, with the reset signal of the microprocessor. Otherwise, if a reset opera- tion occurs while the memory is performing an erase or program operation, the memory may out- put the Status Register information instead of be- ing initialized to the default Asynchronous Random Read. See Table 21 and Figure 17., Reset, Power-Down and Power-up AC Waveform, for more details. Program/Erase Enable (VPEN ).The Program./ Erase Enable input, VPEN , protects all blocks, pre- venting Program and Erase operations from mod- ifying the data. Program/Erase Enable must be kept High (VIH) during all operations when the Pro- gram/Erase Controller is active, otherwise the op- eration is not guaranteed to succeed and data may become corrupt. Latch Enable (L ).The Bus Interface can be con- figured to latch the Address Inputs on the rising edge of Latch Enable, L, for Asynchronous Latch

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB Enable Controlled Read or Write or Synchronous Burst Read operations. In Synchronous Burst Read operations the address is latched on the ac- tive edge of the Clock when Latch Enable is Low, V IL. Once latched, the addresses may change without affecting the address used by the memory. When Latch Enable is Low, VIL, the latch is trans- parent. Latch Enable, L, can remain at VIL for Asynchronous Random Read and Write opera- tions. Burst Clock (K).The Burst Clock, K, is used to synchronize the memory with the external bus dur- ing Synchronous Burst Read operations. Bus sig- nals are latched on the active edge of the Clock. In Synchronous Burst Read mode the address is latched on the first rising clock edge when Latch Enable is Low, VIL, or on the rising edge of Latch Enable, whichever occurs first. During Asynchronous bus operations the Clock is not used. Burst Address Advance (B).The Burst Address Advance, B, controls the advancing of the address by the internal address counter during Synchro- nous Burst Read operations. Burst Address Advance, B, is only sampled on the active clock edge of the Clock when the X-latency time has expired. If Burst Address Advance is Low, VIL, the internal address counter advances. If Burst Address Advance is High, VIH, the internal address counter does not change; the same data remains on the Data Inputs/Outputs and Burst Ad- dress Advance is not sampled until the Y-latency expires. The Burst Address Advance, B, may be tied to VIL. Valid Data Ready (R).The Valid Data Ready output, R, can be used during Synchronous Burst Read operations to identify if the memory is ready to output data or not. The Valid Data Ready output can be configured to be active on the clock edge of the invalid data read cycle or one cycle before. Valid Data Ready, at VIH, indicates that new data is or will be available. When Valid Data Ready is Low, VIL, the previous data outputs remain active. Write Protect (WP).The Write Protect, WP, pro- vides protection against program or erase opera- tions. When Write Protect, WP, is at VIL, the protection status that has been configured in the Block Protection Configuration Register is activat- ed. Program and erase operations to protected blocks are disabled. When Write Protect WP is at VIH all the blocks can be programmed or erased, if no other protection is used. Supply Voltage (VDD ).The Supply Voltage, VDD , is the core power supply. All internal circuits draw their current from the VDD pin, including the Pro- gram/Erase Controller. Output Supply Voltage (VDDQ ).The Output Sup- ply Voltage, VDDQ , is the output buffer power supply for all operations (Read, Program and Erase) used for DQ0-DQ31 when used as outputs. Input Supply Voltage (VDDQIN ).The Input Sup- ply Voltage, VDDIN , is the power supply for all input signal. Input signals are: K, B, L, W, GD, G, E, A0- A18 and D0-D31, when used as inputs. Ground (VSS and VSSQ ).The Ground VSS is the reference for the internal supply voltage VDD . The Ground VSSQ is the reference for the output and input supplies VDDQ, and VDDQIN . It is essential to connect VSS and VSSQ together. Note: A 0.1µF capacitor should be connected between the Supply Voltages, VDD , VDDQ and VDDIN and the Grounds, VSS and VSSQ to decou- ple the current surges from the power supply. The PCB track widths must be sufficient to car- ry the currents required during all operations of the parts, see Table 15., DC Characteristics, for maximum current supply requirements. Don’t Use (DU).This pin should not be used as it is internally connected. Its voltage level can be be- tween VSS and VDDQ or leave it unconnected. Not Connected (NC).This pin is not physically connected to the device.

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB BUS OPERATIONS Each bus operations that controls the memory is described in this section, see Tables 4 and 5 Bus Operations, for a summary. The bus operation is selected through the Burst Configuration Register; the bits in this register are described at the end of this section. On Power-up or after a Hardware Reset the mem- ory defaults to Asynchronous Bus Read and Asyn- chronous Bus Write. No synchronous operation can be performed until the Burst Control Register has been configured. The Electronic Signature, Block Protection Config- uration, CFI or Status Register will be read in asynchronous mode regardless of the Burst Con- trol Register settings. Typically glitches of less than 5ns on Chip Enable or Write Enable are ignored by the memory and do not affect bus operations. Asynchronous Bus Operations For asynchronous bus operations refer to Table 4 together with the following text. Asynchronous Bus Read. Asynchronous Bus Read operations read from the memory cells, or specific registers (Electronic Signature, Block Pro- tection Configuration Register, Status Register, CFI and Burst Configuration Register) in the Com- mand Interface. A valid bus operation involves set- ting the desired address on the Address Inputs, applying a Low signal, V IL, to Chip Enable and Output Enable and keeping Write Enable and Out- put Disable High, VIH. The Data Inputs/Outputs will output the value, see Figure 8., Asynchronous Bus Read AC Waveforms , and Table 16., Asynchronous Bus Read AC Characteristics., for details of when the output becomes valid. Asynchronous Read is the default read mode which the device enters on power-up or on return from Reset/Power-Down. Asynchronous Latch Controlled Bus Read. Asynchronous Latch Controlled Bus Read opera- tions read from the memory cells or specific regis- ters in the Command Interface. The address is latched in the memory before the value is output on the data bus, allowing the address to change during the cycle without affecting the address that the memory uses. A valid bus operation involves setting the desired address on the Address Inputs, setting Chip En- able and Latch Enable Low, VIL and keeping Write Enable High, VIH; the address is latched on the ris- ing edge of Latch Enable. Once latched, the Ad- dress Inputs can change. Set Output Enable Low, VIL, to read the data on the Data Inputs/Outputs; see Figure Figure 9., Asynchronous Latch Con- trolled Bus Read AC Waveforms and Table 17., Asynchronous Latch Controlled Bus Read AC Characteristics, for details on when the output be- comes valid. Note that, since the Latch Enable input is transpar- ent when set Low, VIL, Asynchronous Bus Read operations can be performed when the memory is configured for Asynchronous Latch Enable bus operations by holding Latch Enable Low, VIL throughout the bus operation. Asynchronous Page Read. Asynchronous Page Read operations are used to read from sev- eral addresses within the same memory page. Each memory page is 4 Double-Words and is ad- dressed by the address inputs A0 and A1. Data is read internally and stored in the Page Buff- er. Valid bus operations are the same as Asyn- chronous Bus Read operations but with different timings. The first read operation within the page has identical timings, subsequent reads within the same page have much shorter access times. If the page changes then the normal, longer timings ap- ply again. Page Read does not support Latched Controlled Read. See Figure 10., Asynchronous Page Read AC Waveforms, and Table 18., Asynchronous Page Read AC Characteristics, for details on when the outputs become valid. Asynchronous Bus Write.Asynchronous Bus Write operations write to the Command Interface in order to send commands to the memory or to latch addresses and input data to program. Bus Write operations are asynchronous, the clock, K, is don’t care during Bus Write operations. A valid Asynchronous Bus Write operation begins by setting the desired address on the Address In- puts, and setting Chip Enable, Write Enable and Latch Enable Low, V IL, and Output Enable High, VIH, or Output Disable Low, VIL. The Address In- puts are latched by the Command Interface on the rising edge of Chip Enable or Write Enable, which- ever occurs first. Commands and Input Data are latched on the rising edge of Chip Enable, E, or Write Enable, W, whichever occurs first. Output Enable must remain High, and Output Disable Low, during the whole Asynchronous Bus Write operation. See Figure 11., Asynchronous Write AC Wave- form, and Asynchronous Write and Latch Con- trolled Write AC Characteristics, for details of the timing requirements.

Asynchronous Latch Controlled Bus Write. care during Bus Write operations. Asynchronous Bus Write operation. Output Disable, GD, is at VIL. able or Output Disable inputs. required when the RP input goes High. Table 4. Asynchronous Bus Operations

1. Data, Manufacturer Code, Device Code, Burst Configuration Register, Standby Status and Block Protection Configuration Register

are read using the Asynchronous Bus Read command.

together with the following text. synchronous burst operations. starts from the beginning at address 000000h. input controls the memory burst output. the microprocessor needs to insert wait states. VIH, the last data is still valid. mented at each Burst Clock K rising edge. other higher priority devices. Table 5. Synchronous Burst Read Bus Operations Note: 1. X = Don't Care, VIL or VIH.

1. M15 = 0, Bit M15 is in the Burst Configuration Register.

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB Burst Configuration Register The Burst Configuration Register is used to config- ure the type of bus access that the memory will perform. The Burst Configuration Register is set through the Command Interface and will retain its informa- tion until it is re-configured, the device is reset, or the device goes into Reset/Power-Down mode. The Burst Configuration Register bits are de- scribed in Table 6. They specify the selection of the burst length, burst type, burst X and Y laten- cies and the Read operation. Refer to Figure 5 for examples of synchronous burst configurations. Read Select Bit (M15).The Read Select bit, M15, is used to switch between asynchronous and synchronous Bus Read operations. When the Read Select bit is set to ’1’, Bus Read operations are asynchronous; when the Read Select but is set to ’0’, Bus Read operations are synchronous. On reset or power-up the Read Select bit is set to’1’ for asynchronous accesses. Standby Disable Bit (M14).The Standby Dis- able Bit, M14, is used to disable the Standby mode. When the Standby bit is ‘1’, the device will not enter Standby mode when Chip Enable goes High, V IH. X-Latency Bits (M13-M11).The X-Latency bits are used during Synchronous Bus Read opera- tions to set the number of clock cycles between the address being latched and the first data be- coming available. For correct operation the X-La- tency bits can only assume the values in Table 6., Burst Configuration Register. The X-Latency bits should also be selected in accordance with Note: 1. below Table 6., Burst Configuration Reg- ister. Y-Latency Bit (M9).The Y-Latency bit is used during Synchronous Bus Read operations to set the number of clock cycles between consecutive reads. The Y-Latency value depends on both the X-Latency value and the setting in M9. When the Y-Latency is 1 the data changes each clock cycle; when the Y-Latency is 2 the data changes every second clock cycle. See Table 6., Burst Configuration Register and Note 2.for valid combinations of the Y-Latency, the X-Laten- cy and the Clock frequency. Valid Data Ready Bit (M8).The Valid Data Ready bit controls the timing of the Valid Data Ready output pin, R. When the Valid Data Ready bit is ’0’ the Valid Data Ready output pin is driven Low for the rising clock edge when invalid data is output on the bus. When the Valid Data Ready bit is ’1’ the Valid Data Ready output pin is driven Low one clock cycle prior to invalid data being output on the bus. Wrap Burst Bit (M3).The burst reads can be confined inside the 4 or 8 Word boundary (wrap) or overcome the boundary (no wrap). The Wrap Burst bit is used to select between wrap and no wrap. When the Wrap Burst bit is set to ‘0’ the burst read wraps; when it is set to ‘1’ the burst read does not wrap. Burst Length Bit (M2-M0).The Burst Length bits set the maximum number of Double-Words that can be output during a Synchronous Burst Read operation before the address wraps. Burst lengths of 4 or 8 and continuous burst are available. Table 6., Burst Configuration Register gives the valid combinations of the Burst Length bits that the memory accepts; Table 7., Burst Type Definition, gives the sequence of addresses output from a given starting address for each length. If either a Continuous or a No Wrap Burst Read has been initiated the device will output data syn- chronously. Depending on the starting address, the device activates the Valid Data Ready output to indicate that a delay is necessary before the data is output. If the starting address is aligned to a 4 Double Word boundary, the continuous burst mode will run without activating the Valid Data Ready output. If the starting address is not aligned to a 4 Double Word boundary, Valid Data Ready is activated to indicate that the device needs an in- ternal delay to read the successive words in the ar- ray. M10, M7 to M4 are reserved for future use.

Table 6. Burst Configuration Register is the clock period), , where tLLKH is the value given by the master microcontroller timing specifications.

1. Y latencies can be calculated as: tKHQV + tSYSTEM MARGIN + tKHQV < Y tK.
2. tSYSTEM MARGIN is the time margin required for the calculation.

0 Synchronous Burst Read

1 Asynchronous Read (Default at power-up)

0 Standby Mode Enabled (Default at power-up)

1 Standby Mode Disabled

0 One Burst Clock cycle

1 Two Burst Clock cycles

0 R valid Low during valid Burst Clock edge

1 R valid Low one data cycle before valid Burst Clock edge

111 Continuous

Table 7. Burst Type Definition

Figure 5. Example Burst Configuration X-1-1-1

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB COMMAND INTERFACE All Bus Write operations to the memory are inter- preted by the Command Interface. Commands consist of one or more sequential Bus Write oper- ations. The Commands are summarized in Table 8., Commands. Refer to Table 8 in conjunction with the text descriptions below. Read Memory Array Command The Read Memory Array command returns the memory to Read mode. One Bus Write cycle is re- quired to issue the Read Memory Array command and return the memory to Read mode. Subse- quent read operations will output the addressed memory array data. Once the command is issued the memory remains in Read mode until another command is issued. From Read mode Bus Read commands will access the memory array. Read Electronic Signature Command The Read Electronic Signature command is used to read the Manufacturer Code, the Device Code, the Block Protection Configuration Register and the Burst Configuration Register. One Bus Write cycle is required to issue the Read Electronic Sig- nature command. Once the command is issued, subsequent Bus Read operations, depending on the address specified, read the Manufacturer Code, the Device Code, the Block Protection Con- figuration or the Burst Configuration Register until another command is issued; see Table 9., Read Electronic Signature. Read Query Command The Read Query Command is used to read data from the Common Flash Interface (CFI) Memory Area. One Bus Write cycle is required to issue the Read Query Command. Once the command is is- sued subsequent Bus Read operations, depend- ing on the address specified, read from the Common Flash Interface Memory Area. Read Status Register Command The Read Status Register command is used to read the Status Register. One Bus Write cycle is required to issue the Read Status Register com- mand. Once the command is issued subsequent Bus Read operations read the Status Register un- til another command is issued. The Status Register information is present on the output data bus (DQ0-DQ7) when Chip Enable E and Output Enable G are at VIL and Output Dis- able is at VIH. An interactive update of the Status Register bits is possible by toggling Output Enable or Output Dis- able. It is also possible during a Program or Erase operation, by disactivating the device with Chip Enable at VIH and then reactivating it with Chip En- able and Output Enable at VIL and Output Disable at VIH. The content of the Status Register may also be read at the completion of a Program, Erase or Suspend operation. During a Block Erase, Pro- gram, Tuning Protection Program or Tuning Pro- tection Unlock command, DQ7 indicates the Program/Erase Controller status. It is valid until the operation is completed or suspended. See the section on the Status Register and Table 11 for details on the definitions of the Status Reg- ister bits. Clear Status Register Command The Clear Status Register command can be used to reset bits 1, 3, 4 and 5 in the Status Register to ‘0’. One Bus Write is required to issue the Clear Status Register command. Once the command is issued the memory returns to its previous mode, subsequent Bus Read operations continue to out- put the same data. The bits in the Status Register are sticky and do not automatically return to ‘0’ when a new Pro- gram, Erase, Block Protect or Block Unprotect command is issued. If any error occurs then it is essential to clear any error bits in the Status Reg- ister by issuing the Clear Status Register com- mand before attempting a new Program, Erase or Resume command. Block Erase Command The Block Erase command can be used to erase a block. It sets all of the bits in the block to ‘1’. All previous data in the block is lost. If the block is pro- tected then the Erase operation will abort, the data in the block will not be changed and the Status Register will output the error. Two Bus Write operations are required to issue the command; the first write cycle sets up the Block Erase command, the second write cycle confirms the Block erase command and latches the block address in the internal state machine and starts the Program/Erase Controller. The sequence is aborted if the Confirm command is not given and the device will output the Status Register Data with bits 4 and 5 set to '1'. Once the command is issued subsequent Bus Read operations read the Status Register. See the section on the Status Register for details on the definitions of the Status Register bits. During the Erase operation the memory will only accept the Read Status Register command and the Program/ Erase Suspend command. All other commands will be ignored. The command can be executed using V DD . If VPEN is at VIH, the operation can be performed. If VPEN goes below VIH, the operation aborts, the VPEN Status bit in the Status Register is set to ‘1’ and the command must be re-issued.

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB Typical Erase times are given in Table 10. See Appendix A, Figure 22., Block Erase Flow- chart and Pseudo Code, for a suggested flowchart on using the Block Erase command. Erase All Main Blocks Command The Erase All Main Blocks command is used to erase all 63 Main Blocks, without affecting the Pa- rameter Blocks. Issuing the Erase All Main Blocks command sets every bit in each Main Block to '1'. All data previ- ously stored in the Main Blocks are lost. Two Bus Write cycles are required to issue the Erase All Main Blocks command. The first cycle sets up the command, the second cycle confirms the command and starts the Program/Erase Con- troller. If the Confirm Command is not given the sequence is aborted, and Status Register bits 4 and 5 are set to '1'. If the address given in the second cycle is located in a protected block, the Erase All Main Blocks op- eration aborts. The data remains unchanged in all blocks and the Status Register outputs the error. Once the Erase All Main Blocks command has been issued, subsequent Bus Read operations output the Status Register. See the STATUS REGISTER section for details. During an Erase All Main Blocks operation, only the Read Status Register command is accepted by the memory; any other command are ignored. Erase All Main Blocks, once started, cannot be suspended. The Erase All Main Blocks command can be exe- cuted using V DD . If VPEN is at VIH, the operation will be performed. If VPEN is lower than VIH the op- eration aborts and the Status Register VPEN bit (bit 3) is set to '1'. Program Command The Program command is used to program the memory array. Two Bus Write operations are re- quired to issue the command; the first write cycle sets up the Program command, the second write cycle latches the address and data to be pro- grammed and starts the Program/Erase Control- ler. A program operation can be aborted by writing FFFFFFFFh to any address after the program set- up command has been given. The Program command is also used to program the OTP block. Refer to Table 8., Commands, for details of the address. Once the command is issued subsequent Bus Read operations read the Status Register. See the section on the Status Register for details on the definitions of the Status Register bits. During the Program operation the memory will only accept the Read Status Register command and the Pro- gram/Erase Suspend command. All other com- mands will be ignored. If Reset/Power-down, RP , falls to VIL during pro- gramming the operation will be aborted. The command can be executed using VDD . If VPEN is at VIH, the operation can be performed. If VPEN goes below VIH, the operation aborts, the VPEN Status bit in the Status Register is set to ‘1’ and the command must be re-issued. See Appendix A, Figure 20., Program Flowchart and Pseudo Code, for a suggested flowchart on using the Program command. Write to Buffer and Program Command The Write to Buffer and Program Command makes use of the device’s double Word (32 bit) Write Buffer to speed up programming. Up to eight Double Words can be loaded into the Write Buffer and programmed into the memory. Four successive steps are required to issue the- command. 1. One Bus Write operation is required to set up the Write to Buffer and Program Command. Any Bus Read operations will start to output the Status Register after the 1st cycle. 2. Use one Bus Write operation to write the selected memory Block Address (any address in the block where the values will be programmed can be used) along with the value N on the Data Inputs/Outputs, where N+1 is the number of Words to be programmed. The maximum value of N+1 is 8 Words. 3. Use N+1 Bus Write operations to load the address and data for each Word into the Write Buffer. The address must be between Start Address and Start Address plus N, where Start Address is the first word address. 4. Finally, use one Bus Write operation to issue the final cycle to confirm the command and start the Program operation. If any address is outside the block boundaries or if the correct sequence is not followed, Status Reg- ister bits 4 and 5 are set to ‘1’ and the operation will abort without affecting the data in the memory ar- ray. A protected block must be unprotected using the Blocks Unprotect command. During a Write to Buffer and Program operation the memory will only accept the Read Status Reg- ister and the Program/Erase Suspend commands. All other commands are ignored. The Write to Buffer and Program command can be executed using V DD . If VPEN is at VIH, the operation will be performed. If VPEN is lower than VIH the operation aborts and the Status Register VPEN bit (bit 3) is set to '1'.

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB The Status Register should be cleared before re- issuing the command. Program/Erase Suspend Command The Program/Erase Suspend command is used to pause a Program or Erase operation. The com- mand will only be accepted during a Program or Erase operation. It can be issued at any time dur- ing a program or erase operation. The command is ignored if the device is already in suspend mode. One Bus Write cycle is required to issue the Pro- gram/Erase Suspend command and pause the Program/Erase Controller. Once the command is issued it is necessary to poll the Program/Erase Controller Status bit (bit 7) to find out when the Program/Erase Controller has paused; no other commands will be accepted until the Program/ Erase Controller has paused. After the Program/ Erase Controller has paused, the memory will con- tinue to output the Status Register until another command is issued. During the polling period between issuing the Pro- gram/Erase Suspend command and the Program/ Erase Controller pausing it is possible for the op- eration to complete. Once the Program/Erase Controller Status bit (bit 7) indicates that the Pro- gram/Erase Controller is no longer active, the Pro- gram Suspend Status bit (bit 2) or the Erase Suspend Status bit (bit 6) can be used to deter- mine if the operation has completed or is suspend- ed. For timing on the delay between issuing the Program/Erase Suspend command and the Pro- gram/Erase Controller pausing see Table 10. During Program/Erase Suspend the Read Memo- ry Array, Read Status Register, Read Electronic Signature, Read Query and Program/Erase Re- sume commands will be accepted by the Com- mand Interface. Additionally, if the suspended operation was Erase then the Program, the Write to Buffer and Program, the Set/Clear Block Protec- tion Configuration Register and the Program Sus- pend commands will also be accepted. When a program operation is completed inside a Block Erase Suspend the Read Memory Array command must be issued to reset the device in Read mode, then the Erase Resume command can be issued to complete the whole sequence. Only the blocks not being erased may be read or programmed cor- rectly. See Appendix A, Figure 21., Program Suspend & Resume Flowchart and Pseudo Code, and Figure 23., Erase Suspend & Resume Flowchart and Pseudo Code, for suggested flowcharts on using the Program/Erase Suspend command. Program/Erase Resume Command The Program/Erase Resume command can be used to restart the Program/Erase Controller after a Program/Erase Suspend operation has paused it. One Bus Write cycle is required to issue the Pro- gram/Erase Resume command. See Appendix A, Figure 21., Program Suspend & Resume Flowchart and Pseudo Code, and Figure 23., Erase Suspend & Resume Flowchart and Pseudo Code, for suggested flowcharts on using the Program/Erase Suspend command. Set Burst Configuration Register Command. The Set Burst Configuration Register command is used to write a new value to the Burst Configura- tion Register which defines the burst length, type, X and Y latencies, Synchronous/Asynchronous Read mode. Two Bus Write cycles are required to issue the Set Burst Configuration Register command. The first cycle writes the setup command. The second cy- cle writes the address where the new Burst Con- figuration Register content is to be written, and confirms the command. If the command is not con- firmed, the sequence is aborted and the device outputs the Status Register with bits 4 and 5 set to ‘1’. Once the command is issued the memory re- turns to Read mode as if a Read Memory Array command had been issued. The value for the Burst Configuration Register is always presented on A0-A15. M0 is on A0, M1 on A1, etc.; the other address bits are ignored. Tuning Protection Unlock Command The Tuning Protection Unlock command unlocks the tuning protected blocks by writing the 64bit Tuning Protection Code (M58BW032B only). After a reset or power-up the blocks are locked and so a Tuning Protection Unlock command must be is- sued to allow program or erase operations on tun- ing protected block or to program a new Tuning Protection Code. Read operations output the Sta- tus Register content after the unlock operation has started. The Tuning Protection Code is composed of 64 bits, but the data bus is 32 bits wide so four (2 x 2) write cycles are required to unlock the device. ■ The first write cycle issues the Tuning Protection Unlock Setup command (78h). ■ The second write cycle inputs the first 32 bits of the tuning protection code on the data bus, at address 00000h. Bit 7 of the Status Register should now be checked to verify that the device has successfully stored the first part of the code in the internal reg- ister. If b7 = ‘1’, the device is ready to accept the second part of the code. This does not mean that the first 32 bits match the tuning protection code, simply that it was correctly stored for the compar- ing. If b7 = ‘0’, the user must wait for this bit setting (refer to write cycle AC timings).

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB ■ The third write cycle re-issues the Tuning Protection Unlock Setup command (78h). ■ The fourth write cycle inputs the second 32 bits of the code at address 00001h. Bit 7 of the Status Register should again be checked to verify that the device has successfully stored the second part of the code. When the de- vice is ready (b7 = ‘1’), the tuning protection status can be monitored on Status Register bit0. If b0 = ‘0’ the device is locked; b0 = ‘1’ the device is un- locked. If the device is still locked a Read Memory Array command must be issued before re-issuing the Tuning Protection Unlock command. Device locked means that the 64 bit password is wrong. If the unlock operation is attempted using a wrong code on an already unlocked device, the device becomes locked. Status register bit 4 is set to '1' if there has been a verify failure. Tuning Protection Unlock command aborts if V PEN drops below VIH or RP goes to VIL. Once the device is successfully unlocked, a Read Memory Array command must be issued to return the memory to read mode before issuing any other commands. The user can then program or erase all blocks, depending on WP and VPEN status and on the protection status of each block. At this point, it is also possible to configure a new protec- tion code. To write a new protection code into the device tuning register, the user must perform the Tuning Protection Program sequence. The device can be re-locked with a reset or power-down. See Appendix A, Figure 24, 25 and 26 for suggest- ed flowcharts for using the Tuning Protection Un- lock command. Tuning Protection Program Command. The Tuning Protection Program command is used to program a new Tuning Protection Code which can be configured by the designer of the applica- tion (M58BW032B only). The device should be un- locked by the Tuning Protection Unlock command before issuing the Tuning Protection Program command. Read operations output the Status Register con- tent after the program operation has started. The Tuning Protection Code is composed of 64 bits, but the data bus is 32 bits wide so four (2 x 2) write cycles are required to program the code. ■ The first write cycle issues the Tuning Protection Program Setup command (48h). ■ The second write cycle inputs the first 32 bits of the new tuning protection code on the data bus, at address 00000h. Bit 7 of the Status Register should now be checked to verify that the device has successfully stored the first part of the code in the internal reg- ister. If b7 = ‘1’, the device is ready to accept the second part of the code. If b7 = ‘0’, the user must wait for this bit setting (refer to write cycle AC tim- ings). ■ The third write cycle re-issues the Tuning Protection Program Setup command (48h). ■ The fourth write cycle inputs the second 32 bits of the new code at address 00001h. Bit 7 of the Status Register should again be checked to verify that the device has successfully stored the second part of the code. When the de- vice is ready (b7 = ‘1’). After completion Status Register bit 4 is set to '1' if there has been a pro- gram failure. Programming aborts if VPEN drops below VIH or RP goes to VIL. A Read Memory Array command must be issued to return the memory to read mode before issuing any other commands. Once the code has been changed a device reset or power-down will make the protection active with the new code. See Appendix A, Figure 24, 25 and 26 for suggest- ed flowcharts for using the Tuning Protection Pro- gram command. Set Block Protection Configuration Register Command The Set Block Protection Configuration Register command is used to configure the Block Protec- tion Configuration Register to ‘Protected’, for a specific block. Protected blocks are fully protected from program or erase when WP pin is Low, VIL. The status of a protected block can be changed to ‘Unprotected’ by using the Clear Block Protection Configuration Register command. At power-up, all block are configured as ‘Protected’. Two bus operations are required to issue a Set Block Protection Configuration Register com- mand: ■ The first cycle writes the setup command ■ The second write cycle specifies the address of the block to protect and confirms the command. If the command is not confirmed, the sequence is aborted and the device outputs the Status Register with bits 4 and 5 set to ‘1’. To protect multiple blocks, the Set Block Protec- tion Configuration Register command must be re- peated for each block. Any attempt to re-protect a block already protected does not change its status. Clear Block Protection Configuration Register Command. The Clear Block Protection Configuration Register command is used to configure the Block Protec- tion Configuration Register to ‘Unprotected’, for a

tions to this block, regardless of the WP pin status. tected does not affect its status. Table 8. Commands

1. The Manufacturer Code, the Device Code, the Burst Configuration Register, and the Block Protection Configuration Register of

each block are read using the Read Electronic Signature command.

1. Cycles 1 and 2 input the first 32 bits of the code, cycles 3 and 4 the second 32 bits of the code.

Table 9. Read Electronic Signature Note: 1. x= B or D version of the device.

1. BCR= Burst Configuration Register.
2. SBA is the start address of each block.

Table 10. Program, Erase Times and Program Erase Endurance Cycles

512 Kbit Block Erase 1 2 s

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB STATUS REGISTER The Status Register provides information on the current or previous Program, Erase, Block Protect or Tuning Protection operation. The various bits in the Status Register convey information and errors on the operation. They are output on DQ7-DQ0. To read the Status Register the Read Status Reg- ister command can be issued. The Status Register is automatically read after Program, Erase, Block Protect, Program/Erase Resume commands. The Status Register can be read from any address. The contents of the Status Register can be updat- ed during an erase or program operation by tog- gling the Output Enable or Output Disable pins or by dis-activating (Chip Enable, V IH) and then reac- tivating (Chip Enable and Output Enable, VIL, and Output Disable, VIH.) the device. The Status Register bits are summarized in Table 11., Status Register Bits. Refer to Table 11 in con- junction with the following text descriptions. Program/Erase Controller Status (Bit 7) The Program/Erase Controller Status bit indicates whether the Program/Erase Controller is active or inactive. When the Program/Erase Controller Sta- tus bit is set to ‘0’, the Program/Erase Controller is active; when bit7 is set to ‘1’, the Program/Erase Controller is inactive. The Program/Erase Controller Status is set to ‘0’ immediately after a Program/Erase Suspend com- mand is issued until the Program/Erase Controller pauses. After the Program/Erase Controller paus- es the bit is set to ‘1’. During Program and Erase operations the Pro- gram/Erase Controller Status bit can be polled to find the end of the operation. The other bits in the Status Register should not be tested until the Pro- gram/Erase Controller completes the operation and the bit is set to ‘1’. After the Program/Erase Controller completes its operation the Erase Status (bit5), Program/Tuning Protection Unlock status (bit4) bits should be test- ed for errors. Erase Suspend Status (Bit 6) The Erase Suspend Status bit indicates that an Erase operation has been suspended and is wait- ing to be resumed. The Erase Suspend Status should only be considered valid when the Pro- gram/Erase Controller Status bit is set to ‘1’ (Pro- gram/Erase Controller inactive); after a Program/ Erase Suspend command is issued the memory may still complete the operation rather than enter- ing the Suspend mode. When the Erase Suspend Status bit is set to ‘0’, the Program/Erase Controller is active or has com- pleted its operation; when the bit is set to ‘1’, a Pro- gram/Erase Suspend command has been issued and the memory is waiting for a Program/Erase Resume command. When a Program/Erase Resume command is is- sued the Erase Suspend Status bit returns to ‘0’. Erase Status (Bit 5) The Erase Status bit can be used to identify if the memory has failed to verify that the block has erased correctly. The Erase Status bit should be read once the Program/Erase Controller Status bit is High (Program/Erase Controller inactive). When the Erase Status bit is set to ‘0’, the memory has successfully verified that the block has erased correctly. When the Erase Status bit is set to ‘1’, the Program/Erase Controller has applied the maximum number of pulses to the block and still failed to verify that the block has erased correctly. Once set to ‘1’, the Erase Status bit can only be re- set to ‘0’ by a Clear Status Register command or a hardware reset. If set to ‘1’ it should be reset be- fore a new Program or Erase command is issued, otherwise the new command will appear to fail. Program/ Write to Buffer and Program/Tuning Protection Unlock Status (Bit 4) The Program/Write to Buffer and Program/Tuning Protection Unlock Status bit is used to identify a Program failure, a Write to Buffer and Program failure or a Tuning Protection Code verify failure. Bit4 should be read once the Program/Erase Con- troller Status bit is High (Program/Erase Controller inactive). When bit4 is set to ‘0’ the memory has successful- ly verified that the device has programmed cor- rectly or that the correct Tuning Protection Code has been written. When bit4 is set to ‘1’ the device has failed to verify that the data has been pro- grammed correctly or that the correct Tuning Pro- tection code has been written. Once set to 1’, the Program Status bit can only be reset to ‘0’ by a Clear Status Register command or a hardware reset. If set to ‘1’ it should be reset be- fore a new Program or Erase command is issued, otherwise the new command will appear to fail. V PEN Status (Bit 3). The VPEN Status bit can be used to identify if a program or erase operation has been attempted when VPEN is Low, VIL. When Bit 3 is set to ‘0’ no program or erase oper- ations have been attempted with VPEN Low, VIL, since the last Clear Status Register command, or hardware reset. When Bit 3 is set to ‘1’ a program or erase opera- tion has been attempted with VPEN Low, VIL. Once set to ‘1’, Bit 3 can only be reset by an Clear Status Register command or a hardware reset. If set to ‘1’ it should be reset before a new program

command will appear to fail. than entering the Suspend mode. to modify the contents of a protected block. unlocked (Tuning Protection is disabled). locked and so bit0 is set to ‘0’. Table 11. Status Register Bits Note: 1. For the M58BW032D version the Tuning Protection Status bit is always set to ‘1’.

4 Program Status,

Table 12. Absolute Maximum Ratings Note: 1. Compliant with the ECOPACK® 7191395 specification for Lead-free soldering processes.

Table 15. DC Characteristics Note: 1. The Standby mode can be disabled by setting the Standby Disable bit (M14) of the Burst Configuration Register to ‘1’.

Figure 8. Asynchronous Bus Read AC Waveforms Table 16. Asynchronous Bus Read AC Characteristics. Note: 1. Output Enable G may be delayed up to tELQV - tGLQV after the falling edge of Chip Enable E without increasing tELQV .

Figure 9. Asynchronous Latch Controlled Bus Read AC Waveforms Table 17. Asynchronous Latch Controlled Bus Read AC Characteristics

Figure 10. Asynchronous Page Read AC Waveforms Table 18. Asynchronous Page Read AC Characteristics Note: For other timings see Table 16., Asynchronous Bus Read AC Characteristics..

Figure 11. Asynchronous Write AC Waveform

Figure 12. Asynchronous Latch Controlled Write AC Waveform

Table 19. Asynchronous Write and Latch Controlled Write AC Characteristics

Figure 13. Synchronous Burst Read (Data Valid from ’n’ Clock Rising Edge) Note: n depends on Burst X-Latency.

Table 20. Synchronous Burst Read AC Characteristics Note: 1. Data output should be read on the valid clock edge.

1. For other timings see Table 16., Asynchronous Bus Read AC Characteristics..

Figure 14. Synchronous Burst Read (Data Valid from ’n’ Clock Rising Edge) Note: For set up signals and timings see Synchronous Burst Read.

Figure 17. Reset, Power-Down and Power-up AC Waveform Table 21. Reset, Power-Down and Power-up AC Characteristics Note: 1. This time is tPHEL + tAVQV or tPHEL + tELQV .

Figure 18. LBGA80 10x12mm - 8x10 ball array, 1mm pitch, Bottom View Package Outline Note: Drawing is not to scale. Table 22. LBGA80 10x12mm - 8x10 ball array, 1mm pitch, Package Mechanical Data

Figure 19. PQFP80 - 80 lead Plastic Quad Flat Pack, Package Outline Note: Drawing is not to scale. Table 23. PQFP80 - 80 lead Plastic Quad Flat Pack, Package Mechanical Data

Table 24. Ordering Information Scheme Note: Devices are shipped from the factory with the memory content bits erased to ’1’. vice, please contact the ST Sales Office nearest to you.

Figure 20. Program Flowchart and Pseudo Code Note: 1. If an error is found, the Status Register must be cleared before further P/E operations.

Figure 21. Program Suspend & Resume Flowchart and Pseudo Code

Figure 22. Block Erase Flowchart and Pseudo Code Note: 1. If an error is found, the Status Register must be cleared before further P/E operations.

Figure 23. Erase Suspend & Resume Flowchart and Pseudo Code

Figure 24. Unlock Device and Change Tuning Protection Code Flowchart

Figure 25. Unlock Device and Program a Tuning Protected Block Flowchart

Figure 26. Unlock Device and Erase a Tuning Protected Block Flowchart

Figure 27. Power-up Sequence to Burst the Flash

Figure 28. Command Interface and Program Erase Controller Flowchart (a)

Figure 29. Command Interface and Program Erase Controller Flowchart (b)

Figure 30. Command Interface and Program Erase Controller Flowchart (c)

Figure 31. Command Interface and Program Erase Controller Flowchart (d)

Figure 32. Command Interface and Program Erase Controller Flowchart (e)

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB

REVISION HISTORY

Table 25. Document Revision History 20-Oct-2003 1.0 First Issue. Table 5, DC Characteristics. 10., Program, Erase Times and Program Erase Endurance Cycles. 27-Apr-2004 2.0 A19 added in Figure 4.PQFP Connections (Top view through package). Table 6.Burst Configuration Register, Note 1 updated. DQ8-DQ15 and R signal names updated in Table 1., Signal Names. Description of Valid Data Ready (R).signal updated. Burst Length Bit (M2-M0).paragraph updated in Burst Configuration Register section. Clear Block Protection Configuration Register Command. updated. Standby Status removed from Table 9., Read Electronic Signature. Definition of bit 4 updated in STATUS REGISTER section. 05-Nov-2004 4.0 Datasheet status changed to Preliminary Data.

M58BW032BT, M58BW032BB, M58BW032DT, M58BW032DB Information furnished is believed to be accurate and reliable. However, STMicroelectronics assumes no responsibility for the consequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent or patent rights of STMicroelectronics. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all information previously supplied. STMicroelectronics products are not authorized for use as critical components in life support devices or systems without express written approval of STMicroelectronics. The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners © 2004 STMicroelectronics - All rights reserved STMicroelectronics group of companies Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan - Malaysia - Malta - Morocco - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America