linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Weber <thomas.weber.linux@googlemail.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Thomas Weber <thomas.weber.linux@googlemail.com>,
	Jarkko Nikula <jhnikula@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org
Subject: Re: 2.6.38 not booting on sbc8100 (aka devkit8000)
Date: Fri, 08 Apr 2011 09:25:35 +0200	[thread overview]
Message-ID: <4D9EB86F.1020601@gmail.com> (raw)
In-Reply-To: <BANLkTimUOyAWtgfoOSgQxXWdQehST5PDaA@mail.gmail.com>

Am 08.04.2011 10:03, schrieb Belisko Marek:
> On Fri, Apr 8, 2011 at 9:00 AM, Thomas Weber
> <thomas.weber.linux@googlemail.com> wrote:
>> Am 25.03.2011 08:53, schrieb Belisko Marek:
>>> On Fri, Mar 25, 2011 at 8:13 AM, Jarkko Nikula <jhnikula@gmail.com> wrote:
>>>> On Thu, 24 Mar 2011 12:00:30 -0700
>>>> Tony Lindgren <tony@atomide.com> wrote:
>>>>
>>>>> * Belisko Marek <marek.belisko@gmail.com> [110324 08:18]:
>>>>>> On Thu, Mar 24, 2011 at 4:18 PM, Tony Lindgren <tony@atomide.com> wrote:
>>>>>>
>>>>>>> * Belisko Marek <marek.belisko@gmail.com> [110324 02:50]:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Try to run 2.6.38 on my sbc8100
>>>>>>>> (use mach-type for devkit8000 because boards are similar) board but
>>>>>>>> when u-boot load it to ram I see just:
>>>> ...
>>>>>>> Can you enable DEBUG_LL and EARLY_PRINTK in your .config
>>>>>>> and add earlyprintk to your cmdline? Then you should see
>>>>>>> what goes wrong.
>>>>>>>
>>>>>> Forgot to mention. I already test this options but result is same like I
>>>>>> report in
>>>>>> first email.
>>>>>
>>>>> Maybe add some printk statements to start_kernel function in
>>>>> init/main.c and see if you get any output?
>>>>>
>>>> For earlyprintk worth to check also
>>>> arch/arm/plat-omap/include/plat/uncompress.h that there is entry for
>>>> sbc8100 (double check with devkit8000 as there is entry for it and if
>>>> you are re-using the mach-type).
>>> Thanks for hint. It was missing there so I add line:
>>> DEBUG_LL_OMAP3(3, devkit8000); (I'm convince linux to use mach-type
>>> for devkit8000)
>>> But still same result.
>>> Bytes transferred = 2898680 (2c3af8 hex)
>>> ## Booting kernel from Legacy Image at 80300000 ...
>>>    Image Name:   Linux-2.6.37-00001-g88870c9-dirt
>>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>>    Data Size:    2898616 Bytes =  2.8 MB
>>>    Load Address: 80008000
>>>    Entry Point:  80008000
>>>    Verifying Checksum ... OK
>>>    Loading Kernel Image ... OK
>>> OK
>>>
>>> Starting kernel ...
>>>
>>> Anybody with devkit8000 have success to run 2.6.37 kernel on board?

I run actually 2.6.38.
/ # uname -a
Linux 192.168.250.2 2.6.38-09676-ge63e9ed #8 Tue Mar 22 13:07:44 CET
2011 armv7l GNU/Linux

>>>>
>>>> --
>>>> Jarkko
>>>>
>>>
>>> regards,
>>>
>>> marek
>>>
>>
>> Hello Marek,
>>
>> yes, it is running. But your mach-type is wrong. Thats not the mach-type
>> from devkit8000, it is spark. What version of u-boot are you running?
> Well my u-boot return different mach-type but I always override it when
> kernel start (in arch/arm/kernel/head.S ldr r1,=0x.. mach-type).
> But still no luck.

What machine-id are you passing in? devkit8000 is 2330
Thomas
>>
>> Thomas
>>
>>
> 
> thanks,
> 
> marek
> 


  reply	other threads:[~2011-04-08  8:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  9:52 2.6.38 not booting on sbc8100 (aka devkit8000) Belisko Marek
2011-03-24 15:18 ` Tony Lindgren
     [not found]   ` <AANLkTik8PW4ad2_4=UxzvL-V7HcpH0=dg-Un5NLkj6Yi@mail.gmail.com>
2011-03-24 19:00     ` Tony Lindgren
2011-03-25  7:13       ` Jarkko Nikula
2011-03-25  7:53         ` Belisko Marek
2011-04-08  7:00           ` Thomas Weber
2011-04-08  8:03             ` Belisko Marek
2011-04-08  7:25               ` Thomas Weber [this message]
2011-03-25  7:57       ` Belisko Marek
2011-03-25  8:27         ` Jarkko Nikula
2011-03-25  9:32           ` Belisko Marek

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=4D9EB86F.1020601@gmail.com \
    --to=thomas.weber.linux@googlemail.com \
    --cc=jhnikula@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek.belisko@gmail.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

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

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