Re: [oe] Updates to meta-browser (master) in 2016-05-20
Can someone send me a link to unsubscribe from this list .. Thanks On Sat, May 21, 2016 at 2:55 AM, Otavio Salvador wrote: > Hello, > > I pushed following updates: > > commit 825ea9349fe9b7da39f1de0c3e8e15d9d62f2774 (HEAD -> pending, > origin/master, origin/HEAD) > Author: Carlos Rafael Giani > Date: Fri May 20 13:41:47 2016 +0200 > > chromium: Add workarounds for compiler errors > > Signed-off-by: Carlos Rafael Giani > Signed-off-by: Otavio Salvador > > Regards, > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://code.ossystems.com.br > Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Please someone unsubscribe me from the list!!
Hi Guys, I have hit the "unsubscribe" button many times on the web site, but I have received no confirmation email ... can anyone do the deed .. Thanks. Cheers, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Admin: Unsubscribe me please
Can someone please un-subscribe me from the list, my attempts at doing so from the unsubscribe page have met with failure .. (I never get the confirmation email ..) Thanks, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] VLC and OpenGLES
Hi All, Can someone tell me how to build VLC or mplayer in openembedded with OpenGLES support .. I have the ogles demos working fine .. Just want to try video playing and would like eventually to get XBMC to run with ogles support as well. Many Thanks, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Error building gnome image ... xsltproc
Hmmm, now I get the following similar error ...
| xsltproc -o gdm-C.omf --stringparam db2omf.basename gdm --stringparam
db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook
XML V4.1.2//EN" --stringparam db2omf.lang C --stringparam db2omf.omf_dir
"/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help"
--stringparam db2omf.omf_in
"/home/bmentink/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/a
rmv7a-angstrom-linux-gnueabi/gdm-2.32.2-r4/gdm-2.32.2/docs/gdm.omf.in"
`/home/bmentink/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroo
ts/i686-linux/usr/bin/pkg-config --variable db2omf gnome-doc-utils`
C/gdm.xml || { rm -f "gdm-C.omf"; exit 1; }
| warning: failed to load external entity
"/usr/share/xml/gnome/xslt/docbook/omf/db2omf.xsl"
| cannot parse /usr/share/xml/gnome/xslt/docbook/omf/db2omf.xsl
| make[2]: *** [gdm-C.omf] Error 1
I have installed all the docbook stuff I can find on my host ..
Any idea's on this one?
Cheers,
Bernie
--
I want to die peacefully in my sleep, like my grandfather, not screaming
and yelling like the passengers in his car.
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of
Bernard Mentink
Sent: Tuesday, 6 September 2011 9:34 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Error building gnome image ... xsltproc
Many thanks Paul ... That fixed it.
Cheers,
Bernie
--
I want to die peacefully in my sleep, like my grandfather, not screaming
and yelling like the passengers in his car.
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of
Paul Menzel
Sent: Tuesday, 6 September 2011 9:22 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Error building gnome image ... xsltproc
Dear Bernard,
Am Dienstag, den 06.09.2011, 07:23 +1200 schrieb Bernard Mentink:
> Hi Guys,
>
> Am trying to build the systemd-gnome-image and I get a error when
> executing xsltproc on docbook.xsl, error is:
>
> xsltproc -nonet
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xs
> l
> udisks-daemon.xml
> I/O error : Attempt to load network entity
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xs
> l
> warning: failed to load external entity
> "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.x
> sl
> "
> cannot parse
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xs
> l
>
> I suspect this is a proxy issue: Anyone have a solution for this.
I do not know if you use oe-core/meta-oe or oe.dev/oe-classic. For
oe.dev you have to install it on the build host.
$ sudo aptitude install docbook-xsl
Thanks,
Paul
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Error building gnome image ... xsltproc
Many thanks Paul ... That fixed it. Cheers, Bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: openembedded-devel-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Paul Menzel Sent: Tuesday, 6 September 2011 9:22 a.m. To: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Error building gnome image ... xsltproc Dear Bernard, Am Dienstag, den 06.09.2011, 07:23 +1200 schrieb Bernard Mentink: > Hi Guys, > > Am trying to build the systemd-gnome-image and I get a error when > executing xsltproc on docbook.xsl, error is: > > xsltproc -nonet > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xs > l > udisks-daemon.xml > I/O error : Attempt to load network entity > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xs > l > warning: failed to load external entity > "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.x > sl > " > cannot parse > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xs > l > > I suspect this is a proxy issue: Anyone have a solution for this. I do not know if you use oe-core/meta-oe or oe.dev/oe-classic. For oe.dev you have to install it on the build host. $ sudo aptitude install docbook-xsl Thanks, Paul ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Error building gnome image ... xsltproc
Hi Guys, Am trying to build the systemd-gnome-image and I get a error when executing xsltproc on docbook.xsl, error is: xsltproc -nonet http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl udisks-daemon.xml I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl " cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl I suspect this is a proxy issue: Anyone have a solution for this. Regards, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Howto get Video Framebuufer working
Hi Guys, Can anyone give me a helping hand getting graphics/framebuffer working on a new i.mx31 platform. I have configured everything I can think of that is required in the kernel (see relevent section below) and the i.mx31 viddeo driver is definetely getting built. (See the object files below) However, I do not see any /dev/fb0 device What do I need to do to get one going? Cheers, Bernie. -- video stuff built --- ls drivers/video/*.o drivers/video/built-in.o drivers/video/fbcvt.o drivers/video/fbsysfs.o drivers/video/cfbcopyarea.o drivers/video/fbmem.o drivers/video/modedb.o drivers/video/cfbfillrect.o drivers/video/fbmon.o drivers/video/mx3fb.o drivers/video/cfbimgblt.odrivers/video/fb_notify.o drivers/video/fbcmap.o drivers/video/fb.o --- kernel config - # # Graphics support # CONFIG_DRM=m # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set CONFIG_FB_FOREIGN_ENDIAN=y CONFIG_FB_BOTH_ENDIAN=y # CONFIG_FB_BIG_ENDIAN is not set # CONFIG_FB_LITTLE_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set CONFIG_FB_MX3=y # CONFIG_FB_BROADSHEET is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=y # CONFIG_LCD_L4F00242T03 is not set # CONFIG_LCD_LMS283GF05 is not set # CONFIG_LCD_LTV350QV is not set # CONFIG_LCD_TDO24M is not set # CONFIG_LCD_VGG2432A4 is not set # CONFIG_LCD_PLATFORM is not set # CONFIG_LCD_S6E63M0 is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y CONFIG_BACKLIGHT_GENERIC=y CONFIG_BACKLIGHT_PWM=y # CONFIG_BACKLIGHT_ADP8860 is not set # # Display device support # CONFIG_DISPLAY_SUPPORT=y # # Display hardware drivers # ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Startx? Where is it?
Hi Charles, I don't seem to have a /dev/fb0, even though I cave compiled in MXC framebuffer support and framebuffer console So no penguin just yet. Had a good look though the config options and turned on everything that seemd to be relevent ... But no joy. I don't have an xinit program or /usr/bin/Xfbdev .. By the way, I have a few kernel modules in my root filesystem (not to do with the framebuffer, built that as static) but tried a modprobe on the box to try and load a module, but it complained about not finding it .. Also lsmod shows no modules loaded by automagically by udev .. Cheers, Bernie -- -Original Message- From: Charles Manning [mailto:mannin...@actrix.gen.nz] Sent: Thursday, 11 August 2011 2:25 p.m. To: openembedded-devel@lists.openembedded.org Cc: Bernard Mentink Subject: Re: [oe] Startx? Where is it? On Thursday 11 August 2011 12:36:16 Bernard Mentink wrote: > Hi All, > > I have finally got a booting console image (Angstrom) logged in via > SSH and now want to try and get X working. Good going Bernie! > > I have built the Angstom-x11-image and have unpacked it into my NFS > root ... but the problem is I see no startx command. How do you start > X in this distro? > > I have also built frame-buffer support into my kernel, can someone > tell me how to test that .. xinit eg. xinit /usr/bin/xmessage "Hello Bernie" -- /usr/bin/Xfbdev ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Startx? Where is it?
Hi All, I have finally got a booting console image (Angstrom) logged in via SSH and now want to try and get X working. I have built the Angstom-x11-image and have unpacked it into my NFS root ... but the problem is I see no startx command. How do you start X in this distro? I have also built frame-buffer support into my kernel, can someone tell me how to test that .. Cheers, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Init process help please
Hi Guys, I am porting Linux to an imx31 based target and have the kernel booting and the NFS filesystem booting and I see the kernel messages in the ram buffer uptill where it states: "Freeing init memory: 104K" However, I do not see any more messages regarding the init process, how do I know if it has started? (By the way, I don't have a serial console working at present ..) I am currently exporting a root filesystem via NFS, I am not sure If I am doing it correctly but I have: "console=ttymxc0,115200 root=/dev/nfs ip=dhcp nfsroot=10.3.16.71:/export,v3,tcp" as my kernel argument and I have un-compressed my root file system Into my /export directory i.e I have bin/sbin/home etc under /exports ... is this correct? By the way I have built the Angstom-console-ads31.. Image. I am not sure what program starts, is it /sbin/init? It currently is a link to /sbin/init.sysvinit The root filesystem seems to be mounter as per ram dump: .<4> device= eth0, addr=10.3. 16.116, mask=255 .0.0.0, gw=255.2 55.255.255,.<4> host=10.3.16 .116, domain=, n is-domain=(none) ,.<4> bootse rver=255.255.255 .255, rootserver =10.3.16.71, roo tpath=.<4>Warnin g: unable to ope n an initial con sole..<5>Looking 13/3 on 10.3 up port of RPC .16.71.<5>Lookin g up port of RPC 15/3 on 10. 3.16.71.<4>VFS: Mounted root (nf s filesystem) on device 0:11..<6 >Freeing init me mory: 104K Any ideas? Cheers, bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Bitbake syntax error
Hi Guys, I am getting the following error while trying to build the bootstrap-image, my bitbake is version 1.12.0. --- error --- gnueabi/bootstrap-image-1.0-r0/temp/log.do_package_update_index_ipk.2777 9 Log data follows: | + do_package_update_index_ipk | + set -x | + ipkgarchs='all any noarch arm armv4 armv4t armv5te armv6 mx31ads' | + '[' '!' -z '' ']' | + mkdir -p /home/bmentink/devel/build/tmp/deploy/eglibc/ipk | + touch /home/bmentink/devel/build/tmp/deploy/eglibc/ipk/Packages | + opkg-make-index -r /home/bmentink/devel/build/tmp/deploy/eglibc/ipk/Packages -p /home/bmentink/devel/build/tmp/deploy/eglibc/ipk/Packages -l /home/bmentink/devel/build/tmp/deploy/eglibc/ipk/Packages.filelist -m /home/bmentink/devel/build/tmp/deploy/eglibc/ipk | File "/home/bmentink/devel/build/tmp/sysroots/i686-linux/usr/bin/opkg-make-in dex", line 128 | print pkg_dir + "/" + old_filename | ^ | SyntaxError: invalid syntax NOTE: package bootstrap-image-1.0-r0: task do_package_update_index_ipk: Failed Any idea's? Cheers, Bernie. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Serial Console name for i.mx31
Charles... And as I said earlier, I have been looking in drivers/serial/mx.c, that is where I saw that the function serial_imx_probe was not being called if you remember ... My problem is what bit of code calls that function .. It is NOT in that module .. I am trying to get to the code that calls the ...probe to see Why it is not being called ... That is in some other module .. But I can't trace it due to all the vectored execution .. All the CONFIG_xxx defines are defined and yes, it is compiled in, because if you remember earlier, I said I put debug statements in the .. Init() Function and that was being called, I put debug statements in the ...probe() and that is NOT being called I see these printk outputs in the kernel ring buffer . All the obvious things are covered Charles .. >the driver layers (and hence serial drivers) only get set up later in >the piece by serial_imx_probe() once the OS is running. It's the "later" part I am trying to find ... I repeat, the bit of code that calls serial_imx_probe(), I may be thick, but I can't trace where it is .. All I know is that the driver is "registered" correctly (platform_register_driver() outputs no error messages), but the ..probe is not called. I am trying to find the bit of code that finds that there is an builtin imx31 serial peripheral and trys to load the driver for it The only code I could find is the function platform_driver_register() in ../drivers/base which loads all the "platform" drivers .. I am currently trying to put some debug stuff in that file to see why the driver is not being loaded/probed .. I hope I am being clear this time .. -Original Message- From: Charles Manning [mailto:mannin...@actrix.gen.nz] Sent: Monday, 1 August 2011 1:24 p.m. To: openembedded-devel@lists.openembedded.org Cc: Bernard Mentink Subject: Re: [oe] Serial Console name for i.mx31 Bernie... As I said, look in the serial driver code. Where that is will depend on what Linux tree you are using. On a tree I looked at now it is in drivers/serial/imx.c . It could also be under drivers/tty/... As I said, there are setups for two different sets of code in there: one for the console and one for drivers. The console is used during early boot because the driver layers (and hence serial drivers) only get set up later in the piece by serial_imx_probe() once the OS is running. imx_console_xxx functions relate to the console support. imx_console_setup() sets up the actual console. There are a bunch of defines CONFIG_SERIAL_IMX_CONSOLE, IMX_CONSOLE etc. Make sure those are configured and all the console code is actually being compiled in and initialised properly. On Monday 01 August 2011 13:03:16 Bernard Mentink wrote: > Funny Man! . What code The problem is finding the relevent > bits ... As everything seems to be executed as tables of function > pointers, it is very hard to fine what links with what .. > > (remember Charles, this is my 1st time getting into Embedded linux code > Give me a break!) > > -Original Message- > From: Charles Manning [mailto:mannin...@actrix.gen.nz] > Sent: Monday, 1 August 2011 11:34 a.m. > To: openembedded-devel@lists.openembedded.org > Cc: Bernard Mentink > Subject: Re: [oe] Serial Console name for i.mx31 > > Look at the code. > > That will tell you exactly what is going on. > > On Monday 01 August 2011 11:24:12 Bernard Mentink wrote: > > Hi Charles, > > > > Thanks, but I thought that it was obvious that I am hooked upto the > > 1st > > imx31 serial port as I am using ttymxc0 .. ;-) I have tried seeing if > > I am getting output on any other serial port (we have 4 of the 5 > > brought out to connectors ..) > > > > The example .config file for the imx shows a kernel argument of > > "console=ttymxc0,115200" with no parity/bits setting so I don't think > > That will make any difference ... But I will try it. > > > > Cheers, > > B. > > > > > > > > > > -Original Message- > > From: Charles Manning [mailto:mannin...@actrix.gen.nz] > > Sent: Monday, 1 August 2011 11:17 a.m. > > To: openembedded-devel@lists.openembedded.org > > Cc: Bernard Mentink > > Subject: Re: [oe] Serial Console name for i.mx31 > > > > Bernie > > > > You have to hook up to the UART that is wired to what you're watching. > > Nobody on this list knows what serial port you are connected to. > > > > NB That the early console stuff is set up as a console through console > > > > initialisation. THis is not the same as setting up the serial ports > > for driver usage. > > > > As for the actual setting, it does not look good compared to what I am > > > > used to be
Re: [oe] Serial Console name for i.mx31
Funny Man! . What code The problem is finding the relevent bits ... As everything seems to be executed as tables of function pointers, it is very hard to fine what links with what .. (remember Charles, this is my 1st time getting into Embedded linux code Give me a break!) -Original Message- From: Charles Manning [mailto:mannin...@actrix.gen.nz] Sent: Monday, 1 August 2011 11:34 a.m. To: openembedded-devel@lists.openembedded.org Cc: Bernard Mentink Subject: Re: [oe] Serial Console name for i.mx31 Look at the code. That will tell you exactly what is going on. On Monday 01 August 2011 11:24:12 Bernard Mentink wrote: > Hi Charles, > > Thanks, but I thought that it was obvious that I am hooked upto the > 1st > imx31 serial port as I am using ttymxc0 .. ;-) I have tried seeing if > I am getting output on any other serial port (we have 4 of the 5 > brought out to connectors ..) > > The example .config file for the imx shows a kernel argument of > "console=ttymxc0,115200" with no parity/bits setting so I don't think > That will make any difference ... But I will try it. > > Cheers, > B. > > > > > -Original Message- > From: Charles Manning [mailto:mannin...@actrix.gen.nz] > Sent: Monday, 1 August 2011 11:17 a.m. > To: openembedded-devel@lists.openembedded.org > Cc: Bernard Mentink > Subject: Re: [oe] Serial Console name for i.mx31 > > Bernie > > You have to hook up to the UART that is wired to what you're watching. > Nobody on this list knows what serial port you are connected to. > > NB That the early console stuff is set up as a console through console > initialisation. THis is not the same as setting up the serial ports > for driver usage. > > As for the actual setting, it does not look good compared to what I am > used to because it does not set all the parameters. > > console=ttymxc0,115200n8 > > But what actually is used will depend on the console setup (search for > console in the imx31 serial driver code. > > On Monday 01 August 2011 10:44:07 Bernard Mentink wrote: > > Hi, > > > > Can anyone verify what the kernel command line option should be to > > use the first imx31 uart? As far as I can tell it is > > "console=ttymxc0,115200" > > > > The reason I ask, is that I am seeing the kernel messages in the ram > > kernel ring buffer, but not seing them come out the serial console. > > > > I am porting linux to our own hardware which is similar to the > > LogicPD LiteKit platform (I have compiled the kernel for this > > platform ..) > > > > Debugging into the serial driver in ../drivers/serial/mx31 .. I see > > the > > > function init_serial_init() being called ( .. and it's printk > > message > > is > > > in the buffer) but I am not seeing the serial_imx_probe() being > > called .. > > > > I do not understand the the registering of platform drivers enough > > to work out how the kernel connects the diver with the hardware > > Can someone enlighten me on how to debug this further . Or even > > better just tell me to use the correct command line option and it > > all bursts into life :-) > > > > Thanks, > > Bernie > > > > In addition: > > > > I added the earlyprintk command to the kernel command line and I do > > see > > > these messages. i.e: > > > > Starting kernel ... > > > > Uncompressing Linux... done, booting the kernel. > > Linux version 2.6.36.1 (bmentink@2570-ArchBox) (gcc version 4.5.3 > > 20110311 (prerelease) (GCC) ) #7 P > > REEMPT Mon Aug 1 09:51:34 NZST 2011 > > CPU: ARMv6-compatible processor [4107b364] revision 4 (ARMv6TEJ), > > cr=00c5387f > > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache > > Machine: LogicPD i.MX31 SOM > > bootconsole [earlycon0] enabled > > Memory policy: ECC disabled, Data cache writeback Built 1 zonelists > > in Zone order, mobility grouping on. Total pages: > > 32512 > > Kernel command line: console=ttymxc,115200 > > earlyprintk=serial,ttymxc0,115200,keep > > PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache > > hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash > > table entries: 8192 (order: 3, 32768 bytes) > > Memory: 128MB = 128MB total > > Memory: 126744k/126744k available, 4328k reserved, 0K highmem > > Virtual kernel memory layout: > > vector : 0x - 0x1000 ( 4 kB) > > fixmap : 0xfff0 - 0xfffe ( 896 kB) > > DMA : 0xffc0 - 0xffe0 ( 2 MB) > >
Re: [oe] Serial Console name for i.mx31
Hi Charles, Thanks, but I thought that it was obvious that I am hooked upto the 1st imx31 serial port as I am using ttymxc0 .. ;-) I have tried seeing if I am getting output on any other serial port (we have 4 of the 5 brought out to connectors ..) The example .config file for the imx shows a kernel argument of "console=ttymxc0,115200" with no parity/bits setting so I don't think That will make any difference ... But I will try it. Cheers, B. -Original Message- From: Charles Manning [mailto:mannin...@actrix.gen.nz] Sent: Monday, 1 August 2011 11:17 a.m. To: openembedded-devel@lists.openembedded.org Cc: Bernard Mentink Subject: Re: [oe] Serial Console name for i.mx31 Bernie You have to hook up to the UART that is wired to what you're watching. Nobody on this list knows what serial port you are connected to. NB That the early console stuff is set up as a console through console initialisation. THis is not the same as setting up the serial ports for driver usage. As for the actual setting, it does not look good compared to what I am used to because it does not set all the parameters. console=ttymxc0,115200n8 But what actually is used will depend on the console setup (search for console in the imx31 serial driver code. On Monday 01 August 2011 10:44:07 Bernard Mentink wrote: > Hi, > > Can anyone verify what the kernel command line option should be to use > the first imx31 uart? As far as I can tell it is > "console=ttymxc0,115200" > > The reason I ask, is that I am seeing the kernel messages in the ram > kernel ring buffer, but not seing them come out the serial console. > > I am porting linux to our own hardware which is similar to the LogicPD > LiteKit platform (I have compiled the kernel for this platform ..) > > Debugging into the serial driver in ../drivers/serial/mx31 .. I see the > function init_serial_init() being called ( .. and it's printk message is > in the buffer) but I am not seeing the serial_imx_probe() being called > .. > > I do not understand the the registering of platform drivers enough to > work out how the kernel connects the diver with the hardware Can > someone enlighten me on how to debug this further . Or even better > just tell me to use the correct command line option and it all bursts > into life :-) > > Thanks, > Bernie > > In addition: > > I added the earlyprintk command to the kernel command line and I do see > these messages. i.e: > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > Linux version 2.6.36.1 (bmentink@2570-ArchBox) (gcc version 4.5.3 > 20110311 (prerelease) (GCC) ) #7 P > REEMPT Mon Aug 1 09:51:34 NZST 2011 > CPU: ARMv6-compatible processor [4107b364] revision 4 (ARMv6TEJ), > cr=00c5387f > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache > Machine: LogicPD i.MX31 SOM > bootconsole [earlycon0] enabled > Memory policy: ECC disabled, Data cache writeback > Built 1 zonelists in Zone order, mobility grouping on. Total pages: > 32512 > Kernel command line: console=ttymxc,115200 > earlyprintk=serial,ttymxc0,115200,keep > PID hash table entries: 512 (order: -1, 2048 bytes) > Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) > Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) > Memory: 128MB = 128MB total > Memory: 126744k/126744k available, 4328k reserved, 0K highmem > Virtual kernel memory layout: > vector : 0x - 0x1000 ( 4 kB) > fixmap : 0xfff0 - 0xfffe ( 896 kB) > DMA : 0xffc0 - 0xffe0 ( 2 MB) > vmalloc : 0xc880 - 0xf400 ( 696 MB) > lowmem : 0xc000 - 0xc800 ( 128 MB) > modules : 0xbf00 - 0xc000 ( 16 MB) > .init : 0xc0008000 - 0xc001e000 ( 88 kB) > .text : 0xc001e000 - 0xc02e1000 (2828 kB) > .data : 0xc02f6000 - 0xc030c6e0 ( 90 kB) > Hierarchical RCU implementation. > RCU-based detection of stalled CPUs is disabled. > Verbose stalled-CPUs detection is disabled. > NR_IRQS:180 > MXC IRQ initialized > MXC GPIO hardware > > So it seems there is nothing wrong with the "ttymxc0" port assignment > ... It's just the main serial console is just not working .. > > Cheers, > B. > > > > > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Serial Console name for i.mx31
Hi, Can anyone verify what the kernel command line option should be to use the first imx31 uart? As far as I can tell it is "console=ttymxc0,115200" The reason I ask, is that I am seeing the kernel messages in the ram kernel ring buffer, but not seing them come out the serial console. I am porting linux to our own hardware which is similar to the LogicPD LiteKit platform (I have compiled the kernel for this platform ..) Debugging into the serial driver in ../drivers/serial/mx31 .. I see the function init_serial_init() being called ( .. and it's printk message is in the buffer) but I am not seeing the serial_imx_probe() being called .. I do not understand the the registering of platform drivers enough to work out how the kernel connects the diver with the hardware Can someone enlighten me on how to debug this further . Or even better just tell me to use the correct command line option and it all bursts into life :-) Thanks, Bernie In addition: I added the earlyprintk command to the kernel command line and I do see these messages. i.e: Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.36.1 (bmentink@2570-ArchBox) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #7 P REEMPT Mon Aug 1 09:51:34 NZST 2011 CPU: ARMv6-compatible processor [4107b364] revision 4 (ARMv6TEJ), cr=00c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: LogicPD i.MX31 SOM bootconsole [earlycon0] enabled Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: console=ttymxc,115200 earlyprintk=serial,ttymxc0,115200,keep PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 126744k/126744k available, 4328k reserved, 0K highmem Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xfff0 - 0xfffe ( 896 kB) DMA : 0xffc0 - 0xffe0 ( 2 MB) vmalloc : 0xc880 - 0xf400 ( 696 MB) lowmem : 0xc000 - 0xc800 ( 128 MB) modules : 0xbf00 - 0xc000 ( 16 MB) .init : 0xc0008000 - 0xc001e000 ( 88 kB) .text : 0xc001e000 - 0xc02e1000 (2828 kB) .data : 0xc02f6000 - 0xc030c6e0 ( 90 kB) Hierarchical RCU implementation. RCU-based detection of stalled CPUs is disabled. Verbose stalled-CPUs detection is disabled. NR_IRQS:180 MXC IRQ initialized MXC GPIO hardware So it seems there is nothing wrong with the "ttymxc0" port assignment ... It's just the main serial console is just not working .. Cheers, B. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Serial Console name for i.mx31
Hi, Can anyone verify what the kernel command line option should be to use the first imx31 uart? As far as I can tell it is "console=ttymxc0,115200" The reason I ask, is that I am seeing the kernel messages in the ram kernel ring buffer, but not seing them come out the serial console. I am porting linux to our own hardware which is similar to the LogicPD LiteKit platform (I have compiled the kernel for this platform ..) Debugging into the serial driver in ../drivers/serial/mx31 .. I see the function init_serial_init() being called ( .. and it's printk message is in the buffer) but I am not seeing the serial_imx_probe() being called .. I do not understand the the registering of platform drivers enough to work out how the kernel connects the diver with the hardware Can someone enlighten me on how to debug this further . Or even better just tell me to use the correct command line option and it all bursts into life :-) Thanks, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Kernel boot problems
Thanks for explaination Charles. Anu idea's on how to debug the Serial console bringup? I have printascii() available to use as a debug tool Any pointers to where the serial console code is would be appreciated .. This is very frustrating, as I can see all the kernel come up fine in the kernal buffer in RAM, just not out the serial console port .. Cheers, bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: openembedded-devel-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Charles Manning Sent: Friday, 29 July 2011 4:07 p.m. To: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Kernel boot problems > Hi Gary, > > Did as you suggested .. no printout from serial_imx_probe() is seen, > so I guess it isn't been called, will have to trace it back to see why not. > This is going to be tedious .. > > EDIT: However the function imx_serial_init() is being called and > completes without errors, so I don't know why the probe is not being > called .. > Any ideas? The serial initialisation probably happens twice: Once for the early console stuff to give to the tracing before the uncompressing. Then again for setting up the "real" device tree when the decompressed kernel is being booted. I think the probing is only during the second. > > Thanks, > bernie > > > -- > -- > -- > I want to die peacefully in my sleep, like my grandfather, not > screaming and yelling like the passengers in his car. > > -Original Message- > From: Gary Thomas [mailto:g...@mlbassoc.com] > Sent: Friday, 29 July 2011 10:42 a.m. > To: Bernard Mentink > Cc: openembedded-devel@lists.openembedded.org > Subject: Re: [oe] Kernel boot problems > > On 2011-07-28 16:10, Bernard Mentink wrote: >> Hi Gary, >> >> Further down I see a confirmation of the boot params ... i.e >> console=ttymxc0,115200 >> >> 8030d600: 73747369 206e6920 656e6f5a 64726f20 ists in Zone ord >> 8030d610: 202c7265 69626f6d 7974696c 6f726720 er, mobility gro >> 8030d620: 6e697075 6e6f2067 5420202e 6c61746f uping on. Total >> 8030d630: 67617020 203a7365 31353233 353c0a32 pages: 32512.<5 >> 8030d640: 72654b3e 206c656e 6d6d6f63 20646e61>Kernel command >> 8030d650: 656e696c 6f63203a 6c6f736e 74743d65 line: console=tt >> 8030d660: 63786d79 31312c30 30303235 3e363c0a ymxc0,115200.<6> >> 8030d670: 20444950 68736168 62617420 6520656c PID hash table e >> 8030d680: 6972746e 203a7365 20323135 64726f28 ntries: 512 (ord >> 8030d690: 203a7265 202c312d 38343032 74796220 er: -1, 2048 byt >> 8030d6a0: 0a297365 443e363c 72746e65 61632079 es).<6>Dentry ca >> 8030d6b0: 20656863 68736168 62617420 6520656c che hash table e >> 8030d6c0: 6972746e 203a7365 38333631 6f282034 ntries: 16384 (o >> 8030d6d0: 72656472 2c34203a 35353620 62203633 rder: 4, 65536 b >> 8030d6e0: 73657479 363c0a29 6f6e493e 632d6564 ytes).<6>Inode-c >> 8030d6f0: 65686361 73616820 61742068 20656c62 ache hash table >> >> The only mention of serial port is: >> >> 8030df00: 20656e69 69676572 72657473 3c0a6465 ine registered.< >> 8030df10: 6f693e36 68637320 6c756465 63207265 6>io scheduler c >> 8030df20: 72207166 73696765 65726574 64282064 fq registered (d >> 8030df30: 75616665 0a29746c 533e363c 61697265 efault).<6>Seria >> 8030df40: 49203a6c 6420584d 65766972 353c0a72 l: IMX driver.<5 >> 8030df50: 7968703e 70616d73 616c7020 726f6674>physmap platfor >> 8030df60: 6c66206d 20687361 69766564 203a6563 m flash device: >> 8030df70: 30303230 30303030 20746120 30303061 0200 at a000 >> 8030df80: 30303030 3e363c0a 73796870 2d70616d .<6>physmap- >> 8030df90: 73616c66 3a302e68 756f4620 3120646e flash.0: Found 1 >> 8030dfa0: 36317820 76656420 73656369 20746120 x16 devices at >> 8030dfb0: 20307830 31206e69 69622d36 61622074 0x0 in 16-bit ba >> 8030dfc0: 202e6b6e 756e614d 74636166 72657275 nk. Manufacturer >> 8030dfd0: 20444920 30307830 39383030 69684320 ID 0x89 Chi >> 8030dfe0: 44492070 30783020 31393830 353c0a63 p ID 0x00891c.<5 >> 8030dff0: 7075533e 74726f70 726f6620 6d6f6320>Support for com >> >> .. And yes I did turn on early debug in the kernel config .. But I >> don't see any extra messages out the serial port. >> How can I check that my .config ch
Re: [oe] Kernel boot problems
Hi Gary, Did as you suggested .. no printout from serial_imx_probe() is seen, so I guess it isn't been called, will have to trace it back to see why not. This is going to be tedious .. EDIT: However the function imx_serial_init() is being called and completes without errors, so I don't know why the probe is not being called .. Any ideas? Thanks, bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: Gary Thomas [mailto:g...@mlbassoc.com] Sent: Friday, 29 July 2011 10:42 a.m. To: Bernard Mentink Cc: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Kernel boot problems On 2011-07-28 16:10, Bernard Mentink wrote: > Hi Gary, > > Further down I see a confirmation of the boot params ... i.e > console=ttymxc0,115200 > > 8030d600: 73747369 206e6920 656e6f5a 64726f20ists in Zone ord > 8030d610: 202c7265 69626f6d 7974696c 6f726720er, mobility gro > 8030d620: 6e697075 6e6f2067 5420202e 6c61746fuping on. Total > 8030d630: 67617020 203a7365 31353233 353c0a32 pages: 32512.<5 > 8030d640: 72654b3e 206c656e 6d6d6f63 20646e61>Kernel command > 8030d650: 656e696c 6f63203a 6c6f736e 74743d65line: console=tt > 8030d660: 63786d79 31312c30 30303235 3e363c0aymxc0,115200.<6> > 8030d670: 20444950 68736168 62617420 6520656cPID hash table e > 8030d680: 6972746e 203a7365 20323135 64726f28ntries: 512 (ord > 8030d690: 203a7265 202c312d 38343032 74796220er: -1, 2048 byt > 8030d6a0: 0a297365 443e363c 72746e65 61632079es).<6>Dentry ca > 8030d6b0: 20656863 68736168 62617420 6520656cche hash table e > 8030d6c0: 6972746e 203a7365 38333631 6f282034ntries: 16384 (o > 8030d6d0: 72656472 2c34203a 35353620 62203633rder: 4, 65536 b > 8030d6e0: 73657479 363c0a29 6f6e493e 632d6564ytes).<6>Inode-c > 8030d6f0: 65686361 73616820 61742068 20656c62ache hash table > > The only mention of serial port is: > > 8030df00: 20656e69 69676572 72657473 3c0a6465ine registered.< > 8030df10: 6f693e36 68637320 6c756465 632072656>io scheduler c > 8030df20: 72207166 73696765 65726574 64282064fq registered (d > 8030df30: 75616665 0a29746c 533e363c 61697265efault).<6>Seria > 8030df40: 49203a6c 6420584d 65766972 353c0a72l: IMX driver.<5 > 8030df50: 7968703e 70616d73 616c7020 726f6674>physmap platfor > 8030df60: 6c66206d 20687361 69766564 203a6563m flash device: > 8030df70: 30303230 30303030 20746120 303030610200 at a000 > 8030df80: 30303030 3e363c0a 73796870 2d70616d.<6>physmap- > 8030df90: 73616c66 3a302e68 756f4620 3120646eflash.0: Found 1 > 8030dfa0: 36317820 76656420 73656369 20746120 x16 devices at > 8030dfb0: 20307830 31206e69 69622d36 616220740x0 in 16-bit ba > 8030dfc0: 202e6b6e 756e614d 74636166 72657275nk. Manufacturer > 8030dfd0: 20444920 30307830 39383030 69684320 ID 0x89 Chi > 8030dfe0: 44492070 30783020 31393830 353c0a63p ID 0x00891c.<5 > 8030dff0: 7075533e 74726f70 726f6620 6d6f6320>Support for com > > .. And yes I did turn on early debug in the kernel config .. But I > don't see any extra messages out the serial port. > How can I check that my .config changes have propagated through ok? .. Do you have CONFIG_SERIAL_IMX_CONSOLE in your config? You can just grep for 'SERIAL_IMX_CONSOLE' in .config You could also edit drivers/serial/imx.c and put some printk() messages in serial_imx_probe() to see if it's being called to register your device. Of course, you'll have to look at the log_buf to read the messages :-) I notice that your bootargs don't specify a file system. Perhaps if you added that the system could actually make it up to multi-user and you could log in (serial, SSH, ...) > -- > -- > -- > I want to die peacefully in my sleep, like my grandfather, not > screaming and yelling like the passengers in his car. > > -----Original Message- > From: Gary Thomas [mailto:g...@mlbassoc.com] > Sent: Friday, 29 July 2011 9:40 a.m. > To: Bernard Mentink > Cc: openembedded-devel@lists.openembedded.org > Subject: Re: [oe] Kernel boot problems > > On 2011-07-28 14:51, Bernard Mentink wrote: >> Many thanks for that, >> >> I had a look through the buffer and I see pretty much normal bootup >> text ... It just isn't coming out of the serial port .. >> >> The only error I saw was the following: >> - >> 8030cf80: 0001 3a534656 6e614320VFS: Can >> 8030cf9
Re: [oe] Kernel boot problems
Hi Gary, Did as you suggested .. no printout from serial_imx_probe() is seen, so I guess it isn't been called, will have to trace it back to see why not. This is going to be tedious .. Thanks, bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: Gary Thomas [mailto:g...@mlbassoc.com] Sent: Friday, 29 July 2011 10:42 a.m. To: Bernard Mentink Cc: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Kernel boot problems On 2011-07-28 16:10, Bernard Mentink wrote: > Hi Gary, > > Further down I see a confirmation of the boot params ... i.e > console=ttymxc0,115200 > > 8030d600: 73747369 206e6920 656e6f5a 64726f20ists in Zone ord > 8030d610: 202c7265 69626f6d 7974696c 6f726720er, mobility gro > 8030d620: 6e697075 6e6f2067 5420202e 6c61746fuping on. Total > 8030d630: 67617020 203a7365 31353233 353c0a32 pages: 32512.<5 > 8030d640: 72654b3e 206c656e 6d6d6f63 20646e61>Kernel command > 8030d650: 656e696c 6f63203a 6c6f736e 74743d65line: console=tt > 8030d660: 63786d79 31312c30 30303235 3e363c0aymxc0,115200.<6> > 8030d670: 20444950 68736168 62617420 6520656cPID hash table e > 8030d680: 6972746e 203a7365 20323135 64726f28ntries: 512 (ord > 8030d690: 203a7265 202c312d 38343032 74796220er: -1, 2048 byt > 8030d6a0: 0a297365 443e363c 72746e65 61632079es).<6>Dentry ca > 8030d6b0: 20656863 68736168 62617420 6520656cche hash table e > 8030d6c0: 6972746e 203a7365 38333631 6f282034ntries: 16384 (o > 8030d6d0: 72656472 2c34203a 35353620 62203633rder: 4, 65536 b > 8030d6e0: 73657479 363c0a29 6f6e493e 632d6564ytes).<6>Inode-c > 8030d6f0: 65686361 73616820 61742068 20656c62ache hash table > > The only mention of serial port is: > > 8030df00: 20656e69 69676572 72657473 3c0a6465ine registered.< > 8030df10: 6f693e36 68637320 6c756465 632072656>io scheduler c > 8030df20: 72207166 73696765 65726574 64282064fq registered (d > 8030df30: 75616665 0a29746c 533e363c 61697265efault).<6>Seria > 8030df40: 49203a6c 6420584d 65766972 353c0a72l: IMX driver.<5 > 8030df50: 7968703e 70616d73 616c7020 726f6674>physmap platfor > 8030df60: 6c66206d 20687361 69766564 203a6563m flash device: > 8030df70: 30303230 30303030 20746120 303030610200 at a000 > 8030df80: 30303030 3e363c0a 73796870 2d70616d.<6>physmap- > 8030df90: 73616c66 3a302e68 756f4620 3120646eflash.0: Found 1 > 8030dfa0: 36317820 76656420 73656369 20746120 x16 devices at > 8030dfb0: 20307830 31206e69 69622d36 616220740x0 in 16-bit ba > 8030dfc0: 202e6b6e 756e614d 74636166 72657275nk. Manufacturer > 8030dfd0: 20444920 30307830 39383030 69684320 ID 0x89 Chi > 8030dfe0: 44492070 30783020 31393830 353c0a63p ID 0x00891c.<5 > 8030dff0: 7075533e 74726f70 726f6620 6d6f6320>Support for com > > .. And yes I did turn on early debug in the kernel config .. But I > don't see any extra messages out the serial port. > How can I check that my .config changes have propagated through ok? .. Do you have CONFIG_SERIAL_IMX_CONSOLE in your config? You can just grep for 'SERIAL_IMX_CONSOLE' in .config You could also edit drivers/serial/imx.c and put some printk() messages in serial_imx_probe() to see if it's being called to register your device. Of course, you'll have to look at the log_buf to read the messages :-) I notice that your bootargs don't specify a file system. Perhaps if you added that the system could actually make it up to multi-user and you could log in (serial, SSH, ...) > -- > -- > -- > I want to die peacefully in my sleep, like my grandfather, not > screaming and yelling like the passengers in his car. > > -Original Message- > From: Gary Thomas [mailto:g...@mlbassoc.com] > Sent: Friday, 29 July 2011 9:40 a.m. > To: Bernard Mentink > Cc: openembedded-devel@lists.openembedded.org > Subject: Re: [oe] Kernel boot problems > > On 2011-07-28 14:51, Bernard Mentink wrote: >> Many thanks for that, >> >> I had a look through the buffer and I see pretty much normal bootup >> text ... It just isn't coming out of the serial port .. >> >> The only error I saw was the following: >> - >> 8030cf80: 0001 3a534656 6e614320VFS: Can >> 8030cf90: 20746f6e 6e65706f 6f6f7220 65642074not open root de >> 8030cfa0: 65636976 6e282220 296c6c75 726f2022vice "(null)" or >> 8030cfb0
Re: [oe] Kernel boot problems
Hi Gary, Yes, I have CONFIG_SERIAL_IMX_CONSOLE=y in my .config and I have confirmed it is being used. I will try the printk in the serial driver ... Thanks, was looking for where that was .. I want to get the kernal up and running before I introduce the root file system .. But if I get stuck on this serial issue, I may do as you suggest. Thanks, bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: Gary Thomas [mailto:g...@mlbassoc.com] Sent: Friday, 29 July 2011 10:42 a.m. To: Bernard Mentink Cc: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Kernel boot problems On 2011-07-28 16:10, Bernard Mentink wrote: > Hi Gary, > > Further down I see a confirmation of the boot params ... i.e > console=ttymxc0,115200 > > 8030d600: 73747369 206e6920 656e6f5a 64726f20ists in Zone ord > 8030d610: 202c7265 69626f6d 7974696c 6f726720er, mobility gro > 8030d620: 6e697075 6e6f2067 5420202e 6c61746fuping on. Total > 8030d630: 67617020 203a7365 31353233 353c0a32 pages: 32512.<5 > 8030d640: 72654b3e 206c656e 6d6d6f63 20646e61>Kernel command > 8030d650: 656e696c 6f63203a 6c6f736e 74743d65line: console=tt > 8030d660: 63786d79 31312c30 30303235 3e363c0aymxc0,115200.<6> > 8030d670: 20444950 68736168 62617420 6520656cPID hash table e > 8030d680: 6972746e 203a7365 20323135 64726f28ntries: 512 (ord > 8030d690: 203a7265 202c312d 38343032 74796220er: -1, 2048 byt > 8030d6a0: 0a297365 443e363c 72746e65 61632079es).<6>Dentry ca > 8030d6b0: 20656863 68736168 62617420 6520656cche hash table e > 8030d6c0: 6972746e 203a7365 38333631 6f282034ntries: 16384 (o > 8030d6d0: 72656472 2c34203a 35353620 62203633rder: 4, 65536 b > 8030d6e0: 73657479 363c0a29 6f6e493e 632d6564ytes).<6>Inode-c > 8030d6f0: 65686361 73616820 61742068 20656c62ache hash table > > The only mention of serial port is: > > 8030df00: 20656e69 69676572 72657473 3c0a6465ine registered.< > 8030df10: 6f693e36 68637320 6c756465 632072656>io scheduler c > 8030df20: 72207166 73696765 65726574 64282064fq registered (d > 8030df30: 75616665 0a29746c 533e363c 61697265efault).<6>Seria > 8030df40: 49203a6c 6420584d 65766972 353c0a72l: IMX driver.<5 > 8030df50: 7968703e 70616d73 616c7020 726f6674>physmap platfor > 8030df60: 6c66206d 20687361 69766564 203a6563m flash device: > 8030df70: 30303230 30303030 20746120 303030610200 at a000 > 8030df80: 30303030 3e363c0a 73796870 2d70616d.<6>physmap- > 8030df90: 73616c66 3a302e68 756f4620 3120646eflash.0: Found 1 > 8030dfa0: 36317820 76656420 73656369 20746120 x16 devices at > 8030dfb0: 20307830 31206e69 69622d36 616220740x0 in 16-bit ba > 8030dfc0: 202e6b6e 756e614d 74636166 72657275nk. Manufacturer > 8030dfd0: 20444920 30307830 39383030 69684320 ID 0x89 Chi > 8030dfe0: 44492070 30783020 31393830 353c0a63p ID 0x00891c.<5 > 8030dff0: 7075533e 74726f70 726f6620 6d6f6320>Support for com > > .. And yes I did turn on early debug in the kernel config .. But I > don't see any extra messages out the serial port. > How can I check that my .config changes have propagated through ok? .. Do you have CONFIG_SERIAL_IMX_CONSOLE in your config? You can just grep for 'SERIAL_IMX_CONSOLE' in .config You could also edit drivers/serial/imx.c and put some printk() messages in serial_imx_probe() to see if it's being called to register your device. Of course, you'll have to look at the log_buf to read the messages :-) I notice that your bootargs don't specify a file system. Perhaps if you added that the system could actually make it up to multi-user and you could log in (serial, SSH, ...) > -- > -- > -- > I want to die peacefully in my sleep, like my grandfather, not > screaming and yelling like the passengers in his car. > > -Original Message- > From: Gary Thomas [mailto:g...@mlbassoc.com] > Sent: Friday, 29 July 2011 9:40 a.m. > To: Bernard Mentink > Cc: openembedded-devel@lists.openembedded.org > Subject: Re: [oe] Kernel boot problems > > On 2011-07-28 14:51, Bernard Mentink wrote: >> Many thanks for that, >> >> I had a look through the buffer and I see pretty much normal bootup >> text ... It just isn't coming out of the serial port .. >> >> The only error I saw was the following: >> - >> 8030cf80: 0001 3a534656 6e614320VFS: Can >> 8030cf90: 20746f6
Re: [oe] Kernel boot problems
Hi Gary, Further down I see a confirmation of the boot params ... i.e console=ttymxc0,115200 8030d600: 73747369 206e6920 656e6f5a 64726f20ists in Zone ord 8030d610: 202c7265 69626f6d 7974696c 6f726720er, mobility gro 8030d620: 6e697075 6e6f2067 5420202e 6c61746fuping on. Total 8030d630: 67617020 203a7365 31353233 353c0a32 pages: 32512.<5 8030d640: 72654b3e 206c656e 6d6d6f63 20646e61>Kernel command 8030d650: 656e696c 6f63203a 6c6f736e 74743d65line: console=tt 8030d660: 63786d79 31312c30 30303235 3e363c0aymxc0,115200.<6> 8030d670: 20444950 68736168 62617420 6520656cPID hash table e 8030d680: 6972746e 203a7365 20323135 64726f28ntries: 512 (ord 8030d690: 203a7265 202c312d 38343032 74796220er: -1, 2048 byt 8030d6a0: 0a297365 443e363c 72746e65 61632079es).<6>Dentry ca 8030d6b0: 20656863 68736168 62617420 6520656cche hash table e 8030d6c0: 6972746e 203a7365 38333631 6f282034ntries: 16384 (o 8030d6d0: 72656472 2c34203a 35353620 62203633rder: 4, 65536 b 8030d6e0: 73657479 363c0a29 6f6e493e 632d6564ytes).<6>Inode-c 8030d6f0: 65686361 73616820 61742068 20656c62ache hash table The only mention of serial port is: 8030df00: 20656e69 69676572 72657473 3c0a6465ine registered.< 8030df10: 6f693e36 68637320 6c756465 632072656>io scheduler c 8030df20: 72207166 73696765 65726574 64282064fq registered (d 8030df30: 75616665 0a29746c 533e363c 61697265efault).<6>Seria 8030df40: 49203a6c 6420584d 65766972 353c0a72l: IMX driver.<5 8030df50: 7968703e 70616d73 616c7020 726f6674>physmap platfor 8030df60: 6c66206d 20687361 69766564 203a6563m flash device: 8030df70: 30303230 30303030 20746120 303030610200 at a000 8030df80: 30303030 3e363c0a 73796870 2d70616d.<6>physmap- 8030df90: 73616c66 3a302e68 756f4620 3120646eflash.0: Found 1 8030dfa0: 36317820 76656420 73656369 20746120 x16 devices at 8030dfb0: 20307830 31206e69 69622d36 616220740x0 in 16-bit ba 8030dfc0: 202e6b6e 756e614d 74636166 72657275nk. Manufacturer 8030dfd0: 20444920 30307830 39383030 69684320 ID 0x89 Chi 8030dfe0: 44492070 30783020 31393830 353c0a63p ID 0x00891c.<5 8030dff0: 7075533e 74726f70 726f6620 6d6f6320>Support for com .. And yes I did turn on early debug in the kernel config .. But I don't see any extra messages out the serial port. How can I check that my .config changes have propagated through ok? .. Regards, bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: Gary Thomas [mailto:g...@mlbassoc.com] Sent: Friday, 29 July 2011 9:40 a.m. To: Bernard Mentink Cc: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Kernel boot problems On 2011-07-28 14:51, Bernard Mentink wrote: > Many thanks for that, > > I had a look through the buffer and I see pretty much normal bootup > text ... It just isn't coming out of the serial port .. > > The only error I saw was the following: > - > 8030cf80: 0001 3a534656 6e614320VFS: Can > 8030cf90: 20746f6e 6e65706f 6f6f7220 65642074not open root de > 8030cfa0: 65636976 6e282220 296c6c75 726f2022vice "(null)" or > 8030cfb0: 6b6e7520 6e776f6e 6f6c622d 32286b63 unknown-block(2 > 8030cfc0: 64646100 3d72 303a.addr=:0 > 8030cfd0: 69202c31 2d3d7172 000a2931 203938301, irq=-1)..089 > 8030cfe0: 30373178 2a29 30307830 63313938x170).. 0x00891c > 8030cff0: 203a 7830202d 6566 30303030..0 - 0xfffe > 8030d000: 28202020 36393820 29426b20 2020200a ( 896 kB). > 8030d010: 414d4420 20202020 30203a20 6378 DMA : 0xffc > 8030d020: 30303030 202d2030 7830 303030650 - 0xffe000 > 8030d030: 20203030 20202820 4d203220 200a294200 ( 2 MB). > 8030d040: 76202020 6c6c616d 3a20636f 63783020 vmalloc : 0xc > 8030d050: 30303834 20303030 7830202d 30303466480 - 0xf400 > 8030d060: 30303030 28202020 30363720 29424d20 ( 760 MB) > 8030d070: 2020200a 776f6c20 206d656d 30203a20.lowmem : 0 > 8030d080: 30306378 30303030 202d2030 34637830xc000 - 0xc4 > 8030d090: 30303030 20203030 20202820 4d20343600 ( 64 M > 8030d0a0: 200a2942 6d202020 6c75646f 3a207365B).modules : > 8030d0b0: 62783020 30303066 20303030 7830202d 0xbf00 - 0x > 8030d0c0: 30303063 30303030 28202020 36312020c000 ( 16 > 8030d0d0: 29424d20 2020200a 2e202020 74696e69 MB). .init > 8030d0e0: 30203a20 30306378 30303830 202d2030 : 0xc0008000 - > 8030d0f0: 30637830 30653130 20203030 202028200xc001e000 ( > 8030d100: 6b203838 200a294
Re: [oe] Kernel boot problems
- I am not sure why it is not printing out the port, my boot param = "console=ttymxc0,115200" And the relevent part of conf/machine/mx31ads.conf = SERIAL_CONSOLE = "115200 ttymxc0" Any idea's? Cheers, Bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: Gary Thomas [mailto:g...@mlbassoc.com] Sent: Thursday, 28 July 2011 11:22 p.m. To: openembedded-devel@lists.openembedded.org Cc: Bernard Mentink Subject: Re: [oe] Kernel boot problems On 2011-07-27 20:20, Bernard Mentink wrote: > > Hi Guys, > > I have got a bit further with my efforts to boot linux on an imx31 > based platform using u-boot. > > My console output is now: > > > uboot> bootm 8010 > ## Booting kernel from Legacy Image at 8010 ... > Image Name: Angstrom/2.6.36/mx31ads > Created: 2011-07-28 2:03:27 UTC > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size:1586172 Bytes = 1.5 MiB > Load Address: 8f00 > Entry Point: 8f00 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > --- > > So it seems to be getting to the 1st part of the kernel boot process, > then hangs (I presume the last line comes from kernel code.) I don't > know if the kernel is hanging, or if I don't have any more serial out > > I am passing "console=ttymxc0,115200" to the kernel .. > Can someone confirm: > A) If I have the correct Entry point, or does this need to be offset > into the kernel? .. > B) Is the serial console parameters correct? > C) What is the correct way to set up the memory map? (my ram starts at > 0x8000, ends at 0x8fff) > D) Is there a way to debug initial kernel stuff with serial output? > In the above, I have decompressed the kernel to the top of the 256M ram, > but have only advertised 120M via the bootloader ... for now, not > knowing what is correct and not wanting the kernel to stomp all over > itself running in ram. Analyzing this failure can be hard. If you have some sort of JTAG setup you might be able to break in at this point, figure out where it's hanging up, etc. Even if you don't have JTAG, there might be some crumbs left around for you to look at. Linux keeps everything that goes to the "console" in a circular buffer __log_buf[]. Look up that symbol in System.map (which will be found in your linux build tree). Here's the tricky part - the map will show a logical address, but U-Boot only knows physical addresses. Normally the mapping is pretty easy, e.g. on my OMAP/3530 I might see: $ grep __log_buf linux-2.6.37/System.map c0527058 b __log_buf So in U-Boot, I would look at the buffer like this: U-Boot> md 0x80527058 80527058: 4c3e353c 78756e69 72657620 6e6f6973<5>Linux version 80527068: 362e3220 2e37332e 67282033 6d6f6874 2.6.37.3 (gthom 80527078: 74407361 6e617469 67282029 76206363as@titan) (gcc v 80527088: 69737265 34206e6f 312e362e 31303220ersion 4.6.1 201 80527098: 32363031 70282037 65726572 7361656c10627 (prereleas 805270a8: 28202965 29434347 23202920 72462031e) (GCC) ) #1 Fr 805270b8: 754a2069 3232206c 3a393020 303a3135i Jul 22 09:51:0 ... Keep looking through this buffer until it stops with useful characters. That may tell you where the kernel got hung up and why. If you find only garbage, it may be more difficult to tell. Note: hopefully your board has a RESET button which you can use to get back into U-Boot once the kernel boot process hangs. Power cycling to reset the board won't work as the contents of RAM will likely be destroyed. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Kernel boot problems
Hi Guys, I have got a bit further with my efforts to boot linux on an imx31 based platform using u-boot. My console output is now: uboot> bootm 8010 ## Booting kernel from Legacy Image at 8010 ... Image Name: Angstrom/2.6.36/mx31ads Created: 2011-07-28 2:03:27 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1586172 Bytes = 1.5 MiB Load Address: 8f00 Entry Point: 8f00 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. --- So it seems to be getting to the 1st part of the kernel boot process, then hangs (I presume the last line comes from kernel code.) I don't know if the kernel is hanging, or if I don't have any more serial out I am passing "console=ttymxc0,115200" to the kernel .. Can someone confirm: A) If I have the correct Entry point, or does this need to be offset into the kernel? .. B) Is the serial console parameters correct? C) What is the correct way to set up the memory map? (my ram starts at 0x8000, ends at 0x8fff) D) Is there a way to debug initial kernel stuff with serial output? In the above, I have decompressed the kernel to the top of the 256M ram, but have only advertised 120M via the bootloader ... for now, not knowing what is correct and not wanting the kernel to stomp all over itself running in ram. Many Thanks, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Kernel load address issue
Hi Chris, Many thanks for that. However I only have a uImage in my build, no zImage so can't do a diff to find the offset, is there another way to find that out? Maybe you or someone else knows what script in openembedded calls the mkimage utility so I can find what parameters are passed .. By the way, I set UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT to be the same (0x8040, a bit past u-boot and the environment) in my config file, I am not sure if the entry point should be the same as the load address. Cheers, Bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: openembedded-devel-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Chris Verges Sent: Thursday, 28 July 2011 2:12 a.m. To: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Kernel load address issue On Wed, Jul 27, 2011 at 06:00:07AM +, Mats Kärrman wrote: > Starting kernel ... > > And there it hangs ... I don't know who printed out the "Starting > kernel" was it uboot or the kernel? If uboot, how do I pass kernel > arguments (i.e the console serial params) with this method of booting? Hi Bernie, I've experienced this before when the UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT values in the machine config file for OpenEmbedded aren't properly set to the correct value. You may want to double check those values. Also, try setting your bootm address just a tag higher in memory than the actual UBOOT_ENTRYPOINT. I forgot what the exact uboot-mkimage header put on the uImage is, but you can do a hex diff between the zImage and uImage files to figure it out. That offset can sometimes cause some odd booting problems. So if your ENTRYPOINT is 0x830 and the uboot-mkimage offset is 0xC0, for example, you'd need to bootm 0x83000C0. (Again, double check the uboot-mkimage offset.) Good luck, Chris ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Kernel load address issue
I have got a bit further now, I get:
-
uboot> bootm 8040
## Booting kernel from Legacy Image at 8040 ...
Image Name: Angstrom/2.6.36/mx31ads
Created: 2011-07-26 22:30:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:1765848 Bytes = 1.7 MiB
Load Address: 8040
Entry Point: 8040
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
And there it hangs ... I don't know who printed out the "Starting
kernel" was it uboot or the kernel?
If uboot, how do I pass kernel arguments (i.e the console serial params)
with this method of booting?
(I am using: " dhcp 0x8040 IP:file" followed by the above bootm .. )
Thanks,
Bernie
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of
Bernard Mentink
Sent: Wednesday, 27 July 2011 10:32 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
Hi Martin,
Thanks for that (and to Gary for the same answer) ..
By the way, where do I find this sort of information out? I especially
would like to know how to configure the kernel, modify source code etc,
Within the openembedded system ..
Are there some good "howto's" out there?
Thanks,
Bernie
--
I want to die peacefully in my sleep, like my grandfather, not screaming
and yelling like the passengers in his car.
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of
Martin Jansa
Sent: Wednesday, 27 July 2011 10:27 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 10:14:50AM +1200, Bernard Mentink wrote:
> Many thanks for the reply,
>
> By the way where is the machine.conf file, I can't seem to find it
> anywhere ..
in your case probably
conf/machine/mx31ads.conf or something like that
I meant ${MACHINE}.conf and machine.conf was just example, sorry I
wasn't clear.
Cheers,
>
> Cheers,
> Bernie
>
>
> --
> --
> --
> I want to die peacefully in my sleep, like my grandfather, not
> screaming and yelling like the passengers in his car.
>
> -Original Message-
> From: openembedded-devel-boun...@lists.openembedded.org
> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf
> Of Martin Jansa
> Sent: Wednesday, 27 July 2011 10:03 a.m.
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] Kernel load address issue
>
> On Wed, Jul 27, 2011 at 09:51:28AM +1200, Bernard Mentink wrote:
> >
> > Hi Guys,
> >
> > I am new to OE, but have managed to get u-boot working on my target,
> > got TFTP working so I can transfer a kernel to RAM.
> > I have modified my conf/local.conf file so that when a kernel is
> > built
>
> > a uImage binary is created that u-boot can use. (added line
> > KERNEL_IMAGETYPE = "uImage")
> >
> > However When I try to boot the image in the bootloader, I get this:
> >
> > uboot> bootm 0x8030
> > ## Booting kernel from Legacy Image at 8030 ...
> >Image Name: Angstrom/2.6.36/mx31ads
> >Created: 2011-07-26 19:55:31 UTC
> >Image Type: ARM Linux Kernel Image (uncompressed)
> >Data Size:1765856 Bytes = 1.7 MiB
> >Load Address: 20008000
> >Entry Point: 20008000
>
> machine.conf can define
> UBOOT_ENTRYPOINT = "0x80008000"
> UBOOT_LOADADDRESS = "0x80008000"
>
> both used in kernel.bbclass
> /OE/dev/classes/kernel.bbclass:UBOOT_ENTRYPOINT ?= "20008000"
> /OE/dev/classes/kernel.bbclass:UBOOT_LOADADDRESS ?=
> "${UBOOT_ENTRYPOINT}"
> /OE/dev/classes/kernel.bbclass:uboot-mkimage -A
> ${UBOOT_ARCH} -O linux -T kernel -C none -a ${UBOOT_LOADADDRESS} -e
> $ENTRYPOINT -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin
> arch/${ARCH}/boot/uImage
>
> Cheers,
>
> >Verifying Checksum ... OK
> >Loading Kernel Image ... <-- gets stuck here! ...
> >
> > The Load Address is wrong, my ram starts at 0x8000 ... can
> > someone
>
> > tell me how to change this? I presume mkimage is responsible for
> > this as the kernel is configured as relocatable ..
> >
> > Many Thanks,
> > Bernie
> >
> &
Re: [oe] Kernel load address issue
Hi Martin,
Thanks for that (and to Gary for the same answer) ..
By the way, where do I find this sort of information out? I especially
would like to know how to configure the kernel, modify source code etc,
Within the openembedded system ..
Are there some good "howto's" out there?
Thanks,
Bernie
--
I want to die peacefully in my sleep, like my grandfather, not screaming
and yelling like the passengers in his car.
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of
Martin Jansa
Sent: Wednesday, 27 July 2011 10:27 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 10:14:50AM +1200, Bernard Mentink wrote:
> Many thanks for the reply,
>
> By the way where is the machine.conf file, I can't seem to find it
> anywhere ..
in your case probably
conf/machine/mx31ads.conf or something like that
I meant ${MACHINE}.conf and machine.conf was just example, sorry I
wasn't clear.
Cheers,
>
> Cheers,
> Bernie
>
>
> --
> --
> --
> I want to die peacefully in my sleep, like my grandfather, not
> screaming and yelling like the passengers in his car.
>
> -Original Message-
> From: openembedded-devel-boun...@lists.openembedded.org
> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf
> Of Martin Jansa
> Sent: Wednesday, 27 July 2011 10:03 a.m.
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] Kernel load address issue
>
> On Wed, Jul 27, 2011 at 09:51:28AM +1200, Bernard Mentink wrote:
> >
> > Hi Guys,
> >
> > I am new to OE, but have managed to get u-boot working on my target,
> > got TFTP working so I can transfer a kernel to RAM.
> > I have modified my conf/local.conf file so that when a kernel is
> > built
>
> > a uImage binary is created that u-boot can use. (added line
> > KERNEL_IMAGETYPE = "uImage")
> >
> > However When I try to boot the image in the bootloader, I get this:
> >
> > uboot> bootm 0x8030
> > ## Booting kernel from Legacy Image at 8030 ...
> >Image Name: Angstrom/2.6.36/mx31ads
> >Created: 2011-07-26 19:55:31 UTC
> >Image Type: ARM Linux Kernel Image (uncompressed)
> >Data Size:1765856 Bytes = 1.7 MiB
> >Load Address: 20008000
> >Entry Point: 20008000
>
> machine.conf can define
> UBOOT_ENTRYPOINT = "0x80008000"
> UBOOT_LOADADDRESS = "0x80008000"
>
> both used in kernel.bbclass
> /OE/dev/classes/kernel.bbclass:UBOOT_ENTRYPOINT ?= "20008000"
> /OE/dev/classes/kernel.bbclass:UBOOT_LOADADDRESS ?=
> "${UBOOT_ENTRYPOINT}"
> /OE/dev/classes/kernel.bbclass:uboot-mkimage -A
> ${UBOOT_ARCH} -O linux -T kernel -C none -a ${UBOOT_LOADADDRESS} -e
> $ENTRYPOINT -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin
> arch/${ARCH}/boot/uImage
>
> Cheers,
>
> >Verifying Checksum ... OK
> >Loading Kernel Image ... <-- gets stuck here! ...
> >
> > The Load Address is wrong, my ram starts at 0x8000 ... can
> > someone
>
> > tell me how to change this? I presume mkimage is responsible for
> > this as the kernel is configured as relocatable ..
> >
> > Many Thanks,
> > Bernie
> >
> >
> >
> >
> >
> > ___
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev
> > el
>
> --
> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Kernel load address issue
Many thanks for the reply,
By the way where is the machine.conf file, I can't seem to find it
anywhere ..
Cheers,
Bernie
--
I want to die peacefully in my sleep, like my grandfather, not screaming
and yelling like the passengers in his car.
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of
Martin Jansa
Sent: Wednesday, 27 July 2011 10:03 a.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Kernel load address issue
On Wed, Jul 27, 2011 at 09:51:28AM +1200, Bernard Mentink wrote:
>
> Hi Guys,
>
> I am new to OE, but have managed to get u-boot working on my target,
> got TFTP working so I can transfer a kernel to RAM.
> I have modified my conf/local.conf file so that when a kernel is built
> a uImage binary is created that u-boot can use. (added line
> KERNEL_IMAGETYPE = "uImage")
>
> However When I try to boot the image in the bootloader, I get this:
>
> uboot> bootm 0x8030
> ## Booting kernel from Legacy Image at 8030 ...
>Image Name: Angstrom/2.6.36/mx31ads
>Created: 2011-07-26 19:55:31 UTC
>Image Type: ARM Linux Kernel Image (uncompressed)
>Data Size:1765856 Bytes = 1.7 MiB
>Load Address: 20008000
>Entry Point: 20008000
machine.conf can define
UBOOT_ENTRYPOINT = "0x80008000"
UBOOT_LOADADDRESS = "0x80008000"
both used in kernel.bbclass
/OE/dev/classes/kernel.bbclass:UBOOT_ENTRYPOINT ?= "20008000"
/OE/dev/classes/kernel.bbclass:UBOOT_LOADADDRESS ?=
"${UBOOT_ENTRYPOINT}"
/OE/dev/classes/kernel.bbclass:uboot-mkimage -A
${UBOOT_ARCH} -O linux -T kernel -C none -a ${UBOOT_LOADADDRESS} -e
$ENTRYPOINT -n "${DISTRO_NAME}/${PV}/${MACHINE}" -d linux.bin
arch/${ARCH}/boot/uImage
Cheers,
>Verifying Checksum ... OK
>Loading Kernel Image ... <-- gets stuck here! ...
>
> The Load Address is wrong, my ram starts at 0x8000 ... can someone
> tell me how to change this? I presume mkimage is responsible for this
> as the kernel is configured as relocatable ..
>
> Many Thanks,
> Bernie
>
>
>
>
>
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Kernel load address issue
Hi Guys, I am new to OE, but have managed to get u-boot working on my target, got TFTP working so I can transfer a kernel to RAM. I have modified my conf/local.conf file so that when a kernel is built a uImage binary is created that u-boot can use. (added line KERNEL_IMAGETYPE = "uImage") However When I try to boot the image in the bootloader, I get this: uboot> bootm 0x8030 ## Booting kernel from Legacy Image at 8030 ... Image Name: Angstrom/2.6.36/mx31ads Created: 2011-07-26 19:55:31 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1765856 Bytes = 1.7 MiB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Loading Kernel Image ... <-- gets stuck here! ... The Load Address is wrong, my ram starts at 0x8000 ... can someone tell me how to change this? I presume mkimage is responsible for this as the kernel is configured as relocatable .. Many Thanks, Bernie ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Errors on fetching files
Hi Guys, I am getting the following fetch errors when trying to compile .. I am behind a http proxy so have made sure the wget, svn,cvs,ftp,git etc work ... and they do on the command line, however I am still getting these errors. A dump of the current error is below .. If I "wget" the file it is complaining about and install it in the ~/sources directory and add an md5checksum file as well, it gets past this error next time I run Until the next time. So the question is if wget works from the command line why does it not work from bitbake Unless it uses another method to get the file, but I see nothing in the .bb file to indicate what program is used .. Any and all help appreciated. Thanks, Bernie -- METADATA_REVISION = "b59743b" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "mx31ads" DISTRO= "angstrom" DISTRO_VERSION= "v2011.07" TARGET_FPU= "hard" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing RunQueue Tasks NOTE: Running task 114 of 606 (ID: 571, virtual:native:/home/bmentink/devel/openembedded/recipes/sqlite/sqlite3_ 3.6.23.1.bb, do_fetch) --2011-07-14 11:17:29-- http://www.sqlite.org/sqlite-3.6.23.1.tar.gz NOTE: package sqlite3-native-3.6.23.1-r4.0: task do_fetch: Started Resolving www.sqlite.org... 67.18.92.124 Connecting to www.sqlite.org|67.18.92.124|:80... failed: Connection refused. --2011-07-14 11:17:30-- http://mirrors.openembedded.org/sqlite-3.6.23.1.tar.gz Resolving mirrors.openembedded.org... 82.197.159.157 Connecting to mirrors.openembedded.org|82.197.159.157|:80... failed: Connection refused. --2011-07-14 11:17:30-- http://sources.openembedded.org/sqlite-3.6.23.1.tar.gz Resolving sources.openembedded.org... 140.211.169.165 Connecting to sources.openembedded.org|140.211.169.165|:80... failed: Connection refused. --2011-07-14 11:17:30-- http://www.angstrom-distribution.org/unstable/sources/sqlite-3.6.23.1.ta r.gz Resolving www.angstrom-distribution.org... 188.40.83.200 Connecting to www.angstrom-distribution.org|188.40.83.200|:80... failed: Connection refused. NOTE: package sqlite3-native-3.6.23.1-r4.0: task Fetch failed: Unable to fetch URL http://www.sqlite.org/sqlite-3.6.23.1.tar.gz from any source.: Failed ERROR: Function 'Fetch failed: Unable to fetch URL http://www.sqlite.org/sqlite-3.6.23.1.tar.gz from any source.' failed ERROR: Task 571 (virtual:native:/home/bmentink/devel/openembedded/recipes/sqlite/sqlite3 _3.6.23.1.bb, do_fetch) failed with exit code '1' ERROR: 'virtual:native:/home/bmentink/devel/openembedded/recipes/sqlite/sqlite3 _3.6.23.1.bb' failed ------------ --- Bernard Mentink Caterpillar Trimble Control Technologies P.O. Box 8729, Riccarton 11 Birmingham Drive, Christchurch New Zealand Phone +64-3-9635335 Fax +64-3-9635417 Email bment...@trimble.co.nz ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Debugging u-boot
Hi Charles, Building for Angstom and imx31 .. Cheers, Bernie -- I want to die peacefully in my sleep, like my grandfather, not screaming and yelling like the passengers in his car. -Original Message- From: Charles Manning [mailto:mannin...@actrix.gen.nz] Sent: Tuesday, 12 July 2011 10:17 a.m. To: openembedded-devel@lists.openembedded.org Cc: Bernard Mentink Subject: Re: [oe] Debugging u-boot Hmmm. What are you building for? Works fine for me using the Angstrom build for omap3 (beagleboard, overo etc). On Friday 08 July 2011 07:25:04 Bernard Mentink wrote: > Hi Charles, > > Tried that but got the following linker error: > > -- error > --- > > | > |/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstr > |om-l > |inux-gnueabi/bin/ld: failed to merge target specific data of file > |emutls_s.o > |/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstr > |om-l > |inux-gnueabi/bin/ld: error: > | > |/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnuea > |bi/g > |cc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm > |-angs trom-linux-gnueabi/./gcc/crtendS.o uses VFP register arguments, > |./libgcc_s.so.1.tmp does not > |/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstr > |om-l > |inux-gnueabi/bin/ld: failed to merge target specific data of file > |/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnuea > |bi/g > |cc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm > |-angs trom-linux-gnueabi/./gcc/crtendS.o collect2: ld returned 1 exit > |status > | make[2]: *** [libgcc_s.so] Error 1 > | make[2]: Leaving directory > | > |`/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnue > |abi/ > |gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.ar > |m-ang strom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgcc' make[1]: > |*** [all-target-libgcc] Error 2 > | make[1]: Leaving directory > | > |`/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnue > |abi/ > |gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.ar > |m-ang strom-linux-gnueabi' make: *** [all] Error 2 > | + die 'oe_runmake failed' > | + oefatal 'oe_runmake failed' > | + echo FATAL > > NOTE: package gcc-cross-sdk-4.5-r36.2+svnr170880: task do_compile: >Failed > ERROR: Function 'do_compile' failed (see >/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi >/gcc >-cross-sdk-4.5-r36.2+svnr170880/temp/log.do_compile.14514 for further > information) ERROR: Task 594 > (/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb, > do_compile) failed with exit code '1' ERROR: > '/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb' >failed > >--- > >-- > > Any idea what it could be? > > Cheers, > bernie > > > > > >--- > >--- I want to die peacefully in my sleep, like my >grandfather, not screaming and yelling like the passengers in his car. > > -Original Message- > From: openembedded-devel-boun...@lists.openembedded.org > [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf > Of Charles Manning Sent: Thursday, 7 July 2011 1:52 p.m. > To: openembedded-devel@lists.openembedded.org > Subject: Re: [oe] Debugging u-boot > > On Thu, Jul 7, 2011 at 1:13 PM, Bernard Mentink wrote: > > Hi Charles, > > > > Didn't know you were lurking on this list ... ;-) > > You can run but you can't hide. > > > I have built for the angstom distro (arm-angstrom-linux-gnueabi-*), > > but the tools got put in my project path I described in my earlier > > email, but There was no GDB included for some reason .. > > The regular toolchian than oe builds for its own purposes does not use > gdb because gdb is not needed for building. That toolchain is intended > for use within OE bitbakery only. > > A meta-toolchain is built as a standalone toolchain intended for use > outside of OE (eg. if you pull u-boot to a standalone directory for > development purposes or want to do your own app development outside of > OE.) > > > How do you build the meta-toolchain, and how will that help. > > bitbake meta-toolchain. > > This makes a toolchain which you
Re: [oe] Debugging u-boot
Hi Charles,
Tried that but got the following linker error:
-- error
---
|
/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld:
failed to merge target specific data of file emutls_s.o
|
/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld:
error:
/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o
uses VFP register arguments, ./libgcc_s.so.1.tmp does not
|
/home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld:
failed to merge target specific data of file
/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o
| collect2: ld returned 1 exit status
| make[2]: *** [libgcc_s.so] Error 1
| make[2]: Leaving directory
`/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgcc'
| make[1]: *** [all-target-libgcc] Error 2
| make[1]: Leaving directory
`/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi'
| make: *** [all] Error 2
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL
NOTE: package gcc-cross-sdk-4.5-r36.2+svnr170880: task do_compile: Failed
ERROR: Function 'do_compile' failed (see
/home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/temp/log.do_compile.14514
for further information)
ERROR: Task 594
(/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb, do_compile)
failed with exit code '1'
ERROR: '/home/bernie/Stuff/openembedded/recipes/gcc/gcc-cross-sdk_4.5.bb' failed
-
Any idea what it could be?
Cheers,
bernie
--
I want to die peacefully in my sleep, like my grandfather, not screaming and
yelling like the passengers in his car.
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Charles
Manning
Sent: Thursday, 7 July 2011 1:52 p.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Debugging u-boot
On Thu, Jul 7, 2011 at 1:13 PM, Bernard Mentink
wrote:
> Hi Charles,
>
> Didn't know you were lurking on this list ... ;-)
You can run but you can't hide.
>
> I have built for the angstom distro (arm-angstrom-linux-gnueabi-*),
> but the tools got put in my project path I described in my earlier email, but
> There was no GDB included for some reason ..
The regular toolchian than oe builds for its own purposes does not use gdb
because gdb is not needed for building. That toolchain is intended for use
within OE bitbakery only.
A meta-toolchain is built as a standalone toolchain intended for use outside of
OE (eg. if you pull u-boot to a standalone directory for development purposes
or want to do your own app development outside of
OE.)
>
> How do you build the meta-toolchain, and how will that help.
bitbake meta-toolchain.
This makes a toolchain which you can unpack thus:
$ cd /
$ sudo tar xvjf
${OETOP}/tmp/deploy/glibc/sdk/angstrom-2009.X-test-20110301-armv7a-linux-gnueabi-toolchain.tar.bz2
[NB your toolchain name will be something different]
To set up all the paths etc use
. /usr/local/angstrom/arm/environment-setup
Google openembedded metatoolchain will also give some interesting info.
NB If you're building apps and need extra libraries you will need to make your
own SDK. That's a bit more effort and you don't need all that just for gdbing
u-boot
-- Charles
>
> Cheers,
> Bernie
>
>
> --
> I want to die peacefully in my sleep, like my
> grandfather, not screaming and yelling like the passengers in his car.
>
> -Original Message-
> From: openembedded-devel-boun...@lists.openembedded.org
> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf
> Of Charles Manning
> Sent: Thursday, 7 July 2011 12:38 p.m.
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] Debugging u-boot
>
> Bernie
>
> What toolchain are you building?
>
> If you build meta-toolchain that s
Re: [oe] Debugging u-boot
Hi Charles,
Didn't know you were lurking on this list ... ;-)
I have built for the angstom distro (arm-angstrom-linux-gnueabi-*), but the
tools got put in my project path I described in my earlier email, but
There was no GDB included for some reason ..
How do you build the meta-toolchain, and how will that help.
Cheers,
Bernie
--
I want to die peacefully in my sleep, like my grandfather, not screaming and
yelling like the passengers in his car.
-Original Message-
From: openembedded-devel-boun...@lists.openembedded.org
[mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Charles
Manning
Sent: Thursday, 7 July 2011 12:38 p.m.
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Debugging u-boot
Bernie
What toolchain are you building?
If you build meta-toolchain that should build all the stuff you can put into
/usr/local/angstrom/arm/... which includes gdb.
That should then work with a JTAG debugger etc.
-- Charles
On Thu, Jul 7, 2011 at 11:25 AM, Bernard Mentink
wrote:
> Hi All,
>
> Can some one please tell me how to debug u-boot on my target. I have
> built u-boot for similar hardware and I want to debug with gdb, but
> cannot even find the cross-compile version of gdb, It does not exist
> in the directory "build/tmp/sysroots/i686-linux/usr/armv6/bin/" where
> the other cross-compile tools live ..
>
> I want to execute "${CROSS_COMPILE}gdb u-boot"
> .. and breakpoint at some very early symbol . Some steps to
> achieving this would be much appreciated ..
>
> Many Thanks,
> Bernie
>
>
>
>
> ___
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Debugging u-boot
Hi All,
Can some one please tell me how to debug u-boot on my target. I have
built u-boot for similar hardware and I want to debug with gdb, but
cannot even find the cross-compile version of gdb,
It does not exist in the directory
"build/tmp/sysroots/i686-linux/usr/armv6/bin/" where the other
cross-compile tools live ..
I want to execute "${CROSS_COMPILE}gdb u-boot"
.. and breakpoint at some very early symbol . Some steps to
achieving this would be much appreciated ..
Many Thanks,
Bernie
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Porting OE to new hardware
Thanks Khem, That helps a lot. On the kernel config issue there is one thing I don't understand. I have set up to do an ARM i.mx31 build, but when I did a "make menuconfig" in the /build/tmp/.../kernelx directory, it only shows x86 options, I don't know where all the i.mx31 kernel options are. Thanks, Bernie On Wed, Mar 31, 2010 at 7:03 AM, Khem Raj wrote: > On Mon, Mar 29, 2010 at 12:29 PM, Bernard Mentink > wrote: > > Hi All, > > > > I am jumping across to this email list as the user one has very little > > traffic. > > > > I have just found OE and would like to use it to get Linux up and running > on > > some custom hardware. The hardware is currently running the logicloader > > bootloader from LogicPD and a YAFFS2 filesystem. > > > > I have found very little info on the steps necessary to port to new > > hardware. As far as OE is concerned, I have built an image after altering > > the MACHINE and DISTRO to something close to what I need. > > I now have a zimage (kernel) and a rootFS. > > > > However I have a number of questions: > > > > 1. To boot with zimage with logicloader, I have to load the image into > > memory at an address, and then execute it at the start code which I > presume > > is an offset the start of the image. Can anyone tell me how I can find > > the relevant map file to work out > > what offset I need to apply? I did a search for *.map files in the > build/tmp > > direcory and found nada .. > > this post tells how to load linux kernel using logicloader. It might help > you. > > http://forums.freescale.com/t5/Other-Microcontrollers/load-zImage-or-vmlinux-using-LogicLoader/td-p/32749;jsessionid=F6F40E5BF81249CFF86028A7AB86DE29 > > > > > 2. How do I do a kernel config? Is there an option to pass to bitbake to > do > > that, or do I have to find the kernel source and do it manually, then > > rebuild with bitbake? > > You can copy the .config you want into > recipes/linux///defconfig file and it > will use > it to build the kernel for you machine. You can also edit the .config > on fly search the ml on how to do it. > > > > > 3. What src files in the kernel do I need to to maybe alter to get the > > serial port and memory map right for my target hardware .. > > > > you can specify serial port in kernel commandline too unless your board > needs > a special handling of serial port. > > > 4. Once I get the kernel booting, I need it to load the rootfs, initially > I > > can boot that from NFS, but I would like to eventually load it from my > YAFFS > > NAND partition, how do I do that? > > you can do that thru kernel commandline. > > > > > > > Hope someone can give me some pointers in the right direction ... I would > > love to kick off WinCE from this hardware ;-) > > > > Cheers, > > Bernie > > > > -- > > You always have believers and scepticts.. A True inventor is always a > > believer.. > > ___ > > Openembedded-devel mailing list > > Openembedded-devel@lists.openembedded.org > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > > > > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > -- You always have believers and scepticts.. A True inventor is always a believer.. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Porting OE to new hardware
Thanks, but doesn't help at all I think it requires a level of understanding I don't have yet ... Cheers, Bernie On Tue, Mar 30, 2010 at 8:33 AM, Izak Burger wrote: > Hi Bernard, > > I found this page during my searches for similar info: > > http://wiki.openembedded.net/index.php/Adding_a_new_Machine > > Don't know how useful or up to date it is though, I'm still new to > these parts and to OE in general, but I thought I'd post that here in > case it is useful. > > regards, > Izak > > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > -- You always have believers and scepticts.. A True inventor is always a believer.. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] Porting OE to new hardware
Hi All, I am jumping across to this email list as the user one has very little traffic. I have just found OE and would like to use it to get Linux up and running on some custom hardware. The hardware is currently running the logicloader bootloader from LogicPD and a YAFFS2 filesystem. I have found very little info on the steps necessary to port to new hardware. As far as OE is concerned, I have built an image after altering the MACHINE and DISTRO to something close to what I need. I now have a zimage (kernel) and a rootFS. However I have a number of questions: 1. To boot with zimage with logicloader, I have to load the image into memory at an address, and then execute it at the start code which I presume is an offset the start of the image. Can anyone tell me how I can find the relevant map file to work out what offset I need to apply? I did a search for *.map files in the build/tmp direcory and found nada .. 2. How do I do a kernel config? Is there an option to pass to bitbake to do that, or do I have to find the kernel source and do it manually, then rebuild with bitbake? 3. What src files in the kernel do I need to to maybe alter to get the serial port and memory map right for my target hardware .. 4. Once I get the kernel booting, I need it to load the rootfs, initially I can boot that from NFS, but I would like to eventually load it from my YAFFS NAND partition, how do I do that? Hope someone can give me some pointers in the right direction ... I would love to kick off WinCE from this hardware ;-) Cheers, Bernie -- You always have believers and scepticts.. A True inventor is always a believer.. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
