- Thread Starter
- #121
What are some of the differences between revisions E3, E4 and E6
The E3 Venice ends with BP in the OPN code, whereas the E6 Venice ends with BW.
E.g.
Desktop A64 939 (90 nm SOI DSL) Venice
Rev E3 Venice
3000+: ADA3000DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 1.8 GHz, x9, 67 W
3200+: ADA3200DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 2.0 GHz, x10, 67 W
3500+: ADA3500DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 2.2 GHz, x11, 67 W
3800+: ADA3800DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 2.4 GHz, x12, 89 W
Rev E6 Venice
3000+: ADA3000DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 1.8 GHz, x9, 67 W
3200+: ADA3200DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 2.0 GHz, x10, 67 W
3500+: ADA3500DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 2.2 GHz, x11, 67 W
3800+: ADA3800DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 2.4 GHz, x12, 89 W
...
E.g. as of 0508, the 5-letter stepping:
CBBLE (Venice E3)
LBBLE (Venice E3)
YBBLE (Venice E3)
LBBWE (Venice E6)
...
Other E4 such as FX and Manchster, E6 such as Toledo are
E.g.
Desktop A64 X2 939 (90 nm SOI DSL) Toledo
3800+: ADA3800DAA5CD 1.35/1.4V (JH E6 rev, 00020F32h) Toledo, 2x 512 KB L2, 2.0 GHz, x10, 89 W (512 KB L2 per core "disabled")
4400+: ADA4400DAA6CD 1.35/1.4V (JH E6 rev, 00020F32h) Toledo, 2x 1 MB L2, 2.2 GHz, x11, 110 W
4800+: ADA4800DAA6CD 1.35/1.4V (JH E6 rev, 00020F32h) Toledo, 2x 1 MB L2, 2.4 GHz, x12, 110 W
Desktop A64 X2 939 (90 nm SOI DSL) Manchester
3800+: ADA3800DAA5BV 1.35/1.4V (BH E4 rev, 00020FB1h) Manchester, 2x 512 KB L2, 2.0 GHz, x10, 89 W
4200+: ADA4200DAA5BV 1.35/1.4V (BH E4 rev, 00020FB1h) Manchester, 2x 512 KB L2, 2.2 GHz, x11, 89 W
4600+: ADA4600DAA5BV 1.35/1.4V (BH E4 rev, 00020FB1h) Manchester, 2x 512 KB L2, 2.4 GHz, x12, 89 W
Desktop A64 939 (90 nm SOI DSL) San Diego
3500+: ADA3500DAA4BN 1.35/1.4V (SH E4 rev, 00020F71h) SanDiego, 512 KB L2, 2.2 GHz, x11, 67 W (512 KB L2 "disabled")
3700+: ADA3700DAA5BN 1.35/1.4V (SH E4 rev, 00020F71h) SanDiego, 1 MB L2, 2.2 GHz, x11, 89 W
4000+: ADA4000DAA5BN 1.35/1.4V (SH E4 rev, 00020F71h) SanDiego, 1 MB L2, 2.4 GHz, x12, 89 W
From an AMD tech doc, the differences between
E3 (DH-E3 Venice) on one hand,
E4 (SH-E4 FX, BH-E4 Manchester) and
E6 (includes DH-E6 Venice and JH-E6 Toledo) on the other,
are Erratum 113, 114 and 116.
E3 had the erratum 113, 114 and 116,
the SH-E4 (FX), BH-E4 (Manchester) and the DH-E6 (Venice), JH-E6 (Toledo) have them fixed.
The BH-E4, JH-E6 now have the Erratum 123 and 124 (for dual core).
For details about the various erratum, refer to the AMD tech doc 25759.
Further, these errata 123 and 124 for the E4 and E6 reveisions are logical changes and fixes, so IMO (not supported by actual data), the overclockability of these different revisions per core, which is mainly determined by the physical circuits, transistor properties and manufacturing process, should be about the same for these different revisions, except the normal variability presented among the silicon wafers over time.
DH-E3 had these three 113, 114, 116 erratum, and
the newer revisions such as SH-E4, BH-E4, SH-E5, DH-E6 and JH-E6 have them fixed.
Dual core overclockability is related to its associated single core like this.
Dual core overclocking estimation from single core statistic
A64 940, 754, 939 CPU Models, OPN code, rating
Revisions and steppings
How to identify the physical core of an A64 (post 86)
The E3 Venice ends with BP in the OPN code, whereas the E6 Venice ends with BW.
E.g.
Desktop A64 939 (90 nm SOI DSL) Venice
Rev E3 Venice
3000+: ADA3000DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 1.8 GHz, x9, 67 W
3200+: ADA3200DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 2.0 GHz, x10, 67 W
3500+: ADA3500DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 2.2 GHz, x11, 67 W
3800+: ADA3800DAA4BP 1.35/1.4V (DH E3 rev, 00020FF0h) Venice, 512 KB L2, 2.4 GHz, x12, 89 W
Rev E6 Venice
3000+: ADA3000DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 1.8 GHz, x9, 67 W
3200+: ADA3200DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 2.0 GHz, x10, 67 W
3500+: ADA3500DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 2.2 GHz, x11, 67 W
3800+: ADA3800DAA4BW 1.35/1.4V (DH E6 rev, 00020FF2h) Venice, 512 KB L2, 2.4 GHz, x12, 89 W
...
E.g. as of 0508, the 5-letter stepping:
CBBLE (Venice E3)
LBBLE (Venice E3)
YBBLE (Venice E3)
LBBWE (Venice E6)
...
Other E4 such as FX and Manchster, E6 such as Toledo are
E.g.
Desktop A64 X2 939 (90 nm SOI DSL) Toledo
3800+: ADA3800DAA5CD 1.35/1.4V (JH E6 rev, 00020F32h) Toledo, 2x 512 KB L2, 2.0 GHz, x10, 89 W (512 KB L2 per core "disabled")
4400+: ADA4400DAA6CD 1.35/1.4V (JH E6 rev, 00020F32h) Toledo, 2x 1 MB L2, 2.2 GHz, x11, 110 W
4800+: ADA4800DAA6CD 1.35/1.4V (JH E6 rev, 00020F32h) Toledo, 2x 1 MB L2, 2.4 GHz, x12, 110 W
Desktop A64 X2 939 (90 nm SOI DSL) Manchester
3800+: ADA3800DAA5BV 1.35/1.4V (BH E4 rev, 00020FB1h) Manchester, 2x 512 KB L2, 2.0 GHz, x10, 89 W
4200+: ADA4200DAA5BV 1.35/1.4V (BH E4 rev, 00020FB1h) Manchester, 2x 512 KB L2, 2.2 GHz, x11, 89 W
4600+: ADA4600DAA5BV 1.35/1.4V (BH E4 rev, 00020FB1h) Manchester, 2x 512 KB L2, 2.4 GHz, x12, 89 W
Desktop A64 939 (90 nm SOI DSL) San Diego
3500+: ADA3500DAA4BN 1.35/1.4V (SH E4 rev, 00020F71h) SanDiego, 512 KB L2, 2.2 GHz, x11, 67 W (512 KB L2 "disabled")
3700+: ADA3700DAA5BN 1.35/1.4V (SH E4 rev, 00020F71h) SanDiego, 1 MB L2, 2.2 GHz, x11, 89 W
4000+: ADA4000DAA5BN 1.35/1.4V (SH E4 rev, 00020F71h) SanDiego, 1 MB L2, 2.4 GHz, x12, 89 W
From an AMD tech doc, the differences between
E3 (DH-E3 Venice) on one hand,
E4 (SH-E4 FX, BH-E4 Manchester) and
E6 (includes DH-E6 Venice and JH-E6 Toledo) on the other,
are Erratum 113, 114 and 116.
E3 had the erratum 113, 114 and 116,
the SH-E4 (FX), BH-E4 (Manchester) and the DH-E6 (Venice), JH-E6 (Toledo) have them fixed.
The BH-E4, JH-E6 now have the Erratum 123 and 124 (for dual core).
For details about the various erratum, refer to the AMD tech doc 25759.
The two errata 123 and 124 are documented in this AMD tech doc 25759, page 80 and 81 respectively.AMD tech doc 25759.pdf said:113 Enhanced Write-Combining Feature Causes System Hang
114 DDR Data Pin Drive Strength Also Affects Command/Address Pins
116 DDR Chip Selects Tristated One Clock Early in Power Down Mode
...
123 Bypassed Reads May Cause Data Corruption or System Hang in Dual Core Processors
124 STPCLK Throttling Causes Violation of VDD_ac Specification on Some Dual-Core Processors
Further, these errata 123 and 124 for the E4 and E6 reveisions are logical changes and fixes, so IMO (not supported by actual data), the overclockability of these different revisions per core, which is mainly determined by the physical circuits, transistor properties and manufacturing process, should be about the same for these different revisions, except the normal variability presented among the silicon wafers over time.
DH-E3 had these three 113, 114, 116 erratum, and
the newer revisions such as SH-E4, BH-E4, SH-E5, DH-E6 and JH-E6 have them fixed.
Dual core overclockability is related to its associated single core like this.
Dual core overclocking estimation from single core statistic
A64 940, 754, 939 CPU Models, OPN code, rating
Revisions and steppings
How to identify the physical core of an A64 (post 86)
Last edited: