Embedded controller: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (Reverted edits by RafaelOrtiz (Talk); changed back to last version by Php5)
mNo edit summary
Line 3: Line 3:
{{OBX source dev|projects/openec}}
{{OBX source dev|projects/openec}}
{{Olpcboxbottom}}
{{Olpcboxbottom}}
[[Category:Firmware]]
[[Category:SoC Project]]
{{OLPC}}
= Introduction =
= Introduction =


OLPC is now working in an Open implementation of the XOs Embedded Controller
OLPC is now working in an Open implementation of the XOs Embedded Controller.
The code of the EC is programed to a [[Image:KB3700-ds-01.pdf]] that has an 8051 microprocessor, for the code to be open we need to compile everything in [[SDCC]] or OFW.
The need for an open implementation is due to the fact that the actual EC has some flakiness in the recovery process.(among many other things).
An example of a bug of the old EC can be found in {{ticket|477}}


== Background ==
== Background ==

The EC is programed in the KB3700 and it has a paramount importance in controlling the XO when the CPU is not active.
For doing so the KB3700 has to communicate with the CPU via the [[Revised_EC_Port_6C_Command_Protocol|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]]).
But the KB3700 has to communicate also with the DS2657 (The battery charger) via the 1 wire Dallas protocol.
One can deduce some of the inside programing of the EC via the [http://dev.laptop.org/~rafael/EcDump1.fth ec-dump.fth] under OpenFirmware.
Running the ec-dump script give us valuable data about internals of the ec, mostly 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\~rafael\EcDump1.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\~rafael\EcDump1.fth

= Actual development =
= Actual development =


All the work is going to be in the git repository [http://dev.laptop.org/git.do?p=projects/openec;a=summary]
All the work is going to be in the git repository [http://dev.laptop.org/git.do?p=projects/openec;a=summary OpenEC]

To get this code in your machine please do:
git-clone git://dev.laptop.org/projects/openec

''For info check [[Importing_your_project]]''

== Desired Features ==
* Failsafe Code
* Easy debugging
* Forth/C implementation.
* GCC compilable.


== Preliminary Work ==
== To Do ==
* Testin


==Mail list==
* http://dev.laptop.org/~joel/ec-test.git/


* http://lists.laptop.org/listinfo/openec


[[Category:EC]]
[[Category:EC]]

Revision as of 01:37, 23 August 2007

  english | español | 한국어 HowTo [ID# 61059]  +/-  
  This page is monitored by the OLPC team.

Introduction

OLPC is now working in an Open implementation of the XOs Embedded Controller. The code of the EC is programed to a File:KB3700-ds-01.pdf that has an 8051 microprocessor, for the code to be open we need to compile everything in SDCC or OFW. The need for an open implementation is due to the fact that the actual EC has some flakiness in the recovery process.(among many other things). An example of a bug of the old EC can be found in #477


Background

The EC is programed in the KB3700 and it has a paramount importance in controlling the XO when the CPU is not active. For doing so the KB3700 has to communicate 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). But the KB3700 has to communicate also with the DS2657 (The battery charger) via the 1 wire Dallas protocol. One can deduce some of the inside programing of the EC via the ec-dump.fth under OpenFirmware. Running the ec-dump script give us valuable data about internals of the ec, mostly 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\~rafael\EcDump1.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\~rafael\EcDump1.fth

Actual development

All the work is going to be in the git repository OpenEC

To get this code in your machine please do:

git-clone git://dev.laptop.org/projects/openec

For info check Importing_your_project

Desired Features

  • Failsafe Code
  • Easy debugging
  • Forth/C implementation.
  • GCC compilable.

To Do

  • Testin

Mail list