Neo Debug Board Schematics or Pinouts

2007-08-18 Thread wee . kiampeng
Hi folks,

I will like to to have a peek at the Neo debug board's schematics or
pinouts. I need to access the uarts as well as the jtag. Does anyone have
any idea?

-- 
Kiam Peng



___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Neo Debug Board Schematics or Pinouts

2007-08-18 Thread Joachim Steiger
wee.kiampeng wrote:
> Hi folks,
> 
> I will like to to have a peek at the Neo debug board's schematics or
> pinouts. I need to access the uarts as well as the jtag. Does anyone have
> any idea?
> 

we already are in the process of releasing the neo debug board
schematics since we believe that it would be useful not only for the
moko, but for a lot of different usecases for the embedded hacker community.

please give us some more time do do this properly.


if you need to access the serial of the ftdi via the 2.54mm spacing port
( J10 ) the pinout is as follows:

1  TXD
2  RXD
3  RTS
4  CTS
5  DSR
6  DTR
7  DCD
8  RI
9  GND
10 VCC (3.3V)


remember, this is the port B of the ftdi2232D so the mapping is
BDBUS0-BDBUS7 pin 1 to pin 8

to get a serial from your linux kernel do this:

modprobe ftdi_sio vendor=0x1457 product=0x5118

then you get 2 serial of which one will vanish as soon as you start
openocd to use portA as jtag

J1 on the debug board is JTAG in regular arm 20pin out



kind regards

--

Joachim Steiger

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Neo Debug Board Schematics or Pinouts

2007-08-18 Thread andy selby
> > I will like to to have a peek at the Neo debug board's schematics or
> > pinouts. I need to access the uarts as well as the jtag. Does anyone have
> > any idea?
> >
>
> we already are in the process of releasing the neo debug board
> schematics since we believe that it would be useful not only for the
> moko, but for a lot of different usecases for the embedded hacker community.

Are these the pinouts your looking for?
http://www.hardwarebook.info/JTAG

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


RE: Neo Debug Board Schematics or Pinouts

2007-08-22 Thread Heilpern, Mark
Are these signals TTL level or are they already RS-232? If they are TTL,
is there any reason I could not use the BrainStem from Acroname
(http://www.acroname.com/robotics/parts/S13-SERIAL-INT-CONN.html) to
overcome this? (That device only uses TXD, RXD, and of course power and
ground).



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joachim
Steiger
Sent: Saturday, August 18, 2007 2:43 PM
To: community@lists.openmoko.org; [EMAIL PROTECTED]
Subject: Re: Neo Debug Board Schematics or Pinouts

wee.kiampeng wrote:
> Hi folks,
> 
> I will like to to have a peek at the Neo debug board's schematics or
> pinouts. I need to access the uarts as well as the jtag. Does anyone
have
> any idea?
> 

we already are in the process of releasing the neo debug board
schematics since we believe that it would be useful not only for the
moko, but for a lot of different usecases for the embedded hacker
community.

please give us some more time do do this properly.


if you need to access the serial of the ftdi via the 2.54mm spacing port
( J10 ) the pinout is as follows:

1  TXD
2  RXD
3  RTS
4  CTS
5  DSR
6  DTR
7  DCD
8  RI
9  GND
10 VCC (3.3V)


remember, this is the port B of the ftdi2232D so the mapping is
BDBUS0-BDBUS7 pin 1 to pin 8

to get a serial from your linux kernel do this:

modprobe ftdi_sio vendor=0x1457 product=0x5118

then you get 2 serial of which one will vanish as soon as you start
openocd to use portA as jtag

J1 on the debug board is JTAG in regular arm 20pin out



kind regards

--

Joachim Steiger

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

NOTE: The information in this message is intended for the personal and 
confidential use
of the designated recipient(s) named above. To the extent the recipient(s) 
is/are bound
by a non-disclosure agreement, or other agreement that contains an obligation of
confidentiality, with AuthenTec, then this message and/or any attachments shall 
be
considered confidential information and subject to the confidentiality terms of 
that
agreement.  If the reader of this message is not the intended recipient named 
above, you
are notified that you have received this document in error, and any review, 
dissemination,
distribution or copying of this message is strictly prohibited. If you have 
received this
document in error, please delete the original message and notify the sender 
immediately.
Thank you.

AuthenTec, Inc.  http://www.authentec.com



___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Neo Debug Board Schematics or Pinouts

2007-08-22 Thread Joachim Steiger
Heilpern, Mark wrote:
> Are these signals TTL level or are they already RS-232? If they are TTL,
> is there any reason I could not use the BrainStem from Acroname
> (http://www.acroname.com/robotics/parts/S13-SERIAL-INT-CONN.html) to
> overcome this? (That device only uses TXD, RXD, and of course power and
> ground).

it is 3.3V cmos logic so NO RS-232 levels.

you could use that board you linked to connect to the serial console of
a moko, i think. at least in theory because you still need to build an
adapter for the fpc. and supply it with 3.3V (the specs of the brainstem
say it can be used with 3.3V)

you just need to keep in mind that the serial is getting switched on and
off by GSM_EN and some latches on the debug board.


kind regards

--

Joachim Steiger

___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community