From: "W.P." <laurentp@wp.pl>
To: linux-mips@linux-mips.org
Subject: Re: Advice needed.
Date: Wed, 07 Feb 2007 19:07:14 +0100 [thread overview]
Message-ID: <45CA1552.3080100@wp.pl> (raw)
In-Reply-To: <24895.201.240.249.124.1170686083.squirrel@www.amilda.org>
<cut>
>The configuration structure is difficult to understand (even if you have
>the C header containing the struct)
>
>
I don't have any header files for flash. Do you? In tarballs for BR,
there is no source for utilities like flash.
I'm trying to "decode" this structure, variable-by-variable. I have used
your flash utility source
>Just use the "flash" program.
>
>
The one, that comes with original firmware? But what about webs, as i
looked into, this needs too some knowledge of flash datastructures.?
About webs -> will try to add some printf for debugging, and see.
BTW, maybe the JP3 connector (just 12 little holes) is the JTAG. Will
upload photo i think tomorrow. I have checked this with ohmometer and
pin-map of 8186, and it seems to be JTAG + RESET+ something(?). You have
published schema of JTAG cable, but what software shall anyone use?
W.Piotrzkowski.
next prev parent reply other threads:[~2007-02-07 18:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 16:52 Advice needed W.P.
2007-01-31 17:22 ` David Daney
2007-01-31 18:16 ` W.P.
[not found] ` <1170276219.6791.18.camel@localhost>
2007-01-31 21:34 ` W.P.
2007-01-31 21:39 ` Sergio Aguayo
2007-01-31 21:59 ` Florian Fainelli
2007-01-31 22:28 ` W.P.
2007-02-01 13:09 ` Sergio Aguayo
2007-02-01 14:50 ` W.P.
2007-02-02 13:43 ` Sergio Aguayo
[not found] ` <45C3BB23.2070309@wp.pl>
2007-02-03 5:57 ` Sergio Aguayo
[not found] ` <45C45DDA.1000805@wp.pl>
2007-02-05 14:34 ` Sergio Aguayo
2007-02-07 18:07 ` W.P. [this message]
2007-02-08 15:09 ` Sergio Aguayo
2007-02-08 15:16 ` Sergio Aguayo
2007-02-08 17:41 ` W.P.
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=45CA1552.3080100@wp.pl \
--to=laurentp@wp.pl \
--cc=linux-mips@linux-mips.org \
/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