So what do you recommend for me to build out something that will use the
FFUART on the console-st, and have DTR set and RTS cleared? I am happy
to hardwire one of them - eg I could tie DTR to VCC. I would like to
have at least one under software control (I plan on using Perl or
Python, since my C skills are old and weak). Is there something off the
20 pads (U3) that would be easy to control? What about pulling the Y0
CTS signal? I don't plan on using the USB port, so I could even cut pin
1 on U$18 if needed.
I asked a similar question 2 weeks ago, but you and steve both
recommended the HWUART board - but it looks like I would have to give up
my netMMC board if I did that.
On 3/15/2008 11:48 PM, Dave Hylands wrote:
> Hi Paul,
> On Sat, Mar 15, 2008 at 5:04 PM, Paul Faulstich, SEnnovation
> <paul@...> wrote:
>> Thanks Dave, but I'm still confused. When you say "use of the network"
>> do you mean just bluetooth, or do you mean any network, including
>> ethernet? That HWUART port is important to me, so I'll be bummed if I
>> can't use it plus ethernet. (I'll have to use an ST and wire my own flow
> It's use of a baord plugged into the 92 pin connector.
> The NPWE signal is one of the signals connected to the network
> controller on the netMMC board. It is multiplexed with the HWRXD pin.
> So you can't use the network controller and the HWUART at the same
> I'm pretty sure you can use bluetooth via the BTUART and still use the
> HWUART. However you can't use the network on any of the 92-pin cards
> and still use the HWUART.
> NPIOW is also multiplexed with HWRTS
> NPIOR is also multiplexed with HWCTS
> These two signals are used with the SD card on the netMMC. Similar
> conflicts exist on the other connex 92-pin cards.