I am now trying to get the latest coreboot v2 installed on an Arima HDAMA board. This is the output I got after flashing it and doing a hard reset:
coreboot-2.3 Thu Oct 15 16:17:26 MDT 2009 starting... (0,1) link=01 (1,0) link=01 02 nodes initialized. SBLink=00 NC node|link=00 Ram1.00 Ram1.01 Ram2.00 RAM end at 0x00100000 kB Ram2.01 RAM end at 0x00200000 kB Ram3 while waiting for BSP signal to STOP, timeout in ap 01
It just hangs there and I don't get anymore output. Any suggestions? Thanks.
-----Original Message----- From: coreboot-bounces@coreboot.org [mailto:coreboot-bounces@coreboot.org] On Behalf Of Hugh Greenberg Sent: Thursday, October 15, 2009 5:24 PM To: coreboot@coreboot.org Subject: [coreboot] arima hdama problem
I am now trying to get the latest coreboot v2 installed on an Arima HDAMA board. This is the output I got after flashing it and doing a hard reset:
coreboot-2.3 Thu Oct 15 16:17:26 MDT 2009 starting... (0,1) link=01 (1,0) link=01 02 nodes initialized. SBLink=00 NC node|link=00 Ram1.00 Ram1.01 Ram2.00 RAM end at 0x00100000 kB Ram2.01 RAM end at 0x00200000 kB Ram3 while waiting for BSP signal to STOP, timeout in ap 01
It just hangs there and I don't get anymore output. Any suggestions? Thanks.
Can you send ldoptions and coreboot_*.map? I've seen something similar when things get messed up there.
Thanks, Myles
Myles,
Attached are the files. Thanks.
On Fri, Oct 16, 2009 at 11:32 AM, Hugh Greenberg hng@lanl.gov wrote:
Myles,
Attached are the files. Thanks.
Can you apply the loglevel patch (or set loglevel to 9), and run it again. I don't see the problem I thought I might.
Let's work with the Kconfig version. Here's a patch that makes it a lot closer to newconfig.
Signed-off-by: Myles Watson mylesgw@gmail.com
Thanks, Myles
On Thu, Oct 15, 2009 at 05:23:38PM -0600, Hugh Greenberg wrote:
I am now trying to get the latest coreboot v2 installed on an Arima HDAMA board. This is the output I got after flashing it and doing a hard reset:
Just in case, make sure you do _not_ use "make menuconfig" for building coreboot yet, the support for that is not yet finished and random breakage is to be expected on some boards.
If this was a kconfig build, please retry with ./builtdarget and compare results.
Uwe.
I was using the make menuconfig since I got better results with it for the last board I put coreboot on. I retried with ./buildtarget as you suggested and I got the same result.
One thing I used to do with these boards, when testing, was remove CPU1 and see if it would work with just one. It's a useful data point.
ron