Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Jun 2007 12:58:57 -0700
From:      Darren Pilgrim <phi@evilphi.com>
To:        David King <dking@ketralnis.com>
Cc:        freebsd-chat@freebsd.org
Subject:   Re: Where software meets hardware..
Message-ID:  <467D7B81.1040305@evilphi.com>
In-Reply-To: <B93C45F6-0D62-4EE6-946E-9E8DF277A37D@ketralnis.com>
References:  <200706211233.l5LCXuYv082845@lurza.secnetix.de> <B93C45F6-0D62-4EE6-946E-9E8DF277A37D@ketralnis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
David King wrote:
>> The BIOS is also simply a piece of software, stored
>> in a chip on the mainboard.
> 
> In memory, a program's bits are represented by the voltages of  
> transistors in particular places on a DRAM chip. On a CD, by the  
> width of pits in the surface of the CD. In chips like BIOS and other  
> types of firmware that don't need power to maintain their state but  
> that can be re-written, how are the bits physically represented, and  
> how are they read out to memory?

Look up hot-carrier injection and quantum electron tunneling.  Basically 
such devices use over-voltage to cause electron migration within the 
device.  The migrated electrons result in measurable changes in the 
electrical characteristics of the gate (i.e., threshold voltage).  The 
process is reversable but destructive, since you can't put the electrons 
back exactly where they were before.  This is also why EEPROMs and flash 
devices have write-count lifetimes.

-- 
Darren Pilgrim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?467D7B81.1040305>