[ptxdist] 'uImage-mini2440' -> '/dev/nand0.kernel.bb' No space left on device

[ptxdist] 'uImage-mini2440' -> '/dev/nand0.kernel.bb' No space left on device

[Stella GZ]

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                     
                                                                           
     
tftp failed: error -28                                                          
                                                 
My kernel's image size is:
-rw-r--r--  1 stella stella 2132696 abr 29 17:28 uImage-mini2440

Can anyone help me?
Thanks

Regards,
Stella.




-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] 'uImage-mini2440' -> '/dev/nand0.kernel.bb' No space left on device

[Alexander Aring]

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

Re: [ptxdist] 'uImage-mini2440' -> '/dev/nand0.kernel.bb' No space left on device

[Juergen Borleis]

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