From: Rob B. <ro...@li...> - 2007-06-06 11:17:11
|
Hi, I know this has been covered to some extent previously, but here goes ... My issue is with the boot speed of a connex 400XM, it has U-boot 1.1.4 (shipped version) buildroot ver 1424 (was shipped with1161) From boot I have a 2 sec U-boot interrupt window (press any key ..), 18 sec JFFS2 scan, and 8 sec linux boot I'm looking for time savings in any of these areas. I have seen the posts describing loading the uImage from a separate flash partition and will try this are there any other things I should be doing, and is a 3 to 5 sec boot time really achievable? cheers ---rob |
From: Dave H. <dhy...@gm...> - 2007-06-06 13:09:18
|
Hi Rob, > I know this has been covered to some extent previously, but here goes ... > My issue is with the boot speed of a connex 400XM, it has U-boot 1.1.4 > (shipped version) buildroot ver 1424 (was shipped with1161) > From boot I have a 2 sec U-boot interrupt window (press any key ..), > 18 sec JFFS2 scan, and 8 sec linux boot > I'm looking for time savings in any of these areas. I have seen the > posts describing loading the uImage from a separate flash partition and > will try this > are there any other things I should be doing, and is a 3 to 5 sec boot > time really achievable? Loading uImage from a seperate partition replaces the 18 second JFFS2 scan with a much smaller (1-2 second) load of the kernel. A big part of the 8 second time is still scanning JFFS2 when it mounts. Replacing that with a read-only file system like cramfs will further reduce the boot time, and perhaps having a small wirtable partition for storing stuff that really changes. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Craig H. <cr...@gu...> - 2007-06-06 18:14:27
|
On Jun 6, 2007, at 6:09 AM, Dave Hylands wrote: > Hi Rob, > >> I know this has been covered to some extent previously, but here >> goes ... >> My issue is with the boot speed of a connex 400XM, it has U-boot >> 1.1.4 >> (shipped version) buildroot ver 1424 (was shipped with1161) >> From boot I have a 2 sec U-boot interrupt window (press any key ..), >> 18 sec JFFS2 scan, and 8 sec linux boot >> I'm looking for time savings in any of these areas. I have seen the >> posts describing loading the uImage from a separate flash >> partition and >> will try this >> are there any other things I should be doing, and is a 3 to 5 sec >> boot >> time really achievable? > > Loading uImage from a seperate partition replaces the 18 second JFFS2 > scan with a much smaller (1-2 second) load of the kernel. > > A big part of the 8 second time is still scanning JFFS2 when it > mounts. Replacing that with a read-only file system like cramfs will > further reduce the boot time, and perhaps having a small wirtable > partition for storing stuff that really changes. ...and depending on what you mean by "boot time", mounting the rw partition only after you start everything else up (ie re-order the stuff in /etc/inittab maybe) might get you to a login prompt before the system "waits" to mount the rw filesystem. Note the JFFS2 will take a while to mount even when read-only, since the scan is building up an in-RAM list of all the valid inodes, since stuff later in the FS image can "overrule" stuff that's physically earlier. C |
From: Karthik B. <k.i...@gm...> - 2007-06-06 19:13:52
|
Hi Rob, Since it's an XM and not an XM-BT, do you have a bluetooth module? I was able to shave off a great deal of time from the boot of my XM stopping the bluetooth scan and initialization (since I don't have a module anyways). I simply moved S30bluetooth out of /etc/init.d...have you already done this? -Karthik On 6/6/07, Craig Hughes <cr...@gu...> wrote: > > On Jun 6, 2007, at 6:09 AM, Dave Hylands wrote: > > > Hi Rob, > > > >> I know this has been covered to some extent previously, but here > >> goes ... > >> My issue is with the boot speed of a connex 400XM, it has U-boot > >> 1.1.4 > >> (shipped version) buildroot ver 1424 (was shipped with1161) > >> From boot I have a 2 sec U-boot interrupt window (press any key ..), > >> 18 sec JFFS2 scan, and 8 sec linux boot > >> I'm looking for time savings in any of these areas. I have seen the > >> posts describing loading the uImage from a separate flash > >> partition and > >> will try this > >> are there any other things I should be doing, and is a 3 to 5 sec > >> boot > >> time really achievable? > > > > Loading uImage from a seperate partition replaces the 18 second JFFS2 > > scan with a much smaller (1-2 second) load of the kernel. > > > > A big part of the 8 second time is still scanning JFFS2 when it > > mounts. Replacing that with a read-only file system like cramfs will > > further reduce the boot time, and perhaps having a small wirtable > > partition for storing stuff that really changes. > > ...and depending on what you mean by "boot time", mounting the rw > partition only after you start everything else up (ie re-order the > stuff in /etc/inittab maybe) might get you to a login prompt before > the system "waits" to mount the rw filesystem. Note the JFFS2 will > take a while to mount even when read-only, since the scan is building > up an in-RAM list of all the valid inodes, since stuff later in the > FS image can "overrule" stuff that's physically earlier. > > C > > > ------------------------------------------------------------------------- > 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 > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Demetris Z. <fgc...@cy...> - 2007-06-13 16:56:30
|
How can I see the current revision on Gumstix? Is there a way ? |
From: Dave H. <dhy...@gm...> - 2007-06-13 17:11:34
|
> How can I see the current revision on Gumstix? Is there a way ? cat /etc/gumstix-release -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Demetris Z. <fgc...@cy...> - 2007-06-13 17:12:54
|
Tnx Dave -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dave Hylands Sent: Wednesday, June 13, 2007 8:12 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] See Revision > How can I see the current revision on Gumstix? Is there a way ? cat /etc/gumstix-release -- 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 gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Demetris Z. <fgc...@cy...> - 2007-06-13 18:06:15
|
Is ttyS1 the BT UART ? |
From: Dave H. <dhy...@gm...> - 2007-06-13 18:10:34
|
> Is ttyS1 the BT UART ? The mapping is printed on the console every time you boot. pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Demetris Z. <fgc...@cy...> - 2007-06-13 16:58:00
|
How can I see the revision of the buildroot that I have on my gumstix ? |
From: Dave C. <gu...@mo...> - 2007-08-06 02:50:35
|
Following up on the subject of a post (below) from a couple of months ago: I have a new potential application for a Verdex, but for this application getting the boot time down into the five or six second range is going to be critical for going into field testing and production. I've tried to read up on this subject in the archives and wiki as well as I could, but I still have a couple of questions that maybe somebody can address briefly: 1) Rob, of the original post below, if you are seeing this, were you able to get your Conex boot time into the 3-5 second range as you had hoped? 2) Is there anything new in the architecture or firmware for the Verdex, that potentially allows it to boot faster than the previous PXA255 gumstix? 3) If anybody else has had experience with optimizing the boot time of a gumstix, I'd very much appreciate hearing what you were able to achieve; it'd be a great help to me if I could shorten my trial-and-error learning curve by drawing on some other people's prior experiences here. Thanks much-- --Dave C. At 02:14 PM 6/6/2007, you wrote: >>> I know this has been covered to some extent previously, but here >>> goes ... >>> My issue is with the boot speed of a connex 400XM, it has U-boot >>> 1.1.4 >>> (shipped version) buildroot ver 1424 (was shipped with1161) >>> From boot I have a 2 sec U-boot interrupt window (press any key ..), >>> 18 sec JFFS2 scan, and 8 sec linux boot >>> I'm looking for time savings in any of these areas. I have seen the >>> posts describing loading the uImage from a separate flash >>> partition and >>> will try this >>> are there any other things I should be doing, and is a 3 to 5 sec >>> boot >>> time really achievable? >> >> Loading uImage from a seperate partition replaces the 18 second JFFS2 >> scan with a much smaller (1-2 second) load of the kernel. >> >> A big part of the 8 second time is still scanning JFFS2 when it >> mounts. Replacing that with a read-only file system like cramfs will >> further reduce the boot time, and perhaps having a small wirtable >> partition for storing stuff that really changes. > >...and depending on what you mean by "boot time", mounting the rw >partition only after you start everything else up (ie re-order the >stuff in /etc/inittab maybe) might get you to a login prompt before >the system "waits" to mount the rw filesystem. Note the JFFS2 will >take a while to mount even when read-only, since the scan is building >up an in-RAM list of all the valid inodes, since stuff later in the >FS image can "overrule" stuff that's physically earlier. |