From: Sascha Hauer <s.hauer@pengutronix.de>
To: Peter Kardos <kardos.peter.sk@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: AT91RM9200 hang in atmel_serial_putc
Date: Thu, 18 Aug 2016 09:38:31 +0200 [thread overview]
Message-ID: <20160818073831.GL20657@pengutronix.de> (raw)
In-Reply-To: <7f89efef-2805-34d8-db7d-f3bc53d8e21a@gmail.com>
Hi Peter,
On Thu, Aug 18, 2016 at 03:08:36AM +0200, Peter Kardos wrote:
> Greetings,
>
> I'm looking for a AT91 specialist that could help me debug barebox v2016.08.
>
> I have a custom board running AT91RM9200 that came with a really old custom
> u-boot (v1.1.4, no ubifs support)...
>
> The first bootloader I've ported (barebox v2015.07, using AT91RM9200ek as
> template) almost works; I'm having trouble getting networking (ping, dhcp)
> working with Micrel KSZ8721 phy. But it boots, works with the Flash, etc...
> With hopes, that this (networking issue) is resolved with the latest barebox
> release (using the same patchset and config) I've found (??) a another
> issue.
>
> At first it seemed the board just does not boot, after having a look with a
> j-link it seems the board "hangs" in atmel_serial_putc().
> I've tried to look at the AT91RM9200 init (lowlevel, peripherals, driver)
> and could not find any significant change (rewrite, define changes, etc)...
So you have a jtag debugger attached, does it support showing registers?
What is the value of uart->base? Is it correct?
Also you could compare the UART registers with the ones from a working
U-Boot/barebox. Does atmel_serial_init_port() do everything correctly?
Finally it may be that the clock is disabled for some reason, then the
values written to the UART would never be shifted out.
Which instance of the UART are you using? It seems we have:
static struct clk_lookup usart_clocks_lookups[] = {
CLKDEV_CON_DEV_ID("usart", "atmel_usart0", &mck),
CLKDEV_CON_DEV_ID("usart", "atmel_usart1", &usart0_clk),
CLKDEV_CON_DEV_ID("usart", "atmel_usart2", &usart1_clk),
CLKDEV_CON_DEV_ID("usart", "atmel_usart3", &usart2_clk),
CLKDEV_CON_DEV_ID("usart", "atmel_usart4", &usart3_clk),
};
The first clock seems to be always-on, but the others could be turned off.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 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
next prev parent reply other threads:[~2016-08-18 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 1:08 Peter Kardos
2016-08-18 7:38 ` Sascha Hauer [this message]
2016-08-18 8:00 ` Peter Kardos
2016-08-18 21:15 ` Peter Kardos
2016-08-22 6:10 ` Sascha Hauer
2016-08-22 9:00 ` Peter Kardos
2016-08-22 20:39 ` Peter Kardos
2016-08-24 12:24 ` Sascha Hauer
2016-08-25 20:53 ` Peter Kardos
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=20160818073831.GL20657@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=kardos.peter.sk@gmail.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