Intel launches Atom C2000 revision C0 - fixing AVR54

Terry Kennedy

Well-Known Member
Jun 25, 2015
1,067
505
113
New York City
www.glaver.org
Revision history "April 2018"
Time machine :)
And they changed the specification to unsupport reconfiguring the LPC pins as GPIO:

"All of the LPC interface signals (Table 10) are defined as muxed with GPIO signals. This implies that if the LPC interface is not used in your design these signals can be GPIO signals. This specification change removes the muxed support of GPIO signals for all LPC signals except LPC_CLKOUT1. These signals must be left in their default (LPC) state and not de-selected via software to be GPIO pins. Bits [26:21] and bits [29:28] in register SC_USE_SEL should not be set to 1."

<rant>Why does Intel disable text copy when just about any PDF utility allows that to be enabled?</rant>
 

xnaas

New Member
Mar 24, 2017
7
0
1
Texas
xnaas.info
Good on Intel for fixing that problem. Sucks it took so long and so much damage has been caused to companies and businesses...but hey, stuff happens. Hopefully this inspires them to do some additional testing before releasing the C3000 CPUs... :)
 

TJ Ferdon

New Member
May 5, 2017
1
0
1
59
Good on Intel for fixing that problem.
However they have "found" this error after years of production and "exactly" before before announcing the new c3000's...

Sucks it took so long and so much damage has been caused to companies and businesses...but hey, stuff happens.
And the end users? They have suffered the greatest damage, because they can not claim any damage from Intel directly (as can the big companies that have implemented this faulty processor familiy) and for the majority of cases, until now, the companies itself that have implemented these processors during the last years on their products, don't want to replace the units affected....so for end users the damage remains, they have to "pay" for something that it's not their fault.

What a sad situation for the entire industry...stuff happens, sure, but in this situation there are the usual wrong behaviors.

Just my 2cents
 
Last edited: