gumstix

Craig Hughes wrote:
> If this happens again, dump your arp table on the gumstix, and see if 
> anything looks funky.  I've had weird similar networking issues with  my
> big desktop linux box when something on the network borked arp 
> resolution and the linux box somehow got confused and could no longer 
> talk to anything.  I think the resolution was just to manually add a 
> couple arp records for key servers on my LAN (probably ifdown/ifup 
> would do the trick too)
Ok, will do. Thanks for the advice, but I hope this doesn't repeat
itself. :)

-- 
Kindest regards / Med vennlig hilsen,
 Jørgen P. Tjernø
 <jorgen@...>

--
Regist. Linux User #344952

Experience is the name everyone gives to their mistakes.
  -- Oscar Wilde

Hi guys,

The doc-wiki-FAQ talks about 0-80 screws. How much is that
in =B5miles? Does anyone know what size screws I need
in metric terms? Will M1,4 fit? (It's for the gumstix boards,
of course.)

And is there any danger of shorting some of the PCB layers if
the screw is too tight?

		Kees

On Wed, 2005-11-23 at 11:26 -0800, Gordon Kruberg wrote:
> Here is my initial proposal, to be implemented over the next few days 
> without contrary offerings:
> 
> 1) use svn with Eagle format files.
> 2) Create a repository at svn.gumstix.com/svn/Eagle
> 3) Directory/File structure as follows, where [BoardName] is a board 
> name assigned by Craig. 
>     Eagle/Gumstix/[BoardName]/[BoardName].sch
>     Eagle/Gumstix/[BoardName]/[BoardName].brd
>     Eagle/lbr/gumstix.lbr
>     Eagle/ulp/
>     Eagle/scr/
> 
> 4) the ulp and scr are folders for shared utilities-- that we will be 
> anble to use for diff/inspect/automatic generation, etc.
> 5) svn co into the home Eagle will automatically put these into the 
> Eagle folders you use.  svn update at the Eagle level will update them; 
> commit, likewise, for those with commit permissions.
> 
> Gordon

Sounds great, can't wait :)

Phil

I am trying to build the fcgi library for the gumstix.

My toolchain has been built with SOFT_FLOAT=3Dtrue.

If I run the fcgi configure script like:

 CC=3Darm-linux-gcc ./configure --target=3Darm-linux --host=3Darm-linux

followed by make I get the following error:

 ../libfcgi/.libs/libfcgi.so: undefined reference to `frexp'

If I export LIBS=3D-lfloat and then run configure as above, configure fai=
ls
with error messages similar to the following in config.log:

./lib/gcc/arm-linux-uclibc/3.4.2/../../../../arm-linux-uclibc/lib/libfloa=
t.so:
 undefined reference to `___float64_lt'

Any suggestions as to what I am not doing correctly?

Regards

Steven

_________________________________________________________________

Steven Brydon - Application Developer
Virtual Spectator International
Mob: +64 29 712 1790
Ph: +64 9 913 6890
Fax: +64 9 913 6899

http://www.virtualspectator.com


Notice of confidentiality: This communication contains information that i=
s
confidential and may also be privileged. It is for the exclusive use of
the intended recipient. If you=92re not the intended recipient, please no=
te
that any form of distribution, copying or use of this communication or th=
e
information in it is strictly prohibited. If you have received this
communication in error, please delete the email and all other electronic
or hard copies of it. Thank you.
_________________________________________________________________________=
_

I wrote:

> Hi,
>
> I think this is a single problem, but might be wrong.

... and I was wrong. 

At least on my revision 649 build, perl produces the 'Your random 
numbers are not that random' message because it is using a broken 
library function (drand48()) to get floating-point PRNs.  In my gumstix 
build uClibc's drand48() seems to use the wrong floating point format, 
the first and second 32 bit halves were reversed.  This has something to 
do with the value of the flag __FLOAT_WORD_ORDER. 

This fault also rendered perl's rand() function useless.  It could be 
replicated with the following code cross-compiled for the GS:

#include <stdio.h>
#include <stdlib.h>
int main(void) {
  for( i = 0; i < 10; i++ ) {
    printf("%f\n",drand48());
  }
    return 0;
}

I tried to change the setting in the uClibc build to fix my drand48() 
problem but got terribly tangled up. 
My shameful, quick work-around is to modify perl/config.sh as follows:

doublesize='8'
-drand01='drand48()'
+drand01='((double)lrand48())/2147483648.0'
drand48_r_proto='0'
dynamic_ext=''

And then rerun make in the perl buildroot directory. 

This fixes both my startup problem and rand() problem.  The lack of 
output from /dev/random doesn't seem to upset perl at all. 
John P, I hope this helps with your issues too.

Dave

Hello all, I am happy to report that we have received the go ahead to
open source the design of the gumstix daughterboard used in our 6" SVGA
electrophoretic display developer's kit. I designed this board
specifically for the kit, but it is useful for our customers to be able
to examine, modify, and expand on the design. It might also be useful
for some people on this list.

I've put up a little page on the wiki with this message and a picture of
the board at:
http://www.gumstix.org/tikiwiki/tiki-index.php?page=3Dlyre

Enjoy!
-Holly

You can download the files from:

http://sourceforge.net/projects/thinspace/

Click on the "download" button, then choose "lyre"



Here is the README.TXT that comes with the package:

---------------------------------------------------------------------
All files copyright E Ink Corporation 2005
Available for use under the E Ink Public Source License.
See LICENSE.TXT or http://support.eink.com/license.txt for details

Description of files:

/doc
        lyre_x01_BOM.csv   - Bill of materials for board
        lyre_x01.DXF       - Mechanical export of PCB design
        lyre_x01.NET       - PADS ASCII netlist
        lyre_x01_pcb.pdf   - PDF of layout
        lyre_x01.PRT       - PADS ASCII partfile
        lyre_x01_sch.pdf   - PDF of schematic
        lyre_x01_inuse.jpg - scan of the board in use

/protel_project
        CAM for lyre_x01   - CAM files (gerber, NC drill, pick&place)
        others...          - protel project files



Brief description of board:


Lyre was designed as a support board for a 6" SVGA electrophoretic
display developer's kit engineered and released by E Ink in 2005. The
core of the display controller used in the kit is an ASIC named
Apollo. The controller board itself, which has the ASIC and its
supporting parts plus power supplies needed for the display, was named
Hecuba after one of Apollo's lady friends. Lyre serves a subsidiary
role to the display controller, and was named after Apollo's preferred
instrument.

The Lyre board basically acts as a connector to wire up some GPIOs on
the Gumstix single board computer used in the kit to the Hecuba
controller board. It also breaks out some other lines from the Gumstix
board and incorporates a few other functions.

- Interface to Hecuba 6" EPD display controller through JP6

- Serial lines for a terminal connection over JP10 (external
level shifter and DB9 board required)

- JTAG lines via JP10 to theoretically reburn the gumstix if you erase th=
e
bootloader. Have not tried this yet.


- Mini-B USB connection through JP5

- 4 GPIO lines for buttons/switches through JP2

- Two series cell Lithium-ion battery charger

- DC/Battery power sequencer

- DC in via JP4, for operation and battery charging

- Battery connection at JP8

- Low battery detection (doesn't work in rev x01)

- reset switch at S1

- Battery cutout switch at S2

- Red LED for charger status

- Blue LED under software control from gumstix


- 4.0V power supply for gumstix

- 3.3V power supply for other digital circuits and displays

- Connector for Sony ACX705AKM reflective color display

- Expansion connector at JP3; includes all signals for external board
with UCB1400 audio/touchscreen IC, other I2C devices, or whatever
people can think of. Unfortunately didn't put power on this connector,
but I didn't want to go up to the 20 pin FPC since I didn't have room.


As built in the kit, the board is implemented as 0.5mm thick FR-4, so
that it would fit inside an ebook case we have designed with a gumstix
mounted on top. It could easily be built as 0.8mm or 1.6mm, which
would help make it a little cheaper.