Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(114) |
Apr
(35) |
May
(60) |
Jun
(52) |
Jul
(121) |
Aug
(170) |
Sep
(343) |
Oct
(147) |
Nov
(185) |
Dec
(172) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(319) |
Feb
(505) |
Mar
(614) |
Apr
(358) |
May
(344) |
Jun
(306) |
Jul
(558) |
Aug
(506) |
Sep
(639) |
Oct
(863) |
Nov
(705) |
Dec
(562) |
| 2006 |
Jan
(828) |
Feb
(1229) |
Mar
(1099) |
Apr
(856) |
May
(1099) |
Jun
(943) |
Jul
(1109) |
Aug
(975) |
Sep
(928) |
Oct
(1174) |
Nov
(1120) |
Dec
(948) |
| 2007 |
Jan
(858) |
Feb
(1095) |
Mar
(1143) |
Apr
(1178) |
May
(1255) |
Jun
(1092) |
Jul
(1373) |
Aug
(904) |
Sep
(848) |
Oct
(1552) |
Nov
(823) |
Dec
(973) |
| 2008 |
Jan
(1303) |
Feb
(1093) |
Mar
(1173) |
Apr
(1258) |
May
(664) |
Jun
(461) |
Jul
(613) |
Aug
(452) |
Sep
(387) |
Oct
(411) |
Nov
(466) |
Dec
(608) |
| 2009 |
Jan
(529) |
Feb
(452) |
Mar
(482) |
Apr
(679) |
May
(545) |
Jun
(588) |
Jul
(519) |
Aug
(675) |
Sep
(441) |
Oct
(556) |
Nov
(472) |
Dec
(471) |
| 2010 |
Jan
(799) |
Feb
(622) |
Mar
(659) |
Apr
(479) |
May
(631) |
Jun
(698) |
Jul
(802) |
Aug
(666) |
Sep
(533) |
Oct
(797) |
Nov
(459) |
Dec
(486) |
| 2011 |
Jan
(792) |
Feb
(526) |
Mar
(748) |
Apr
(506) |
May
(477) |
Jun
(528) |
Jul
(642) |
Aug
(418) |
Sep
(494) |
Oct
(374) |
Nov
(355) |
Dec
(424) |
| 2012 |
Jan
(476) |
Feb
(491) |
Mar
(606) |
Apr
(462) |
May
(275) |
Jun
(278) |
Jul
(241) |
Aug
(205) |
Sep
(215) |
Oct
(296) |
Nov
(317) |
Dec
(108) |
| 2013 |
Jan
(317) |
Feb
(228) |
Mar
(157) |
Apr
(108) |
May
(120) |
Jun
(123) |
Jul
(136) |
Aug
(204) |
Sep
(169) |
Oct
(152) |
Nov
(103) |
Dec
(164) |
| 2014 |
Jan
(153) |
Feb
(190) |
Mar
(147) |
Apr
(51) |
May
(131) |
Jun
(70) |
Jul
(99) |
Aug
(49) |
Sep
(28) |
Oct
(37) |
Nov
(43) |
Dec
(50) |
| 2015 |
Jan
(53) |
Feb
(48) |
Mar
(49) |
Apr
(83) |
May
(44) |
Jun
(163) |
Jul
(58) |
Aug
(39) |
Sep
(105) |
Oct
(73) |
Nov
(57) |
Dec
(82) |
| 2016 |
Jan
(64) |
Feb
(60) |
Mar
(37) |
Apr
(42) |
May
(113) |
Jun
(51) |
Jul
(56) |
Aug
(37) |
Sep
(26) |
Oct
(40) |
Nov
(28) |
Dec
(19) |
| 2017 |
Jan
(27) |
Feb
(28) |
Mar
(27) |
Apr
(31) |
May
(8) |
Jun
(10) |
Jul
(23) |
Aug
(5) |
Sep
(7) |
Oct
(31) |
Nov
(3) |
Dec
(1) |
| 2018 |
Jan
(1) |
Feb
(9) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(52) |
2
(22) |
|
3
(41) |
4
(76) |
5
(42) |
6
(43) |
7
(60) |
8
(51) |
9
(23) |
|
10
(10) |
11
(5) |
12
(27) |
13
(64) |
14
(39) |
15
(31) |
16
(17) |
|
17
(8) |
18
(24) |
19
(33) |
20
(37) |
21
(54) |
22
(51) |
23
(12) |
|
24
(12) |
25
(59) |
26
(70) |
27
(24) |
28
(41) |
29
(54) |
30
(10) |
|
From: Jonathan Rodgers <J.Rodgers@ke...> - 2007-06-25 23:22:37
|
Hi All, I am a newbie to the Gumstix platform. I am an electronic and electrical design engineer. I have an application for the Gumstix platform for monitoring Electricity Utility Assets and logging data, and am awaiting arrival of a Verdex XL6P system (My first Gumstix, I can't wait!). Unfortunately I have only come across the power of the Linux platform in the past few months, and so am inexperienced in this field. I want to order a Compact Flash card so I will have it on arrival of my system, but I need a little help with choosing the maximum size of card when using JFFS2. I want to know what are the limitations of the JFFS2 system on the Verdex. >From reading the specs of JFFS2 I think that as the whole media is scanned at mount time a table is created. Is this table in RAM, and if so, how big can it get for a specific size of media? Is the table size dependant on the number of individual files created? What are the consequences of using a CF card of upto 16GB in size? Will this create RAM problems. What if I were to use say only 100 to 200 large files on it to store data? What commands do I need to use to erase the media(aka format it) and to mount it correctly? Thanks in advance, Jonathan. >> CONFIDENTIALITY NOTICE << The information contained in this e-mail is intended only for the individual to whom it is addressed. It may contain legally privileged or confidential information or otherwise be exempt from disclosure. If you have received this message in error or there are any problems, please notify the sender immediately and delete the message from your computer. You must not use, disclose, copy or alter this message for any unauthorised purpose. Neither Kelman Ltd. nor any of its subsidiaries will be liable for any direct, special, indirect or consequential damages as a result of any virus being passed on, or arising from the alteration of the contents of this message by a third party. |
|
From: DJ Delorie <dj@de...> - 2007-06-25 22:29:19
|
"Jeff Sadowski" <jeff.sadowski@...> writes: > oh yeah and by the way great pictures :-) Thanks! Two tips: make sure your camera supports a "macro" focus, and put a piece of paper in front of the flash to avoid glare. |
|
From: DJ Delorie <dj@de...> - 2007-06-25 22:28:28
|
"Marc Nicholas" <geekything@...> writes: > That looks awfully like an ad-hoc solder stencil in one of the > pics...did you make it or get it made for you? Details please :) I made it at home. If you can etch circuit boards, you can etch brass also. I used toner transfer and FeCl, but the first one didn't line up with the board completely (the scale was off a bit) so I just cut it up and taped it back together again in the right place. I've since etched a second one that's properly scaled, so it's a single piece, but not much bigger than the board itself. The stencil you see in the photo is just a paper print of the stencil, not the actual stencil. See http://www.delorie.com/pcb/brass/ for some photos of the brass (not the furnace board stencil, but some practice ones). |
|
From: Jeff Sadowski <jeff.sadowski@gm...> - 2007-06-25 21:56:48
|
oh yeah and by the way great pictures :-) On 6/25/07, Marc Nicholas <geekything@...> wrote: > That looks awfully like an ad-hoc solder stencil in one of the pics...did > you make it or get it made for you? Details please :) > > (I say ad-hoc as it doesn't seem to be a full board, fitted Mylar stencil). > > -marc > > On 6/25/07, DJ Delorie <dj@...> wrote: > > > > Many thanks to all who helped me get to this point... my central > > heating/cooling system now has a gumstix running it! (along with five > > other MCUs ;) > > > > http://www.delorie.com/house/furnace/pcb2/ > > > > The main software is all custom, using the GPIO and serial lines to > > program the five R8C chips, and i2c to communicate with them when > > they're running. Yes, the DIN-8 connector is the console. The > > transplanted ethernet jack (Pulse J0011D21) works fine. Power is > > about 4.5v; it's a 5v switcher and a 2A diode drop. > > > > The web server is boa/perl/cgi. I had to rebuild microperl to support > > %ENV and installed index.cgi as the "build a directory script" so that > > it was the default home page. > > > > DJ > > > > PS: Hey gumstix folks, next time you design an ethernet board, please > > put thermals around the ground pins on the ethernet jack ;-) > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > gumstix-users mailing list > > gumstix-users@... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
|
From: Marc Nicholas <geekything@gm...> - 2007-06-25 21:29:07
|
That looks awfully like an ad-hoc solder stencil in one of the pics...did you make it or get it made for you? Details please :) (I say ad-hoc as it doesn't seem to be a full board, fitted Mylar stencil). -marc On 6/25/07, DJ Delorie <dj@...> wrote: > > > Many thanks to all who helped me get to this point... my central > heating/cooling system now has a gumstix running it! (along with five > other MCUs ;) > > http://www.delorie.com/house/furnace/pcb2/ > > The main software is all custom, using the GPIO and serial lines to > program the five R8C chips, and i2c to communicate with them when > they're running. Yes, the DIN-8 connector is the console. The > transplanted ethernet jack (Pulse J0011D21) works fine. Power is > about 4.5v; it's a 5v switcher and a 2A diode drop. > > The web server is boa/perl/cgi. I had to rebuild microperl to support > %ENV and installed index.cgi as the "build a directory script" so that > it was the default home page. > > DJ > > PS: Hey gumstix folks, next time you design an ethernet board, please > put thermals around the ground pins on the ethernet jack ;-) > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
|
From: Dave Hylands <dhylands@gm...> - 2007-06-25 21:09:24
|
Hi Alex, On 6/25/07, Blyskun Alexander M Civ AFIT/ENG <ALEXANDER.BLYSKUN@...> wrote: > Dave, > I'm trying to conduct an easy test of this by connecting COM1 > hyperterminal to the GUMSTIX pins. The jumpers are in place on the > UARTS pins as you have specified. I'm sure I have my COM1 connected > properly (it is through a RS232/TTL level converter however). > But, my PWM channels aren't working at all. Was this a proper > way to test? The gumstix port is the FFUART port on the gumstix. What I normally do is run a program like sertest on the gumstix. <http://docswiki.gumstix.com/Sample_code/C/Serial>; So with your hyperterminal connected up to the GUMSTIX port, you should be at a linux prompt and be able to enter linux commands. You'd transfer the sertest program to the gumstix and run something like: sertest --port=ttyS2 --baud=9600 Then anything you type (in your hyperterminal session) will be sent to /dev/ttyS2 (aka STUART), and anything sertest receives will be printed by sertest. Also note, that you need to make sure that the robostix is actually running; <http://docswiki.gumstix.com/Robostix_power>; I normally use one of the LEDs as a heartbeat that flashes so I can tell that the program is running. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
|
From: DJ Delorie <dj@de...> - 2007-06-25 21:09:24
|
"Jeff Sadowski" <jeff.sadowski@...> writes: > I'm thinking https login I'm blocking the whole computer. |
|
From: Dave Hylands <dhylands@gm...> - 2007-06-25 21:03:19
|
Hi Demetris, > you are saying if if ( read( gPortFd, &ch, 1 ) equals to 1 then (do > whatever) > > else continue. > > but i don't want to continue. I want to wait untill i get that 1 byte. The else continue part is just to cover error conditions, like you passed in a bad file descriptor, or somebody is trying to send a signal. Generally speaking if you get anything other than 1 it means that you'll just get the same error the next time you call it. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
|
From: Christian Hentschel <chentschel@be...> - 2007-06-25 20:59:25
|
Hi,
I faced some weird problems suddenly on my gusmtix. It was running
non-stop for quite long but today it started with flash jffs2 problems.
Now the connex-400-bt wont boot any more.
Please, any advice on this?!. Is the board useless now?. Should i
return it to gumstix service?
Thanks in advance.
This is the log i found when i got into the connex via kermit:
Node totlen on flash (0x00000000) != totlen from node ref (0x00000044)
done.
Node CRC 2020089d != calculated CRC 614749a5 for node at 00a0fd40
Node CRC e1843002 != calculated CRC 8a497bc2 for node at 00a10518
Node CRC a54a3c20 != calculated CRC 5398c85e for node at 00a10db0
Node CRC 48010409 != calculated CRC 8c988c47 for node at 00a11768
Node CRC 2020089d != calculated CRC 614749a5 for node at 00a0fd40
Then i booted and got this message:
U-Boot 1.1.4 (Nov 6 2006 - 11:20:03) - 400 MHz - 1161
*** Welcome to Gumstix ***
U-Boot code: A3F00000 -> A3F25DE4 BSS: -> A3F5AF00
RAM Configuration:
Bank #0: a0000000 64 MB
Flash: 16 MB
Using default environment
SMC91C1111-0
Net: SMC91C1111-0
Hit any key to stop autoboot: 0
Instruction Cache is ON
### JFFS2 loading 'boot/uImage' to 0xa2000000
Scanning JFFS2 FS: ..... done.
find_inode failed for name=boot
### JFFS2 LOAD ERROR<0> for boot/uImage!
|
|
From: Sibilsky <bsibilsky@co...> - 2007-06-25 20:57:17
|
Nevermind, Initially I wasn't able to see the rest of the responses. I =
was
using the dash shell and have changed it to bash. Hopefully that will =
fix
things.
Brian
-----Original Message-----
From: gumstix-users-bounces@...
[mailto:gumstix-users-bounces@...] On Behalf Of bSib1
Sent: Monday, June 25, 2007 3:41 PM
To: gumstix-users@...
Subject: Re: [Gumstix-users] Need help: Flash-Problems
Juergen, did you ever figure out why you were getting the "-e" in your
modprobe.conf file. I switched to a new build maching and am now getting
them as well. ...with similiar failures as you described??
Brian Sibilsky
Juergen Quade wrote:
>=20
> My gumstix is booting again...
> For the protocol: I changed two things.
>=20
> 1. I erased the flash with the command
> >>jerase<< instead of >>erase<<.
>=20
> BTW: What is the difference between "erase" and "jerase"?
>=20
> 2. I exchanged the defect "modprobe.conf" file in the
> root filesystem. I still do not know what part of the
> build process is responsible for the defects in the
> file...
>=20
> Juergen
>=20
>=20
> On Fri, May 25, 2007 at 11:36:35AM +0200, Juergen Quade wrote:
>> Hi all,
>>=20
>> I think I need some help!
>> Reflashing my verdex-xm4-bt failed. I tried it twice,
>> first with r1321, second with 1352.
>>=20
>> Flashing seemed to work well, but when booting the
>> system it stopped with the following messages:
>>=20
>> ...
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line =
39:
>> ignoring bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line =
42:
>> ignoring bad line starting with '-e'
>>=20
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a60000 failed: -22
>> Newly-erased block contained word 0xffffffef at offset =
0x00a41de0
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a40000 failed: -22
>> Gumstix Flash ROM: Chip not ready after erase suspended: =
status =3D
>> 0x0
>>=20
>> I am still using (presinstalled) u-boot 1.1.4. Therefore
>> in case of r1352 I loaded the kernel via zmodem and booted
>> via bootm-command. That seems to work well...
>>=20
>> gum> loadb a2000000
>> gum> bootm a2000000
>>=20
>> Find attach my Kermit-session.log-file.
>>=20
>> Any help is appreciated!
>>=20
>> Juergen.
>=20
>> ?
>>=20
>>=20
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>>=20
>>=20
>> *** Welcome to Gumstix ***
>>=20
>>=20
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>>=20
>> RAM Configuration:
>>=20
>> Bank #0: a0000000 64 MB
>>=20
>> Flash: 16 MB
>>=20
>> Using default environment
>>=20
>>=20
>>=20
>> SMC91C1111-0
>>=20
>> Net: SMC91C1111-0
>>=20
>> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20
>> Instruction Cache is ON
>> ### JFFS2 loading 'boot/uImage' to 0xa2000000
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =
=08=08\ =08=08| =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =
=08=08. =08=08. =08=08- =08=08. =08=08\ =08=08. =08=08. =08=08| =
=08=08/
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>>=20
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz ?
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>> Net: SMC91C1111-0
>> Hit any key to stop autoboot: 2 =08=08=08 0=20
>> GUM> loadb a2000000
>> ## Ready for binary (kermit) download to 0xA2000000 at 115200 bps...
>> ## Total Size =3D 0x006f7984 =3D 7305604 Bytes
>> ## Start Addr =3D 0xA2000000
>> GUM> crc32 a2000000 ${filesys=08 =08=08 =08ize}
>> CRC32 for a2000000 ... a26f7983 =3D=3D> 79c08dbc
>> GUM> protect on 1:0-1
>> Protect Flash Sectors 0-1 in Bank # 1
>> .. done
>> GUM> erase all
>> Erase Flash Bank # 1 - Warning: 2 protected sectors will not be =
erased!
>>
.........................................................................=
...
.....................................................
>> done
>> GUM> cp.b a2000000 40000 ${filesize}
>> Copy to Flash... done
>> GUM> boot
>> Instruction Cache is ON
>> ### JFFS2 loading 'boot/uImage' to 0xa2000000
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =
=08=08\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =
=08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =
=08=08\
>> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =
=08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =
=08=08/
>> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done.
>> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000
>> ## Booting image at a2000000 ...
>> Image Name: uImage
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 858388 Bytes =3D 838.3 kB
>> Load Address: a0008000
>> Entry Point: a0008000
>> OK
>>=20
>> Starting kernel ...
>>=20
>> Linux version 2.6.18gum (quade@...) (gcc version 4.1.1) #1 Fri =
May
>> 25 09:53:26 CEST 2007
>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f
>> Machine: The Gumstix Platform
>> Memory policy: ECC disabled, Data cache writeback
>> Run Mode clock: 208.00MHz (*16)
>> Turbo Mode clock: 416.00MHz (*2.0, active)
>> Memory clock: 104.00MHz (/2)
>> System bus clock: 104.00MHz=20
>> CPU0: D VIVT undefined 5 cache
>> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> Built 1 zonelists. Total pages: 16384
>> Kernel command line: console=3DttyS0,115200n8 root=3D1f01 =
rootfstype=3Djffs2
>> reboot=3Dcold,hard
>> PID hash table entries: 512 (order: 9, 2048 bytes)
>> start_kernel(): bug: interrupts were enabled early
>> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>> Memory: 64MB =3D 64MB total
>> Memory: 63128KB available (1396K code, 285K data, 64K init)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> NET: Registered protocol family 16
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 512 (order: -1, 2048 bytes)
>> TCP established hash table entries: 2048 (order: 1, 8192 bytes)
>> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
>> TCP: Hash tables configured (established 2048 bind 1024)
>> TCP reno registered
>> JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
>> Initializing Cryptographic API
>> io scheduler noop registered
>> io scheduler cfq registered (default)
>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART
>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART
>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 20) is a STUART
>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit
>> bankwidth)
>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Using buffer write method
>> cfi_cmdset_0001: Erase suspend on write enabled
>> Using static partitions on Gumstix Flash ROM
>> Creating 2 MTD partitions on "Gumstix Flash ROM":
>> 0x00000000-0x00040000 : "Bootloader"
>> 0x00040000-0x01000000 : "RootFS"
>> TCP bic registered
>> VFS: Mounted root (jffs2 filesystem).
>> Freeing init memory: 64K
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> NET: Registered protocol family 1
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00840000 failed: -22
>> Newly-erased block contained word 0xfffeffff at offset 0x008202c4
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00820000 failed: -22
>> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D =
0x0
>> ?
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>> Net: SMC91C1111-0
>> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20
>> Instruction Cache is ON
>> ### JFFS2 loading 'boot/uImage' to 0xa2000000
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =
=08=08\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =
=08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =
=08=08\
>> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =
=08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =
=08=08/
>> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done.
>> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000
>> ## Booting image at a2000000 ...
>> Image Name: uImage
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 858388 Bytes =3D 838.3 kB
>> Load Address: a0008000
>> Entry Point: a0008000
>> OK
>>=20
>> Starting kernel ...
>>=20
>> Linux version 2.6.18gum (quade@...) (gcc version 4.1.1) #1 Fri =
May
>> 25 09:53:26 CEST 2007
>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f
>> Machine: The Gumstix Platform
>> Memory policy: ECC disabled, Data cache writeback
>> Run Mode clock: 208.00MHz (*16)
>> Turbo Mode clock: 416.00MHz (*2.0, active)
>> Memory clock: 104.00MHz (/2)
>> System bus clock: 104.00MHz=20
>> CPU0: D VIVT undefined 5 cache
>> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> Built 1 zonelists. Total pages: 16384
>> Kernel command line: console=3DttyS0,115200n8 root=3D1f01 =
rootfstype=3Djffs2
>> reboot=3Dcold,hard
>> PID hash table entries: 512 (order: 9, 2048 bytes)
>> start_kernel(): bug: interrupts were enabled early
>> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>> Memory: 64MB =3D 64MB total
>> Memory: 63128KB available (1396K code, 285K data, 64K init)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> NET: Registered protocol family 16
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 512 (order: -1, 2048 bytes)
>> TCP established hash table entries: 2048 (order: 1, 8192 bytes)
>> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
>> TCP: Hash tables configured (established 2048 bind 1024)
>> TCP reno registered
>> JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
>> Initializing Cryptographic API
>> io scheduler noop registered
>> io scheduler cfq registered (default)
>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART
>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART
>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 20) is a STUART
>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit
>> bankwidth)
>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Using buffer write method
>> cfi_cmdset_0001: Erase suspend on write enabled
>> Using static partitions on Gumstix Flash ROM
>> Creating 2 MTD partitions on "Gumstix Flash ROM":
>> 0x00000000-0x00040000 : "Bootloader"
>> 0x00040000-0x01000000 : "RootFS"
>> TCP bic registered
>> VFS: Mounted root (jffs2 filesystem).
>> Freeing init memory: 64K
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> NET: Registered protocol family 1
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: =
ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: =
ignoring
>> bad line starting with '-e'
>>=20
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a20000 failed: -22
>> Newly-erased block contained word 0xffbfffff at offset 0x00a001f0
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a00000 failed: -22
>> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D =
0x0
>> ?
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>> Net: SMC91C1111-0
>> Hit any key to stop autoboot: 2 =08=08=08 0=20
>> GUM> ls
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =
=08=08\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =
=08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =
=08=08-
>> =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =
=08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =
=08=08|
>> =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done.
>> drwxr-xr-x 0 Fri May 25 08:04:06 2007 bin
>> drwxr-xr-x 0 Fri May 25 07:54:34 2007 boot
>> drwxr-xr-x 0 Fri May 25 08:04:08 2007 dev
>> drwxr-xr-x 0 Fri May 25 08:04:08 2007 etc
>> drwxr-xr-x 0 Mon Nov 22 17:20:58 1999 home
>> drwxr-xr-x 0 Fri May 25 08:04:06 2007 lib
>> drwxr-xr-x 0 Fri May 25 07:08:09 2007 mnt
>> drwxr-xr-x 0 Mon Nov 22 17:21:08 1999 opt
>> drwxr-xr-x 0 Wed Nov 03 00:54:07 1999 proc
>> drwxr-xr-x 0 Fri May 25 07:08:09 2007 root
>> drwxr-xr-x 0 Fri May 25 08:04:07 2007 sbin
>> drwxr-xr-x 0 Fri May 25 07:08:09 2007 sys
>> drwxr-xr-x 0 Thu Jun 29 23:20:38 2000 tmp
>> drwxr-xr-x 0 Fri May 25 08:02:12 2007 usr
>> drwxr-xr-x 0 Fri May 25 07:42:49 2007 var
>> GUM>=20
>> =
-------------------------------------------------------------------------=
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>=20
>=20
> =
-------------------------------------------------------------------------=
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>=20
>=20
--=20
View this message in context:
http://www.nabble.com/Need-help%3A-Flash-Problems-tf3815114.html#a1129512=
8
Sent from the Gumstix mailing list archive at Nabble.com.
-------------------------------------------------------------------------=
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
gumstix-users mailing list
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users
|
|
From: Jeff Sadowski <jeff.sadowski@gm...> - 2007-06-25 20:55:36
|
> > Web page control of heating is pretty cool :-) > > Yup, but you've got to make sure the firewall is set up right ;-) I'm thinking https login |
|
From: DJ Delorie <dj@de...> - 2007-06-25 20:48:03
|
"Jeff Sadowski" <jeff.sadowski@...> writes: > What are you using for thermostat? do you just have a analog one > hooked up to gpio's? All the sensors use the Dallas 1-wire protocol (four of the R8C's manage this, one for each of four zones). Each zone's thermostat has a temperature/humidity sensor based on the DS2438 chip and HIH-3600 sensor, plus one of Seetron's smart LCD displays. So, two wires - 1wire for sensors and buttons, and serial for the LCD - are used for each zone. The "outside" sensor is the same, but no LCD display ;-) The pushbuttons just connect one of four DS2401 chips to the 1wire bus. The R8Cs can see when they're present so they know when the button's pushed. The previous board used a beige box PC. It still bit-banged the 1wire bus, but it had to disable interrupts and do one zone at a time, so it was much slower. At some point in the future, I hope to put a tiny MCU in each thermostat, and run a plain serial protocol to each one. > I was thinking of using usb thermometers at stations and have them > report over a secure encrypted wireless network. It's also a good zigbee task, but in my case, I already had all the wires to the old (mechanical) thermostats, so I just reused them. Each thermostat gets +5 and GND. > Web page control of heating is pretty cool :-) Yup, but you've got to make sure the firewall is set up right ;-) |
|
From: bSib1 <bsibilsky@co...> - 2007-06-25 20:41:09
|
Juergen, did you ever figure out why you were getting the "-e" in your
modprobe.conf file. I switched to a new build maching and am now getting
them as well. ...with similiar failures as you described??
Brian Sibilsky
Juergen Quade wrote:
>=20
> My gumstix is booting again...
> For the protocol: I changed two things.
>=20
> 1. I erased the flash with the command
> >>jerase<< instead of >>erase<<.
>=20
> BTW: What is the difference between "erase" and "jerase"?
>=20
> 2. I exchanged the defect "modprobe.conf" file in the
> root filesystem. I still do not know what part of the
> build process is responsible for the defects in the
> file...
>=20
> Juergen
>=20
>=20
> On Fri, May 25, 2007 at 11:36:35AM +0200, Juergen Quade wrote:
>> Hi all,
>>=20
>> I think I need some help!
>> Reflashing my verdex-xm4-bt failed. I tried it twice,
>> first with r1321, second with 1352.
>>=20
>> Flashing seemed to work well, but when booting the
>> system it stopped with the following messages:
>>=20
>> ...
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39:
>> ignoring bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42:
>> ignoring bad line starting with '-e'
>>=20
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a60000 failed: -22
>> Newly-erased block contained word 0xffffffef at offset 0x00a41de=
0
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a40000 failed: -22
>> Gumstix Flash ROM: Chip not ready after erase suspended: status =
=3D
>> 0x0
>>=20
>> I am still using (presinstalled) u-boot 1.1.4. Therefore
>> in case of r1352 I loaded the kernel via zmodem and booted
>> via bootm-command. That seems to work well...
>>=20
>> gum> loadb a2000000
>> gum> bootm a2000000
>>=20
>> Find attach my Kermit-session.log-file.
>>=20
>> Any help is appreciated!
>>=20
>> Juergen.
>=20
>> ?
>>=20
>>=20
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>>=20
>>=20
>> *** Welcome to Gumstix ***
>>=20
>>=20
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>>=20
>> RAM Configuration:
>>=20
>> Bank #0: a0000000 64 MB
>>=20
>> Flash: 16 MB
>>=20
>> Using default environment
>>=20
>>=20
>>=20
>> SMC91C1111-0
>>=20
>> Net: SMC91C1111-0
>>=20
>> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20
>> Instruction Cache is ON
>> ### JFFS2 loading 'boot/uImage' to 0xa2000000
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08=
\ =08=08| =08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08.=
=08=08. =08=08- =08=08. =08=08\ =08=08. =08=08. =08=08| =08=08/=20
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>>=20
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz ?
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>> Net: SMC91C1111-0
>> Hit any key to stop autoboot: 2 =08=08=08 0=20
>> GUM> loadb a2000000
>> ## Ready for binary (kermit) download to 0xA2000000 at 115200 bps...
>> ## Total Size =3D 0x006f7984 =3D 7305604 Bytes
>> ## Start Addr =3D 0xA2000000
>> GUM> crc32 a2000000 ${filesys=08 =08=08 =08ize}
>> CRC32 for a2000000 ... a26f7983 =3D=3D> 79c08dbc
>> GUM> protect on 1:0-1
>> Protect Flash Sectors 0-1 in Bank # 1
>> .. done
>> GUM> erase all
>> Erase Flash Bank # 1 - Warning: 2 protected sectors will not be erased!
>> ........................................................................=
.........................................................
>> done
>> GUM> cp.b a2000000 40000 ${filesize}
>> Copy to Flash... done
>> GUM> boot
>> Instruction Cache is ON
>> ### JFFS2 loading 'boot/uImage' to 0xa2000000
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08=
\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08-=
=08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\
>> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/
>> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done.
>> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000
>> ## Booting image at a2000000 ...
>> Image Name: uImage
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 858388 Bytes =3D 838.3 kB
>> Load Address: a0008000
>> Entry Point: a0008000
>> OK
>>=20
>> Starting kernel ...
>>=20
>> Linux version 2.6.18gum (quade@...) (gcc version 4.1.1) #1 Fri May
>> 25 09:53:26 CEST 2007
>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f
>> Machine: The Gumstix Platform
>> Memory policy: ECC disabled, Data cache writeback
>> Run Mode clock: 208.00MHz (*16)
>> Turbo Mode clock: 416.00MHz (*2.0, active)
>> Memory clock: 104.00MHz (/2)
>> System bus clock: 104.00MHz=20
>> CPU0: D VIVT undefined 5 cache
>> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> Built 1 zonelists. Total pages: 16384
>> Kernel command line: console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Dj=
ffs2
>> reboot=3Dcold,hard
>> PID hash table entries: 512 (order: 9, 2048 bytes)
>> start_kernel(): bug: interrupts were enabled early
>> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>> Memory: 64MB =3D 64MB total
>> Memory: 63128KB available (1396K code, 285K data, 64K init)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> NET: Registered protocol family 16
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 512 (order: -1, 2048 bytes)
>> TCP established hash table entries: 2048 (order: 1, 8192 bytes)
>> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
>> TCP: Hash tables configured (established 2048 bind 1024)
>> TCP reno registered
>> JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
>> Initializing Cryptographic API
>> io scheduler noop registered
>> io scheduler cfq registered (default)
>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART
>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART
>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 20) is a STUART
>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit
>> bankwidth)
>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Using buffer write method
>> cfi_cmdset_0001: Erase suspend on write enabled
>> Using static partitions on Gumstix Flash ROM
>> Creating 2 MTD partitions on "Gumstix Flash ROM":
>> 0x00000000-0x00040000 : "Bootloader"
>> 0x00040000-0x01000000 : "RootFS"
>> TCP bic registered
>> VFS: Mounted root (jffs2 filesystem).
>> Freeing init memory: 64K
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> NET: Registered protocol family 1
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:53 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:54 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:55 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:56 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:57 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:58 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:21:59 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:00 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:01 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:02 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:22:03 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00840000 failed: -22
>> Newly-erased block contained word 0xfffeffff at offset 0x008202c4
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00820000 failed: -22
>> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D 0x0
>> ?
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>> Net: SMC91C1111-0
>> Hit any key to stop autoboot: 2 =08=08=08 1 =08=08=08 0=20
>> Instruction Cache is ON
>> ### JFFS2 loading 'boot/uImage' to 0xa2000000
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08=
\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08-=
=08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\
>> =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/
>> =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done.
>> ### JFFS2 load complete: 858452 bytes loaded to 0xa2000000
>> ## Booting image at a2000000 ...
>> Image Name: uImage
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 858388 Bytes =3D 838.3 kB
>> Load Address: a0008000
>> Entry Point: a0008000
>> OK
>>=20
>> Starting kernel ...
>>=20
>> Linux version 2.6.18gum (quade@...) (gcc version 4.1.1) #1 Fri May
>> 25 09:53:26 CEST 2007
>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=3D0000397f
>> Machine: The Gumstix Platform
>> Memory policy: ECC disabled, Data cache writeback
>> Run Mode clock: 208.00MHz (*16)
>> Turbo Mode clock: 416.00MHz (*2.0, active)
>> Memory clock: 104.00MHz (/2)
>> System bus clock: 104.00MHz=20
>> CPU0: D VIVT undefined 5 cache
>> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
>> Built 1 zonelists. Total pages: 16384
>> Kernel command line: console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Dj=
ffs2
>> reboot=3Dcold,hard
>> PID hash table entries: 512 (order: 9, 2048 bytes)
>> start_kernel(): bug: interrupts were enabled early
>> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>> Memory: 64MB =3D 64MB total
>> Memory: 63128KB available (1396K code, 285K data, 64K init)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> NET: Registered protocol family 16
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 512 (order: -1, 2048 bytes)
>> TCP established hash table entries: 2048 (order: 1, 8192 bytes)
>> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
>> TCP: Hash tables configured (established 2048 bind 1024)
>> TCP reno registered
>> JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
>> Initializing Cryptographic API
>> io scheduler noop registered
>> io scheduler cfq registered (default)
>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq =3D 22) is a FFUART
>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq =3D 21) is a BTUART
>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq =3D 20) is a STUART
>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit
>> bankwidth)
>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Intel/Sharp Extended Query Table at 0x010A
>> Using buffer write method
>> cfi_cmdset_0001: Erase suspend on write enabled
>> Using static partitions on Gumstix Flash ROM
>> Creating 2 MTD partitions on "Gumstix Flash ROM":
>> 0x00000000-0x00040000 : "Bootloader"
>> 0x00040000-0x01000000 : "RootFS"
>> TCP bic registered
>> VFS: Mounted root (jffs2 filesystem).
>> Freeing init memory: 64K
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> request_module: runaway loop modprobe net-pf-1
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> NET: Registered protocol family 1
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:30 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:31 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:32 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:33 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:34 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:35 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:36 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:37 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:38 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:39 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 39: ignoring
>> bad line starting with '-e'
>>=20
>> Dec 31 16:00:40 modprobe: WARNING: /etc/modprobe.conf line 42: ignoring
>> bad line starting with '-e'
>>=20
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a20000 failed: -22
>> Newly-erased block contained word 0xffbfffff at offset 0x00a001f0
>> Gumstix Flash ROM: buffer write error (status 0xd0)
>> Write clean marker to block at 0x00a00000 failed: -22
>> Gumstix Flash ROM: Chip not ready after erase suspended: status =3D 0x0
>> ?
>>=20
>> U-Boot 1.1.4 (Mar 1 2007 - 17:06:18) - PXA270@... MHz - 1321
>>=20
>> *** Welcome to Gumstix ***
>>=20
>> U-Boot code: A3F00000 -> A3F25850 BSS: -> A3F5AE70
>> RAM Configuration:
>> Bank #0: a0000000 64 MB
>> Flash: 16 MB
>> Using default environment
>>=20
>> SMC91C1111-0
>> Net: SMC91C1111-0
>> Hit any key to stop autoboot: 2 =08=08=08 0=20
>> GUM> ls
>> Scanning JFFS2 FS: =08=08| =08=08. =08=08/ =08=08- =08=08\ =08=08| =
=08=08/ =08=08. =08=08- =08=08\ =08=08| =08=08.=20
>> =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08. =08=08=
\ =08=08| =08=08/ =08=08- =08=08. =08=08\ =08=08| =08=08/ =08=08-
>> =08=08\ =08=08. =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08-=
=08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08. =08=08| =08=08/ =08=08-
>> =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =
=08=08| =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08\ =08=08|
>> =08=08/ =08=08- =08=08\ =08=08| =08=08/ =08=08- =08=08 done.
>> drwxr-xr-x 0 Fri May 25 08:04:06 2007 bin
>> drwxr-xr-x 0 Fri May 25 07:54:34 2007 boot
>> drwxr-xr-x 0 Fri May 25 08:04:08 2007 dev
>> drwxr-xr-x 0 Fri May 25 08:04:08 2007 etc
>> drwxr-xr-x 0 Mon Nov 22 17:20:58 1999 home
>> drwxr-xr-x 0 Fri May 25 08:04:06 2007 lib
>> drwxr-xr-x 0 Fri May 25 07:08:09 2007 mnt
>> drwxr-xr-x 0 Mon Nov 22 17:21:08 1999 opt
>> drwxr-xr-x 0 Wed Nov 03 00:54:07 1999 proc
>> drwxr-xr-x 0 Fri May 25 07:08:09 2007 root
>> drwxr-xr-x 0 Fri May 25 08:04:07 2007 sbin
>> drwxr-xr-x 0 Fri May 25 07:08:09 2007 sys
>> drwxr-xr-x 0 Thu Jun 29 23:20:38 2000 tmp
>> drwxr-xr-x 0 Fri May 25 08:02:12 2007 usr
>> drwxr-xr-x 0 Fri May 25 07:42:49 2007 var
>> GUM>=20
>> ------------------------------------------------------------------------=
-
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>=20
>=20
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>=20
>=20
--=20
View this message in context: http://www.nabble.com/Need-help%3A-Flash-Prob=
lems-tf3815114.html#a11295128
Sent from the Gumstix mailing list archive at Nabble.com.
|
|
From: Blyskun Alexander M Civ AFIT/ENG <ALEXANDER.BLYSKUN@af...> - 2007-06-25 20:34:14
|
Dave, I'm trying to conduct an easy test of this by connecting COM1 hyperterminal to the GUMSTIX pins. The jumpers are in place on the UARTS pins as you have specified. I'm sure I have my COM1 connected properly (it is through a RS232/TTL level converter however). =20 But, my PWM channels aren't working at all. Was this a proper way to test? thanks=20 Alex Blyskun Electrical Engineering Intern Advanced Navigation Technology (ANT) Center AFIT/ENG -----Original Message----- From: gumstix-users-bounces@... [mailto:gumstix-users-bounces@...] On Behalf Of Dave Hylands Sent: Monday, June 25, 2007 2:26 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] robostix/gumstix communication Hi Alex, > I don't need to program the robostix through the gumstix; I just need > to send commands from my PC to the gumstix via wifi in real time, and > then onto the robostix for PWM control. I'd prefer to keep it uart. > Does your message apply here also? I'll worry about the PC>wifi>gumstix > portion later; I just want to make sure my uart>robostix>pwm channels > programming is appropriate. The same jumper as is used when programming the robostix from the gumstix will connect the STUART port on the gumstix with the UART0 port on the robostix. You don't NEED to program the robostix, it jsut happens to use the exact same hardware lines, so the same jumper works for both situations. --=20 Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
From: Jeff Sadowski <jeff.sadowski@gm...> - 2007-06-25 20:16:12
|
:-) so cool. Its making me want to do something similar. What are you using for thermostat? do you just have a analog one hooked up to gpio's? I was thinking of using usb thermometers at stations and have them report over a secure encrypted wireless network. Web page control of heating is pretty cool :-) On 6/25/07, DJ Delorie <dj@...> wrote: > > Many thanks to all who helped me get to this point... my central > heating/cooling system now has a gumstix running it! (along with five > other MCUs ;) > > http://www.delorie.com/house/furnace/pcb2/ > > The main software is all custom, using the GPIO and serial lines to > program the five R8C chips, and i2c to communicate with them when > they're running. Yes, the DIN-8 connector is the console. The > transplanted ethernet jack (Pulse J0011D21) works fine. Power is > about 4.5v; it's a 5v switcher and a 2A diode drop. > > The web server is boa/perl/cgi. I had to rebuild microperl to support > %ENV and installed index.cgi as the "build a directory script" so that > it was the default home page. > > DJ > > PS: Hey gumstix folks, next time you design an ethernet board, please > put thermals around the ground pins on the ethernet jack ;-) > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
|
From: Demetris Zavorotnichenko <fgcity4652@cy...> - 2007-06-25 19:44:13
|
My MCU is sending 1 (as in a byte 1)
so i want to make the program stop at a point and wait for the Atmega to
send "1"
if 1 is send then continue with the program. if not then wait until it gets
1.
with the code :
> if ( read( gPortFd, &ch, 1 ) == 1 )
> {
> //... got one character now...
> }
you are saying if if ( read( gPortFd, &ch, 1 ) equals to 1 then (do
whatever)
else continue.
but i don't want to continue. I want to wait untill i get that 1 byte.
Demetris Z.
----- Original Message -----
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users."
<gumstix-users@...>
Sent: Monday, June 25, 2007 10:35 PM
Subject: Re: [Gumstix-users] Serial Code Question
> Hi Demetris,
>
> On 6/25/07, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> By doing :
>>
>> if ( read( gPortFd, &ch, 1 ) == 1 )
>> {
>> //... got one character now...
>> }
>>
>> then if "read( gPortFd, &ch, 1 )" is equal to 0 then won't the program
>> continue from there?
>
> It shouldn't ever return 0 if you've set things up right. It should
> only return 1 to indicate that it read one character or -1 to indicate
> that an error occurred.
>
> If you use fcntl and FNDELAY, then you can get a return of 0, but
> otherwise it shouldn't happen.
>
> --
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
|
|
From: Dave Hylands <dhylands@gm...> - 2007-06-25 19:35:53
|
Hi Demetris,
On 6/25/07, Demetris Zavorotnichenko <fgcity4652@...> wrote:
> By doing :
>
> if ( read( gPortFd, &ch, 1 ) == 1 )
> {
> //... got one character now...
> }
>
> then if "read( gPortFd, &ch, 1 )" is equal to 0 then won't the program
> continue from there?
It shouldn't ever return 0 if you've set things up right. It should
only return 1 to indicate that it read one character or -1 to indicate
that an error occurred.
If you use fcntl and FNDELAY, then you can get a return of 0, but
otherwise it shouldn't happen.
--
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/
|
|
From: DJ Delorie <dj@de...> - 2007-06-25 19:18:18
|
Many thanks to all who helped me get to this point... my central heating/cooling system now has a gumstix running it! (along with five other MCUs ;) http://www.delorie.com/house/furnace/pcb2/ The main software is all custom, using the GPIO and serial lines to program the five R8C chips, and i2c to communicate with them when they're running. Yes, the DIN-8 connector is the console. The transplanted ethernet jack (Pulse J0011D21) works fine. Power is about 4.5v; it's a 5v switcher and a 2A diode drop. The web server is boa/perl/cgi. I had to rebuild microperl to support %ENV and installed index.cgi as the "build a directory script" so that it was the default home page. DJ PS: Hey gumstix folks, next time you design an ethernet board, please put thermals around the ground pins on the ethernet jack ;-) |
|
From: Demetris Zavorotnichenko <fgcity4652@cy...> - 2007-06-25 19:13:57
|
By doing :
if ( read( gPortFd, &ch, 1 ) == 1 )
{
//... got one character now...
}
then if "read( gPortFd, &ch, 1 )" is equal to 0 then won't the program
continue from there?
or with this command it will wait intil "read( gPortFd, &ch, 1 )" is going
to be equal to 1 ?
Demetris Z.
----- Original Message -----
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users."
<gumstix-users@...>
Sent: Monday, June 25, 2007 9:58 PM
Subject: Re: [Gumstix-users] Serial Code Question
> Hi Demtris,
>
> On 6/25/07, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> Then what would be the best way to do this without consuming allot of CPU
>> ?
>
> Don't call fcntl with FNODELAY and do call cfmakeraw.
>
> Then your reads will block until one character is available.
>
> Just a simple
>
> if ( read( gPortFd, &ch, 1 ) == 1 )
> {
> //... got one character now...
> }
>
> will block until a single character is read. Normally commands and
> responses have some type of delimiter like a newline or carriage
> return, and you write a routine that reads one whole line into a
> buffer.
>
> --
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
|
|
From: Dave Hylands <dhylands@gm...> - 2007-06-25 18:58:18
|
Hi Demtris,
On 6/25/07, Demetris Zavorotnichenko <fgcity4652@...> wrote:
> Then what would be the best way to do this without consuming allot of CPU ?
Don't call fcntl with FNODELAY and do call cfmakeraw.
Then your reads will block until one character is available.
Just a simple
if ( read( gPortFd, &ch, 1 ) == 1 )
{
//... got one character now...
}
will block until a single character is read. Normally commands and
responses have some type of delimiter like a newline or carriage
return, and you write a routine that reads one whole line into a
buffer.
--
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/
|
|
From: Demetris Zavorotnichenko <fgcity4652@cy...> - 2007-06-25 18:54:41
|
I didn't use fndelay
i used the following loop :
while (( bytesRead = read( gPortFd, &ch, 1 )) < 1 ){bytesRead = read(
gPortFd, &ch, 1 )}so when i send "1" to the serial then it out's from the
loop.is this ok ?
Demetris Z.
----- Original Message -----
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users."
<gumstix-users@...>
Sent: Monday, June 25, 2007 7:46 PM
Subject: Re: [Gumstix-users] Serial Code Question
> Hi Demetris,
>
> On 6/25/07, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> Tnx dave. I wanted to ask something else about this.
>>
>> I understand that in order to read from the Serial I do the following:
>>
>> fcntl(fd, F_SETFL, FNDELAY);
>>
>> I need Gumstix to wait on that point of code (when it reads the Serial)
>> until Gumstix receives "OK" and then continue. How do I do that ?
>
> Calling fcntl(fd, F_SETFL, FNDELAY) says that you DON'T want it to block.
>
> Calling cfmakeraw set VMIN & VTIME such that asking for a single
> character will block until a character is available.
>
> You'd be far better off to not use the fcntl call and just read for
> single characters. Reading for more than one character also works, but
> you need to be prepared for the case where only one character is
> available.
>
> putting your read in a while loop with FNDELAY will cause your process
> to consume 100% of the CPU while it's waiting for the data, which will
> generally cause other problems as your system gets more complex.
>
> --
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
|
|
From: Demetris Zavorotnichenko <fgcity4652@cy...> - 2007-06-25 18:49:24
|
Then what would be the best way to do this without consuming allot of CPU ? I would really appriciate the help on this. Demetris Z. ----- Original Message ----- From: "Dave Hylands" <dhylands@...> To: "General mailing list for gumstix users." <gumstix-users@...> Sent: Monday, June 25, 2007 7:46 PM Subject: Re: [Gumstix-users] Serial Code Question > Hi Demetris, > > On 6/25/07, Demetris Zavorotnichenko <fgcity4652@...> wrote: >> Tnx dave. I wanted to ask something else about this. >> >> I understand that in order to read from the Serial I do the following: >> >> fcntl(fd, F_SETFL, FNDELAY); >> >> I need Gumstix to wait on that point of code (when it reads the Serial) >> until Gumstix receives "OK" and then continue. How do I do that ? > > Calling fcntl(fd, F_SETFL, FNDELAY) says that you DON'T want it to block. > > Calling cfmakeraw set VMIN & VTIME such that asking for a single > character will block until a character is available. > > You'd be far better off to not use the fcntl call and just read for > single characters. Reading for more than one character also works, but > you need to be prepared for the case where only one character is > available. > > putting your read in a while loop with FNDELAY will cause your process > to consume 100% of the CPU while it's waiting for the data, which will > generally cause other problems as your system gets more complex. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
From: Dave Hylands <dhylands@gm...> - 2007-06-25 18:26:22
|
Hi Alex, > I don't need to program the robostix through the gumstix; I just need > to send commands from my PC to the gumstix via wifi in real time, and > then onto the robostix for PWM control. I'd prefer to keep it uart. > Does your message apply here also? I'll worry about the PC>wifi>gumstix > portion later; I just want to make sure my uart>robostix>pwm channels > programming is appropriate. The same jumper as is used when programming the robostix from the gumstix will connect the STUART port on the gumstix with the UART0 port on the robostix. You don't NEED to program the robostix, it jsut happens to use the exact same hardware lines, so the same jumper works for both situations. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
|
From: Blyskun Alexander M Civ AFIT/ENG <ALEXANDER.BLYSKUN@af...> - 2007-06-25 17:58:56
|
Dave, I don't need to program the robostix through the gumstix; I just need to send commands from my PC to the gumstix via wifi in real time, and then onto the robostix for PWM control. I'd prefer to keep it uart. Does your message apply here also? I'll worry about the PC>wifi>gumstix portion later; I just want to make sure my uart>robostix>pwm channels programming is appropriate. Thanks very much Alex Blyskun Electrical Engineering Intern Advanced Navigation Technology (ANT) Center AFIT/ENG -----Original Message----- From: gumstix-users-bounces@... [mailto:gumstix-users-bounces@...] On Behalf Of Dave Hylands Sent: Monday, June 25, 2007 12:33 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] robostix/gumstix communication HI Alex, > I currently have a PWM controller program working on my robostix. I send > commands through hyperterminal to the uart and it will adjust 4 > servos/motors. I now need to be able to command the robostix through the > gumstix (it will later be connected to the PC through wifi). Is there a > uart to connect from the gumstix to robostix (this would make for an easy > code transfer; I would just have to learn how to com from my PC to the > gumstix). If not what can I use to communicate from the gumstix to > robostix? If you build the jumpers required to program the robostix from the gumstix, as per this page: <http://docswiki.gumstix.com/Robostix_gumstix_ISP>; then you will have connected the STUART port (ttyS2) on the gumstix with UART0 on the robostix. You can also use I2C and/or SPI to communicate between the gumstix and robostix if you ever want to free up those serial ports for other purposes. --=20 Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
From: Jeff Sadowski <jeff.sadowski@gm...> - 2007-06-25 17:51:35
|
I'm still a noob with LCD screens But I think that there are too many competing connections for LCD screens. You would need docs on any screen you buy/salvage. As for disks: on the vertex you can plug in a usb disk meaning you can buy a usb case for an ide disk. On 6/24/07, Henry Cooke <aninfinitenumberofmonkeys@...> wrote: > Hello there all, > I'm thinking about attempting to build a media player/PDA using a > Gumstix machine, the idea being that if I build a touch screen (and > maybe even a few accelerometers) into it, there's huge potential for > playing with many different interface ideas. > > However, I'm more of a software person than a hardware person (though > no stranger to a soldering iron ;) ), so I have a few questions: > > It would appear that Gumstix connects to a touch screen through a > four-wire interface. Is this four-wire connector a standard for all > LCD touch screens? Could I, for example, cannibalise a screen out of > an old Palm V and use that, or is there a specific range of screens > that can be used? Is there any model or models favoured by users of > this list? > > Is it possible to hook a Gumstix up to an IDE or SATA drive? I seem to > remember reading somewhere that Compact Flash is pinout-compatible > with IDE. Does this mean that I could hook an IDE drive directly to a > cfstix adaptor with some fancy wiring, or am I missing something? > > Many thanks, and apologies for naivit=E9, > Henry > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |