Embedded controller: Difference between revisions
RafaelOrtiz (talk | contribs) mNo edit summary |
|||
| Line 9: | Line 9: | ||
== Introduction == |
== Introduction == |
||
The XO laptop uses a small micro-controller, an ENE KB3700 ([[Image:KB3700-ds-01.pdf]]), to control the battery charging operation and perform other tasks associated with starting and stopping the laptop. |
|||
| ⚫ | |||
This Embedded Controller (EC) consists of a 8051 micro-controller, a dedicated LPC interface to communicate with the processor, and an SPI Flash ROM interface. The SPI Flash ROM supports two code segments, and a table of [[Manufacturing Data]]. The EC supports the Boot Hub Protocol, allowing the XO's main processor to boot from one of the code segments in the SPI Flash. |
|||
The code running on the XO's EC, while heavily modified and supported by OLPC, was originally written by two different companies. OLPC has had no success convincing those companies to open source their code. |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
=== Background === |
=== Background === |
||
Revision as of 05:13, 1 February 2009
Introduction
The XO laptop uses a small micro-controller, an ENE KB3700 (File:KB3700-ds-01.pdf), to control the battery charging operation and perform other tasks associated with starting and stopping the laptop. This Embedded Controller (EC) consists of a 8051 micro-controller, a dedicated LPC interface to communicate with the processor, and an SPI Flash ROM interface. The SPI Flash ROM supports two code segments, and a table of Manufacturing Data. The EC supports the Boot Hub Protocol, allowing the XO's main processor to boot from one of the code segments in the SPI Flash.
The code running on the XO's EC, while heavily modified and supported by OLPC, was originally written by two different companies. OLPC has had no success convincing those companies to open source their code.
The OLPC community is now working in an Open Source implementation of the XO's Embedded Controller firmware.
We have chosen to implement the firmware in C, using SDCC as our compiler. Efforts are also under way to have CamelForth, a Forth implementation for the 8051, run on the KB3700.
Background
The EC, implemented as a KB3700, has a paramount importance in controlling the XO when the CPU is not active. To do so, the KB3700 communicates with the CPU via the EC protocol, this protocol is managed in the ports 0x66 and 0x62 of the KB3700. These two ports are serially connected with the 0x6C and 0x68 ports of the CPU (for more info check Ec specification).
The KB3700 also communicates with the Maxim DS2756 battery fuel gauge IC within the battery pack, via the 1-wire Dallas protocol. DS2756 data sheet.
One can deduce part of the internal state of the EC using ec-dump.fth under OpenFirmware. Running the ec-dump script gives us valuable data about internals of the EC, being the EC Register Settings.
The procedure to run ec-dump over internet in a wireless connection is:
ok wifi media lab 802.11 *change it to your name AP ok fl http:\\18.85.2.147\~joel\ec-dump.fth *change to your AP IP direction
Running ec-dump over internet and saving the file in a USB key:
ok wifi media lab 802.11 *change it to your name AP ok fload http:\\18.85.2.147\~rafael\to-file.fth ok to-file u:\ec-dump fload http:\\18.85.2.147\~joel\ec-dump.fth
OpenEC firmware project
OpenEC is an effort for an open implementation of the firmware on the EC. It currently is in an early stage and not functional yet.
Related Documentation
- See other articles in Category:EC