mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: oselas@community.pengutronix.de
Cc: Stella GZ <gzestela@gmail.com>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] 'uImage-mini2440' -> '/dev/nand0.kernel.bb' No space left on device
Date: Wed, 30 Apr 2014 09:15:22 +0200	[thread overview]
Message-ID: <201404300915.22347.jbe@pengutronix.de> (raw)
In-Reply-To: <loom.20140429T173603-399@post.gmane.org>

Hi Stella,

the failure seems more Mini2440 platform related than PTXdist related. So, our 
OSELAS community mailing list would be a better location to discuss this 
issue.

On Tuesday 29 April 2014 17:43:15 Stella GZ wrote:
> 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

Ohh, yes. I just start my kernels via TFTP and NFS. Longer time not tested if 
they still fit into the NAND partition.... :(

[jbe@thebe]> ll platform-mini2440/images/linuximage
-rw-r--r-- 1 jbe ptx 2155440 Apr 30 08:54 platform-mini2440/images/linuximage

[jbe@thebe]> cat configs/platform-friendlyarm-mini2440/barebox-128m-env/config
#!/bin/sh

machine=mini2440
[...]
# partition definition in the NAND
nand_parts="512k(barebox),384k(bareboxenv),2048k(kernel),-(root)"
[...]

The "2048k(kernel)" part defines a 2097152 space in the NAND for the kernel, 
but the kernel file itself is of 2155440 bytes in size. *BANG*

Yes. The current 3.14 Linux kernel is too large for this small NAND partition. 
You now have the choice (as Alexander already pointed out):

 - enlarge the kernel partition by modifying Barebox's default configuration
   in "configs/platform-friendlyarm-mini2440/barebox-128m-env/config" or at
   runtime with the (same) file in "/env/config"

 - or shrink the kernel. By accident I have left the symbol inclusion enabled
   in the current kernel config.

Without these symbols the kernel is smaller and should fit again into the 
existing NAND partition.

[jbe@thebe]> ll platform-mini2440/images/linuximage
-rw-r--r-- 1 jbe ptx 1908320 Apr 30 09:05 platform-mini2440/images/linuximage

To disable the symbols, run:

$ ptxdist menuconfig kernel
   General setup  --->
     -*- Configure standard kernel features (expert users)  --->
       [ ]   Load all symbols for debugging/ksymoops <------------ disable it

These symbols are required for debugging purposes only.

This also reminds me: the 3.14 kernel config is a copy of the 3.13 config, 
which is a copy of the 3.12 config, which is a copy of the 3.11 config...
All these kernel images will not fit into the NAND kernel partition due to 
enabled debug symbols. m( ...I'm going to change it.

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2014-04-30  7:15 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
2014-04-30  7:15 ` Juergen Borleis [this message]

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=201404300915.22347.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=gzestela@gmail.com \
    --cc=oselas@community.pengutronix.de \
    --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