All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Cc: "Marty E. Plummer" <hanetzer@startmail.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: rk3399-gru-kevin: issues on bringup
Date: Tue, 2 Nov 2021 17:05:32 -0600	[thread overview]
Message-ID: <CAPnjgZ2Wb4Rq=U209VzszeDj2ac97Qs62rkvRd14xQCfOSVWyA@mail.gmail.com> (raw)
In-Reply-To: <36a426d2-6745-91e4-2878-a2c6f831c697@gmail.com>

Hi Alpher,

On Mon, 1 Nov 2021 at 17:25, Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote:
>
> Hi,
>
> I've had some recent success with my gru-kevin and wanted to update you
> on this. Long story short, I can boot from SPI flash and have the
> display, keyboard, eMMC, microSD card, USB disks all work (however with
> some hacks); but can't boot into Linux. Things seem to hang shortly
> after "Starting kernel..." but I don't know if something fails in U-Boot
> or if I get a kernel panic. (I still have no serial console).
>
> There are three relevant branches on my GitHub repo now, please have a
> look. The first is for what I intend to send upstream soon enough. The
> other two include hacks and additional patches that build on top of the
> first, meant to improve things on a per-board basis:
>
>     https://github.com/alpernebbi/u-boot/tree/rk3399-gru-chromebooks
>     https://github.com/alpernebbi/u-boot/tree/rk3399-gru-kevin
>     https://github.com/alpernebbi/u-boot/tree/rk3399-gru-bob
>
> I have no idea if the gru-bob versions work. I just thought things I did
> for gru-kevin are applicable to it as well and decided I should include
> them in case anyone wants to test.
>
>
> I also want to ask you some things I'm indecisive about, before posting
> the rk3399-gru-chromebooks branch as patches.
>
> Most of the patches are small config and dts changes that I've grouped
> by whatever effect they have. Should I squash them into one commit each
> for config/dts?

Probably best.

>
> Simon, I've edited some of your patches and kept you as author &
> sign-off. Are you OK with the edited versions, am I doing things right? See:
>
>
> https://github.com/alpernebbi/u-boot/commit/8c658b7811f4324cd699bd035e802f9339efa8f7
>
> https://github.com/alpernebbi/u-boot/commit/c2c68f23e10a51b8d34c00764a33fc847d785f60
>
> https://github.com/alpernebbi/u-boot/commit/995454193906e04bfb4e0e38f2bf1a18634a1ebf

LGTM

>
> Marty, your (second) chromebook_kevin support patch didn't have your
> sign-off. Is it OK to add it? See:
>
>
> https://github.com/alpernebbi/u-boot/commit/4cee351e012dc26714640e868069b5cc4b5a8329
>
> I also think I should squash my gru-kevin changes into that commit, add
> a commit message about board status, and keep Marty as author & sign-off
> while adding myself as Co-authored-by & sign-off. Any better ideas on
> how to structure the patches?
>
> Do both of you want to be in /board/google/gru/MAINTAINERS? I have three
> of us listed there right now, but no idea if that's fine with you two.
>
> Hope you can spare time on this.

I actually have bob in my lab but I have not tried the Chrome OS boot
script on it. I could probably add kevin.

$ do-try-int.sh bob
Revision 77680d8f85b94ffe690b8fe1f35767aef8b1415a, board bob

Checking revision 77680d8f85b94ffe690b8fe1f35767aef8b1415a
/vid/software/devel/ubtest
tbot starting ...
├─Parameters:
│     rev        = '77680d8f85b94ffe690b8fe1f35767aef8b1415a'
│     clean      = False
├─Calling uboot_build_and_flash ...
│   ├─bob is on port 9904 and uses /dev/pts/39
│   ├─POWERON (bob)
│   ├─Calling uboot_build ...
│   │   ├─Calling uboot_checkout ...
│   │   │   ├─Builder: bob
│   │   │   └─Done. (1.038s)
│   │   ├─Configuring build ...
│   │   ├─Calling uboot_make ...
│   │   │   └─Done. (9.073s)
│   │   └─Done. (10.454s)
│   ├─Calling uboot_flash ...
│   │   └─Done. (0.677s)
│   ├─POWEROFF (bob)
│   └─Done. (11.868s)
├─────────────────────────────────────────
└─SUCCESS (11.994s)
tbot starting ...
├─Calling interactive_board ...
│   ├─bob is on port 9904 and uses /dev/pts/39
│   ├─POWERON (bob)
│   ├─Entering interactive shell (CTRL+D to exit) ...
�Channel 0: LPDDR3, 933MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR3, 933MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride

U-Boot SPL 2021.10-00181-g77680d8f85b (Nov 02 2021 - 09:07:44 -0600)
Trying to boot from SPI
rockchip_rk3399_pinctrl pinctrl: pinctrl_select_state_full:
uclass_get_device_by_phandle_id: err=-19
rockchip_rk3399_pinctrl pinctrl: pinctrl_select_state_full:
uclass_get_device_by_phandle_id: err=-19
ns16550_serial serial@ff1a0000: pinctrl_select_state_full:
uclass_get_device_by_phandle_id: err=-19


U-Boot 2021.10-00181-g77680d8f85b (Nov 02 2021 - 09:07:44 -0600)

Model: Google Bob
DRAM:  3.9 GiB
Cannot find regulator pwm init_voltage
MMC:   mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Got rc -1, expected 100
Failed to probe keyboard 'keyboard-controller'
In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Google Bob
Net:   No ethernet found.
Hit any key to stop autoboot:  0
=>

Regards,
Simon

  parent reply	other threads:[~2021-11-02 23:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 17:35 rk3399-gru-kevin: issues on bringup 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2020-07-20  3:32 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
2020-08-03 13:49             ` Simon Glass
2020-08-04  2:13               ` Simon Glass
2020-08-07  3:03                 ` Marty E. Plummer

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='CAPnjgZ2Wb4Rq=U209VzszeDj2ac97Qs62rkvRd14xQCfOSVWyA@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=alpernebiyasak@gmail.com \
    --cc=hanetzer@startmail.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.