XO 1.75 B1: Difference between revisions
m (→Description) |
|||
(72 intermediate revisions by 10 users not shown) | |||
Line 4: | Line 4: | ||
== Description == |
== Description == |
||
The B1 are the fourth prototypes of the [[Hardware# |
The B1 are the fourth prototypes of the [[Hardware#XO-1.75_Laptop|XO-1.75]] built. Electrically, these are [[XO1.75_A3_B1_Changes#A3_Electrical_Fixes|very similar]] to the [[XO_1.75_A3|A3 prototypes]]. Several hundred were made in July, 2011, for distribution to software developers. |
||
Due to a flaw in the security system, each laptop bricked itself ten days after manufacture. The fix is to connect a serial cable and flash a new version of firmware after Q4B05. See [[XO 1.75 11089 Fix]] for how to fix, and see <trac>11089</trac> for technical details. |
|||
Remember, this is a prototype, there are design faults. See below for hardware restrictions. See http://dev.laptop.org/1.75 for tickets that are not closed, in the XO-1.75 firmware or software milestones. |
|||
== Identification == |
== Identification == |
||
These are the first fully assembled XO-1.75 laptops. While production 1.75 laptops will be identifiable by two rows of raised dots on the hinge cover, B1 laptops only have three dots (identical to the XO-1.5). |
These are the first fully assembled XO-1.75 laptops. While production 1.75 laptops will be identifiable by two rows of raised dots on the hinge cover, B1 laptops only have three dots (identical to the XO-1.5). |
||
One way of identifying them is the slow blink of the WLAN LED when they are associated, due to the Outdoor Light Sensor turning the LED off to take a reading (this was moved to the storage LED in C1). |
|||
Two versions were built: |
Two versions were built: |
||
* Motherboard ID 1B1 --- these units do not have an internal full-size SD card slot, and instead provide SDRAM for use by the [[DCON]]. These units are assembled into a green/white case with a non-membrane keyboard. |
* Motherboard ID 1B1 --- these units do not have an internal full-size SD card slot, and instead provide SDRAM for use by the [[DCON]]. These units are assembled into a green/white case with a non-membrane keyboard. Some of these units are also equipped with a multitouch-capable projected capacitance touchscreen to be used as XO-3 development kits (no touchscreen is planned on XO-1.75). |
||
* Motherboard ID 1B2 --- these units have an internal full-size SD card slot, but no SDRAM for the DCON. These units are assembled into green/white cases with membrane keyboards. |
* Motherboard ID 1B2 --- these units have an internal full-size SD card slot, but no SDRAM for the DCON. These units are assembled into green/white cases with membrane keyboards. |
||
Line 20: | Line 26: | ||
If you [[Disassembly_top|disassemble the laptop (instructions)]], you will see: |
If you [[Disassembly_top|disassemble the laptop (instructions)]], you will see: |
||
[[Image:XO1. |
[[Image:XO1.75_B1_mobo_annotated_bot.png|800px|center|Annotated image of XO-1.75 motherboard]] |
||
== Software == |
|||
* [[Media:XO1.75_A2_mobo_top.jpg|Photo of motherboard]] |
|||
See [[XO_1.75#Software|XO-1.75 software]]. |
|||
⚫ | |||
XO-1.75 B1 use Q4Bxx firmware releases. These will not work on an XO-1 or XO-1.5. The current firmware release for B1 is [[http://dev.laptop.org/~wmb/q4b04.rom|Q4B04]]. |
|||
See [[XO_1.75#Software_Restrictions|XO-1.75 general software restrictions]]. The only XO-1.75 B1 specific software restrictions are: |
|||
There are three distinct pieces of software on the XO: |
|||
* [[Embedded_controller|Embedded controller (EC)]] firmware |
|||
* [[Open_Firmware|Open Firmware (OFW)]] |
|||
* Operating System and UI |
|||
* a very slow accelerometer data rate, due to a workaround for a hardware problem that caused [[#Occasional_accelerometer_hangs|occasional read hangs]], |
|||
Each resides in a different storage device on the motherboard, and can be updated individually --- instructions are included below. |
|||
* if the unit has a forgetful RTC (<trac>10999</trac>) then several date and time related software features may fail. |
|||
== Firmware Restrictions == |
|||
At this point, OFW automatically upgrades the EC firmware at boot time, if the installed version is older than the version included in OFW. The laptop must have both a charged battery and external power supplied at boot time for this to happen. |
|||
=== White Screen === |
|||
Sometime in the future, the OS image will automatically upgrade OFW if necessary. This is not currently working (<trac>11071</trac>). |
|||
If you just unwrapped an XO-1.75 B1, tried to boot it, and got a white screen, you're experiencing <trac>11089</trac>. Instructions for fixing this are [[XO_1.75_11089_Fix|here]]. The fix is permanent. |
|||
=== White Screen with XO only, then reboot === |
|||
===Upgrading OFW=== |
|||
Q4B08 and earlier did not indicate when EC reflash was in progress. Fixed in Q4B09. <trac>11117</trac>. |
|||
== Hardware Restrictions == |
|||
To upgrade the version of [[Open Firmware]], place a recent release of the Q4XYY firmware onto an SD device, and place it in the external SD slot. |
|||
⚫ | |||
Interrupt the [[Open_Firmware|Open Firmware (OFW)]] boot process by pressing the ESC key. |
|||
===Loss of first character on resume=== |
|||
Type (assuming a q4b04 release): |
|||
Unfortunately, we learned too late that the Armada 610 SoC takes a while to wake up from a deep sleep. When a user wakes an XO-1.75 B1/C1 laptop with a keypress, the first key code sent by the keyboard is lost by the SoC (<trac>11401</trac>). This was fixed by having the EC stall the keyboard until the SoC wakes, but requires that [[XO_1.75_B1_ECOs#Loss_of_first_keypress_when_suspended|resistors be added to the board]]. |
|||
flash ext:\q4b04.rom |
|||
Reboot by holding down the power button once this is completed. If you need to do this to a bare motherboard, you can use the flash! command which skips the tests for two sources of power. |
|||
===Upgrading the EC code=== |
|||
Download the latest EC code from: [http://dev.laptop.org/pub/ec/ http://dev.laptop.org/pub/ec/]. It should be prefixed by "cl2" (e.g. cl2-4.0.2.02.img). Place this file on a USB stick or SD card, and insert it into the laptop being reprogrammed. |
|||
From OFW, type: |
|||
flash-ec u:\your_filename.img |
|||
If you need to do this to a bare motherboard, you can use the flash-ec! command which skips the tests for two sources of power. |
|||
===Upgrading Linux=== |
|||
Linux images for the B1 are available at [http://build.laptop.org/F13-arm/ http://build.laptop.org/F13-arm/]. |
|||
====Installing from OpenFirmware using USB==== |
|||
You will need the .zd version of the OS image. Download it, then: |
|||
# Place the image on a USB stick, and insert it into any of the XO-1.75 laptop's USB ports. |
|||
# Get the [[Ok]] prompt, |
|||
# Install onto the internal SD card, by typing: |
|||
fs-update u:\os19.zd |
|||
====Installing from OpenFirmware using SD card==== |
|||
You will need the .zd version of the OS image. Download it, then: |
|||
# Place the image on an SD card, and insert it into the XO-1.75 laptop's external SD slot. |
|||
# Get the [[Ok]] prompt, |
|||
# Install onto the internal SD card, by typing: |
|||
fs-update ext:\os19.zd |
|||
====Installing from Linux using an XO-1.5==== |
|||
To install on an XO-1.5, boot an XO-1.5 to Linux, insert the SD card in the XO-1.5 external slot, then: |
|||
zcat os19.img.gz > /dev/mmcblk1 |
|||
... and then power down, remove the SD card, and insert it in the XO-1.75. |
|||
====Installing from OpenFirmware using an XO-1.5==== |
|||
You will need the .zd version of the OS image. Download it, then: |
|||
# Place the image on a USB stick, and insert it into the XO-1.5 laptop's USB port. |
|||
# Get the [[Ok]] prompt, |
|||
# To install onto the internal SD card, type: |
|||
fs-update u:\os19.zd |
|||
To install an image onto the external SD card, you need to type: |
|||
devalias fsdisk ext:0 |
|||
fs-update u:\os19.zd |
|||
... and then power down, remove the SD card, and insert it in the XO-1.75. |
|||
⚫ | |||
⚫ | |||
=== Possibility of Shorting Vin === |
=== Possibility of Shorting Vin === |
||
If a large force is applied to the back panel, near the DC power input, there is good chance that the heat spreader will short the main internal power rail. |
If a large force is applied to the back panel, near the DC power input, there is good chance that the heat spreader will short the main internal power rail. This can be prevented by placing a piece of tape (electrical or cellulose) on the underside of the heat spreader, on the corner nearest the DC Power jack ([[Media:XO-1.75-Vin-Fix.jpg|photo]])or the factory fitted modification [[Media:Factory mod.JPG|photo]]. |
||
If Vin is shorted with the main battery present, the main battery may act very dead (even if fully charged) until the laptop applies power to it again. |
|||
This can be prevented by placing a piece of tape (electrical or cellulose) on the underside of the heat spreader, on the corner nearest the DC Power jack. |
|||
If you have not modified your laptop to fix this, we recommend removing the main battery before carrying it in a book bag. |
|||
=== Occasional Accelerometer Hangs === |
=== Occasional Accelerometer Hangs === |
||
We did not get a hardware fix for <trac>11041</trac> or <trac>10882</trac> onto the B1. A software fix |
We did not get a hardware fix for <trac>11041</trac> or <trac>10882</trac> onto the B1. A software fix was applied which should prevent this problem from happening, by lowering the data rate, and is present in OFW Q4B05 and kernel in os36. |
||
=== Antitheft === |
=== Antitheft === |
||
Line 114: | Line 66: | ||
=== Operation w. Solar Cell === |
=== Operation w. Solar Cell === |
||
Twenty-eight of the motherboards don't have the right resistor values for operation with a solar |
Twenty-eight of the motherboards don't have the right resistor values for operation with a solar panel. These should be units with both a touchscreen and a non-membrane keyboard. If you have problems using a solar panel, please contact wad or Richard. |
||
=== Occasional Clock Reset === |
|||
Some units lose the real-time clock stored value over a power cycle. <trac>10999</trac>. |
|||
== Documentation == |
== Documentation == |
||
[[Image:1.75_serial_connector.png|thumbnail|Location of serial port]] |
|||
Supporting documentation for these boards (all in PDF): |
Supporting documentation for these boards (all in PDF): |
||
* [[XO-1.75|Detailed Specifications]] |
|||
* [[Media:XO_1.75_Pinouts_A2.pdf|Pinouts]] |
* [[Media:XO_1.75_Pinouts_A2.pdf|Pinouts]] |
||
* [[Media:XO_1.75_Connectors_B1.pdf|Connector Locations]] |
* [[Media:XO_1.75_Connectors_B1.pdf|Connector Locations]] |
||
Line 124: | Line 82: | ||
* [[Media:XO_1.75_EC_Pinout_v9.pdf|EC Pinout]] |
* [[Media:XO_1.75_EC_Pinout_v9.pdf|EC Pinout]] |
||
* Component locations: [[Media:XO_1.75_Parts_Bottom_B1.pdf|bottom]], [[Media:XO_1.75_Parts_Top_B1.pdf|top]] |
* Component locations: [[Media:XO_1.75_Parts_Bottom_B1.pdf|bottom]], [[Media:XO_1.75_Parts_Top_B1.pdf|top]] |
||
* Unbricking [[SPI_FLASH_Recovery_for_XO-1.75_Using_CForth|using CForth]] and [[SPI_FLASH_Recovery_for_XO-1.75_Using_JTAG|using JTAG]]. |
|||
* It is possible to [[Voltage_Testing_of_XO-1.75|run the SoC at a different core voltage]] |
|||
* [[XO_1.75_Motherboard|Motherboard photos]] |
|||
'''Please note that production boards may have different pin mappings and connector locations.''' |
'''Please note that production boards may have different pin mappings and connector locations.''' |
Latest revision as of 04:40, 10 April 2012
XO-1.75 Laptop Beta test model 1, also known as B1.
Description
The B1 are the fourth prototypes of the XO-1.75 built. Electrically, these are very similar to the A3 prototypes. Several hundred were made in July, 2011, for distribution to software developers.
Due to a flaw in the security system, each laptop bricked itself ten days after manufacture. The fix is to connect a serial cable and flash a new version of firmware after Q4B05. See XO 1.75 11089 Fix for how to fix, and see <trac>11089</trac> for technical details.
Remember, this is a prototype, there are design faults. See below for hardware restrictions. See http://dev.laptop.org/1.75 for tickets that are not closed, in the XO-1.75 firmware or software milestones.
Identification
These are the first fully assembled XO-1.75 laptops. While production 1.75 laptops will be identifiable by two rows of raised dots on the hinge cover, B1 laptops only have three dots (identical to the XO-1.5).
One way of identifying them is the slow blink of the WLAN LED when they are associated, due to the Outdoor Light Sensor turning the LED off to take a reading (this was moved to the storage LED in C1).
Two versions were built:
- Motherboard ID 1B1 --- these units do not have an internal full-size SD card slot, and instead provide SDRAM for use by the DCON. These units are assembled into a green/white case with a non-membrane keyboard. Some of these units are also equipped with a multitouch-capable projected capacitance touchscreen to be used as XO-3 development kits (no touchscreen is planned on XO-1.75).
- Motherboard ID 1B2 --- these units have an internal full-size SD card slot, but no SDRAM for the DCON. These units are assembled into green/white cases with membrane keyboards.
Both versions use internal eMMC for Linux.
Photographs:
If you disassemble the laptop (instructions), you will see:
Software
See XO-1.75 software.
Software Restrictions
See XO-1.75 general software restrictions. The only XO-1.75 B1 specific software restrictions are:
- a very slow accelerometer data rate, due to a workaround for a hardware problem that caused occasional read hangs,
- if the unit has a forgetful RTC (<trac>10999</trac>) then several date and time related software features may fail.
Firmware Restrictions
White Screen
If you just unwrapped an XO-1.75 B1, tried to boot it, and got a white screen, you're experiencing <trac>11089</trac>. Instructions for fixing this are here. The fix is permanent.
White Screen with XO only, then reboot
Q4B08 and earlier did not indicate when EC reflash was in progress. Fixed in Q4B09. <trac>11117</trac>.
Hardware Restrictions
There is a list of recommended modifications (ECOs). There is also a list of changes proposed from B1 to C1.
Loss of first character on resume
Unfortunately, we learned too late that the Armada 610 SoC takes a while to wake up from a deep sleep. When a user wakes an XO-1.75 B1/C1 laptop with a keypress, the first key code sent by the keyboard is lost by the SoC (<trac>11401</trac>). This was fixed by having the EC stall the keyboard until the SoC wakes, but requires that resistors be added to the board.
Possibility of Shorting Vin
If a large force is applied to the back panel, near the DC power input, there is good chance that the heat spreader will short the main internal power rail. This can be prevented by placing a piece of tape (electrical or cellulose) on the underside of the heat spreader, on the corner nearest the DC Power jack (photo)or the factory fitted modification photo.
If Vin is shorted with the main battery present, the main battery may act very dead (even if fully charged) until the laptop applies power to it again.
Occasional Accelerometer Hangs
We did not get a hardware fix for <trac>11041</trac> or <trac>10882</trac> onto the B1. A software fix was applied which should prevent this problem from happening, by lowering the data rate, and is present in OFW Q4B05 and kernel in os36.
Antitheft
The antitheft circuitry, by default, does not prevent reprogramming the OFW SPI Flash. It will prevent reprogramming of the EC. Fixing this is a trivial ECO.
Operation w. Solar Cell
Twenty-eight of the motherboards don't have the right resistor values for operation with a solar panel. These should be units with both a touchscreen and a non-membrane keyboard. If you have problems using a solar panel, please contact wad or Richard.
Occasional Clock Reset
Some units lose the real-time clock stored value over a power cycle. <trac>10999</trac>.
Documentation
Supporting documentation for these boards (all in PDF):
- Detailed Specifications
- Pinouts
- Connector Locations
- GPIO Mappings
- EC Pinout
- Component locations: bottom, top
- Unbricking using CForth and using JTAG.
- It is possible to run the SoC at a different core voltage
- Motherboard photos
Please note that production boards may have different pin mappings and connector locations.