mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lars Pedersen <lapeddk@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Getting serial console output on new imx7d tqma7 board UART4
Date: Mon, 3 Aug 2020 09:56:46 +0200	[thread overview]
Message-ID: <CAKd8=Gs2qryoo4Vd79aytUTWquAeQX2R3neEEUW3n44xTJt8gw@mail.gmail.com> (raw)
In-Reply-To: <61831111-a404-b312-8fbe-06b1b80eaf03@pengutronix.de>

Thanks for the feedback.

I will order an i.MX7 EVK board and try to get it working. I guess
that we were a little too confident that the TQma7d board would work
out of the box with only minor tweaks.

/Lars Pedersen

On Thu, 30 Jul 2020 at 15:55, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
> Hi,
>
> On 7/30/20 12:16 PM, Lars Pedersen wrote:
> > Thanks for the quick response :) I have made some inline comments
> >
> > Additionally I have fixed the __dtb_z_ unrelated issue, but still
> > troubles to get some output. Could you maybe send me a barebox binary
> > for an mx6 or mx7 board? I'm still unsure if it has the correct binary
> > format.
>
> Can you not compile a i.MX7-EVK barebox and run it on the EVK?
> If this doesn't work, this is a different issue.
>
>
> > My current Kconfig values look like this. Maybe you can see something
> > missing.I have patched drivers/regulator/Kconfig (ARCH_IMX7) so that I
> > can enable REGULATOR_PFUZE, which is used on the tqma7d board. From
> > what I can see the NXP i.MX7 SabreSD board uses a PF3000 PMIC too so
> > iam unsure why it can work without this fix.
>
> DEBUG_LL lets barebox print a > symbol first thing it boots. This should
> work for you regardless of any PMIC configuration.
>
> >>> So I guess that the DCD table part now should be correct. So the
> >>> question is if this is and lowlevel.c/board.c boilerplate issue or
> >>> maybe I need something in the Kconfig menu.
> >>
> >> Enable CONFIG_DEBUG_LL and see how far barebox comes.
> >> See the inline comment from my last mail.
> >
> > I missed some of the last comments but I have already enabled
> > CONFIG_DEBUG_LL and can't get any console output to appear. UART4 has
> > been selected in the menu for this.
>
> Then that's what you need to focus on. Prior to that '>', not much
> code has run. If you don't come that far, chances are you set up your serial port
> wrong (looks correct to me though) or your DCD table is wrong...
>
> Cheers,
> Ahmad
>
> --
> Pengutronix e.K.                           |                             |
> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-08-03  7:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 16:52 Lars Pedersen
2020-07-29 17:22 ` Ahmad Fatoum
2020-07-30  6:58   ` Lars Pedersen
2020-07-30  7:25     ` Ahmad Fatoum
2020-07-30 10:16       ` Lars Pedersen
2020-07-30 13:55         ` Ahmad Fatoum
2020-08-03  7:56           ` Lars Pedersen [this message]
2020-08-03 21:51         ` Sascha Hauer
2020-08-04 12:53           ` Lars Pedersen
2020-08-03 10:10 ` Ahmad Fatoum
2020-08-04 13:07   ` Lars Pedersen
2020-08-04 16:15     ` Ahmad Fatoum
2020-08-04 19:21       ` Lars Pedersen
2020-08-05  8:49         ` Ahmad Fatoum
2020-08-05  9:37           ` Lars Pedersen
2020-08-05  9:48             ` Ahmad Fatoum
2020-08-05 11:12               ` Lars Pedersen
2020-08-05 12:30                 ` Ahmad Fatoum
2020-08-05 15:00                   ` Lars Pedersen
2020-08-10  8:00                     ` Sascha Hauer

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='CAKd8=Gs2qryoo4Vd79aytUTWquAeQX2R3neEEUW3n44xTJt8gw@mail.gmail.com' \
    --to=lapeddk@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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