All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Galileo instructions
Date: Mon, 14 Sep 2015 20:49:15 +0800	[thread overview]
Message-ID: <CAEUhbmUTt0_Rryj9hRb-8dzEb3Zw_-SMfL4taZpm_0HCtCwQ-w@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ2g_kH4xANwjy-LhaJv-EsvEOiJHALt+LdWhUhT=G5hng@mail.gmail.com>

Hi Simon,

On Mon, Sep 14, 2015 at 8:45 PM, Simon Glass <sjg@chromium.org> wrote:
> Hi Bin,
>
> On 13 September 2015 at 03:28, Bin Meng <bmeng.cn@gmail.com> wrote:
>> Hi Simon,
>>
>> On Sun, Sep 13, 2015 at 5:06 AM, Simon Glass <sjg@chromium.org> wrote:
>>> Hi Bin,
>>>
>>> I have a Galileo Gen 2 and am trying to get U-Boot to start on it. The
>>> first problem I have is that the schematic says the chip is a W25Q64FV
>>> which I think is an 8MB part, but the image produced is only 1MB.
>>
>> Yes, the board has an 8MB SPI flash, but U-Boot (u-boot.rom) only
>> utilizes the last 1MB.
>>
>>>
>>> Also I know that there is a Gen 1 and a Gen 2. I recall you saying
>>> that U-Boot supports the Gen 2 but can easily support the Gen 1. But
>>> perhaps I have done something wrong.
>>>
>>
>> I've verified U-Boot can boot on both gen1 and gen2 boards.
>
> Thanks.
>>
>>> I downloaded the BSP from here:
>>>
>>> https://downloadcenter.intel.com/download/23197/Intel-Quark-BSP
>>>
>>> File name: Board_Support_Package_Sources_for_Intel_Quark_v1.1.0.7z
>>> Version: 1.1.0 (Latest)
>>>
>>> Date: 03/03/2015
>>> Size: 2.72 MB
>>>
>>> Any hints? I am using a dediprog em100 with a test clip over the flash chip.
>>>
>>
>> It's not clear to me what issue you got. It looks like there might be
>> some issue for dediporg em100 to handle the rom size mismatch? If this
>> is the case, you can just create an 8MB u-boot.rom with the 1MB
>> version with other 7MB filled up with 0xFFs.
>
> OK I did this and it works, thanks.

So it's indeed the dediprog em100 cannot handle the rom mismatch?

> Why don't we just change the ROM size? This point is not mentioned in README.x86.
>

1MB is enough for U-Boot. u-boot.rom does not necessarily have to
match the SPI flash size. And on Galileo since there is no Intel ME,
so we don't need to create a whole 8MB rom. This is the same as Intel
CrownBay, which has a 2MB SPI flash, but still 1MB u-boot.rom.

Regards,
Bin

  reply	other threads:[~2015-09-14 12:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-12 21:06 [U-Boot] Galileo instructions Simon Glass
2015-09-13  9:28 ` Bin Meng
2015-09-14 12:45   ` Simon Glass
2015-09-14 12:49     ` Bin Meng [this message]
2015-09-14 12:51       ` Simon Glass
2015-09-14 13:59         ` Bin Meng
2015-09-14 14:32           ` Bin Meng
2015-09-15  1:52             ` Simon Glass
2015-09-15  2:06               ` Bin Meng
2015-09-15  2:15                 ` Simon Glass
2015-09-15  2:30                   ` Bin Meng
2015-09-21 19:41                     ` Simon Glass
2015-09-22  2:06                       ` Bin Meng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEUhbmUTt0_Rryj9hRb-8dzEb3Zw_-SMfL4taZpm_0HCtCwQ-w@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.