From: Sean Anderson <seanga2@gmail.com>
To: u-boot@lists.denx.de
Subject: How to debug HW startup?
Date: Sat, 11 Jan 2020 15:42:33 -0500 [thread overview]
Message-ID: <7cb03dcf-91a3-448d-3fa3-754d4bad0af3@gmail.com> (raw)
In-Reply-To: <ff834bf1-af33-2aec-31c6-603fb50d1e5c@mclink.it>
> Could You share a Linkit _defconfig with early serial debug enabled?
> I'm decidedly missing something as, even enabling
>
> CONFIG_DEBUG_UART=y
> CONFIG_DEBUG_UART_BASE=0x10000e00
> CONFIG_DEBUG_UART_CLOCK=20
> CONFIG_DEBUG_UART_SHIFT=2
> CONFIG_DEBUG_UART_ANNOUNCE=y
>
> I still have plenty of errors:
>
> /home/mcon/vocore/__V2__/Buildroot/recov/host/bin/mipsel-linux-ld.bfd:
> arch/mips/cpu/start.o: in function `wr_done':
> (.text+0x650): undefined reference to `debug_uart_init'
> /home/mcon/vocore/__V2__/Buildroot/recov/host/bin/mipsel-linux-ld.bfd:
> (.text+0x654): undefined reference to `debug_uart_init'
> /home/mcon/vocore/__V2__/Buildroot/recov/host/bin/mipsel-linux-ld.bfd:
> board/vocore/vocore2/built-in.o: in function `board_early_init_f':
> (.text.board_early_init_f+0x10): undefined reference to `printhex8'
> /home/mcon/vocore/__V2__/Buildroot/recov/host/bin/mipsel-linux-ld.bfd:
> common/built-in.o: in function `putc':
> (.text.putc+0x18): undefined reference to `printch'
> /home/mcon/vocore/__V2__/Buildroot/recov/host/bin/mipsel-linux-ld.bfd:
> common/built-in.o: in function `puts':
> (.text.puts+0x2c): undefined reference to `printch'
>
You need to pick a debug uart driver, e.g. CONFIG_DEBUG_UART_NS16550.
next prev parent reply other threads:[~2020-01-11 20:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 17:28 How to debug HW startup? Mauro Condarelli
2020-01-10 6:31 ` Stefan Roese
2020-01-10 9:06 ` Mauro Condarelli
2020-01-10 13:33 ` Stefan Roese
2020-01-11 19:00 ` Mauro Condarelli
2020-01-11 20:42 ` Sean Anderson [this message]
2020-01-11 21:38 ` Mauro Condarelli
2020-01-11 23:58 ` Sean Anderson
2020-01-12 0:22 ` Mauro Condarelli
2020-01-13 6:53 ` Stefan Roese
2020-01-13 10:24 ` Mauro Condarelli
2020-01-13 11:39 ` Stefan Roese
2020-01-13 12:24 ` Mauro Condarelli
2020-01-13 12:45 ` Stefan Roese
2020-01-13 14:14 ` Mauro Condarelli
2020-01-13 23:08 ` Mauro Condarelli
2020-01-14 11:03 ` Mauro Condarelli
2020-01-14 23:55 ` Debugging VoCore2 ROM Startup (was: How to debug HW startup?) Mauro Condarelli
2020-01-15 7:25 ` Debugging VoCore2 ROM Startup Stefan Roese
2020-01-15 9:04 ` Mauro Condarelli
2020-01-15 9:31 ` Stefan Roese
2020-01-15 9:51 ` Stefan Roese
2020-01-15 10:23 ` Mauro Condarelli
2020-01-15 10:48 ` Stefan Roese
2020-01-15 12:50 ` Mauro Condarelli
2020-01-15 15:04 ` Stefan Roese
2020-01-15 15:55 ` Mauro Condarelli
2020-01-15 16:20 ` Stefan Roese
2020-01-15 17:25 ` Mauro Condarelli
2020-01-16 6:33 ` Stefan Roese
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=7cb03dcf-91a3-448d-3fa3-754d4bad0af3@gmail.com \
--to=seanga2@gmail.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.