public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Ezequiel Garcia" <ezequiel.garcia@collabora.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: "Paul Burton" <paul.burton@mips.com>,
	"kernelci@groups.io" <kernelci@groups.io>
Subject: Re: MIPS test results
Date: Fri, 14 Dec 2018 04:43:09 +0000	[thread overview]
Message-ID: <997-5c133500-1-763d5380@188620748> (raw)
In-Reply-To: <7h5zvxorrd.fsf@baylibre.com>

On Thursday, December 13, 2018 21:51 -03, Kevin Hilman <khilman@baylibre.com> wrote:

> Paul Burton <paul.burton@mips.com> writes:
>
> [...]
>
> > For the Ci20 there are 2 main options:
> >
> >   1) Use a U-Boot uImage.
> >
> >      The Ci20 ships with the U-Boot bootloader by default, and expects
> >      to load kernels packages in the legacy U-Boot uImage format. When
> >      you build the kernel, if you have the U-Boot mkimage tool in your
> >      $PATH, you should get a arch/mips/boot/uImage.gz file. You then
> >      load this into DDR using U-Boot, for example using the tftp
> >      command, and run the bootm command to boot the kernel.
> >
> >      Of note is that Ezequiel Garcia, CC'd, is currently working on
> >      upstreaming Ci20 support in U-Boot.
>
> u-boot is the preferred option, and I just tried it on my Ci20, but it
> seems the u-boot on this board doesn't find the network, so I can't
> DHCP/TFTP (log below[1]).
>
> If I just let the kernel boot that is flashed on the board, it boots up
> an OpenWRT image and is able to DHCP and get an IP address, so I know
> the network interface is working.
>
> Maybe Ezequiel has a newer version of u-boot with working network
> support I could try?  If so, please also send instructions for how to
> (re)flash u-boot, (or maybe boot a new u-boot from the SD card?)
>

Hey Kevin,

Yes, I have. I will push a branch for you and let you know,
so you can test with some recent U-Boot.

However... this log you have here is not from the CI20 board,
which is JZ4780 SoC, but from some development board
with a Pistachio SoC!

I thought those were dead, but it seems there are
some Pistachio boards around ?


Ezequiel

> Kevin
>
> [1]
> U-Boot SPL 2015.07-rc2 (Jul 14 2016 - 12:16:30)
>
>
> U-Boot 2015.07-rc2 (Jul 14 2016 - 12:16:30 +0000)
>
> MIPS(interAptiv): IMG Pistachio 546MHz.
> Model: IMG Marduk
> DRAM:  256 MiB
> NAND:  512 MiB
> MMC:   Synopsys Mobile storage: 0
> SF: Detected W25Q16CL with page size 256 Bytes, erase size 4 KiB, total 2 MiB
> *** Warning - bad CRC, using default environment
>
> In:    uart@18101500
> Out:   uart@18101500
> Err:   uart@18101500
> Net:   No valid Mac-addr found from dtb
>
> Error: ethernet@18140000 address not set.
> No ethernet found.
> Hit any key to stop autoboot:  0
> pistachio # dhcp
> mdio_register: non unique device name 'ethernet@18140000'
> ethernet@18140000:0 is connected to ethernet@18140000.  Reconnecting to ethernet@18140000
>
> Error: ethernet@18140000 address not set.
> mdio_register: non unique device name 'ethernet@18140000'
> ethernet@18140000:0 is connected to ethernet@18140000.  Reconnecting to ethernet@18140000
>
> Error: ethernet@18140000 address not set.
> mdio_register: non unique device name 'ethernet@18140000'
> ethernet@18140000:0 is connected to ethernet@18140000.  Reconnecting to ethernet@18140000
>
> Error: ethernet@18140000 address not set.
> mdio_register: non unique device name 'ethernet@18140000'
> ethernet@18140000:0 is connected to ethernet@18140000.  Reconnecting to ethernet@18140000
>
> Error: ethernet@18140000 address not set.
> No ethernet found.
> mdio_register: non unique device name 'ethernet@18140000'
> ethernet@18140000:0 is connected to ethernet@18140000.  Reconnecting to ethernet@18140000
>
> Error: ethernet@18140000 address not set.
> pistachio #


  reply	other threads:[~2018-12-14  4:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181128233013.nymedsx2ukdx2otq@pburton-laptop>
     [not found] ` <7hr2f3afkb.fsf@baylibre.com>
     [not found]   ` <20181130234118.3vntmrbz5vom2sji@pburton-laptop>
2018-12-03 17:36     ` MIPS test results Kevin Hilman
2018-12-12 20:02       ` Paul Burton
2018-12-14  0:51         ` Kevin Hilman
2018-12-14  4:43           ` Ezequiel Garcia [this message]
2018-12-14 17:03             ` Kevin Hilman
2018-12-14 17:43               ` Ezequiel Garcia
2018-12-14 18:54               ` Paul Burton
2018-12-15  1:28                 ` Kevin Hilman
2018-12-15  1:58                   ` Guenter Roeck
2018-12-15  4:26                   ` Paul Burton

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=997-5c133500-1-763d5380@188620748 \
    --to=ezequiel.garcia@collabora.com \
    --cc=kernelci@groups.io \
    --cc=khilman@baylibre.com \
    --cc=paul.burton@mips.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox