All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot support for board(s) meesc, otc570
Date: Fri, 21 Jan 2011 14:21:34 +0100	[thread overview]
Message-ID: <4D39885E.9030601@emk-elektronik.de> (raw)
In-Reply-To: <4D397E6A.1050100@esd.eu>

Hello Daniel,
> Hello Reinhard,
>> Which USART is the output coming from instead? Is it really console output
>> or maybe some other, independent pulses?
> 
> I don't know, to which USART the output goes. I guess you assume, my
> "GPIO debugging" was to meassure the pulses on the USART pins. But no, my
> GPIO debugging was as follows:
> -set gpio pin with led attached
> -send characters by puts() (wherever it goes) ;-)
> -reset gpio pin
> -measure time between high- and low- rising edge on gpio pin
> -calculate baudrate
> 
> (on DBGU pin, there is no pulse at all past starting U-Boot)
> 
>>
>> Can you verify that the value for ATMEL_BASE_DBGU in at91sam9263.h is
>> correct?
> 
> Yes, according to datasheet, Debug Unit Control Register (DBGU_CR) is
> located at 0xFFFFEE00.
> And in at91sam9263.h is defined:
> #define ATMEL_BASE_DBGU         0xffffee00
(I could have made an error there while reworking)

I think its now safe to assume that the DBGU UART is really used, but maybe
the GPIO pins are not correctly assigned to it. Try to look in the
at91sam9263_devices.c area, seriald_init().. Is it called, and does it do the
"right" thing?

It must be something rather trivial...

Best Regards,
Reinhard

  reply	other threads:[~2011-01-21 13:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101127215828.7CD40220233A@lilith>
     [not found] ` <4D072AED.6080703@esd.eu>
     [not found]   ` <4D355CFC.5050806@esd.eu>
     [not found]     ` <4D356200.5000801@aribaud.net>
     [not found]       ` <4D3577A9.8050505@esd.eu>
2011-01-18 12:25         ` [U-Boot] U-Boot support for board(s) meesc, otc570 Reinhard Meyer
2011-01-20  7:48           ` Daniel Gorsulowski
2011-01-21  6:43             ` Reinhard Meyer
2011-01-21  9:11               ` Daniel Gorsulowski
2011-01-21 10:44                 ` Reinhard Meyer
2011-01-21 11:17                   ` Daniel Gorsulowski
2011-01-21 11:50                     ` Reinhard Meyer
2011-01-21 12:39                       ` Daniel Gorsulowski
2011-01-21 13:21                         ` Reinhard Meyer [this message]
2011-01-24 11:39                 ` Daniel Gorsulowski
2011-01-24 12:08                   ` Reinhard Meyer
2011-01-25 18:13                   ` Albert ARIBAUD
2011-04-11 10:11                   ` Reinhard Meyer

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=4D39885E.9030601@emk-elektronik.de \
    --to=u-boot@emk-elektronik.de \
    --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.