From: Scott L. <sml...@gm...> - 2008-05-06 14:13:44
|
On Fri, May 2, 2008 at 10:27 AM, Scott Lerman <sml...@gm...> wrote: > > > I think your board has u-boot 1.1.4 instead of the newer 1.2 on it. You need > > to update the u-boot to 1.2 which will then be compatible with the seperate > > kernel and roofs images that get created by the OE bitbake process. > > > > In 1.1.4 the kernel and rootfs we both contained in a single image. > > > > Marc > > > > > -----Original Message----- > > > From: gum...@li... [mailto:gumstix-users- > > > bo...@li...] On Behalf Of Scott Lerman > > > Sent: Thursday, May 01, 2008 12:33 PM > > > To: gum...@li... > > > Subject: [Gumstix-users] OS version on Netstix 400xm-cf > > > > > > Not sure if this made it through the first time. Sorry if this is a > > > duplicate mail. > > > > > > I just got my first Netstix 400xm-cf to test out (with the goal of > > > getting Python running on it), but I'm having some trouble figuring > > > out what guide to go by. The gumstix.com info page says that it comes > > > with OpenEmbedded, so I'm following > > > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > > > a-Linux-login-session/111.html > > > to flash a new image over ssh. A couple of the steps don't match > > > what's on the Netstix though. The guide has: > > > > > > $ cat /proc/mtd > > > dev: size erasesize name > > > mtd0: 00040000 00020000 "Bootloader" > > > mtd1: 00ec0000 00020000 "RootFS" > > > mtd2: 00100000 00020000 "Kernel" > > > > > > The Netstix outputs this: > > > > > > # cat /proc/mtd > > > dev: size erasesize name > > > mtd0: 00040000 00020000 "Bootloader" > > > mtd1: 00fc0000 00020000 "RootFS" > > > > > > The Netstix also doesn't have the /usr/bin/flash* executables that the > > > guide mentions. Is there any way to know for sure what the Netstix is > > > running? If it really isn't running OpenEmbedded, is there a way to > > > (and should I) put OpenEmbedded on it, or should I stick with the > > > Buildroot guides on gumstix.org? Thanks for the help. > > > > > > -- > > > Scott Lerman > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > > Don't miss this year's exciting event. There's still time to save $100. > > > Use priority code J8TL2D2. > > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/jav > > > aone > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > Is there a how-to somewhere about upgrading uBoot over SSH (assuming > it's possible)? I found the link to the image > (http://gumstix.net/feeds/u-boot/u-boot-connex-400-r1578.bin) but > don't see any information on that page about how to flash the image. I > did find the guide at > http://docwiki.gumstix.org/Replacing_the_filesystem_image#Flashing_over_SSH_.2F_ethernet > but I'm not sure if that's correct for the version I have. If those > are the correct instructions, do I need to have a new OE disk image > ready to install at the same time? > > > -- > Scott Lerman > Anyone? I'm still trying to find a how-to on upgrading uBoot over SSH on a Netstix. -- Scott Lerman |
From: Stafford W. <sta...@gm...> - 2008-05-06 23:51:17
|
> Anyone? I'm still trying to find a how-to on upgrading uBoot over SSH > on a Netstix. > Scott, The instructions on http://docwiki.gumstix.org/Replacing_the_filesystem_image regarding Flashing over SSH /Ethernet are for the earlier versions of buildroot where linux still prescribed that the kernel was located on the same partition as the filesystem. This has since changed, and you will notice further down the page there are instructions on how to build the root-filesystem (under U-Boot version). Also, note that under the Flashing over SSH / Ethernet for buildroot, the section with a small bold title called "A small but very important note". If you do not perform that step, after reboot your 'stix will not boot, hence denying any further access over SSH. If after flashing for any reason you can't boot: no Ethernet. If you are able to update u-boot to the latest version, and use later filesystems for either buildroot or OE, then the OE instructions for flashing over Ethernet (http://www.gumstix.net/Documentation/view/Developer-how-to-s/Reflashing-fro m-a-linux-login-session/109.html) will work for both builds. I assume that this could be done over Ethernet, however it would require some manual un/re-mounting at flash time to allow for the separate filesystem/kernel partitions, of which are beyond my capabilities. Finally, if you are building your own (even default) latest buildroot or OE images for a connex board, you will probably lose Ethernet after boot. I have had to add a script which resets the smc91x (ethernet module) to the boot sequence for ethernet access. Moral of the story: Use serial until you get 100% working images. Cheers, Stafford. |
From: Scott L. <sml...@gm...> - 2008-05-07 00:48:21
|
On Tue, May 6, 2008 at 7:51 PM, Stafford Williams <sta...@gm...> wrote: > > > Anyone? I'm still trying to find a how-to on upgrading uBoot over SSH > > on a Netstix. > > > > Scott, > > The instructions on > http://docwiki.gumstix.org/Replacing_the_filesystem_image regarding Flashing > over SSH /Ethernet are for the earlier versions of buildroot where linux > still prescribed that the kernel was located on the same partition as the > filesystem. This has since changed, and you will notice further down the > page there are instructions on how to build the root-filesystem (under > U-Boot version). > > Also, note that under the Flashing over SSH / Ethernet for buildroot, the > section with a small bold title called "A small but very important note". > If you do not perform that step, after reboot your 'stix will not boot, > hence denying any further access over SSH. If after flashing for any reason > you can't boot: no Ethernet. > > If you are able to update u-boot to the latest version, and use later > filesystems for either buildroot or OE, then the OE instructions for > flashing over Ethernet > (http://www.gumstix.net/Documentation/view/Developer-how-to-s/Reflashing-fro > m-a-linux-login-session/109.html) will work for both builds. I assume that > this could be done over Ethernet, however it would require some manual > un/re-mounting at flash time to allow for the separate filesystem/kernel > partitions, of which are beyond my capabilities. > > Finally, if you are building your own (even default) latest buildroot or OE > images for a connex board, you will probably lose Ethernet after boot. I > have had to add a script which resets the smc91x (ethernet module) to the > boot sequence for ethernet access. > > Moral of the story: Use serial until you get 100% working images. > > Cheers, > Stafford. > > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > I'm not sure if the Netstix has a serial port on it. The only ports I remember having (I don't have it in front of me right now) are Ethernet and CompactFlash. The Netstix is supposed to be using OpenEmbedded, and I think that's going to work better for what I'm trying to do. Will the section on reflashing u-boot at the bottom of http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using-a-Linux-login-session/111.html work for what I have now? If so, is this the process I should be going through: - Download the u-boot image from http://gumstix.net/feeds/u-boot/u-boot-connex-400-r1578.bin - Store the u-boot image at /tmp/uboot.bin - Follow the last section from http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using-a-Linux-login-session/111.html to reflash u-boot - Reboot - Follow the rest of the guide to update the kernel and root filesystem Is that going to work, or is there some other guide I should be following? -- Scott Lerman |
From: Stafford W. <sta...@gm...> - 2008-05-07 01:13:19
|
> I'm not sure if the Netstix has a serial port on it. The only ports I > remember having (I don't have it in front of me right now) are > Ethernet and CompactFlash. > > The Netstix is supposed to be using OpenEmbedded, and I think that's > going to work better for what I'm trying to do. Will the section on > reflashing u-boot at the bottom of > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > a-Linux-login-session/111.html > work for what I have now? If so, is this the process I should be going > through: > > - Download the u-boot image from > http://gumstix.net/feeds/u-boot/u-boot-connex-400-r1578.bin > - Store the u-boot image at /tmp/uboot.bin > - Follow the last section from > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > a-Linux-login-session/111.html > to reflash u-boot > - Reboot > - Follow the rest of the guide to update the kernel and root filesystem > > Is that going to work, or is there some other guide I should be following? > > -- > Scott Lerman You can determine if you are running OE by running "cat /etc/gumstix-version". Mine says this: Revision 315M Built on Wed Apr 30 22:39:54 NZST 2008 Build machine: debianbox Target machine: gumstix-custom-connex libc: glibc I think that your method to flash will fail, due to the fact that u-boot 1.2.0 will probably expect the kernel to be in a separate partition so you will not boot after updating u-boot, and hence not have an Ethernet option to continue flashing the filesystem/kernel. The netstix does not have a serial port, you need something like the console-st board ($US20). I highly recommend this board, I lost Ethernet multiple times during my first flash adventures. Stafford. |
From: Scott L. <sml...@gm...> - 2008-05-07 13:23:35
|
On Tue, May 6, 2008 at 9:13 PM, Stafford Williams <sta...@gm...> wrote: > > I'm not sure if the Netstix has a serial port on it. The only ports I > > remember having (I don't have it in front of me right now) are > > Ethernet and CompactFlash. > > > > The Netstix is supposed to be using OpenEmbedded, and I think that's > > going to work better for what I'm trying to do. Will the section on > > reflashing u-boot at the bottom of > > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > > a-Linux-login-session/111.html > > work for what I have now? If so, is this the process I should be going > > through: > > > > - Download the u-boot image from > > http://gumstix.net/feeds/u-boot/u-boot-connex-400-r1578.bin > > - Store the u-boot image at /tmp/uboot.bin > > - Follow the last section from > > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > > a-Linux-login-session/111.html > > to reflash u-boot > > - Reboot > > - Follow the rest of the guide to update the kernel and root filesystem > > > > Is that going to work, or is there some other guide I should be following? > > > > -- > > Scott Lerman > > You can determine if you are running OE by running "cat > /etc/gumstix-version". Mine says this: > > Revision 315M > Built on Wed Apr 30 22:39:54 NZST 2008 > Build machine: debianbox > Target machine: gumstix-custom-connex > libc: glibc > > I think that your method to flash will fail, due to the fact that u-boot > 1.2.0 will probably expect the kernel to be in a separate partition so you > will not boot after updating u-boot, and hence not have an Ethernet option > to continue flashing the filesystem/kernel. > > The netstix does not have a serial port, you need something like the > console-st board ($US20). I highly recommend this board, I lost Ethernet > multiple times during my first flash adventures. > > > > Stafford. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > There is no /etc/gumstix-version file. There is /etc/gumstix-release, which contains: DISTRIB_ID='gumstix' DISTRIB_DESCRIPTION='' DISTRIB_RELEASE='1161' DISTRIB_CODENAME='' BUILD_DATE='Mon Nov 6 11:20:28 PST 2006' BUILD_HOSTNAME='azazel.hughes-family.org' The release number looks like it's in the range of the revision numbers I've seen in the buildroot docs. Am I right that this isn't actually running OpenEmbedded? Is OpenEmbedded generally considered "better" than using buildroot (my goal is to be running some Python code on the device). -- Scott Lerman |
From: Scott L. <sml...@gm...> - 2008-05-07 13:30:29
|
On Tue, May 6, 2008 at 9:13 PM, Stafford Williams <sta...@gm...> wrote: > > I'm not sure if the Netstix has a serial port on it. The only ports I > > remember having (I don't have it in front of me right now) are > > Ethernet and CompactFlash. > > > > The Netstix is supposed to be using OpenEmbedded, and I think that's > > going to work better for what I'm trying to do. Will the section on > > reflashing u-boot at the bottom of > > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > > a-Linux-login-session/111.html > > work for what I have now? If so, is this the process I should be going > > through: > > > > - Download the u-boot image from > > http://gumstix.net/feeds/u-boot/u-boot-connex-400-r1578.bin > > - Store the u-boot image at /tmp/uboot.bin > > - Follow the last section from > > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > > a-Linux-login-session/111.html > > to reflash u-boot > > - Reboot > > - Follow the rest of the guide to update the kernel and root filesystem > > > > Is that going to work, or is there some other guide I should be following? > > > > -- > > Scott Lerman > > You can determine if you are running OE by running "cat > /etc/gumstix-version". Mine says this: > > Revision 315M > Built on Wed Apr 30 22:39:54 NZST 2008 > Build machine: debianbox > Target machine: gumstix-custom-connex > libc: glibc > > I think that your method to flash will fail, due to the fact that u-boot > 1.2.0 will probably expect the kernel to be in a separate partition so you > will not boot after updating u-boot, and hence not have an Ethernet option > to continue flashing the filesystem/kernel. > > The netstix does not have a serial port, you need something like the > console-st board ($US20). I highly recommend this board, I lost Ethernet > multiple times during my first flash adventures. > > > > Stafford. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > There is no /etc/gumstix-version file. There is /etc/gumstix-release, which contains: DISTRIB_ID='gumstix' DISTRIB_DESCRIPTION='' DISTRIB_RELEASE='1161' DISTRIB_CODENAME='' BUILD_DATE='Mon Nov 6 11:20:28 PST 2006' BUILD_HOSTNAME='azazel.hughes-family.org' The release number looks like it's in the range of the revision numbers I've seen in the buildroot docs. Am I right that this isn't actually running OpenEmbedded? Is OpenEmbedded generally considered "better" than using buildroot (my goal is to be running some Python code on the device). As a follow-up (and potential alternative), is there a way to skip reflashing the onboard memory and instead have it boot from a CompactFlash card? I'm planning on using a fairly large number of these that will all be doing the same thing, so being able to put everything on CF cards that can I quickly plug in (and replace as needed) would help a lot. -- Scott Lerman |
From: Stafford W. <sta...@gm...> - 2008-05-08 00:47:27
|
> There is no /etc/gumstix-version file. There is /etc/gumstix-release, > which contains: > > DISTRIB_ID='gumstix' > DISTRIB_DESCRIPTION='' > DISTRIB_RELEASE='1161' > DISTRIB_CODENAME='' > BUILD_DATE='Mon Nov 6 11:20:28 PST 2006' > BUILD_HOSTNAME='azazel.hughes-family.org' > > The release number looks like it's in the range of the revision > numbers I've seen in the buildroot docs. Am I right that this isn't > actually running OpenEmbedded? Is OpenEmbedded generally considered > "better" than using buildroot (my goal is to be running some Python > code on the device). > > As a follow-up (and potential alternative), is there a way to skip > reflashing the onboard memory and instead have it boot from a > CompactFlash card? I'm planning on using a fairly large number of > these that will all be doing the same thing, so being able to put > everything on CF cards that can I quickly plug in (and replace as > needed) would help a lot. > > -- > Scott Lerman Yes, you are running buildroot. One of the main differences is that OE use of ipkg allows you to update the packages running on your 'stix without having to reflash. If you check here http://gumstix.net/feeds/archive/315M/glibc/ipk/armv5te/ you can see there are multiple pre-compiled packages for python (for use with OE). The advantage here, is that you could install one or two packages, see if your code is running, and add/remove more as you go without reflashing. I have never boot from CF, but it is possible, the buildroot instructions for this are located here: http://docwiki.gumstix.org/index.php/Root_filesystems Stafford. |
From: Scott L. <sml...@gm...> - 2008-05-08 01:05:08
|
On Wed, May 7, 2008 at 8:48 PM, Stafford Williams <sta...@gm...> wrote: > > There is no /etc/gumstix-version file. There is /etc/gumstix-release, > > which contains: > > > > DISTRIB_ID='gumstix' > > DISTRIB_DESCRIPTION='' > > DISTRIB_RELEASE='1161' > > DISTRIB_CODENAME='' > > BUILD_DATE='Mon Nov 6 11:20:28 PST 2006' > > BUILD_HOSTNAME='azazel.hughes-family.org' > > > > The release number looks like it's in the range of the revision > > numbers I've seen in the buildroot docs. Am I right that this isn't > > actually running OpenEmbedded? Is OpenEmbedded generally considered > > "better" than using buildroot (my goal is to be running some Python > > code on the device). > > > > As a follow-up (and potential alternative), is there a way to skip > > reflashing the onboard memory and instead have it boot from a > > CompactFlash card? I'm planning on using a fairly large number of > > these that will all be doing the same thing, so being able to put > > everything on CF cards that can I quickly plug in (and replace as > > needed) would help a lot. > > > > -- > > Scott Lerman > > Yes, you are running buildroot. One of the main differences is that OE use > of ipkg allows you to update the packages running on your 'stix without > having to reflash. If you check here > http://gumstix.net/feeds/archive/315M/glibc/ipk/armv5te/ you can see there > are multiple pre-compiled packages for python (for use with OE). The > advantage here, is that you could install one or two packages, see if your > code is running, and add/remove more as you go without reflashing. > > I have never boot from CF, but it is possible, the buildroot instructions > for this are located here: > http://docwiki.gumstix.org/index.php/Root_filesystems > > > > Stafford. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > Looks like OE will be easier to work with than buildroot; I have a fair amount of Linux experience, but I've never really done anything with this type of hardware. Setting up Gumstix devices won't be my primary task, or setting them up will be done by someone else, so the easiest OS would be best. Is there any sane way to put OE on the device I have, or should I call Gumstix and find out if they can send me one that has OE on it? -- Scott Lerman |
From: Stafford W. <sta...@gm...> - 2008-05-11 23:13:04
|
> > Looks like OE will be easier to work with than buildroot; I have a > fair amount of Linux experience, but I've never really done anything > with this type of hardware. Setting up Gumstix devices won't be my > primary task, or setting them up will be done by someone else, so the > easiest OS would be best. Is there any sane way to put OE on the > device I have, or should I call Gumstix and find out if they can send > me one that has OE on it? > > -- > Scott Lerman > Yeah, get a console-st and flash it. Flashing is easy as after the first few times. Stafford. |
From: Scott L. <sml...@gm...> - 2008-05-11 23:59:39
|
On Sun, May 11, 2008 at 7:14 PM, Stafford Williams <sta...@gm...> wrote: > >> >> Looks like OE will be easier to work with than buildroot; I have a >> fair amount of Linux experience, but I've never really done anything >> with this type of hardware. Setting up Gumstix devices won't be my >> primary task, or setting them up will be done by someone else, so the >> easiest OS would be best. Is there any sane way to put OE on the >> device I have, or should I call Gumstix and find out if they can send >> me one that has OE on it? >> >> -- >> Scott Lerman >> > > Yeah, get a console-st and flash it. Flashing is easy as after the first > few times. > > Stafford. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > Except there doesn't seem to be any way to replace buildroot with OE, since they use different partitioning schemes. Unless you know of instructions somewhere to do it, I'll get a replacement. I don't have the time to spend several more days making no progress. -- Scott Lerman |
From: Stafford W. <sta...@gm...> - 2008-05-12 02:53:01
|
> > > > Except there doesn't seem to be any way to replace buildroot with OE, > since they use different partitioning schemes. Unless you know of > instructions somewhere to do it, I'll get a replacement. I don't have > the time to spend several more days making no progress. > Following the serial flashing instructions for OE will update your 'stix to OE. The replacing of u-Boot and the filesystem is done in the bootloader ,when using serial, so the fact that partitions are now how they should be before you start is irrelevant for they never get mounted. I'm not sure if they ship 'stix with OE, I just got two netstix-400 delivered today, and they have buildroot. I am going to change them over to OE (also hopefully today), so I'll try the docs as they are currently written. Stafford. |
From: Stafford W. <sta...@gm...> - 2008-05-12 21:41:29
|
> > Except there doesn't seem to be any way to replace buildroot with OE, > since they use different partitioning schemes. Unless you know of > instructions somewhere to do it, I'll get a replacement. I don't have > the time to spend several more days making no progress. > So yeah, I flashed my netstix-400s from buildroot to oe. Actually just one of them, because I bricked the first one. Never-the-less, the one that was successful took about 25mins from start to finish. =D Stafford. |
From: Scott L. <sml...@gm...> - 2008-05-07 01:26:41
|
On Tue, May 6, 2008 at 9:13 PM, Stafford Williams <sta...@gm...> wrote: > > I'm not sure if the Netstix has a serial port on it. The only ports I > > remember having (I don't have it in front of me right now) are > > Ethernet and CompactFlash. > > > > The Netstix is supposed to be using OpenEmbedded, and I think that's > > going to work better for what I'm trying to do. Will the section on > > reflashing u-boot at the bottom of > > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > > a-Linux-login-session/111.html > > work for what I have now? If so, is this the process I should be going > > through: > > > > - Download the u-boot image from > > http://gumstix.net/feeds/u-boot/u-boot-connex-400-r1578.bin > > - Store the u-boot image at /tmp/uboot.bin > > - Follow the last section from > > http://www.gumstix.net/Software/view/Developer-how-to-s/Reflashing-using- > > a-Linux-login-session/111.html > > to reflash u-boot > > - Reboot > > - Follow the rest of the guide to update the kernel and root filesystem > > > > Is that going to work, or is there some other guide I should be following? > > > > -- > > Scott Lerman > > You can determine if you are running OE by running "cat > /etc/gumstix-version". Mine says this: > > Revision 315M > Built on Wed Apr 30 22:39:54 NZST 2008 > Build machine: debianbox > Target machine: gumstix-custom-connex > libc: glibc > > I think that your method to flash will fail, due to the fact that u-boot > 1.2.0 will probably expect the kernel to be in a separate partition so you > will not boot after updating u-boot, and hence not have an Ethernet option > to continue flashing the filesystem/kernel. > > The netstix does not have a serial port, you need something like the > console-st board ($US20). I highly recommend this board, I lost Ethernet > multiple times during my first flash adventures. > > > > Stafford. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > I'll check /etc/gumstix-version in the morning. If I can't upgrade u-boot because it expects different partitioning, and I can't upgrade the rest of the system because I need a newer version of u-boot, am I just stuck? I don't remember if anything like parted was on there to create a new partition for the kernel. -- Scott Lerman |
From: Chris D. <chr...@gm...> - 2008-05-07 03:18:32
|
> I'll check /etc/gumstix-version in the morning. If I can't upgrade > u-boot because it expects different partitioning, and I can't upgrade > the rest of the system because I need a newer version of u-boot, am I > just stuck? There's always the option of buying a console board or tweener (and serial null-modem cable) and reflashing u-boot that way. Or you can check the mailing list archives - I remember a post from Dave Hylands that listed the patches that needed to be removed/changed to build a monolithic filesyste+kernel. I think those instructions where for buildroot, but you could do the same with OE if you know your way around it. My 2 cents - get a console board ;) > I don't remember if anything like parted was on there to > create a new partition for the kernel. I've not heard of any partitioning tool for flash... in fact I think the partition mapping is compiled into the kernel (but of course I could be wrong). Assuming that the partitioning IS written into the kernel, I see no way to upgrade to the newer u-boot via network since you'd have to boot that new kernel with the new flash partition map to see the 'newer style' partition layout. IIRC you really don't need to upgrade u-boot to use the newer split kernel and rootfs setup, all you have to do is change u-boot's bootargs so that it knows where to find the kernel (the 'root=...' part I think). I think the big advantage to 1.2.0 is you get the katinstall/katload commands (again, its been a while since I've run 1.1.2, and I could be wrong). That being said, I still don't think you can flash a separate rootfs and kernel in your case since the flashcp command relies on the mtd partitions to do its thing, and the 'older' layout isn't ready for the split setup. Chris |