Hi Charles.
____________
 
Is it possible to tell me the options step by step, with rigorous commands in directories like in a doc?
____________________________________________________________________________________
 
My directories are:
_________________
 
1*) mike/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.31-r51/git/arch/arm/omap2/board-overo.c
 
(in board-overo.c I change code in order to declare controller 1 for OMAP 3530 master, chip select 0,
___________________________________________________________________________________
 
SPI pins for OMAP 3530, and declare 1278 to be slave on the SPI bus)
___________________________________________________________
 
 
and:
_____
 
2*) mike/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.31-r51/git/drivers/spi/omap2_mcspi.c
 
(in omap2_mcspi.c I change code in order to send "Hello" on the SPI bus; I want to see pulses on the bus)
________________________________________________________________________________________
 
After re-compiling I get uImage in:
____________________________
 
mike/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.31-r51/git/arch/arm/boot/uImage
 
 
The first compile, produced a uImage (i.e.: uImage-overo.bin), a root file system
__________________________________________________________________
 
(i.e.: omap3-console-image-overo.tar.bz2) -and also MLO and u-boot-overo.bin- in: 
____________________________________________________________________
 
mike/overo-oe/tmp/deploy/glibc/images/overo
 
I need new uImage and new root fs on the SD card to boot Gumstix and start my modified Linux.
_________________________________________________________________________________
 
Ion A. Beza
___________
 
 
On Fri, Jan 29, 2010 at 10:06 AM, Ash Charles <ashcharles@gmail.com> wrote:
Hi Tony,

I understand why you want to build a new rootfs.  Perhaps I wasn't
clear in my previous response:

For option 1, a 'bitbake minimal-image' etc., should build an
image...i.e. a rootfs.
For option 2, copying the modules file over to the gumstix modifies
the current rootfs to include the new modules -> you get the changes
to rootfs that you were looking for.

Does this explain my previous comments a bit better?

-Ash


On Thu, Jan 28, 2010 at 3:31 PM, Tony Oxendahl <toxend@gmail.com> wrote:
> Hi Charles.
> __________
>
> in response to your two options, like this one for example:
> ________________________________________________
>
> "...2) Boot up your gumstix with your old kernel and untar the new
> 'modules' file into the appropriate directory on the gumstix
> (/lib/modules/<kernel version>) and then reboot with the new kernel
> which should now have the correct modules available."
>
> I want to have on my SD card a new uImage and a new root fs,
> ____________________________________________________
>
> boot the Gumstix PALO 43 from the SD card and start my new uImage.
> _____________________________________________________________
>
> Then I test with a logic analyzer the code changes I made in uImage.
> __________________________________________________________
>
> Creating a new uImage is explained here:
> __________________________________
>
> http://blogs.elphel.com/2009/12/openembeddedangstrom-kernel-workflow/
> but creating a new root fs is not.
> __________________________
>
> If I don't create a new root fs to accompany the new uImage, uImage
> accompanied by
> _________________________________________________________________________
>
> the old root fs boots and starts the modified Linux on the SD card, then
> crashes.
> __________________________________________________________________
>
> Once I can create the new root fs, then -per www.gumstix.net "Creating a
> bootable SD card"-
> _____________________________________________________________________________
>
> I can untar the new rootfs on the SD card, and SD will boot the Gumstix.
> ____________________________________________________________
>
>
> Looking at "Installing modules" in:
> _____________________________
>
> http://bec-systems.com/site/521/best-practices-for-kernel-development-with-openembedded
>
> shows two commands for creating a new rootfs after a new uImage was created:
> __________________________________________________________________
>
> rm -rf modules_install; INSTALL_MOD_PATH=modules_install make
> modules_install
> rsync -av modules_install/lib/modules/2.6.22 root@192.168.1.115:/lib/modules
>
> but first command gets the error message:
> ____________________________________
>
> No rules to make target "modules_install". STOP
>
> Please help if you can.
> ___________________
>
> Ion A. Beza.
> ___________
>
>
>
>
>
> On Thu, Jan 28, 2010 at 12:24 PM, Ash Charles <ashcharles@gmail.com> wrote:
>>
>> Hi Tony,
>>
>> I *think* either of these approaches should work...
>> Options:
>> 1) You can do a 'bitbake minimal-image' (or whatever image you like)
>> as long as your image builds using the kernel you've been working on
>> (i.e. the kernel recipe should be the virtual/kernel) and put this
>> image on your gumstix as your rootfs as normal.
>> 2) Boot up your gumstix with your old kernel and untar the new
>> 'modules' file into the appropriate directory on the gumstix
>> (/lib/modules/<kernel version>) and then reboot with the new kernel
>> which should now have the correct modules available.
>>
>> HTH,
>>
>> -Ash
>>
>> On Thu, Jan 28, 2010 at 12:08 PM, Tony Oxendahl <toxend@gmail.com> wrote:
>> > Hi. I have a question that maybe somebody can answer, please.
>> > _____________________________________________________
>> >
>> >
>> > BACKGROUND
>> > :::::::::::::::::::::::::
>> >
>> > I change the Linux kernel by changing code and re-compiling by following
>> > the
>> > steps here:
>> >
>> > _________________________________________________________________________
>> >
>> > http://blogs.elphel.com/2009/12/openembeddedangstrom-kernel-workflow/
>> >
>> > I put the new Linux kernel (i.e.: uImage) on a SD card on a Gumstix
>> > Overo
>> > PALO43.
>> > _____________________________________________________________________
>> >
>> > The PALO 43 boots from a NAND then starts from the SD card my modified
>> > Linux.
>> > ___________________________________________________________________
>> >
>> > The modified Linux crashes. (as seen in the log file of the boot on a
>> > kermit
>> > console
>> >
>> > terminal)_____________________________________________________________________________
>> >
>> > The original Linux (i.e.: the original uImage) didn't crash.
>> > _______________________________________________
>> >
>> > The original Linux had a root file system I put on the SD card.
>> > ____________________________________________________
>> >
>> > That root file system was generated by the first compile:
>> > ________________________________________________
>> >
>> >
>> > http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html
>> >
>> > Subsequent compiles of changes that I make in the Linux kernel, are not
>> > documented in the instructions that I followed
>> >
>> > ___________________________________________________________________________________________________
>> >
>> > in order to re-compile:
>> > __________________
>> >
>> > http://blogs.elphel.com/2009/12/openembeddedangstrom-kernel-workflow/
>> > while the modified Linux needs an accompanying root file system on the
>> > SD
>> > card in order to not crash.
>> >
>> > _________________________________________________________________________________________
>> >
>> >
>> > QUESTION
>> > ::::::::::::::::::
>> >
>> > How to generate a new root file system when I generate a new uImage
>> > (i.e.: a
>> > new Linux kernel with code changes)?
>> >
>> > __________________________________________________________________________________________________
>> >
>> > (when I implement the commands:
>> > _____________________________
>> >
>> > rm -rf modules_install; INSTALL_MOD_PATH=modules_install make
>> > modules_install
>> >
>> > and:
>> > ____
>> > rsync -av modules_install/lib/modules/2.6.22
>> > root@192.168.1.115:/lib/modules
>> >
>> > from a general Open Embedded link (not tailored to bitbake):
>> > ___________________________________________________
>> >
>> >
>> > http://bec-systems.com/site/521/best-practices-for-kernel-development-with-openembedded
>> >
>> > I do get error this message:
>> > _________________________
>> >
>> > No rule to make target 'modules_install'. STOP
>> > )
>> >
>> > Please help.
>> > ___________
>> >
>> > Ion A. Beza.
>> > __________
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > The Planet: dedicated and managed hosting, cloud storage, colocation
>> > Stay online with enterprise data centers and the best network in the
>> > business
>> > Choose flexible plans and management services without long-term
>> > contracts
>> > Personal 24x7 support from experience hosting pros just a phone call
>> > away.
>> > http://p.sf.net/sfu/theplanet-com
>> > _______________________________________________
>> > gumstix-users mailing list
>> > gumstix-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
>> >
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> The Planet: dedicated and managed hosting, cloud storage, colocation
>> Stay online with enterprise data centers and the best network in the
>> business
>> Choose flexible plans and management services without long-term contracts
>> Personal 24x7 support from experience hosting pros just a phone call away.
>> http://p.sf.net/sfu/theplanet-com
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the
> business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users