mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Teresa Gamez <t.gamez@phytec.de>
To: "Breixo López García" <Breixo.Lopez@gmx.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Problem boot PREEMPT_RT kernel
Date: Wed, 27 Mar 2013 14:38:46 +0100	[thread overview]
Message-ID: <5152F666.8010700@phytec.de> (raw)
In-Reply-To: <trinity-dd72bb24-9dee-4ffc-b334-cab25b6865ba-1364382025620@3capp-gmx-bs25>

Am 27.03.2013 12:00, schrieb "Breixo López García":
> Hy Community,
> I have been trying to boot in the phyCORE-AM335x board the preempt_rt 
> kernel from OSELAS
> (https://www.osadl.org/Profile-of-system-in-rack-7-slot-5.qa-profile-r7s5.0.html#kernel)
> I can compile propertly the kernel, but when I do the boot in the 
> board, the following Issue appears in the target console:
> *barebox@Phytec <mailto:barebox@Phytec>* phyCORE-AM335x:/ boot -k tftp 
> -r net
> do_tftpb: /.tftp_tmp_path/linuximage -> /image
> 100Mbps full duplex link detected
> [##################################################write: Out of memory
> Ther kernel image is 4,8MB and I suppose that is out of the reserver 
> area for kernel in the RAM (tftp mode) before it is saved in the 
> flash. Where I can change the value of the started address  or it is 
> other Issue.
> I am using:
> -Toolchain:OSELAS.toolchain-2011.11.3
> -ptxdist: version 2012.03.0

This is an issue when using the OSELAS phyCORE-AM335x rt kernel on the 
Phytec BSP and not related to ptxdist. So this list is the wrong place 
to ask. Please contact the Phytec Support in such cases.

Your malloc space in ram is to small. You have to increase the 
MALLOC_SIZE in the barebox config.
You will face the same problem when trying to flash the image to NAND or 
SPI NOR flash. You
will have to increase the partition size in the environment and also 
update the rootfs.

Regards,
Teresa

> Whit the kernel boot through TFTP and the filesystem NFS:
> barebox config.
> !/bin/sh
> machine=pcm051
> user=
> # use 'dhcp' to do dhcp in barebox and in kernel
> # use 'none' if you want to skip kernel ip autoconfiguration
> #ip=dhcp
> # or set your networking parameters here
> eth0.ipaddr=192.168.3.11
> eth0.netmask=255.255.255.0
> eth0.gateway=192.168.3.1
> eth0.serverip=192.168.3.58
> # can be either 'tftp', 'disk', 'nor' or 'nand'
> kernel_loc=nand
> # can be either 'disk', 'net', 'nand' or 'initrd'
> rootfs_loc=net
> # can be either 'jffs2' 'ext3' or 'ubifs'
> rootfs_type=ext3
> rootfsimage=root-$machine.$rootfs_type
> # The image type of the kernel.
> kernelimage_type=uimage
> kernelimage=linuximage
> if [ -n $user ]; then
>         kernelimage="$user"-"$kernelimage"
> nfsroot="$eth0.serverip:/opt/phyCORE-AM335x-PD12.1.0/NFS/"
>         rootfsimage="$user"-"$rootfsimage"
> else
> nfsroot="$eth0.serverip:/opt/phyCORE-AM335x-PD12.1.0/NFS/"
> fi
> autoboot_timeout=3
> bootargs="console=ttyO0,115200"
>
> #Flash
> nand_parts="128k(xload),128k(xload_backup1),128k(xload_backup2),128k(xload_backu
> nor_parts="128k(xload),512k(barebox),128k(bareboxenv),4M(kernel),-(root)"
> rootfs_mtdblock_nand="12,2048"
> nand_device="omap2-nand.0"
> nor_device="spi_flash"
> rootfs_part_linux_dev=mmcblk0p2
> kernel_part=disk0.0
> # set a fancy prompt (if support is compiled in)
> PS1="\e[1;32mbarebox@\e[1;31m\h:\w\e[0m "
> #Displays
> #bootargs="$bootargs da8xx_fb.panel_name=PV_PD050VL1"
> #bootargs="$bootargs da8xx_fb.panel_name=PV_PD104SLF"
> #bootargs="$bootargs da8xx_fb.panel_name=PV_PM070WL4"
> bootargs="$bootargs da8xx_fb.panel_name=PV_PM070WL4"
> Thanks for your time
> -Regards
> Breixo
>
>


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-03-27 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 11:00 "Breixo López García"
2013-03-27 13:38 ` Teresa Gamez [this message]
2013-03-27 15:17   ` "Breixo López García"

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=5152F666.8010700@phytec.de \
    --to=t.gamez@phytec.de \
    --cc=Breixo.Lopez@gmx.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