All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: rk3399-gru-kevin: issues on bringup
Date: Sun, 2 Aug 2020 21:02:07 -0600	[thread overview]
Message-ID: <CAPnjgZ1yF+FzfXLEBLNQBBG9RKO3JET0k+mU6pE0mDQDhE7rfw@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ2-0psqWRboTuxGnOqXcuQW87iz3LaB=ERgpFyFA9n-hA@mail.gmail.com>

Hi Marty,

On Fri, 31 Jul 2020 at 12:30, Simon Glass <sjg@chromium.org> wrote:
>
> Hi Marty,
>
> On Fri, 31 Jul 2020 at 05:19, Marty E. Plummer <hanetzer@startmail.com> wrote:
> >
> > On Tue, Jul 28, 2020 at 12:58:30PM -0600, Simon Glass wrote:
> > > Hi Marty,
> > >
> > > On Tue, 21 Jul 2020 at 21:07, Marty E. Plummer <hanetzer@startmail.com> wrote:
> > > >
> > > > On Tue, Jul 21, 2020 at 10:21:52AM -0600, Simon Glass wrote:
> > > > > Hi Marty,
> > > > >
> > > > > Did you check spl_boot_device()?
> > > > >
> > > > After sending the initial email I noticed your binman work, which does
> > > > some of the stuff I think I need. My current setup is as follows:
> > > >
> > > >
> > > > > Also take a look at the CONFIG_TARGET stuff in the code as it might
> > > > > speciy BOB but not KEVIN.
> > > > Yeah. I worked that in.
> > > >
> > > > Currently, a rom which is built with these changes (assuming u-boot.rom
> > > > is what I want for SPI booting; strange its only 4mb, aren't these
> > > > devices 8mb flash?) I get no output at all over the servo, aside from
> > > > the EC.
> > >
> > > I think it is only 4MB.
> > >
> > Nah, kevin is deffo 8mb flash chip. Otherwise I wouldn't have been able
> > to shove a 7.xmb kernel+initramfs into a coreboot image and flash it.
>
> Well that's odd. Maybe Kevin got a larger device than gru?
>
> >
> > I have to pad the u-boot.rom with dd to flash it.
> > > I am not sure that I have a kevin. Did you try using the debug UART?
> > >
> > Yeah, assuming you mean `dut-control cpu_uart_pty` with a servo hooked
> > up, and using `socat READLINE /dev/pts/something`. I get no output, but
> > the same chromiumos chroot with vanilla coreboot+depthcharge and
> > hardware config does do output as expected.
> >
> > Perhaps I'm missing something simple.
>
> Probably, it often is. But what?!
>
> I actually just found some old Chromebooks I didn't know i had, so I
> have a Kevin. If you push your tree somewhere I might be able to take
> a look this weekend.

I dug this out but I cannot get it to boot with the em100 emulator.
I'll see if I can figure that out at some point. Sometimes I get
serial garbage as well.

It is surprising that the flash is 8MB when Gru is 4MB. Must have run
out of room.

Regards,
Simon

  reply	other threads:[~2020-08-03  3:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  3:32 rk3399-gru-kevin: issues on bringup Marty E. Plummer
2020-07-21 16:21 ` Simon Glass
2020-07-22  3:06   ` Marty E. Plummer
2020-07-28 18:58     ` Simon Glass
2020-07-31 11:19       ` Marty E. Plummer
2020-07-31 18:30         ` Simon Glass
2020-08-03  3:02           ` Simon Glass [this message]
2020-08-03 13:49             ` Simon Glass
2020-08-04  2:13               ` Simon Glass
2020-08-07  3:03                 ` Marty E. Plummer
2020-08-13 17:35 Alper Nebi Yasak
2021-02-23 15:10 ` Simon Glass
2021-02-23 21:36   ` Marty E. Plummer
2021-02-24 16:31     ` Simon Glass
2021-02-24 17:35       ` Marty E. Plummer
2021-03-11  4:52 ` Simon Glass
2021-03-13 19:39   ` Marty E. Plummer
2021-03-14  1:00     ` Simon Glass
2021-11-01 23:25       ` Alper Nebi Yasak
2021-11-02  8:09         ` Peter Robinson
2021-11-02 11:58           ` Alper Nebi Yasak
2021-11-02 23:05         ` Simon Glass
2021-11-06  3:16           ` Simon Glass
2021-11-07 17:26             ` Alper Nebi Yasak
2021-11-25  0:12               ` Simon Glass
2021-11-25 17:18                 ` Alper Nebi Yasak

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=CAPnjgZ1yF+FzfXLEBLNQBBG9RKO3JET0k+mU6pE0mDQDhE7rfw@mail.gmail.com \
    --to=sjg@chromium.org \
    --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.