mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] 'uImage-mini2440' -> '/dev/nand0.kernel.bb' No space left on device
Date: Tue, 29 Apr 2014 17:56:42 +0200	[thread overview]
Message-ID: <20140429155639.GA30590@omega> (raw)
In-Reply-To: <loom.20140429T173603-399@post.gmane.org>

Hi Stella,

On Tue, Apr 29, 2014 at 03:43:15PM +0000, Stella GZ wrote:
> Hello,
> 
> I'm working with the following configuration:
> OSELAS.Toolchain-2013.12.1
> ptxdist-2014.04.0
> OSELAS.BSP-Pengutronix-Mini2440-HEAD-ada838e
> 
> I can create the kernel and filesystem images correctly, but when I try to
> update my mini2440 (update -t kernel -d nand), I get the following error:  
>                                                                           
> erasing partition /dev/nand0.kernel.bb                               
>              
> flashing uImage-mini2440 to /dev/nand0.kernel.bb                                
>                                                                            
> TFTP from server 192.168.0.136 ('uImage-mini2440' -> '/dev/nand0.kernel.bb')    
>         #################################################################  
>        #################################################################   
>        #################################################################   
>        #################################################################   
>        #################################################################   
>       #################################################################    
>      ###################write: No space left on device                     
>                                                                            
>

I would say it seems that your /dev/nand0.kernel.bb is not big enough
for the kernel image, so the kernel doesn't fit in.

You have two choices:

1)
   Make the kernel smaller. This is more complicated and you should know
   what you doing there. In ptxdist kernelconfig disable some feature or
   compile with -Os.

2)
   Make the /dev/nand0.kernel partition bigger, which should much
   easier to be done. I suppose you have a barebox with a defaultenv in
   version one (You use the update script there).
   In the barebox shell type 'edit /env/config' and search for the part:

   nand_parts="256k(barebox)ro,128k(bareboxenv),3M(kernel),-(root)"

   In this example the kernel partition is 3M which stands for megabyte
   big. Try to increase your partition and reflash kernel and rootfs.
   You need to that afterwards because the kernel partition fill be
   overlapped with the root partition, so be sure you saved everything
   from the rootfs before you do that.

   One notice about the edit command, you can save it with "Ctrl-D" and
   type "saveenv" afterwards. Then reset the board.

- Alex

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-04-29 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 15:43 Stella GZ
2014-04-29 15:56 ` Alexander Aring [this message]
2014-04-30  7:15 ` Juergen Borleis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140429155639.GA30590@omega \
    --to=alex.aring@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox