Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] Nitrogen8M stuck at boot with master branch
Date: Thu, 17 Dec 2020 15:02:41 +0100	[thread overview]
Message-ID: <X9tlAc/YgP1aQuhe@p1g2> (raw)
In-Reply-To: <69c3d27e81a21ac582be4104b28485381a51cdb9.camel@collabora.com>

Hi Ezekiel,

On Thu, Dec 17, 2020 at 10:24:07AM -0300, Ezequiel Garcia wrote:
> Hi Gary,
> 
> Thanks for the reply.
> 
> On Thu, 2020-12-17 at 09:17 +0100, Gary Bisson wrote:
> > Hi,
> > 
> > On Thu, Dec 17, 2020 at 01:03:26AM +0000, Emil Velikov wrote:
> > > On Wed, 16 Dec 2020 at 13:11, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> > > > 
> > > > On Wed, 16 Dec 2020 at 13:10, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> > > > > 
> > > > > Greetings everyone,
> > > > > 
> > > > > Recently I've started thinkering with a Nitrogen8M SBC - the regular
> > > > > one, not the Mini, Nano or SOM ones.
> > > > > 
> > > > > Since this was my first experience with the board, initially I tried
> > > > > the vendor provided Ubuntu image [1], which was working OOTB.
> > > > > 
> > > > > Booting a minimal buildroot (make nitrogen8m_defconfig && make) seems
> > > > > to be getting stuck as below. The full boot log attached.
> > > > > 
> > > > Forgot the boot.log :-)
> > > > 
> > > Upon a closer look, it appears that boot locks up during the first
> > > arm_smccc_smc().
> > > The one in busfreq_probe() for the vendor kernel or imx8m_ddrc_probe()
> > > for the upstream ones.
> > > 
> > > Wild guess is that the built lpddr4_pmu_train firmware has regressed
> > > or we're not using it properly.
> > > 
> > > As always, any hints will be appreciated.
> > 
> > We've seen people having issues with 5.4 kernels when their bootloader
> > was old. Please make sure to upgrade to latest U-Boot [1].
> > 
> > This is due to ATF changes NXP made which seemed to be needed for 5.4.
> > 
> > Regards,
> > Gary
> > 
> > [1] https://boundarydevices.com/how-to-upgrade-u-boot/
> 
> 
> Note that we are using Buildroot's Nitrogen defconfig. Do you think
> we should bump Buildroot's U-Boot?

No if you upgraded to Buildroot's U-Boot it should work. But you have to
explicitely do that upgrade as the image generate by Buildroot goes in
the user partition of the eMMC whereas the bootloader is located into
the boot partition. So when you flash the sdcard image, that doesn't
update the U-Boot binary.

Regards,
Gary

  parent reply	other threads:[~2020-12-17 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACvgo51BjX9MzFbqp+5pim_wjv_B_QSdEcpkz23p+4BCS1-R3g@mail.gmail.com>
     [not found] ` <CACvgo53Ucwqsk7HntMR4o9gshbUFdt4R2OXTk2EPQPYkuXCTVw@mail.gmail.com>
2020-12-17  1:03   ` [Buildroot] Nitrogen8M stuck at boot with master branch Emil Velikov
2020-12-17  8:17     ` Gary Bisson
     [not found]       ` <69c3d27e81a21ac582be4104b28485381a51cdb9.camel@collabora.com>
2020-12-17 14:02         ` Gary Bisson [this message]
2020-12-17 15:05       ` Emil Velikov

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=X9tlAc/YgP1aQuhe@p1g2 \
    --to=gary.bisson@boundarydevices.com \
    --cc=buildroot@busybox.net \
    /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