[werner at openmoko.org: Re: help: debug board interfacing]

Werner Almesberger werner at openmoko.org
Mon Jan 5 15:17:33 CET 2009

Oops, didn't notice that you had dropped the list again until the mail
was already sent. Please try to "reply to all" so that the list is
kept in the loop.

I've also changed the list from "devel" to "hardware", which seems
more appropriate for the topic.

- Werner

----- Forwarded message from Werner Almesberger <werner at openmoko.org> -----

Date: Mon, 5 Jan 2009 12:15:09 -0200
From: Werner Almesberger <werner at openmoko.org>
To: Sreeraj a <writetosrj at gmail.com>
Subject: Re: help: debug board interfacing

Sreeraj a wrote:
> ok. my intention is to use  them as GPIO. planning to start by some
> LED-blinking.

That's easy: you can use the signals EINT3 or any of the SPI signals
just as GPIO. No need to worry about their other functions.

GPIO	DebugV3 signal
-----	--------------

You can change them with the "gpio" utility from

E.g., the following shell command would toggle EINT3:

gta02# while true; do gpio f3=1; gpio f3=0; done

A pre-compiled version of "gpio" is also available from our package
feed under the name s3c24xx-gpio.

> hope to make my neo into a complete interfacing to the Phoenix
> box<http://www.nsc.res.in/%7Eelab/phoenix/>.

Looks nice !

> For that the best way is to use the UART pins, the box connects to the PC
> through UART.

UART is a little tricky. You can use the serial console (ttySAC2),
but then you have to make sure that the kernel doesn't print anything
and that nothing else tries to read the console (stealing the data
the board sends to your application.)

I see that the Phoenix board can also use USB. So that may be an
option as well.

- Werner

----- End forwarded message -----

More information about the hardware mailing list