Based on memory, 00 means fault in RAM. Replace RAM. Could also be
electrostatic damage to CPU or RAM. Could also be age degradation of silicon
chips.
To find the real meaning of 00 takes reading the C code of the CForth startup
payload, which is loaded from SPI Flash.
There is no involveme
Message: 1
Date: Sat, 6 Jun 2020 11:41:33 + (UTC)
From: Yioryos Asprobounitis
To: "devel@lists.laptop.org"
Subject: XO1.75
Message-ID: <2133017554.128519.1591443693...@mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Hi list
I dug out my XOs to check their conditio
From: Yioryos Asprobounitis
Date: Sun, 7 Jun 2020 04:19:22 + (UTC)
> Looks like there is no firmware in this machine!
I don't know the 00 display but this and the following sections should help.
http://wiki.laptop.org/go/Fix_Clock#If_the_screen_does_not_turn_on
> Looks like there is no f
Hi list
I dug out my XOs to check their condition and my XO-1.75 (SKU203) refuses to
boot as if it was wiped out clean or has no microSD card at all.
The screen comes up and nothing further.
Firmware check just show a double zero [00]
Trying to install a fresh OS from USB fails (with the same dou
From: Yioryos Asprobounitis
Date: Sat, 6 Jun 2020 11:41:33 + (UTC)
> The screen comes up and nothing further.
ESC doesn't give the prompt of the Forth PROM?
> Firmware check just show a double zero [00]
Hardware diagnostics? Rocker left cheat code.
http://wiki.laptop.org/go/Cheat_codes
So I've woken up.
The moved startup sound happened in Q4D26 [1] [2] and was intended
not to be noticed, since it should be on the filesystem after an
upgrade. I'm kind of glad somebody noticed. ;-) It shows other
combinations are being tested.
You can fix the problem on your XO-1.75 with 13.1.0
juan wrote:
> Just downgraded do Q4D20 and the original sound has been restored :)
>
> I had no idea that certain OS versions had to be matched to certain
> Firmware versions...
> I always tried to keep up with the latest on my test machines.
we try very hard to maintain both forward and ba
Just downgraded do Q4D20 and the original sound has been restored :)
I had no idea that certain OS versions had to be matched to certain
Firmware versions...
I always tried to keep up with the latest on my test machines.
- Juan
On 06/20/2013 11:41 AM, Daniel Drake wrote:
On Thu, Jun 20, 201
On Thu, Jun 20, 2013 at 11:36 AM, Juan Cubillo wrote:
> That might be an option, but not in my case. Both XOs have Build 13.0.1 and
> Firmware Q4D28.
>
> I'll wait for James to wake up :)
In the mean time maybe you can explain why changing firmware version
and/or OS version is not an option. It m
That might be an option, but not in my case. Both XOs have Build 13.0.1
and Firmware Q4D28.
I'll wait for James to wake up :)
- Juan
On 06/20/2013 09:45 AM, Daniel Drake wrote:
On Thu, Jun 20, 2013 at 9:28 AM, Juan Cubillo wrote:
Hello,
Quick question> I have two 1.75XO that make a "beep
On Thu, Jun 20, 2013 at 9:28 AM, Juan Cubillo wrote:
> Hello,
>
> Quick question> I have two 1.75XO that make a "beep beep" sound while
> booting instead of the usual XO booting sound. Why is this so? Can this be
> changed?
This likely means that you are running a new firmware on an old OS
relea
Hello,
Quick question> I have two 1.75XO that make a "beep beep" sound while
booting instead of the usual XO booting sound. Why is this so? Can this
be changed?
- Juan
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/
2013 at 11:12 AM, Juan Cubillo
> wrote:
> > Yes, I cloned the git repo, changed directory and issued the make command
> > but I get the error described. I'm running this on the latest stable
> image
> > for the xo1.75.
> > From your reply I assume that this error i
On Mon, Apr 1, 2013 at 11:12 AM, Juan Cubillo wrote:
> Yes, I cloned the git repo, changed directory and issued the make command
> but I get the error described. I'm running this on the latest stable image
> for the xo1.75.
> From your reply I assume that this error is not normal
On 04/01/2013 10:56 AM, Daniel Drake wrote:
On Mon, Apr 1, 2013 at 10:51 AM, Juan Cubillo wrote:
Hello,
I'm creating xo1.75 OS images on a 1.75 XO since that's the only ARM
hardware I have around. In order to sign the images I need to compile
bios-crypto following the instruction
On Mon, Apr 1, 2013 at 10:51 AM, Juan Cubillo wrote:
> Hello,
>
> I'm creating xo1.75 OS images on a 1.75 XO since that's the only ARM
> hardware I have around. In order to sign the images I need to compile
> bios-crypto following the instructions from the wiki:
>
Hello,
I'm creating xo1.75 OS images on a 1.75 XO since that's the only ARM
hardware I have around. In order to sign the images I need to compile
bios-crypto following the instructions from the wiki:
http://wiki.laptop.org/go/OS_Builder#Signing_preparation
make is not finishing cor
17 matches
Mail list logo
