[coreboot] Help on setting clock speed in coreboot

[Zoran Stojsavljevic]

Mayuri,

Yes, the easiest way to check if your custom HW is working, to try TX/RX
using Linux Distros Ubuntu or Fedora 24 (I use for all INTEL HW testings
ONLY Fedora 14 and up (latest F24), since I am very very familiar with
Fedora). With putty package, I (at least, not the last) am very familiar
with it.

I would advise to check both reference (E3825) and custom (E3845) boards
with Linux OSes, to see if everything is OK with serial.

If yes, HW is All Cool. Then something else is the problem.

Peter (Stuge) has also a good idea. You should do the both. But at first,
my approach, to save scope measurements (if?).

Zoran

On Wed, Jul 13, 2016 at 7:49 PM, Mayuri Tendulkar <
mayuri.tendulkar at aricent.com> wrote:

> Hi Zoran
>
>
>
> Thanks for ur suggestions.
>
>
>
> When I mentioned I got brkthru means- I was able to bringup coreboot with
> seabios and Ubuntu linux up on my customized board with E3845. Display
> comes up fine.
>
>
>
> But serial is still having some issue and keeps giving out some garbage,
> not sure what is the problem.
>
>
>
> Tiano core payload is still not working, so currently managing with
> seabios, but that’s next on the list to debug. Any advice on this? Anybody
> has tried this?
>
>
>
>
>
> ‘If you did make it with normal AMI/PHOENIX BIOS, you should try to
> install Fedora 24 on the top of it, and install PuTTY terminal (# dnf
> install putty). Please, try to receive something on serial over USB (most
> likely ttyUSB0 device when you insert the serial to USB gadget), settings:
> 115200, 8, 1, no parity, no flow control. BYT in general, especially BYT-I,
> has (as I recall) all good with serial ports, which is not always the case
> with some other families.
>
>
>
> This should work.’
>
>
>
> n  This you are saying after loading OS, I shd check if serial works or
> not right. I can check that. But main point is if I need to debug more on
> coreboot to optimize/tune anything more for my board, I don’t have serial
> up.
>
> n  Display comes up and directly shows payload is loaded, so not able to
> get whats happening before that.
>
>
>
>
>
> Regards
>
> Mayuri
>
>
>
> *From:* Zoran Stojsavljevic [mailto:zoran.stojsavljevic at gmail.com]
> *Sent:* 13 July 2016 10:43
> *To:* Naveed Ghori <naveed.ghori at dti.com.au>
> *Cc:* Mayuri Tendulkar <mayuri.tendulkar at aricent.com>; coreboot <
> coreboot at coreboot.org>
> *Subject:* Re: [coreboot] Help on setting clock speed in coreboot
>
>
>
> > We got some brkthru today. Though serial still shows garbage, *we got
> bios up and then OS also*.
>
> > USB, display came up, but serial still no luck.
>
>
>
> I assumed in my answer that your reference INTEL Valley Island board with
> E3825 works with serial port.
>
>
>
> Did not get the point. Did you get Coreboot running on custom E3845, then
> after Tiano Core as payload, or you just made it work with normal BIOS
> (with Intel BIOS Vendors - IBVs helping you) for your custom board?
>
>
>
> If you did make it with normal AMI/PHOENIX BIOS, you should try to install
> Fedora 24 on the top of it, and install PuTTY terminal (# dnf install
> putty). Please, try to receive something on serial over USB (most likely
> ttyUSB0 device when you insert the serial to USB gadget), settings: 115200,
> 8, 1, no parity, no flow control. BYT in general, especially BYT-I, has (as
> I recall) all good with serial ports, which is not always the case with
> some other families.
>
>
>
> This should work.
>
>
>
> I have for you few suggestions: try to swap your E3825 (Dual Core) SoC
> with E3845 (Quad Core) SoC (exact one you are using on your custom board)
> on your reference board (on Valley Island), and to install/program
> appropriate INTEL/AMI BIOS which supports E3845 Reference Valley Island.
> These two should be pin-to-pin compatible. Maybe even old BIOS will work...
> If you are lucky (so before BIOS reprogramming you should try this)! Then
> if E3845 by any chance works, to try again serial tests.
>
>
>
> Also you can take another path and swap another (new) E3845 with currenly
> used E3845 on your custom board. Maybe your SoC's Serial I/Os on the
> board are damaged... Could also happen.
>
>
>
> You can also try to place E3825 from Reference Valley Island to your
> custom board and try to see if it'll pass BIOS?! If happens, try to test
> serial and see what happens them?
>
>
>
> Please, do not forget the following: the boards equipped with BYT-i E3845
> Stepping D0, and with E3845 Stepping B3 are DUAL Channel memory SoCs. E3825
> Si D0 is SINGLE channel one. I know it (probably) does not have too much to
> do with your problem (just keep this info in mind). This can also influence
> your PCB design, since you have different PCBs... Could be also remote
> source of the problem?!
>
>
>
> My two ad-hoc cent to this problem. ;-)
>
>
>
> Best Regards,
>
> Zoran
>
>
>
> On Wed, Jul 13, 2016 at 3:36 AM, Naveed Ghori <naveed.ghori at dti.com.au>
> wrote:
>
> Great to hear! Serial does give out some useful information too so it will
> be useful.
>
> Maybe try a different board if you have multiples.
>
>
>
> *From:* Mayuri Tendulkar [mailto:mayuri.tendulkar at aricent.com]
> *Sent:* Wednesday, 13 July 2016 8:21 AM
> *To:* Naveed Ghori; coreboot
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> Hi
>
>
>
> We got some brkthru today. Though serial still shows garbage, we got bios
> up and then OS also. USB, display came up, but serial still no luck.
>
>
>
> We will continue debugging. Thanks for all support.
>
>
>
> We are using serial to USB, we tried putty as well as minicom.
>
>
>
> Regards
>
> Mayuri
>
>
>
> *From:* Naveed Ghori [mailto:naveed.ghori at dti.com.au
> <naveed.ghori at dti.com.au>]
> *Sent:* 12 July 2016 17:12
>
>
> *To:* Mayuri Tendulkar <mayuri.tendulkar at aricent.com>; coreboot <
> coreboot at coreboot.org>
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> The only thing I can think of is to use an oscilloscope to see if the
> signal is clear.
>
> No changes were made to the USB as it just comes up to as a COM Port and I
> connect using putty at the required baud rate.
>
> Are you using a Serial to USB or a real RS232 serial port? On Windows
> there are setting for each serial port (where you can set its baud rate
> etc, but I think these are for default connection and do not affect most
> terminal software that connect using a particular baud rate.
>
>
>
> *From:* Mayuri Tendulkar [mailto:mayuri.tendulkar at aricent.com
> <mayuri.tendulkar at aricent.com>]
> *Sent:* Wednesday, 13 July 2016 2:18 AM
> *To:* Naveed Ghori; coreboot
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> Hi
>
>
>
> Minnowboard also uses the same pin BD14 (GPIO_S0_SC[57]) as TX and 61 as
> RX and baud rate 115200.
>
>
>
> We have not enabled post codes, but only enabled serial port console o/p.
>
>
>
> It works fine on Minnowboard, but not on this.
>
>
>
> So not getting any clue.
>
>
>
> Regards
>
> Mayuri
>
>
>
> *From:* Naveed Ghori [mailto:naveed.ghori at dti.com.au
> <naveed.ghori at dti.com.au>]
> *Sent:* 11 July 2016 20:03
> *To:* Mayuri Tendulkar <mayuri.tendulkar at aricent.com>; coreboot <
> coreboot at coreboot.org>
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> First thing is to get serial output as there will probably be other
> hurdles before the display works.
>
> I used coreboot bayleybay as the basis and it had the port mentioned (pin
> BD14 (GPIO_S0_SC[57]))) setup for debug output and the baud rate of 115200.
>
> Minnowboard may be different.
>
> Also,  I had to setup the full 8MB of flash using the FITC tool but this
> is probably not your issue since you probably have serial output already.
>
> All I can think of is baud rate setting under console in “make menuconfig”.
>
>
>
> Also the output may be setup to output POST codes only in which case to a
> text terminal it will like only junk is coming out. Make sure console debug
> level is set to DEBUG or SPEW to get a lot more debug initially.
>
> Also Enable “Serial Port Console output”
>
>
>
>
>
> *From:* Mayuri Tendulkar [mailto:mayuri.tendulkar at aricent.com
> <mayuri.tendulkar at aricent.com>]
> *Sent:* Tuesday, 12 July 2016 10:53 AM
> *To:* Naveed Ghori
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> We didn’t change anything. Our base is valley island. As it was not having
> serial, we took tht part same as Minnowboard (PCU UART)
>
>
>
> Tried different rates but doesn’t work.
>
>
>
> We checked TTL levels, so we were seeing freq as 38.4, so tried tht also.
>
>
>
> Somehow its stuck somewhere as we don’t see USB and display also not
> coming, but nt able to get exact data due to serial prints.
>
>
>
> *From:* Naveed Ghori [mailto:naveed.ghori at dti.com.au
> <naveed.ghori at dti.com.au>]
> *Sent:* 11 July 2016 19:48
> *To:* Mayuri Tendulkar <mayuri.tendulkar at aricent.com>
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> Did you change anything? Is your base Bayley Bay? The default setting for
> it are 115200 with the output pin as per below.
>
> Check the console settings in the menuconfig. If you are getting junk then
> I assume it is already enabled but maybe just the baud is modified by
> mistake.
>
>
>
> *From:* Mayuri Tendulkar [mailto:mayuri.tendulkar at aricent.com
> <mayuri.tendulkar at aricent.com>]
> *Sent:* Tuesday, 12 July 2016 10:45 AM
> *To:* Naveed Ghori
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> But what settings to be added in coreboot config?
>
>
>
> *From:* Naveed Ghori [mailto:naveed.ghori at dti.com.au
> <naveed.ghori at dti.com.au>]
> *Sent:* 11 July 2016 18:42
> *To:* Mayuri Tendulkar <mayuri.tendulkar at aricent.com>; coreboot <
> coreboot at coreboot.org>
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> We take the pins direct off the E3845 (only really need the tx (pin BD14
> (GPIO_S0_SC[57]))). The pins direct are TTL so we had to use a TTL-USB
> serial port converter.
>
>
>
> *From:* Mayuri Tendulkar [mailto:mayuri.tendulkar at aricent.com
> <mayuri.tendulkar at aricent.com>]
> *Sent:* Tuesday, 12 July 2016 9:37 AM
> *To:* Naveed Ghori; coreboot
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> Thanks. We tried 115200, but it didn’t work. We checked TTL levels and
> tried to match, but no luck.
>
>
>
> Are you using PCU UART (same as minnowboard) or anything different?
>
>
>
> *From:* Naveed Ghori [mailto:naveed.ghori at dti.com.au
> <naveed.ghori at dti.com.au>]
> *Sent:* 11 July 2016 18:17
> *To:* Mayuri Tendulkar <mayuri.tendulkar at aricent.com>; coreboot <
> coreboot at coreboot.org>
> *Subject:* Re: Help on setting clock speed in coreboot
>
>
>
> Hi,
>
> Garbage usually means baud rate. Did you try 115200baud?
>
> If you are still getting garbage I would recommend seeing it on the scope
> and making sure voltage levels are fine. The output by default would be TTL
> level and may need to be converted.
>
> I have used some TTL (1.8V if I remember correctly (TTL-232RG) to convert
> the signal so I could read the output.
>
>
>
> Cheers,
>
> Naveed
>
>
>
> *From:* coreboot [mailto:coreboot-bounces at coreboot.org
> <coreboot-bounces at coreboot.org>] *On Behalf Of *Mayuri Tendulkar
> *Sent:* Tuesday, 12 July 2016 8:27 AM
> *To:* coreboot
> *Subject:* [coreboot] Help on setting clock speed in coreboot
>
>
>
> Hi Team
>
>
>
> I have a customized board based on Intel valley island design. Reference
> design uses Intel Baytrail processor E3825, while my design is using E3845.
>
>
>
> I am customizing coreboot for this E3845, but getting just garbage on
> coreboot, so not able to debug where it is stuck.
>
>
>
> When I add memory test as secondary payload, I cd see some operations
> happening on console but not able to decode it.
>
>
>
> Tried with all possible baud rates, but no success. USB and display also
> not enumerating.
>
>
>
> Can you please give some clue? Is it due to different core speed for
> E3835(1.33GHZ) vs E3845(1.91GHz).
>
>
>
> Where is the option to change this in coreboot?
>
>
>
> Appreciate your support.
>
>
>
> Regards
>
> Mayuri
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
>
> --
> coreboot mailing list: coreboot at coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20160713/6a4ed9c8/attachment.html>