All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: schardt <g.schardt@fz-juelich.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Newbie and linux on virtex-II ppc
Date: Mon, 27 Aug 2007 07:09:46 -0600	[thread overview]
Message-ID: <fa686aa40708270609x453092eye6eaf83b65ac2dee@mail.gmail.com> (raw)
In-Reply-To: <46D2C9A5.9030708@fz-juelich.de>

On 8/27/07, schardt <g.schardt@fz-juelich.de> wrote:
> im a student from germany and i try to run linux on a virtex-II with
> integrated powerpc.
> i use the developer board DS-DB-2VP4/7-FG456 from Memec ( i think its
> now avnet)
>
> what is running :
>
>   - Xilinx EDK project (standalone program running fine, and BSP files
> are generated)
>     the project has only one UARTLITE, 82MB SDRAM and a few kByte
> blockram, and the systemace interface
>
>   - crosscompiler toolchain works
>
>   - after modified some defines in the xparameters.h i got a linux 2.4.
> kernel (linuxppc) without compiler errors

I strongly recommend trying to bring up a 2.6 kernel, it's much easier.

>     and yes, the uartlite driver is enabled :)

Don't modify xparams by hand; it's not worth the trouble.  Go into
software setting in your EDK project and select 'linux-2.6' as the OS.
 Generate the libraries and copy the generated xparameters_ml40x.h
into your kernel tree.

>
>
> but, when downloading the zImage.elf via XMD to the SDRAM and starting
> it with the run command nothing happens , or  i think that nothings
> happens because the serial port is quiet.

You can always use System.map in the kernel tree to find out where
__log_buf was linked to.  Look at that location with the debugger to
see if there is a crash message that didn't get printed out.

>
> is it possible to run a kernel that way ? or need i some kind of
> bootloader ?
> or is this complete the wrong way ?

Yes, I use this same method to bring up a kernel on Virtex boards
which don't have a bootloader.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-08-27 13:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27 12:55 Newbie and linux on virtex-II ppc schardt
2007-08-27 13:09 ` Grant Likely [this message]
2007-08-27 14:17   ` schardt
2007-08-27 14:21     ` Grant Likely
2007-08-28  6:51   ` schardt
     [not found]   ` <46D2CFFB.6050602@fz-juelich.de>
     [not found]     ` <fa686aa40708270719s1fd230e9g188948ef02b3eda7@mail.gmail.com>
     [not found]       ` <46D41298.7060109@fz-juelich.de>
2007-08-28 13:06         ` Grant Likely
2007-08-28 13:24           ` schardt
2007-08-28 13:30             ` Grant Likely
2007-08-28 13:39               ` schardt
2007-08-28 13:55                 ` Grant Likely
2007-08-28 14:12                   ` schardt
2007-08-28 14:43                     ` Grant Likely
2007-08-28 14:44                       ` Grant Likely
2007-08-29  9:29                         ` schardt
2007-08-29 13:31                           ` schardt
2007-08-29 14:44                             ` Grant Likely
     [not found]                               ` <46DBA4F9.2010703@fz-juelich.de>
2007-09-03 13:41                                 ` Grant Likely
2007-08-27 13:54 ` Ming Liu

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=fa686aa40708270609x453092eye6eaf83b65ac2dee@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=g.schardt@fz-juelich.de \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.