linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mirek23 <miroslaw.dach@psi.ch>
To: linuxppc-embedded@ozlabs.org
Subject: Re: zImage.elf loads but does not start
Date: Fri, 25 May 2007 08:23:57 -0700 (PDT)	[thread overview]
Message-ID: <10805157.post@talk.nabble.com> (raw)
In-Reply-To: <4656E1B9.9090308@ru.mvista.com>


Hi Andrei,

     Thank you very much for your suggestion. 
I am very grateful for all of your hints. They were always very valuable to
me.

I have set as you mentioned:
#define XPAR_DDR_0_SIZE                 0x2000000

And now all works fine!!!!

The root file system is mounted and I can execute whatever I like from the
rootfile system.
It was just my mistake that I did not noticed the memory size was wrong :(

After all of that I would like to use the GPIO driver to talk to the FPGA
part of the board.
Do you have some experience with that. 

in my xparameters_ml403.h I have two devices defined: LEDs and SWITCHES as
listed below

/* Definitions for peripheral LEDS_8BIT */
#define XPAR_LEDS_8BIT_BASEADDR 0x40000000
#define XPAR_LEDS_8BIT_HIGHADDR 0x4000FFFF
#define XPAR_LEDS_8BIT_DEVICE_ID 0
#define XPAR_LEDS_8BIT_INTERRUPT_PRESENT 0
#define XPAR_LEDS_8BIT_IS_DUAL 0


/* Definitions for peripheral DIP_SWITCHES_8BIT */
#define XPAR_DIP_SWITCHES_8BIT_BASEADDR 0x40020000
#define XPAR_DIP_SWITCHES_8BIT_HIGHADDR 0x4002FFFF
#define XPAR_DIP_SWITCHES_8BIT_DEVICE_ID 1
#define XPAR_DIP_SWITCHES_8BIT_INTERRUPT_PRESENT 0
#define XPAR_DIP_SWITCHES_8BIT_IS_DUAL 0

#define XPAR_GPIO_0_BASEADDR XPAR_LEDS_8BIT_BASEADDR
#define XPAR_GPIO_0_HIGHADDR XPAR_LEDS_8BIT_HIGHADDR
#define XPAR_GPIO_0_IS_DUAL XPAR_LEDS_8BIT_IS_DUAL
#define XPAR_GPIO_0_DEVICE_ID XPAR_LEDS_8BIT_DEVICE_ID
#define XPAR_GPIO_1_BASEADDR XPAR_DIP_SWITCHES_8BIT_BASEADDR
#define XPAR_GPIO_1_HIGHADDR XPAR_DIP_SWITCHES_8BIT_HIGHADDR
#define XPAR_GPIO_1_IS_DUAL XPAR_DIP_SWITCHES_8BIT_IS_DUAL
#define XPAR_GPIO_1_DEVICE_ID XPAR_DIP_SWITCHES_8BIT_DEVICE_ID

but I do not know how exactly to talk to them by means of the xgpio driver.



Best Regards and many many thanks for your support

Mirek




Andrei Konovalov wrote:
> 
> Mirek,
> 
> Miroslaw Dach wrote:
>> I do not know however if the stack is properly configured since I did not 
>> see any parameter in kernel which refers to the stack or heap. 
>> 
>> My bsp i.e xparameteres_ml403.h contains two macros:
>> #define XPAR_DDR_SDRAM_1_MEM0_BASEADDR 0x00000000
>> #define XPAR_DDR_SDRAM_1_MEM0_HIGHADDR 0x01FFFFFF
>> 
>> I have the feeling that they are ignored because I did not find anywhere 
>> in the kernel source those names. 
>> 
>> When kernel boots it prints at the beginning:
>> loaded at:     00400000 004F9138 
>> board data at: 004F7120 004F7138 
>> relocated to:  00404064 0040407C 
>> zimage at:     00404DF1 004F6BBB 
>> avail ram:     004FA000 04000000 
> 
> Have you fixed this?
> 
> For 32 MBytes of DRAM you should have
>    #define XPAR_DDR_0_SIZE                 0x2000000
> in your xparameters_ml403.h file.
> I can't recall the whole story, but EDK 8.2 doesn't
> add this #define when generating the xparameters file,
> so I had to add this line by hand for EDK 8.2 generated
> files. Probably earlier EDK versions did that automatically.
> 
> But your kernel (the bootwrapper to be precise) wouldn't compile
> if XPAR_DDR_0_SIZE were not defined...
> Do you use uboot?
> 
> Thanks,
> Andrei
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 

-- 
View this message in context: http://www.nabble.com/zImage.elf-loads-but-not-starts-tf3607582.html#a10805157
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

  reply	other threads:[~2007-05-25 15:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 15:10 zImage.elf loads but not starts Mirek23
2007-04-23 15:12 ` zImage.elf loads but does not start Mirek23
2007-04-23 16:11   ` Leonid
2007-04-24 16:55     ` Mirek23
2007-04-24 17:11       ` Andrei Konovalov
2007-05-04 15:04       ` Mirek23
2007-05-04 15:41         ` Andrei Konovalov
2007-05-08  9:46           ` Mirek23
2007-05-08 21:46             ` Leonid
2007-05-08 21:50               ` Adrian Craine
2007-05-09 15:02                 ` Charles Krinke
2007-05-10  8:45                   ` Mirek23
2007-05-10 16:05                     ` Mead, Joseph
2007-05-11 11:21                       ` Mirek23
2007-05-15 12:08                         ` Mirek23
2007-05-15 12:29                           ` Andrei Konovalov
2007-05-15 12:45                             ` Miroslaw Dach
2007-05-15 18:07                               ` Andrei Konovalov
2007-05-15 18:49                                 ` Miroslaw Dach
2007-05-18 12:43                                   ` Mirek23
2007-05-25 12:24                                     ` Mirek23
2007-05-25 13:16                                   ` Andrei Konovalov
2007-05-25 15:23                                     ` Mirek23 [this message]
2007-05-25 16:56                                       ` Advice needed Charles Krinke
2007-05-15 13:12                           ` zImage.elf loads but does not start Mead, Joseph
2007-05-18 13:28                             ` Mirek23
2007-04-23 16:24   ` Andrei Konovalov
2007-04-23 17:35   ` Grant Likely
2007-04-24 13:42     ` Mirek23

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=10805157.post@talk.nabble.com \
    --to=miroslaw.dach@psi.ch \
    --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 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).