Re: [coreboot] OpenBMC & KGPE-D16

2018-02-28 Thread Timothy Pearson 
On 02/27/2018 11:15 PM, taii...@gmx.com wrote:
> On 02/22/2018 04:36 PM, Timothy Pearson wrote:
> 
>> Actually, for OpenBMC work, hotplugging is often the only way to go.
>> Just be very careful to align the pins correctly the first time; you
>> don't have a second chance if you misalign the pins and fry the module...
> I stand corrected, but I am nervous about doing this myself - is it
> possible to use a tester clip?

We have not been able to do so.  There are logic circuits onboard the
firmware module that interfere with direct flashing methods.

> Have you found a source for ASMB4 or ASMB5 modules? Many people I know
> who bought their boards on ebay didn't get one and the D8 unfortunately
> doesn't come with them either. I am going to contact ASUS and see if
> they have a stash.

As with most of the obsolete Opteron hardware, our sources are rapidly
drying up.  We have no source for these modules at this time.

-- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-27 Thread taii...@gmx.com 

On 02/22/2018 04:36 PM, Timothy Pearson wrote:


Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the module...
I stand corrected, but I am nervous about doing this myself - is it 
possible to use a tester clip?


Have you found a source for ASMB4 or ASMB5 modules? Many people I know 
who bought their boards on ebay didn't get one and the D8 unfortunately 
doesn't come with them either. I am going to contact ASUS and see if 
they have a stash.


--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-26 Thread James Hebden 
No problems. It took me several patches but I think I better understand
the coding style and project layout now, and tests are passing after a
rebase of the code and responding to review feedback.

Thanks all for taking the time to review and for putting up with the
spam :)

James

On Mon, Feb 26, 2018 at 12:11:09PM -0600, Timothy Pearson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Thank you!  If you have questions during the process please feel free to
> ask.
> 
> On 02/26/2018 04:53 AM, James Hebden wrote:
> > On Sun, Feb 25, 2018 at 04:25:23AM -0600, Timothy Pearson wrote:
> >> On 02/25/2018 02:18 AM, Mike Banon wrote:
>  Any particular reason those patches were not upstreamed?
> >>>
> >>> Because a person who submitted these patches did not fix some problems,
> >>
> >> I'm aware of this.  Upstreaming was never part of the original funding
> >> effort and I haven't had any spare time to try to work on it; been
> >> working on several other projects in what little spare time I have had
> >> over the past year.  If anyone else would like to apply the recommended
> >> cleanups and resubmit I'm fine with that.
> > 
> > I've taken a swing at pushing a patch to address reviewer comments.
> > First time submitting to CoreBoot, fingers crossed :)
> > 
> > https://review.coreboot.org/#/c/coreboot/+/19820/
> > 
> > Best,
> > James
> 
> 
> - -- 
> Timothy Pearson
> Raptor Engineering
> +1 (415) 727-8645 (direct line)
> +1 (512) 690-0200 (switchboard)
> https://www.raptorengineering.com
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQEcBAEBAgAGBQJalE26AAoJEK+E3vEXDOFb068IAJlWLPutfey4ThKYfKAsUfda
> 7DTt0d+xL6qwY0jg7XRYnsYSLftGGTMPcbz/c5+aNKBO3EtYsKAiFgQZexvUP0gY
> jyayYj0b3sDwE6CYParO1iU5WZ4cHOD5B5qRKry2R0drpvsH/We/ZmTwRLPl4Saq
> GEvmcPEomnKM5mS8eNiaAUWRHS36WVoE9KIEdsN26LflhRqELMl3oxFamRQbIoqY
> b+CReKnP7rCFt57ZtFjANAMnRkMU1hAGF2tTSK/WTVafwUwRwpm9vdKDuE4a1nJe
> h3UOiP8MS0IxsAL1mftyPklpmmtXE2I14OZ11C/tKJOBslDyq1Wut9xMuwOp1xc=
> =tSb+
> -END PGP SIGNATURE-
> 
> -- 
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot


signature.asc
Description: PGP signature
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-26 Thread Piotr Kubaj via coreboot 

It's iKVM4.

On 18-02-25 04:23:45, Timothy Pearson wrote:

Actually that's quite odd -- it should not work that way.  There is a
hardware mux that is switched in when the module is installed; only the
BMC can access the DRAM SPD lines without a BMC GPIO being set.

Which module are you using, the iKVM4 or the iKVM5?

On 02/24/2018 11:10 AM, Piotr Kubaj via coreboot wrote:

Strange, I didn't apply any patches. I run D16 with stock coreboot 4.7
and OpenBMC.

Could it be because I have different memory modules (4xKVR16R11D4/16)?

On 18-02-24 12:00:01, coreboot-requ...@coreboot.org wrote:

Send coreboot mailing list submissions to
coreboot@coreboot.org

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
coreboot-requ...@coreboot.org

You can reach the person managing the list at
coreboot-ow...@coreboot.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of coreboot digest..."


Today's Topics:

  1. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  2. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  3. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  4. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  5. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  6. make gitconfig not working for me with git 1.9.1
 (mtur...@codeaurora.org)
  7. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)


--

Message: 1
Date: Fri, 23 Feb 2018 23:38:42 +0100
From: Elisenda Cuadros <li...@e4l.es>
To: Timothy Pearson <tpear...@raptorengineering.com>, Coreboot
<coreboot@coreboot.org>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <024a1ee2-7edc-be52-f87d-3bfbf95aa...@e4l.es>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works
like a charm, it got an ip, I can log through ssh, reboot, etc..

But now I have a new problem. If I try to boot from a halted system,
with BMC module attached, the system fires up but Coreboot hangs:

Unable to detect valid memory on any nodes.? Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1
orange slots.

I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:

Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the
module...

On 02/22/2018 03:22 PM, taii...@gmx.com wrote:

On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:


Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
(~1000rpm)

In the case I have to reflash the module, is it possible to hotplug
it?

Hotplugging is dangerous and not supported, don't do it.

Thank you very much for your support.

You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to
support
OpenBMC, so you need a new version with the patches.

-- next part --
A non-text attachment was scrubbed...
Name: Console_Without_BMC.log.gz
Type: application/gzip
Size: 24422 bytes
Desc: not available
URL:
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0002.bin>

-- next part --
A non-text attachment was scrubbed...
Name: Console_With_BMC.log.gz
Type: application/gzip
Size: 2158 bytes
Desc: not available
URL:
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0003.bin>


--

Message: 2
Date: Fri, 23 Feb 2018 17:01:13 -0600
From: Timothy Pearson <tpear...@raptorengineering.com>
To: Elisenda Cuadros <li...@e4l.es>
Cc: Coreboot <coreboot@coreboot.org>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <5a909d39.40...@raptorengineering.com>
Content-Type: text/plain; charset=UTF-8

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
coreboot-requ...@coreboot.org

You can reach the pe

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-26 Thread Timothy Pearson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thank you!  If you have questions during the process please feel free to
ask.

On 02/26/2018 04:53 AM, James Hebden wrote:
> On Sun, Feb 25, 2018 at 04:25:23AM -0600, Timothy Pearson wrote:
>> On 02/25/2018 02:18 AM, Mike Banon wrote:
 Any particular reason those patches were not upstreamed?
>>>
>>> Because a person who submitted these patches did not fix some problems,
>>
>> I'm aware of this.  Upstreaming was never part of the original funding
>> effort and I haven't had any spare time to try to work on it; been
>> working on several other projects in what little spare time I have had
>> over the past year.  If anyone else would like to apply the recommended
>> cleanups and resubmit I'm fine with that.
> 
> I've taken a swing at pushing a patch to address reviewer comments.
> First time submitting to CoreBoot, fingers crossed :)
> 
> https://review.coreboot.org/#/c/coreboot/+/19820/
> 
> Best,
> James


- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJalE26AAoJEK+E3vEXDOFb068IAJlWLPutfey4ThKYfKAsUfda
7DTt0d+xL6qwY0jg7XRYnsYSLftGGTMPcbz/c5+aNKBO3EtYsKAiFgQZexvUP0gY
jyayYj0b3sDwE6CYParO1iU5WZ4cHOD5B5qRKry2R0drpvsH/We/ZmTwRLPl4Saq
GEvmcPEomnKM5mS8eNiaAUWRHS36WVoE9KIEdsN26LflhRqELMl3oxFamRQbIoqY
b+CReKnP7rCFt57ZtFjANAMnRkMU1hAGF2tTSK/WTVafwUwRwpm9vdKDuE4a1nJe
h3UOiP8MS0IxsAL1mftyPklpmmtXE2I14OZ11C/tKJOBslDyq1Wut9xMuwOp1xc=
=tSb+
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-26 Thread James Hebden 
On Sun, Feb 25, 2018 at 04:25:23AM -0600, Timothy Pearson wrote:
> On 02/25/2018 02:18 AM, Mike Banon wrote:
> >> Any particular reason those patches were not upstreamed?
> > 
> > Because a person who submitted these patches did not fix some problems,
> 
> I'm aware of this.  Upstreaming was never part of the original funding
> effort and I haven't had any spare time to try to work on it; been
> working on several other projects in what little spare time I have had
> over the past year.  If anyone else would like to apply the recommended
> cleanups and resubmit I'm fine with that.

I've taken a swing at pushing a patch to address reviewer comments.
First time submitting to CoreBoot, fingers crossed :)

https://review.coreboot.org/#/c/coreboot/+/19820/

Best,
James


signature.asc
Description: PGP signature
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-25 Thread Timothy Pearson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/25/2018 02:18 AM, Mike Banon wrote:
>> Any particular reason those patches were not upstreamed?
> 
> Because a person who submitted these patches did not fix some problems,

I'm aware of this.  Upstreaming was never part of the original funding
effort and I haven't had any spare time to try to work on it; been
working on several other projects in what little spare time I have had
over the past year.  If anyone else would like to apply the recommended
cleanups and resubmit I'm fine with that.

- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJako8TAAoJEK+E3vEXDOFbtikIALooPL3+eUeog+JWDYy6WmiR
UpzHFR8masKd33ae8+6Sfz3Xh3P0jXvMhVnXPT5QxT1OAMuiOsqRTlp2Tt0ErmJ1
y8FNYVEjBWzWAg8FIJD9IRUlumcVqXRCI2DTDNQJt9ckCtm7mFqaN5oB49TlL0D0
o30+5Gm0kSzXEgC5G9NgiQk/sD06R+l9UDlwJa51ysvl5b5tPMh9eT2jj5kn6uAE
h5BDhruEODJb6E7077wuzKREhZR/gEmUvBmdgUCuPWs2EHZyC6vkAYqIWhjBODtv
dBL5fyPsMnQRua+A+O7suKxt5ieNxx59BOsGwh5XWvubg/Gr7TIDVYDD5lK6Bms=
=tApG
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-25 Thread Timothy Pearson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Actually that's quite odd -- it should not work that way.  There is a
hardware mux that is switched in when the module is installed; only the
BMC can access the DRAM SPD lines without a BMC GPIO being set.

Which module are you using, the iKVM4 or the iKVM5?

On 02/24/2018 11:10 AM, Piotr Kubaj via coreboot wrote:
> Strange, I didn't apply any patches. I run D16 with stock coreboot 4.7
> and OpenBMC.
> 
> Could it be because I have different memory modules (4xKVR16R11D4/16)?
> 
> On 18-02-24 12:00:01, coreboot-requ...@coreboot.org wrote:
>> Send coreboot mailing list submissions to
>> coreboot@coreboot.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mail.coreboot.org/mailman/listinfo/coreboot
>> or, via email, send a message with subject or body 'help' to
>> coreboot-requ...@coreboot.org
>>
>> You can reach the person managing the list at
>> coreboot-ow...@coreboot.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of coreboot digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
>>   2. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
>>   3. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
>>   4. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
>>   5. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
>>   6. make gitconfig not working for me with git 1.9.1
>>  (mtur...@codeaurora.org)
>>   7. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
>>
>>
>> --
>>
>> Message: 1
>> Date: Fri, 23 Feb 2018 23:38:42 +0100
>> From: Elisenda Cuadros <li...@e4l.es>
>> To: Timothy Pearson <tpear...@raptorengineering.com>, Coreboot
>> <coreboot@coreboot.org>
>> Subject: Re: [coreboot] OpenBMC & KGPE-D16
>> Message-ID: <024a1ee2-7edc-be52-f87d-3bfbf95aa...@e4l.es>
>> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>>
>> Hello,
>>
>> Thank you for your reply.
>>
>> I reflashed (same build) the BMC module with a hotplug. Now it works
>> like a charm, it got an ip, I can log through ssh, reboot, etc..
>>
>> But now I have a new problem. If I try to boot from a halted system,
>> with BMC module attached, the system fires up but Coreboot hangs:
>>
>> Unable to detect valid memory on any nodes.? Halting!
>> mct_d: fatalexit
>>
>> If I remove the BMC module the system boots fine.
>>
>> I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1
>> orange slots.
>>
>> I attach both console logs.
>>
>> Regards,
>>
>> - Eli
>>
>>
>>
>> On 22/02/18 22:36, Timothy Pearson wrote:
>>> Actually, for OpenBMC work, hotplugging is often the only way to go.
>>> Just be very careful to align the pins correctly the first time; you
>>> don't have a second chance if you misalign the pins and fry the
>>> module...
>>>
>>> On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
>>>> On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Now I trying to use your OpenBMC port.
>>>>>
>>>>> I followed the instructions and everything was fine (compiling,
>>>>> reading and flashing). I waited several minutes after flashing, but
>>>>> the module didn 't blinked like in the vendor rom, nor did it receive
>>>>> an ip.
>>>>>
>>>>> I halted the system because I thought maybe it needs a cold start.
>>>>>
>>>>> After this, the system doesn't boot with the module plugged in. The
>>>>> fans begin to spin for approximately 1/4 second, but nothing else.
>>>>>
>>>>> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
>>>>> (~1000rpm)
>>>>>
>>>>> In the case I have to reflash the module, is it possible to hotplug
>>>>> it?
>>>> Hotplugging is dangerous and not supported, don't do it.
>>>>> Thank you very much for your support.
>>>> You can use a test clip to externally flash it via a flashing device
>>>> (not sure which can do 16 pins though, I would inquire on the flashrom
>>>> mailinglist)
>>>>
>>>> Are you using the latest coreboot? AFAIK coreboot was patched to
>>>&g

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-25 Thread Piotr Kubaj via coreboot 

Strange, I didn't apply any patches. I run D16 with stock coreboot 4.7 and 
OpenBMC.

Could it be because I have different memory modules (4xKVR16R11D4/16)?

On 18-02-24 12:00:01, coreboot-requ...@coreboot.org wrote:

Send coreboot mailing list submissions to
coreboot@coreboot.org

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
coreboot-requ...@coreboot.org

You can reach the person managing the list at
coreboot-ow...@coreboot.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of coreboot digest..."


Today's Topics:

  1. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  2. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  3. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  4. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  5. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  6. make gitconfig not working for me with git 1.9.1
 (mtur...@codeaurora.org)
  7. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)


--

Message: 1
Date: Fri, 23 Feb 2018 23:38:42 +0100
From: Elisenda Cuadros <li...@e4l.es>
To: Timothy Pearson <tpear...@raptorengineering.com>, Coreboot
<coreboot@coreboot.org>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <024a1ee2-7edc-be52-f87d-3bfbf95aa...@e4l.es>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works 
like a charm, it got an ip, I can log through ssh, reboot, etc..


But now I have a new problem. If I try to boot from a halted system, 
with BMC module attached, the system fires up but Coreboot hangs:


Unable to detect valid memory on any nodes.? Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange 
slots.


I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:

Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the module...

On 02/22/2018 03:22 PM, taii...@gmx.com wrote:

On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:


Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed (~1000rpm)

In the case I have to reflash the module, is it possible to hotplug it?

Hotplugging is dangerous and not supported, don't do it.

Thank you very much for your support.

You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to support
OpenBMC, so you need a new version with the patches.

-- next part --
A non-text attachment was scrubbed...
Name: Console_Without_BMC.log.gz
Type: application/gzip
Size: 24422 bytes
Desc: not available
URL: 
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0002.bin>
-- next part --
A non-text attachment was scrubbed...
Name: Console_With_BMC.log.gz
Type: application/gzip
Size: 2158 bytes
Desc: not available
URL: 
<http://mail.coreboot.org/pipermail/coreboot/attachments/20180223/80d225ea/attachment-0003.bin>

--

Message: 2
Date: Fri, 23 Feb 2018 17:01:13 -0600
From: Timothy Pearson <tpear...@raptorengineering.com>
To: Elisenda Cuadros <li...@e4l.es>
Cc: Coreboot <coreboot@coreboot.org>
Subject: Re: [coreboot] OpenBMC & KGPE-D16
Message-ID: <5a909d39.40...@raptorengineering.com>
Content-Type: text/plain; charset=UTF-8

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
coreboot-requ...@coreboot.org

You can reach the person managing the list at
coreboot-ow...@coreboot.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of coreboot digest..."


Today's Topics:

  1. Re: OpenBMC & KGPE-D16 (Elisenda Cuadros)
  2. Re: OpenBMC & KGPE-D16 (Timothy Pearson)
  3. Re: OpenBMC & KGPE-D16 (E

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-25 Thread Mike Banon 
> Any particular reason those patches were not upstreamed?

Because a person who submitted these patches did not fix some problems,
if you scroll down to comments at
https://review.coreboot.org/#/c/coreboot/+/19820/

Paul Menzel
May 23, 2017

Patch Set 1:

(2 comments)

src/mainboard/asus/kgpe-d16/romstage.c
Line 96:

Add macro or set `dev = PCI_DEV(0, 0x14, 4)`?

Line 118:

Line length?

Arthur Heymans
May 23, 2017

Patch Set 1:

(5 comments)

Change looks good, just pci_def.h macros that could be used a bit more.

src/mainboard/asus/kgpe-d16/romstage.c
Line 93:

Use macros?

Line 101:

#define TEMP_PCI_BUS 0x1

Line 101:

PCI_SECUNDARY_BUS

Line 102:

PCI_SUBORDINATE_BUS

Line 103:

PCI_BASE_ADDRESS_4


On Sun, Feb 25, 2018 at 6:01 AM, Thierry Laurion
 wrote:
> Any particular reason those patches were not upstreamed?
>
>
> Le ven. 23 févr. 2018 21:40, Thierry Laurion  a
> écrit :
>>
>> Timothys patches were mot included un coreboot
>> https://review.coreboot.org/#/c/coreboot/+/19822/
>>
>> Le ven. 23 févr. 2018 17:40, Elisenda Cuadros  a écrit :
>>>
>>> Hello,
>>>
>>> Thank you for your reply.
>>>
>>> I reflashed (same build) the BMC module with a hotplug. Now it works
>>> like a charm, it got an ip, I can log through ssh, reboot, etc..
>>>
>>> But now I have a new problem. If I try to boot from a halted system,
>>> with BMC module attached, the system fires up but Coreboot hangs:
>>>
>>> Unable to detect valid memory on any nodes.  Halting!
>>> mct_d: fatalexit
>>>
>>> If I remove the BMC module the system boots fine.
>>>
>>> I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
>>> slots.
>>>
>>> I attach both console logs.
>>>
>>> Regards,
>>>
>>> - Eli
>>>
>>>
>>>
>>> On 22/02/18 22:36, Timothy Pearson wrote:
>>> > Actually, for OpenBMC work, hotplugging is often the only way to go.
>>> > Just be very careful to align the pins correctly the first time; you
>>> > don't have a second chance if you misalign the pins and fry the
>>> > module...
>>> >
>>> > On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
>>> >> On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
>>> >>
>>> >>> Hi,
>>> >>>
>>> >>> Now I trying to use your OpenBMC port.
>>> >>>
>>> >>> I followed the instructions and everything was fine (compiling,
>>> >>> reading and flashing). I waited several minutes after flashing, but
>>> >>> the module didn 't blinked like in the vendor rom, nor did it receive
>>> >>> an ip.
>>> >>>
>>> >>> I halted the system because I thought maybe it needs a cold start.
>>> >>>
>>> >>> After this, the system doesn't boot with the module plugged in. The
>>> >>> fans begin to spin for approximately 1/4 second, but nothing else.
>>> >>>
>>> >>> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
>>> >>> (~1000rpm)
>>> >>>
>>> >>> In the case I have to reflash the module, is it possible to hotplug
>>> >>> it?
>>> >> Hotplugging is dangerous and not supported, don't do it.
>>> >>> Thank you very much for your support.
>>> >> You can use a test clip to externally flash it via a flashing device
>>> >> (not sure which can do 16 pins though, I would inquire on the flashrom
>>> >> mailinglist)
>>> >>
>>> >> Are you using the latest coreboot? AFAIK coreboot was patched to
>>> >> support
>>> >> OpenBMC, so you need a new version with the patches.
>>> --
>>> coreboot mailing list: coreboot@coreboot.org
>>> https://mail.coreboot.org/mailman/listinfo/coreboot
>
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-24 Thread Thierry Laurion 
Any particular reason those patches were not upstreamed?

Le ven. 23 févr. 2018 21:40, Thierry Laurion  a
écrit :

> Timothys patches were mot included un coreboot
> https://review.coreboot.org/#/c/coreboot/+/19822/
>
> Le ven. 23 févr. 2018 17:40, Elisenda Cuadros  a écrit :
>
>> Hello,
>>
>> Thank you for your reply.
>>
>> I reflashed (same build) the BMC module with a hotplug. Now it works
>> like a charm, it got an ip, I can log through ssh, reboot, etc..
>>
>> But now I have a new problem. If I try to boot from a halted system,
>> with BMC module attached, the system fires up but Coreboot hangs:
>>
>> Unable to detect valid memory on any nodes.  Halting!
>> mct_d: fatalexit
>>
>> If I remove the BMC module the system boots fine.
>>
>> I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
>> slots.
>>
>> I attach both console logs.
>>
>> Regards,
>>
>> - Eli
>>
>>
>>
>> On 22/02/18 22:36, Timothy Pearson wrote:
>> > Actually, for OpenBMC work, hotplugging is often the only way to go.
>> > Just be very careful to align the pins correctly the first time; you
>> > don't have a second chance if you misalign the pins and fry the
>> module...
>> >
>> > On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
>> >> On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> Now I trying to use your OpenBMC port.
>> >>>
>> >>> I followed the instructions and everything was fine (compiling,
>> >>> reading and flashing). I waited several minutes after flashing, but
>> >>> the module didn 't blinked like in the vendor rom, nor did it receive
>> >>> an ip.
>> >>>
>> >>> I halted the system because I thought maybe it needs a cold start.
>> >>>
>> >>> After this, the system doesn't boot with the module plugged in. The
>> >>> fans begin to spin for approximately 1/4 second, but nothing else.
>> >>>
>> >>> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
>> (~1000rpm)
>> >>>
>> >>> In the case I have to reflash the module, is it possible to hotplug
>> it?
>> >> Hotplugging is dangerous and not supported, don't do it.
>> >>> Thank you very much for your support.
>> >> You can use a test clip to externally flash it via a flashing device
>> >> (not sure which can do 16 pins though, I would inquire on the flashrom
>> >> mailinglist)
>> >>
>> >> Are you using the latest coreboot? AFAIK coreboot was patched to
>> support
>> >> OpenBMC, so you need a new version with the patches.
>> --
>> coreboot mailing list: coreboot@coreboot.org
>> https://mail.coreboot.org/mailman/listinfo/coreboot
>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-24 Thread Thierry Laurion 
Timothys patches were mot included un coreboot
https://review.coreboot.org/#/c/coreboot/+/19822/

Le ven. 23 févr. 2018 17:40, Elisenda Cuadros  a écrit :

> Hello,
>
> Thank you for your reply.
>
> I reflashed (same build) the BMC module with a hotplug. Now it works
> like a charm, it got an ip, I can log through ssh, reboot, etc..
>
> But now I have a new problem. If I try to boot from a halted system,
> with BMC module attached, the system fires up but Coreboot hangs:
>
> Unable to detect valid memory on any nodes.  Halting!
> mct_d: fatalexit
>
> If I remove the BMC module the system boots fine.
>
> I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
> slots.
>
> I attach both console logs.
>
> Regards,
>
> - Eli
>
>
>
> On 22/02/18 22:36, Timothy Pearson wrote:
> > Actually, for OpenBMC work, hotplugging is often the only way to go.
> > Just be very careful to align the pins correctly the first time; you
> > don't have a second chance if you misalign the pins and fry the module...
> >
> > On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
> >> On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
> >>
> >>> Hi,
> >>>
> >>> Now I trying to use your OpenBMC port.
> >>>
> >>> I followed the instructions and everything was fine (compiling,
> >>> reading and flashing). I waited several minutes after flashing, but
> >>> the module didn 't blinked like in the vendor rom, nor did it receive
> >>> an ip.
> >>>
> >>> I halted the system because I thought maybe it needs a cold start.
> >>>
> >>> After this, the system doesn't boot with the module plugged in. The
> >>> fans begin to spin for approximately 1/4 second, but nothing else.
> >>>
> >>> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
> (~1000rpm)
> >>>
> >>> In the case I have to reflash the module, is it possible to hotplug it?
> >> Hotplugging is dangerous and not supported, don't do it.
> >>> Thank you very much for your support.
> >> You can use a test clip to externally flash it via a flashing device
> >> (not sure which can do 16 pins though, I would inquire on the flashrom
> >> mailinglist)
> >>
> >> Are you using the latest coreboot? AFAIK coreboot was patched to support
> >> OpenBMC, so you need a new version with the patches.
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-23 Thread Elisenda Cuadros 

After applying these patches it works perfect.

Thank you very much.

Regards,

- Eli


On 24/02/18 00:01, Timothy Pearson wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You need these patches:

https://review.coreboot.org/#/c/19822/

This one in particular:

https://review.coreboot.org/#/c/coreboot/+/19820/

This is noted on the Raptor status page:

https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

See the link to "Initial coreboot patches".

If anyone wants to take over upstreaming of the patches in that list
they are welcome to do so!

On 02/23/2018 04:38 PM, Elisenda Cuadros wrote:

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works
like a charm, it got an ip, I can log through ssh, reboot, etc..

But now I have a new problem. If I try to boot from a halted system,
with BMC module attached, the system fires up but Coreboot hangs:

Unable to detect valid memory on any nodes.  Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
slots.

I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:

Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the module...

On 02/22/2018 03:22 PM, taii...@gmx.com wrote:

On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:


Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
(~1000rpm)

In the case I have to reflash the module, is it possible to hotplug it?

Hotplugging is dangerous and not supported, don't do it.

Thank you very much for your support.

You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to support
OpenBMC, so you need a new version with the patches.


- -- 
Timothy Pearson

Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJakJ03AAoJEK+E3vEXDOFbW/0H/1DOjUMNrB5tOxw1OkGnRVK0
/KucTV0HjqPwtvhyyHeU6T9cFdAAkTHICFeGXXm05GBSeCTXWKOp38xO92hWCp88
zedukp8mq+AAzg6R1yfd6Z3MsD1pmueUKWvV0ca1lxkfAGacUzND0xRXQaO3Jel6
n0VYv0GOSDCjp34MClawUZ7ie309u68YnEQhkyFd56oXsTCfvHl8j2dwO8RmmtJt
gs+JHOTZAMgBSzn8DJigh5hiNA7B93A8Lst/Q+oFfxwibhSWGDXCmdDlcBu/VNcM
ZNF3DYYa6u6bQB8xNvous8HCn5aUEvU2vNbAci+R15S1fNEnO+fn/+F5X96mHyk=
=DRWR
-END PGP SIGNATURE-



--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-23 Thread Elisenda Cuadros 

For me it's a pleasure using it.

It is like magic to my eyes to see a Linux prompt in this tiny module.

Thank you!


On 24/02/18 00:09, Timothy Pearson wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

No worries.  I'm glad you were able to get the BMC running; it's great
to see more users of this technology!

On 02/23/2018 05:09 PM, Elisenda Cuadros wrote:

Sorry, I need to read better.

Thank you.

I am going to try the patches now.

Regards,

- Eli


On 24/02/18 00:01, Timothy Pearson wrote:
You need these patches:

https://review.coreboot.org/#/c/19822/

This one in particular:

https://review.coreboot.org/#/c/coreboot/+/19820/

This is noted on the Raptor status page:

https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

See the link to "Initial coreboot patches".

If anyone wants to take over upstreaming of the patches in that list
they are welcome to do so!

On 02/23/2018 04:38 PM, Elisenda Cuadros wrote:

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works
like a charm, it got an ip, I can log through ssh, reboot, etc..

But now I have a new problem. If I try to boot from a halted system,
with BMC module attached, the system fires up but Coreboot hangs:

Unable to detect valid memory on any nodes.  Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
slots.

I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:

Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the
module...

On 02/22/2018 03:22 PM, taii...@gmx.com wrote:

On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:


Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
(~1000rpm)

In the case I have to reflash the module, is it possible to
hotplug it?

Hotplugging is dangerous and not supported, don't do it.

Thank you very much for your support.

You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to
support
OpenBMC, so you need a new version with the patches.

-- Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
- -- 
Timothy Pearson

Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJakJ8tAAoJEK+E3vEXDOFbgE8H/0fScUm7FW3BPtyuNkUl0KOG
Q2LI1GtlNQtTRRpyPu0baympNxi7Yz0L2n+LMoqu5yfTiqvpMw2WRAppap+6/RR+
MxWXSzhJ2v8DNcAW4+bZfA98m33SDjxz7hy5alZftkqFL2Bbi31X6e7EsIggKyls
/6kVDwY/0uaH7WhBPkk9KMo3pxaI0w4kHvnj969wF9xwGN85rQ+hm5WOJk6JbTwD
9fnw5zx+NTADFO5VebQOfvRYbZuSGvEv/Cjkuh+u8l/pEoGi4dT4NlNJbtOThqVo
uNw5lCUKLsH+imWy/lZqTc7M9CMlPK7hhqUqpdwgrtO5lVUze/BUPZwyTh1YKzc=
=0oAv
-END PGP SIGNATURE-



--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-23 Thread Timothy Pearson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

No worries.  I'm glad you were able to get the BMC running; it's great
to see more users of this technology!

On 02/23/2018 05:09 PM, Elisenda Cuadros wrote:
> Sorry, I need to read better.
> 
> Thank you.
> 
> I am going to try the patches now.
> 
> Regards,
> 
> - Eli
> 
> 
> On 24/02/18 00:01, Timothy Pearson wrote:
> You need these patches:
> 
> https://review.coreboot.org/#/c/19822/
> 
> This one in particular:
> 
> https://review.coreboot.org/#/c/coreboot/+/19820/
> 
> This is noted on the Raptor status page:
> 
> https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php
> 
> See the link to "Initial coreboot patches".
> 
> If anyone wants to take over upstreaming of the patches in that list
> they are welcome to do so!
> 
> On 02/23/2018 04:38 PM, Elisenda Cuadros wrote:
 Hello,

 Thank you for your reply.

 I reflashed (same build) the BMC module with a hotplug. Now it works
 like a charm, it got an ip, I can log through ssh, reboot, etc..

 But now I have a new problem. If I try to boot from a halted system,
 with BMC module attached, the system fires up but Coreboot hangs:

 Unable to detect valid memory on any nodes.  Halting!
 mct_d: fatalexit

 If I remove the BMC module the system boots fine.

 I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
 slots.

 I attach both console logs.

 Regards,

 - Eli



 On 22/02/18 22:36, Timothy Pearson wrote:
> Actually, for OpenBMC work, hotplugging is often the only way to go.
> Just be very careful to align the pins correctly the first time; you
> don't have a second chance if you misalign the pins and fry the
> module...
>
> On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
>> On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
>>
>>> Hi,
>>>
>>> Now I trying to use your OpenBMC port.
>>>
>>> I followed the instructions and everything was fine (compiling,
>>> reading and flashing). I waited several minutes after flashing, but
>>> the module didn 't blinked like in the vendor rom, nor did it receive
>>> an ip.
>>>
>>> I halted the system because I thought maybe it needs a cold start.
>>>
>>> After this, the system doesn't boot with the module plugged in. The
>>> fans begin to spin for approximately 1/4 second, but nothing else.
>>>
>>> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
>>> (~1000rpm)
>>>
>>> In the case I have to reflash the module, is it possible to
>>> hotplug it?
>> Hotplugging is dangerous and not supported, don't do it.
>>> Thank you very much for your support.
>> You can use a test clip to externally flash it via a flashing device
>> (not sure which can do 16 pins though, I would inquire on the flashrom
>> mailinglist)
>>
>> Are you using the latest coreboot? AFAIK coreboot was patched to
>> support
>> OpenBMC, so you need a new version with the patches.
> 
> -- Timothy Pearson
> Raptor Engineering
> +1 (415) 727-8645 (direct line)
> +1 (512) 690-0200 (switchboard)
> https://www.raptorengineering.com

- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJakJ8tAAoJEK+E3vEXDOFbgE8H/0fScUm7FW3BPtyuNkUl0KOG
Q2LI1GtlNQtTRRpyPu0baympNxi7Yz0L2n+LMoqu5yfTiqvpMw2WRAppap+6/RR+
MxWXSzhJ2v8DNcAW4+bZfA98m33SDjxz7hy5alZftkqFL2Bbi31X6e7EsIggKyls
/6kVDwY/0uaH7WhBPkk9KMo3pxaI0w4kHvnj969wF9xwGN85rQ+hm5WOJk6JbTwD
9fnw5zx+NTADFO5VebQOfvRYbZuSGvEv/Cjkuh+u8l/pEoGi4dT4NlNJbtOThqVo
uNw5lCUKLsH+imWy/lZqTc7M9CMlPK7hhqUqpdwgrtO5lVUze/BUPZwyTh1YKzc=
=0oAv
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-23 Thread Elisenda Cuadros 

Sorry, I need to read better.

Thank you.

I am going to try the patches now.

Regards,

- Eli


On 24/02/18 00:01, Timothy Pearson wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You need these patches:

https://review.coreboot.org/#/c/19822/

This one in particular:

https://review.coreboot.org/#/c/coreboot/+/19820/

This is noted on the Raptor status page:

https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

See the link to "Initial coreboot patches".

If anyone wants to take over upstreaming of the patches in that list
they are welcome to do so!

On 02/23/2018 04:38 PM, Elisenda Cuadros wrote:

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works
like a charm, it got an ip, I can log through ssh, reboot, etc..

But now I have a new problem. If I try to boot from a halted system,
with BMC module attached, the system fires up but Coreboot hangs:

Unable to detect valid memory on any nodes.  Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
slots.

I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:

Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the module...

On 02/22/2018 03:22 PM, taii...@gmx.com wrote:

On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:


Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
(~1000rpm)

In the case I have to reflash the module, is it possible to hotplug it?

Hotplugging is dangerous and not supported, don't do it.

Thank you very much for your support.

You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to support
OpenBMC, so you need a new version with the patches.


- -- 
Timothy Pearson

Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJakJ03AAoJEK+E3vEXDOFbW/0H/1DOjUMNrB5tOxw1OkGnRVK0
/KucTV0HjqPwtvhyyHeU6T9cFdAAkTHICFeGXXm05GBSeCTXWKOp38xO92hWCp88
zedukp8mq+AAzg6R1yfd6Z3MsD1pmueUKWvV0ca1lxkfAGacUzND0xRXQaO3Jel6
n0VYv0GOSDCjp34MClawUZ7ie309u68YnEQhkyFd56oXsTCfvHl8j2dwO8RmmtJt
gs+JHOTZAMgBSzn8DJigh5hiNA7B93A8Lst/Q+oFfxwibhSWGDXCmdDlcBu/VNcM
ZNF3DYYa6u6bQB8xNvous8HCn5aUEvU2vNbAci+R15S1fNEnO+fn/+F5X96mHyk=
=DRWR
-END PGP SIGNATURE-



--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-23 Thread Timothy Pearson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You need these patches:

https://review.coreboot.org/#/c/19822/

This one in particular:

https://review.coreboot.org/#/c/coreboot/+/19820/

This is noted on the Raptor status page:

https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php

See the link to "Initial coreboot patches".

If anyone wants to take over upstreaming of the patches in that list
they are welcome to do so!

On 02/23/2018 04:38 PM, Elisenda Cuadros wrote:
> Hello,
> 
> Thank you for your reply.
> 
> I reflashed (same build) the BMC module with a hotplug. Now it works
> like a charm, it got an ip, I can log through ssh, reboot, etc..
> 
> But now I have a new problem. If I try to boot from a halted system,
> with BMC module attached, the system fires up but Coreboot hangs:
> 
> Unable to detect valid memory on any nodes.  Halting!
> mct_d: fatalexit
> 
> If I remove the BMC module the system boots fine.
> 
> I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange
> slots.
> 
> I attach both console logs.
> 
> Regards,
> 
> - Eli
> 
> 
> 
> On 22/02/18 22:36, Timothy Pearson wrote:
>> Actually, for OpenBMC work, hotplugging is often the only way to go.
>> Just be very careful to align the pins correctly the first time; you
>> don't have a second chance if you misalign the pins and fry the module...
>>
>> On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
>>> On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
>>>
 Hi,

 Now I trying to use your OpenBMC port.

 I followed the instructions and everything was fine (compiling,
 reading and flashing). I waited several minutes after flashing, but
 the module didn 't blinked like in the vendor rom, nor did it receive
 an ip.

 I halted the system because I thought maybe it needs a cold start.

 After this, the system doesn't boot with the module plugged in. The
 fans begin to spin for approximately 1/4 second, but nothing else.

 My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
 (~1000rpm)

 In the case I have to reflash the module, is it possible to hotplug it?
>>> Hotplugging is dangerous and not supported, don't do it.
 Thank you very much for your support.
>>> You can use a test clip to externally flash it via a flashing device
>>> (not sure which can do 16 pins though, I would inquire on the flashrom
>>> mailinglist)
>>>
>>> Are you using the latest coreboot? AFAIK coreboot was patched to support
>>> OpenBMC, so you need a new version with the patches.


- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJakJ03AAoJEK+E3vEXDOFbW/0H/1DOjUMNrB5tOxw1OkGnRVK0
/KucTV0HjqPwtvhyyHeU6T9cFdAAkTHICFeGXXm05GBSeCTXWKOp38xO92hWCp88
zedukp8mq+AAzg6R1yfd6Z3MsD1pmueUKWvV0ca1lxkfAGacUzND0xRXQaO3Jel6
n0VYv0GOSDCjp34MClawUZ7ie309u68YnEQhkyFd56oXsTCfvHl8j2dwO8RmmtJt
gs+JHOTZAMgBSzn8DJigh5hiNA7B93A8Lst/Q+oFfxwibhSWGDXCmdDlcBu/VNcM
ZNF3DYYa6u6bQB8xNvous8HCn5aUEvU2vNbAci+R15S1fNEnO+fn/+F5X96mHyk=
=DRWR
-END PGP SIGNATURE-

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-23 Thread Elisenda Cuadros 

Hello,

Thank you for your reply.

I reflashed (same build) the BMC module with a hotplug. Now it works 
like a charm, it got an ip, I can log through ssh, reboot, etc..


But now I have a new problem. If I try to boot from a halted system, 
with BMC module attached, the system fires up but Coreboot hangs:


Unable to detect valid memory on any nodes.  Halting!
mct_d: fatalexit

If I remove the BMC module the system boots fine.

I have 4 Micron MT18JSF25672PDZ-1G4F1DD modules, located in CPU1 orange 
slots.


I attach both console logs.

Regards,

- Eli



On 22/02/18 22:36, Timothy Pearson wrote:

Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the module...

On 02/22/2018 03:22 PM, taii...@gmx.com wrote:

On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:


Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling,
reading and flashing). I waited several minutes after flashing, but
the module didn 't blinked like in the vendor rom, nor did it receive
an ip.

I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The
fans begin to spin for approximately 1/4 second, but nothing else.

My two fans (1 cpu & 1 chassis) have 3 pins and are low speed (~1000rpm)

In the case I have to reflash the module, is it possible to hotplug it?

Hotplugging is dangerous and not supported, don't do it.

Thank you very much for your support.

You can use a test clip to externally flash it via a flashing device
(not sure which can do 16 pins though, I would inquire on the flashrom
mailinglist)

Are you using the latest coreboot? AFAIK coreboot was patched to support
OpenBMC, so you need a new version with the patches.


Console_Without_BMC.log.gz
Description: application/gzip


Console_With_BMC.log.gz
Description: application/gzip
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-23 Thread Thierry Laurion 
Better here, sorry.
https://github.com/osresearch/heads/issues/134

Le ven. 23 févr. 2018 00:26, Thierry Laurion  a
écrit :

> Actually if others of you want to contribute, there is this heads kgpe-d16
> port that permits to flash directly from the heads coreboot payload with
> Timothy's patches on the flashrom tools. You may want to take a look here :
> https://github.com/flammit/heads/pull/9#issuecomment-362022411
>
> Le jeu. 22 févr. 2018 16:37, Timothy Pearson <
> tpear...@raptorengineering.com> a écrit :
>
>> Actually, for OpenBMC work, hotplugging is often the only way to go.
>> Just be very careful to align the pins correctly the first time; you
>> don't have a second chance if you misalign the pins and fry the module...
>>
>> On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
>> > On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
>> >
>> >> Hi,
>> >>
>> >> Now I trying to use your OpenBMC port.
>> >>
>> >> I followed the instructions and everything was fine (compiling,
>> >> reading and flashing). I waited several minutes after flashing, but
>> >> the module didn 't blinked like in the vendor rom, nor did it receive
>> >> an ip.
>> >>
>> >> I halted the system because I thought maybe it needs a cold start.
>> >>
>> >> After this, the system doesn't boot with the module plugged in. The
>> >> fans begin to spin for approximately 1/4 second, but nothing else.
>> >>
>> >> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed
>> (~1000rpm)
>> >>
>> >> In the case I have to reflash the module, is it possible to hotplug it?
>> > Hotplugging is dangerous and not supported, don't do it.
>> >> Thank you very much for your support.
>> > You can use a test clip to externally flash it via a flashing device
>> > (not sure which can do 16 pins though, I would inquire on the flashrom
>> > mailinglist)
>> >
>> > Are you using the latest coreboot? AFAIK coreboot was patched to support
>> > OpenBMC, so you need a new version with the patches.
>>
>>
>> --
>> Timothy Pearson
>> Raptor Engineering
>> +1 (415) 727-8645 (direct line)
>> +1 (512) 690-0200 (switchboard)
>> https://www.raptorengineering.com
>>
>> --
>> coreboot mailing list: coreboot@coreboot.org
>> https://mail.coreboot.org/mailman/listinfo/coreboot
>>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-22 Thread Thierry Laurion 
Actually if others of you want to contribute, there is this heads kgpe-d16
port that permits to flash directly from the heads coreboot payload with
Timothy's patches on the flashrom tools. You may want to take a look here :
https://github.com/flammit/heads/pull/9#issuecomment-362022411

Le jeu. 22 févr. 2018 16:37, Timothy Pearson 
a écrit :

> Actually, for OpenBMC work, hotplugging is often the only way to go.
> Just be very careful to align the pins correctly the first time; you
> don't have a second chance if you misalign the pins and fry the module...
>
> On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
> > On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
> >
> >> Hi,
> >>
> >> Now I trying to use your OpenBMC port.
> >>
> >> I followed the instructions and everything was fine (compiling,
> >> reading and flashing). I waited several minutes after flashing, but
> >> the module didn 't blinked like in the vendor rom, nor did it receive
> >> an ip.
> >>
> >> I halted the system because I thought maybe it needs a cold start.
> >>
> >> After this, the system doesn't boot with the module plugged in. The
> >> fans begin to spin for approximately 1/4 second, but nothing else.
> >>
> >> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed (~1000rpm)
> >>
> >> In the case I have to reflash the module, is it possible to hotplug it?
> > Hotplugging is dangerous and not supported, don't do it.
> >> Thank you very much for your support.
> > You can use a test clip to externally flash it via a flashing device
> > (not sure which can do 16 pins though, I would inquire on the flashrom
> > mailinglist)
> >
> > Are you using the latest coreboot? AFAIK coreboot was patched to support
> > OpenBMC, so you need a new version with the patches.
>
>
> --
> Timothy Pearson
> Raptor Engineering
> +1 (415) 727-8645 (direct line)
> +1 (512) 690-0200 (switchboard)
> https://www.raptorengineering.com
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-22 Thread Timothy Pearson 
Actually, for OpenBMC work, hotplugging is often the only way to go.
Just be very careful to align the pins correctly the first time; you
don't have a second chance if you misalign the pins and fry the module...

On 02/22/2018 03:22 PM, taii...@gmx.com wrote:
> On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:
> 
>> Hi,
>>
>> Now I trying to use your OpenBMC port.
>>
>> I followed the instructions and everything was fine (compiling,
>> reading and flashing). I waited several minutes after flashing, but
>> the module didn 't blinked like in the vendor rom, nor did it receive
>> an ip.
>>
>> I halted the system because I thought maybe it needs a cold start.
>>
>> After this, the system doesn't boot with the module plugged in. The
>> fans begin to spin for approximately 1/4 second, but nothing else.
>>
>> My two fans (1 cpu & 1 chassis) have 3 pins and are low speed (~1000rpm)
>>
>> In the case I have to reflash the module, is it possible to hotplug it?
> Hotplugging is dangerous and not supported, don't do it.
>> Thank you very much for your support.
> You can use a test clip to externally flash it via a flashing device
> (not sure which can do 16 pins though, I would inquire on the flashrom
> mailinglist)
> 
> Are you using the latest coreboot? AFAIK coreboot was patched to support
> OpenBMC, so you need a new version with the patches.


-- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] OpenBMC & KGPE-D16

2018-02-22 Thread taii...@gmx.com 

On 02/17/2018 09:46 AM, Elisenda Cuadros wrote:


Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling, 
reading and flashing). I waited several minutes after flashing, but 
the module didn 't blinked like in the vendor rom, nor did it receive 
an ip.


I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The 
fans begin to spin for approximately 1/4 second, but nothing else.


My two fans (1 cpu & 1 chassis) have 3 pins and are low speed (~1000rpm)

In the case I have to reflash the module, is it possible to hotplug it?

Hotplugging is dangerous and not supported, don't do it.

Thank you very much for your support.
You can use a test clip to externally flash it via a flashing device 
(not sure which can do 16 pins though, I would inquire on the flashrom 
mailinglist)


Are you using the latest coreboot? AFAIK coreboot was patched to support 
OpenBMC, so you need a new version with the patches.


--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

[coreboot] OpenBMC & KGPE-D16

2018-02-17 Thread Elisenda Cuadros 

Hi,

Now I trying to use your OpenBMC port.

I followed the instructions and everything was fine (compiling, reading 
and flashing). I waited several minutes after flashing, but the module 
didn 't blinked like in the vendor rom, nor did it receive an ip.


I halted the system because I thought maybe it needs a cold start.

After this, the system doesn't boot with the module plugged in. The fans 
begin to spin for approximately 1/4 second, but nothing else.


My two fans (1 cpu & 1 chassis) have 3 pins and are low speed (~1000rpm)

In the case I have to reflash the module, is it possible to hotplug it?

Thank you very much for your support.

Regards,

- Eli


On 14/02/18 23:54, Timothy Pearson wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

To try the OpenBMC port you don't need to solder anything; you just need
to find an ASMB4-iKVM module and program it.  Soldering is for if you
want access to the JTAG connector for low-level development (U-Boot
development, mostly).

https://www.asus.com/Commercial-Servers-Workstations/ASMB4iKVM/

The ASMB5-iKVM also works from a hardware perspective, but both may be
hard to find as the KGPE-D16 and the Opterons it uses are now out of
production.

On 02/14/2018 04:50 PM, Elisenda Cuadros wrote:

Yes, I cleaned the CPU before but it's obvious it wasn't shiny :-) .

I want to try your OpenBMC port. I readed I have to solder the 20 pin
connector.

Pin 1 is the squared shape, isn't it? But which is Pin 1 in the female
connector?

Best regards,

- Eli


On 14/02/18 23:42, Timothy Pearson wrote:
Good to hear.  I was going to mention bad CPU but that seemed unlikely;
on this end we always make sure the CPU contacts are shiny before
attempting boot so that could explain the discrepancy.

On 02/14/2018 04:38 PM, Elisenda Cuadros wrote:

Thank you for your reply Timothy.

I removed the heatsink and cleaned the cpu contacts.

Now it boots.

Thank you for your support.

Best regards,

- Eli


On 14/02/18 22:46, Timothy Pearson wrote:
Dead / incompatible DIMM, DIMM(s) in wrong slots, or damaged mainboard.
The fact that the vendor BIOS won't post is a very bad sign, since in
our experience the vendor BIOS is far more forgiving of faulty DIMMs
than coreboot (basically, the vendor BIOS will show something on the VGA
port even if the DIMMs are completely damaged and unable to properly
store data).

On 02/14/2018 03:28 PM, Elisenda Cuadros wrote:

Hello,

I recently bought an Asus KGPE-D16 board, with an Opteron 6238 and 4
Micron MT18JSF25672PDZ-1G4F1DD modules.

Firstly I tried to boot with vendor BIOS but I don't get any output
on VGA.

I have a PCI Post Card and it seems it arrives to 3E and then I
think it
enters in a loop.

I flashed Coreboot with default settings just to try to get some more
useful logs. The result I think is more or less the same, it doesn't
arrive to payload.

Memory is installed in A2,B2,C2 and D2 slots.

I spent multiple hours trying to figure where is the problem.

Do you have any ideas?

I attach the console log.

Thanks in advance.

Best Regards,

- Eli


-- Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com

-- Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
- -- 
Timothy Pearson

Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJahL47AAoJEK+E3vEXDOFbtcoIAJkkd0yqvExnFwqrx2j91sUF
jPkMCTd1lKPMPOYp8lFfDeG9hcBP8RBpuf/G32bhGvjArVEwIgqPWghiygLK6W6M
yn+I+utV6N2XxAzO/y0lnJYtswOF7Ppq9TutBENGdfwh5vlm5sCpLbcp30Fvbd9L
vdUkBhhzfb3BBN/87RvqGzxWiqgYkoOYtfXy7ZndpIFNzeSqsY0+z79uQhrW9EEf
d44OIR/dxJ3nC5pQAlZtbC6jxI1TsP79cUP5d6BZgJfaMCVliNtc/Tat/gTM4kyH
SniuCwEVoPOCxGCUufw6UOZtElm8BlCCE07XclzkkmH9Rk8WugXhhwrnR3yNU+k=
=LqqY
-END PGP SIGNATURE-


-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot