From: Stephen Woodrow <srwoodrow@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] [Cerowrt-devel] Bus Pirate for serial interfacing to the wndr and similar devices
Date: Thu, 31 May 2012 16:54:34 -0400 [thread overview]
Message-ID: <CAMFPzo0zC1W-C54ULpb7LrqsoYeO-kk5iXNa8xFc4xp__XuzSg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw62jmSOnvdUen1Eye9fJJ0AbT41O7NM_i7mMo_ct2+LAw@mail.gmail.com>
On Wed, May 30, 2012 at 10:47 PM, Dave Taht <dave.taht@gmail.com> wrote:
> Given cero bug #379 it seems like I need to get
> a couple of these to truly debug it.
>
> http://dangerousprototypes.com/docs/Bus_Pirate
Another cool thing I should mention about the bus pirate in the
context of Openwrt dev/debugging is that it has an auxillary GPIO pin
available, even when you're using it as a UART. This means that you
could replace the reset button on the bottom of the board with a
transistor (+ resistor if there isn't already one) and be able to
activate the reset button from the comfort of your terminal.
If you coupled this with a remotely switchable power supply, you could
easily put the router into recovery mode without being physically
present (or needing to fiddle with paperclips).
I presume it should be possible to enter the factory recovery mode via
the uboot prompt somehow (thus making the reset button redundant), but
I haven't figured that out yet. If anyone has suggestions I would love
to hear them, as the Openwrt wiki didn't prove as useful as I'd hoped
in this regard.
--steve
prev parent reply other threads:[~2012-05-31 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 2:47 [Thumbgps-devel] " Dave Taht
2012-05-31 4:27 ` Gary E. Miller
2012-05-31 13:40 ` [Thumbgps-devel] [Cerowrt-devel] " Outback Dingo
2012-05-31 20:54 ` Stephen Woodrow [this message]
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=CAMFPzo0zC1W-C54ULpb7LrqsoYeO-kk5iXNa8xFc4xp__XuzSg@mail.gmail.com \
--to=srwoodrow@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
/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