Kernel generates vmImage instead of zImage

Kernel generates vmImage instead of zImage

[Onur Cem Çelebi]

Hi all,

I want to run my DE2-115 board for NIOSII processor with uClinux but
stucked on somewhere. After i compiled the kernel, I got this message.

Image Name:   Linux-3.7.0-01377-g1061bd7
Created:      Mon Mar 25 15:41:30 2013
Image Type:   NIOS II Linux Kernel Image (gzip compressed)
Data Size:    1445018 Bytes = 1411.15 kB = 1.38 MB
Load Address: c8000000
Entry Point:  c8000000
*Kernel: arch/nios2/boot/vmImage is ready*


How to obtain zImage ? Am i missing something ? Any help is greatly
appreciated.


Cem Celebi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130403/afeb5555/attachment.html 

Kernel generates vmImage instead of zImage

[Mulyadi Santosa]

Hi.... :)

On Wed, Apr 3, 2013 at 4:17 PM, Onur Cem ?elebi <occelebi@gmail.com> wrote:
> Image Name:   Linux-3.7.0-01377-g1061bd7
> Created:      Mon Mar 25 15:41:30 2013
> Image Type:   NIOS II Linux Kernel Image (gzip compressed)
> Data Size:    1445018 Bytes = 1411.15 kB = 1.38 MB
> Load Address: c8000000
> Entry Point:  c8000000
> Kernel: arch/nios2/boot/vmImage is ready
>
>
> How to obtain zImage ? Am i missing something ? Any help is greatly
> appreciated.

Can you explain how did you compile that kernel image?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

Kernel generates vmImage instead of zImage

[Onur Cem Çelebi]

After i have configured kernel with "make menuconfig", then i fired "make"
command into terminal. I have seen such a video in which somebody did the
same as me but he is able to get zImage. In my case, no luck !


2013/4/4 Mulyadi Santosa <mulyadi.santosa@gmail.com>

> Hi.... :)
>
> On Wed, Apr 3, 2013 at 4:17 PM, Onur Cem ?elebi <occelebi@gmail.com>
> wrote:
> > Image Name:   Linux-3.7.0-01377-g1061bd7
> > Created:      Mon Mar 25 15:41:30 2013
> > Image Type:   NIOS II Linux Kernel Image (gzip compressed)
> > Data Size:    1445018 Bytes = 1411.15 kB = 1.38 MB
> > Load Address: c8000000
> > Entry Point:  c8000000
> > Kernel: arch/nios2/boot/vmImage is ready
> >
> >
> > How to obtain zImage ? Am i missing something ? Any help is greatly
> > appreciated.
>
> Can you explain how did you compile that kernel image?
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130404/fcbade66/attachment.html 

Kernel generates vmImage instead of zImage

[Christophe Aeschlimann]

Hi,

Le 04.04.2013 10:36, Onur Cem ?elebi a ?crit :
> After i have configured kernel with "make menuconfig", then i fired
> "make" command into terminal. I have seen such a video in which somebody
> did the same as me but he is able to get zImage. In my case, no luck !

Did you try :

make zImage


-- 
Christophe Aeschlimann

Embedded Software Engineer & IT Manager
ACN Advanced Communications Networks S.A.
2000 - Neuch?tel, Switzerland
Tel. +41 32 724 74 31

Kernel generates vmImage instead of zImage

[Onur Cem Çelebi]

Output is:

root at F15:~/ruclinux/uClinux-dist# make zImage
make: *** No rule to make target `zImage'.  Stop.


2013/4/4 Christophe Aeschlimann <c.aeschlimann@acn-group.ch>

> Hi,
>
> Le 04.04.2013 10:36, Onur Cem ?elebi a ?crit :
> > After i have configured kernel with "make menuconfig", then i fired
> > "make" command into terminal. I have seen such a video in which somebody
> > did the same as me but he is able to get zImage. In my case, no luck !
>
> Did you try :
>
> make zImage
>
>
> --
> Christophe Aeschlimann
>
> Embedded Software Engineer & IT Manager
> ACN Advanced Communications Networks S.A.
> 2000 - Neuch?tel, Switzerland
> Tel. +41 32 724 74 31
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130404/9113290a/attachment.html 

Kernel generates vmImage instead of zImage

[Augusto Mecking Caringi]

On Thu, Apr 4, 2013 at 7:02 AM, Onur Cem ?elebi <occelebi@gmail.com> wrote:
>
> Output is:
>
> root at F15:~/ruclinux/uClinux-dist# make zImage
> make: *** No rule to make target `zImage'.  Stop.

Maybe, this is the answer:

"Though zImage is a valid Makefile target for all the architectures we
discussed in depth in Chapter 3, there are other Linux architectures
for which it isn't valid."

http://books.google.com.br/books?id=xnFdWfJAK9wC&pg=PT188&lpg=PT188&dq=zImage+is+a+valid+Makefile+target+for+all+the+architectures+we+discussed+in&source=bl&ots=GFTLM7_665&sig=77Oi5e_TmkXME_5du3H5GdqPw4c&hl=pt-BR&sa=X&ei=xZ5dUeqqIY3x0wH4x4D4Cw&ved=0CD0Q6AEwAQ#v=onepage&q&f=false

--
Augusto Mecking Caringi

Kernel generates vmImage instead of zImage

[Robert P. J. Day]

On Thu, 4 Apr 2013, Augusto Mecking Caringi wrote:

> On Thu, Apr 4, 2013 at 7:02 AM, Onur Cem ?elebi <occelebi@gmail.com> wrote:
> >
> > Output is:
> >
> > root at F15:~/ruclinux/uClinux-dist# make zImage
> > make: *** No rule to make target `zImage'.  Stop.
>
> Maybe, this is the answer:
>
> "Though zImage is a valid Makefile target for all the architectures we
> discussed in depth in Chapter 3, there are other Linux architectures
> for which it isn't valid."
>
> http://books.google.com.br/books?id=xnFdWfJAK9wC&pg=PT188&lpg=PT188&dq=zImage+is+a+valid+Makefile+target+for+all+the+architectures+we+discussed+in&source=bl&ots=GFTLM7_665&sig=77Oi5e_TmkXME_5du3H5GdqPw4c&hl=pt-BR&sa=X&ei=xZ5dUeqqIY3x0wH4x4D4Cw&ved=0CD0Q6AEwAQ#v=onepage&q&f=false

  the set of buildable targets is typically defined by the
arch-specific makefile.  if you look in the top-level Makefile of the
kernel source tree, you'll see a target for building the generic
"vmlinux" kernel image, but little more.

  you need to dig down into the arch-specific directory to see
additional targets.  for example, if you take a look at
arch/arm/boot/Makefile, you'll see:

targets := Image zImage xipImage bootpImage uImage

ifeq ($(CONFIG_XIP_KERNEL),y)

$(obj)/xipImage: vmlinux FORCE
        $(call if_changed,objcopy)
        @$(kecho) '  Kernel: $@ is ready (physical address:
$(CONFIG_XIP_PHYS_ADDR))'

$(obj)/Image $(obj)/zImage: FORCE
        @echo 'Kernel configured for XIP (CONFIG_XIP_KERNEL=y)'
        @echo 'Only the xipImage target is available in this case'
        @false

else

$(obj)/xipImage: FORCE
        @echo 'Kernel not configured for XIP (CONFIG_XIP_KERNEL!=y)'
        @false
... etc etc ...

  in short, all(?) architectures expect a starting point of a vmlinux,
and they will define additional targets as they see fit.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Kernel generates vmImage instead of zImage

[Onur Cem Çelebi]

Thanks to all but my special thanks go to Robert. I've edited
linux-2.6/arch/nios2/Makefile and get it work !

Cheers,
Cem


2013/4/4 Robert P. J. Day <rpjday@crashcourse.ca>

> On Thu, 4 Apr 2013, Augusto Mecking Caringi wrote:
>
> > On Thu, Apr 4, 2013 at 7:02 AM, Onur Cem ?elebi <occelebi@gmail.com>
> wrote:
> > >
> > > Output is:
> > >
> > > root at F15:~/ruclinux/uClinux-dist# make zImage
> > > make: *** No rule to make target `zImage'.  Stop.
> >
> > Maybe, this is the answer:
> >
> > "Though zImage is a valid Makefile target for all the architectures we
> > discussed in depth in Chapter 3, there are other Linux architectures
> > for which it isn't valid."
> >
> >
> http://books.google.com.br/books?id=xnFdWfJAK9wC&pg=PT188&lpg=PT188&dq=zImage+is+a+valid+Makefile+target+for+all+the+architectures+we+discussed+in&source=bl&ots=GFTLM7_665&sig=77Oi5e_TmkXME_5du3H5GdqPw4c&hl=pt-BR&sa=X&ei=xZ5dUeqqIY3x0wH4x4D4Cw&ved=0CD0Q6AEwAQ#v=onepage&q&f=false
>
>   the set of buildable targets is typically defined by the
> arch-specific makefile.  if you look in the top-level Makefile of the
> kernel source tree, you'll see a target for building the generic
> "vmlinux" kernel image, but little more.
>
>   you need to dig down into the arch-specific directory to see
> additional targets.  for example, if you take a look at
> arch/arm/boot/Makefile, you'll see:
>
> targets := Image zImage xipImage bootpImage uImage
>
> ifeq ($(CONFIG_XIP_KERNEL),y)
>
> $(obj)/xipImage: vmlinux FORCE
>         $(call if_changed,objcopy)
>         @$(kecho) '  Kernel: $@ is ready (physical address:
> $(CONFIG_XIP_PHYS_ADDR))'
>
> $(obj)/Image $(obj)/zImage: FORCE
>         @echo 'Kernel configured for XIP (CONFIG_XIP_KERNEL=y)'
>         @echo 'Only the xipImage target is available in this case'
>         @false
>
> else
>
> $(obj)/xipImage: FORCE
>         @echo 'Kernel not configured for XIP (CONFIG_XIP_KERNEL!=y)'
>         @false
> ... etc etc ...
>
>   in short, all(?) architectures expect a starting point of a vmlinux,
> and they will define additional targets as they see fit.
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
>
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130409/7c0d8431/attachment.html 

Kernel generates vmImage instead of zImage

[Onur Cem Çelebi]

In addition, it could be useful to examine the whole output of compilation
I've attacted.


2013/4/4 Onur Cem ?elebi <occelebi@gmail.com>

> After i have configured kernel with "make menuconfig", then i fired "make"
> command into terminal. I have seen such a video in which somebody did the
> same as me but he is able to get zImage. In my case, no luck !
>
>
> 2013/4/4 Mulyadi Santosa <mulyadi.santosa@gmail.com>
>
>> Hi.... :)
>>
>> On Wed, Apr 3, 2013 at 4:17 PM, Onur Cem ?elebi <occelebi@gmail.com>
>> wrote:
>> > Image Name:   Linux-3.7.0-01377-g1061bd7
>> > Created:      Mon Mar 25 15:41:30 2013
>> > Image Type:   NIOS II Linux Kernel Image (gzip compressed)
>> > Data Size:    1445018 Bytes = 1411.15 kB = 1.38 MB
>> > Load Address: c8000000
>> > Entry Point:  c8000000
>> > Kernel: arch/nios2/boot/vmImage is ready
>> >
>> >
>> > How to obtain zImage ? Am i missing something ? Any help is greatly
>> > appreciated.
>>
>> Can you explain how did you compile that kernel image?
>>
>> --
>> regards,
>>
>> Mulyadi Santosa
>> Freelance Linux trainer and consultant
>>
>> blog: the-hydra.blogspot.com
>> training: mulyaditraining.blogspot.com
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130404/f1ea6590/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: outputofmake
Type: application/octet-stream
Size: 18261 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130404/f1ea6590/attachment-0001.obj