mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 2/2] dns325: initial support for D-Link DNS-325
Date: Thu, 26 Jun 2014 11:14:04 +0200	[thread overview]
Message-ID: <20140626091402.GA9502@omega> (raw)
In-Reply-To: <53ABC34E.5040902@gmail.com>

Hi,

On Thu, Jun 26, 2014 at 08:53:02AM +0200, Sebastian Hesselbarth wrote:
> On 06/26/2014 06:27 AM, Alexander Aring wrote:
> > On Sun, Jun 22, 2014 at 11:50:56PM +0200, Sebastian Hesselbarth wrote:
> >> On 06/22/2014 10:34 PM, Alexander Aring wrote:
> >>> This patch add a basic support for the D-Link DNS-325.
> >>>
> >>> Currently only booting via uart with kwboot is supported. The barebox
> >>> kwboot utility doesn't work at the moment. Use kwboot utility from u-boot
> >>> instead.
> >>
> >> Why does kwboot does not work? There is an issue with early Kirkwood's
> >> BootROM and UART boot mode. Just try over and over again. I also recall
> >> modifying the timeouts may help.
> >>
> > 
> > I tried to change the timeouts and it works now. I take these timings from
> > u-boot. Is there any reason why these timings differs?
> 
> IIRC, timings differ because barebox kwboot was mainly tested on Armada
> 370 and that low timings break UART boot mode there. I remember some
> discussion about it a while ago. I'll see if I can find the discussion
> and if there are any hints for timeouts that suite both Kirkwood and
> Armada 370/XP.
> 

ok.

> > Datasheet says nothing about any delay while loop for sending bootmsg.
> > 
> > 
> > Here is my diff with the very small change:
> > 
> > diff --git a/scripts/kwboot.c b/scripts/kwboot.c
> > index e068660..bcb5972 100644
> > --- a/scripts/kwboot.c
> > +++ b/scripts/kwboot.c
> > @@ -34,8 +34,8 @@ static unsigned char kwboot_msg_debug[] = {
> >         0xDD, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77
> >  };
> >  
> > -#define KWBOOT_MSG_REQ_DELAY   1000 /* ms */
> > -#define KWBOOT_MSG_RSP_TIMEO   1000 /* ms */
> > +#define KWBOOT_MSG_REQ_DELAY   10 /* ms */
> > +#define KWBOOT_MSG_RSP_TIMEO   50 /* ms */
> >  
> >  /*
> >   * Xmodem Transfers
> > 
> > 
> > 
> > btw.:
> > 
> > Now I see that the internal ROM bootloader could also boot from SATA
> > device - this sounds interesting. I will try that next weekend.
> 
> Boot source is determined by bootstrap pins, i.e. some pull-up/pull-down
> resistors on board. UART boot mode check was added to BootROM in some
> later Kirkwoods and _additionally_ checks for UART boot source.
> 
> You cannot just change the default boot source without soldering.
> 

... and I don't have any schematics. Okay, maybe I will reverse engineer
the hardware layout one day. I know there are some other not soldered
pin headers, maybe I have luck.

Thanks for this information.

- Alex

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

  reply	other threads:[~2014-06-26  9:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22 20:34 [RFC 1/2] kirkwood: add support for booting via oftree probe Alexander Aring
2014-06-22 20:34 ` [RFC 2/2] dns325: initial support for D-Link DNS-325 Alexander Aring
2014-06-22 21:50   ` Sebastian Hesselbarth
2014-06-23  6:48     ` Alexander Aring
2014-06-26  4:27     ` Alexander Aring
2014-06-26  6:53       ` Sebastian Hesselbarth
2014-06-26  9:14         ` Alexander Aring [this message]
2014-06-24 11:54   ` Sebastian Hesselbarth
2014-06-25  6:57     ` Sascha Hauer
2014-06-22 21:45 ` [RFC 1/2] kirkwood: add support for booting via oftree probe Sebastian Hesselbarth
2014-06-23  6:51   ` Alexander Aring

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=20140626091402.GA9502@omega \
    --to=alex.aring@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=sebastian.hesselbarth@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