Hi Stefan,

is that danube or amazon based board?

On Tue, Sep 24, 2013 at 03:34:24PM -0400, Stefan Monnier wrote:
> So I figure I should try and flash it via tftp, but I have no idea what
> command to use for that.  The webpage
> (http://wiki.openwrt.org/toh/gigaset/sx76x) shows some commands to use
> to replace the primary bootloader, but that doesn't give me enough hints
> to know what commands to use.  Any idea?

In case that is danube board please use openwrt/v2013.07 branch to get
u-boot going:

https://github.com/danielschwierzeck/u-boot-lantiq/commits/openwrt/v2013.07

I'm waiting for next uboot release and then I'll bump the package in
OpenWrt. The httpd in uboot is not and wont be supported anymore (at
least until it is not available in upstream).

Luka

> 
> 
>         Stefan
> 
> Regarding flashing over the "recovery httpd", after soldering the serial
> line, I now see that the upload goes *reeeeeaaaalllly* slow, repeating
> patterns of the form:
> 
> 214253 / 3145732
> 215699 / 3145732
> .........................................................................................................................217145
> / 3145732
> 218591 / 3145732
> 220037 / 3145732
> ........................................................................................................................221483
> / 3145732
> 
> Where every dot is a 1s wait (give or take).  At this rate, it would take
> days before the firmware is uploaded, and when I tried that, the process
> stopped after transferring a bit more than 2MB.
> 
> Not sure what's going on: there always seem to be 3 packets sent
> together, followed by a wait.  The first few packets get sent without
> waiting, but once I get to around 200KB, the wait starts appearing.
> It appears gradually, with an exponential pattern: first 3 blocks
> followed by a single ".", then 3 blocks followed by "..", then 3 blocks
> followed "...", then ".......", then ".............", ... until hitting
> the limit seen above.
> 
> I tried to run a "ping" at the same time, figuring it might disrupt the
> wait, but to avail.  Any idea what might be going on, or how I can try
> to fix it?
> _______________________________________________
> openwrt-devel mailing list
> [email protected]
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to