Re: mcf5272 hanging while relocating

NZG wrote on 31.05.2005 23:18 MET:
>>>The current 82 code had a lot of problems in
>>>the fec, timers, and initialization area. If the 5272 code is in a
>>>similar state then you may need to either use a preloader, or start with
>>>the patched 5282 base and modify it up to offer similar support to the
>>>5282.
>>
>>Guess there's some work ahead to get the rest running when u-boot finally
>>runs from RAM.
> 
> The 82 and 72 are similar in a lot of ways, you may be better off starting 
> from the working 82 code.

I will for sure take a look at all the 5282 changes. So far I've only take the 
ones that I think are really needed for the 5272 as well.

>>I did already do a diff from the EMAC release to the current release
>>version 1.1.2. Did you use a CVS version of the yet unreleased version
>>1.1.3 to base your changes on?
> 
> Actually Zach started the project, and I got the code from him, but I believe 
> he started with 1.1.3.
> 
> 
>>No I did not take this part of your code where you copy a small code
>>segment to the internal ram which activates the approtiate CSx or internal
>>flash. I don't see a need for that. I was woundering why that's really
>>needed - at least on the 5282.
> 
> When you first boot up, the processor will locate either it's external or 

DENX SELF, a more current version?

folks,
is there a more current version of the DENX SELF somewhere?
i am referring to
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/

following "how to build SELF" in the readme
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/README

i see that the paths in
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/URL
are either out of date or completely out of commission.

if someone has a pointer to a more current SELF recipe it
would be appreciated.  otherwise i'll have a go at updating
the current recipe.

OR

if someone has a pointer to a ppc rootfs build script that
would be appreciated as well.

thanks,
jim

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

NS9360 / NS 9750 config file

Re: Support for Samsung 1Giga bit NAND device

Ladislav Michl wrote:
> On Wed, Jun 16, 2004 at 01:53:52PM +0300, Pantelis Antoniou wrote:
> 
>>Andy Hawkins wrote:
>>
>>>Where can I get this patch from? Is this the one Laurent was referring
>>>to (on 30th April)? If so, you say in your message that it's not ready
>>>for inclusion yet...
>>>
>>>Thanks.
>>>
>>>Andy
>>>
>>
>>Search the list archives...
>>
>>It is ready for inclusion, it's just that the Samsung chips are a bit
>>strange and I have none to test.
> 
> 
> Pantelis,
> 
> yesterday I started hacking U-Boot to support Samsung K9F1G08U0M NAND
> flash (2k pages). After few hours I feel you were right - NAND code
> needs rewrite and I'd like to help you with that. Could you upload your
> patch (or even working tarball) somewhere? Searching mailing list
> archive is useless, because you posted patch as attachment and
> sourceforge's mailing list archive cannot handle that.
> 
> thanks,
> 	ladis
> 
> 

I'll try to send something today...

Regards

Pantelis

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

RE: tftpboot question

Hi,

>Hi all, and sorry for disturbing you again.
>I'm trying to load an image from a tftp server using tftpboot.
>Server is reachable, and running. Address of image is correct.
>U-boot contacts the right IP, then tries to load the image and intead
>of printing "#" as documented, prints "T" (it means timeout I
>suppose).
>But I continue getting an error message: "Retry count exceeded"
>Then the procedure starts again.

>What this behaviour can depend from?
>I excluded tftp configuration problems and network problems.

Are you running tftpd on a linux box?  Try turning off your firewall !
Sometimes UDP packets are blocked .... 

Try Tftping small files 1K and see if they work ... And If by chance you are
using montavista binaries for tftpd , in all probability they wont work with
u-boot.It did not work with a PQ2FADS-ZU board for me (even for their
customer support here in INDIA).

Cheers,

.Bharath.

EGO iS NotHinG wIthOuT ArrOgAncE tO BaCk iT uP..."

DISCLAIMER 
This message and any attachment(s) contained here are information that is confidential, proprietary to
HCL Technologies 
and its customers. Contents may be privileged or otherwise protected by law. The information is solely
intended for the 
individual or the entity it is addressed to. If you are not the intended recipient of this message, you are
not authorized to 
read, forward, print, retain, copy or disseminate this message or any part of it. If you have received this
e-mail in error, 
please notify the sender immediately by return e-mail and delete it from your computer

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

Re: compile u-boot with recent toolchain : symbols problem

---------- Forwarded message (without attachement) ----------

On 5/30/05, Wolfgang Denk <wd <at> denx.de> wrote:
> In message <c8f10050526062372e8a833 <at> mail.gmail.com> you wrote:
> >
> > I used to compile U-Boot with ELDK, but I currently need to work with
> > newer toolchain :
> >  - binutils-2.16
> >  - gcc-3.4.3
>
> This looks line a binutils problem, then. May I ask why you  have  to
> use binutils-2.16 ?

We want to test recent toolchain, to see if we should migrate or not
(our policy is to keep tools up-to-date, assuming fixes and new
features are more important than new bugs).

>
> And which exact board are we talking about?

We're talking about "ADS Virtex-II Pro Development board", I use ML300
port (and some parts of ML2 and MicroBlaze ports).

>
> > The "__u_boot_cmd_start" symbol value, generated with this new
> > toolchain, is wrong (U-Boot crashes when relocating the command
> > table).
>
> Can you please provide exact data, like the differences  between  the
> System.map  and  the  u-boot.map  files  when using binutils-2.16 and
> another, working version of binutils? [Please use the _same_  version
> of GCC for this comparison.]

The problem doesn't appear using binutils-2.16 with GCC provided by
ELDK... So it seems to be a GCC problem.

>
> > There are two new sections between "__u_boot_cmd_start" and
> > ".u_boot_cmd" address :
> >  - .data.rel.local
> >  - .data.rel
>
> Can you please show exactly what happens?

I attached 3 binaries :
- u-boot_ELDK, which is compiled with binutils-2.11.93.0.2 (20020207)
and gcc-2.95.4
- u-boot_binutils-2.16, which is compiled with binutils-2.16 and gcc-2.95.4
- u-boot_new_toolchain, which is compiled with binutils-2.16 and gcc-3.4.3

As you can see with this command, "__u_boot_cmd_start" is not at the
right place :
bash# powerpc-405-linux-gnu-nm u-boot_new_toolchain | sort
[...]
0002ab8c A __u_boot_cmd_start
0002ab8c D init_sequence
0002abb8 d failed
0002abbc D op_table
0002ac24 D stdio_names
0002ac30 d av_
0002b038 D z_errmsg
0002b058 D __u_boot_cmd_autoscr
0002b070 D __u_boot_cmd_bdinfo
0002b088 D __u_boot_cmd_reset
0002b0a0 D __u_boot_cmd_go
[...]

Since U-Boot uses the address of "__u_boot_cmd_start" to point to the
first entry of the command table, U-Boot crashes when relocating this
table. Here, the address of "__u_boot_cmd_start" should be 0x0002b058.

I noticed that symbol "init_sequence" belongs to section ".data.rel"
and symbols "failed", "op_table", "stdio_names", "av_" and "z_errmsg"
belong to section ".data.rel.local".

As you can see with this command, these new sections are above the
".u_boot_cmd" section :
bash# powerpc-405-linux-gnu-readelf -S u-boot_new_toolchain
[...]
  [ 1] .text             PROGBITS        00010000 000094 016684 00  AX  0   0  4
  [ 2] .resetvec         PROGBITS        00026684 016718 000004 00  AX  0   0  1
  [ 3] .rodata           PROGBITS        00026688 01671c 003500 00   A  0   0  4
  [ 4] .reloc            PROGBITS        00029c00 019c94 000ab8 00  WA  0   0  1
  [ 5] .data             PROGBITS        0002a6b8 01a74c 0004d4 00  WA  0   0  4
  [ 6] .data.rel         PROGBITS        0002ab8c 01ac20 00002c 00  WA  0   0  4
  [ 7] .data.rel.local   PROGBITS        0002abb8 01ac4c 0004a0 00  WA  0   0  4
  [ 8] .u_boot_cmd       PROGBITS        0002b058 01b0ec 000348 00  WA  0   0  4
[...]

So "__u_boot_cmd_start" points to the start of the ".data.rel" section
instead of the start of ".u_boot_cmd" section.

These new sections are disassembled in attached files
"section_.data.rel.local_dump" and "section_.data.rel_dump".

Thanks.

Best regards, Cedric VINCENT.

> >
> > I don't know what these (new) sections are, but the problem can be
> > solved in "u-boot.lds" :
> > -   __u_boot_cmd_start = .;
> >     .u_boot_cmd : { *(.u_boot_cmd) }
> >     __u_boot_cmd_end = .;
> > +  __u_boot_cmd_start = ADDR(.u_boot_cmd);
>
> I would like to understand this problem first before  deciding  about
> any fixes or patches.
>
> Thanks.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
> "The computer programmer is a creator of universes for which he alone
> is responsible. Universes of virtually unlimited  complexity  can  be
> created  in  the  form  of  computer  programs." - Joseph Weizenbaum,
> _Computer Power and Human Reason_
>

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

Re: PATCH for drivers/cfi_flash.c

Tolkay Orkun wrote:

> I do not have access to the patch file mentioned in that messages to compare

I have sent him a copy

Peter

-------------------------------------------------------------------------
Peter Pearse                                                      ARM Ltd
------------------------ Peter.Pearse <at> arm.com   -------------------------

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

pci_hose_read_config_byte() definition puzzles

Hi all,

I met a PCI init problem and happened to find several
PCI functions like pci_hose_read_config_byte() 
defined and used but no function prototype. It made
me really surprised. I hope I was in an unclear mind
to report it 

Attached is the grep result of u-boot-1.1.3 included
in ELDK3.1.1. Any thoughts?

Thanks in advance!

Sam

_________________________________________________________
Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂
http://cn.rd.yahoo.com/mail_cn/tag/yisou/music/*http://music.yisou.com/
美女明星应有尽有，搜遍美图、艳图和酷图
http://cn.rd.yahoo.com/mail_cn/tag/yisou/image/*http://image.yisou.com
1G就是1000兆，雅虎电邮自助扩容！
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/

[root <at> sam u-boot-1.1.3]# grep -r pci_hose_read_config_byte ./
./board/MAI/AmigaOneG3SE/articiaS_pci.c:        pci_hose_read_config_byte(hose, dev,
PCI_HEADER_TYPE, &header_type);
./board/MAI/AmigaOneG3SE/articiaS_pci.c:            pci_hose_read_config_byte(hose, dev, 0x0B, &c1);
./board/MAI/AmigaOneG3SE/articiaS_pci.c:            pci_hose_read_config_byte(hose, dev, 0x0A, &c2);
./board/MAI/AmigaOneG3SE/articiaS_pci.c:            pci_hose_read_config_byte(hose, dev,
PCI_HEADER_TYPE, &header_type);
./board/MAI/AmigaOneG3SE/articiaS_pci.c:                    pci_hose_read_config_byte(hose, dev,
PCI_SECONDARY_BUS, &secondary_bus);
./board/MAI/AmigaOneG3SE/articiaS_pci.c:            pci_hose_read_config_byte(&articiaS_hose, bridge,
0x3E, &agp_control_0);
./board/Marvell/db64360/pci.c:               pci_hose_read_config_byte_via_dword,
./board/Marvell/db64360/pci.c:               pci_hose_read_config_byte_via_dword,
./board/Marvell/db64460/pci.c:               pci_hose_read_config_byte_via_dword,
./board/Marvell/db64460/pci.c:               pci_hose_read_config_byte_via_dword,
./board/dave/common/pci.c:            pci_hose_read_config_byte_via_dword,
./board/esd/common/pci.c:             pci_hose_read_config_byte_via_dword,
./board/esd/cpci750/pci.c:                   pci_hose_read_config_byte_via_dword,
./board/esd/cpci750/pci.c:                   pci_hose_read_config_byte_via_dword,
./board/evb64260/pci.c:              pci_hose_read_config_byte_via_dword,
./board/evb64260/pci.c:              pci_hose_read_config_byte_via_dword,
./board/mpl/common/pci.c:       pci_hose_read_config_byte(hose, dev, PCI_INTERRUPT_PIN, &pin);
./board/mvblue/mvblue.c:        pci_hose_read_config_byte (hose, bridge, PCI_SECONDARY_BUS, &bus);
./board/sc520_cdp/sc520_cdp.c:  pci_hose_read_config_byte(hose, dev, PCI_INTERRUPT_PIN, &tmp_pin);
./board/sc520_spunk/sc520_spunk.c:      pci_hose_read_config_byte(hose, dev, PCI_INTERRUPT_PIN, &tmp_pin);
./cpu/mpc5xxx/pci_mpc5200.c:            pci_hose_read_config_byte_via_dword,
./cpu/mpc85xx/pci.c:            pci_hose_read_config_byte(hose,
./drivers/pci.c:        pci_hose_read_config_byte (hose, dev, PCI_INTERRUPT_PIN, &pin);
./drivers/pci.c:                pci_hose_read_config_byte(hose, dev, PCI_HEADER_TYPE, &header_type);
./drivers/pci.c:                            pci_hose_read_config_byte(hose, dev, PCI_INTERRUPT_LINE,
./drivers/pci_auto.c:           pci_hose_read_config_byte(hose, dev, PCI_CLASS_PROG, &prg_iface);
./include/pci.h:extern int pci_hose_read_config_byte(struct pci_controller *hose,
./include/pci.h:extern int pci_hose_read_config_byte_via_dword(struct pci_controller *hose,
[root <at> sam u-boot-1.1.3]#

Re: PATCH for drivers/cfi_flash.c

In message <429CCF13.6020809 <at> orkun.us> you wrote:
> 
> So it shall be ;) I'll submit a patch for this.

Thanks.

> Question 1: Should I redo my last patch or submit a patch on top of it 
> assuming that it will go through?

Please send a new summary patch (and if possible let  me  know  which
other,previously submitted patches this obsoletes).

Best regards,

Wolfgang Denk

--

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
One does not thank logic.
	-- Sarek, "Journey to Babel", stardate 3842.4

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

Re: pci_hose_read_config_byte() definition puzzles

In message <20050601070802.49747.qmail <at> web15902.mail.cnb.yahoo.com> you wrote:
>
> I met a PCI init problem and happened to find several
> PCI functions like pci_hose_read_config_byte() 
> defined and used but no function prototype. It made
...
> Attached is the grep result of u-boot-1.1.3 included
> in ELDK3.1.1. Any thoughts?
...
> ./include/pci.h:extern int pci_hose_read_config_byte(struct pci_controller *hose,

This looks very much like a prototype definition to me.

Best regards,

Wolfgang Denk

--

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd <at> denx.de
Once at a social gathering, Gladstone said to Disraeli,  "I  predict,
Sir,  that  you  will die either by hanging or of some vile disease".
Disraeli replied, "That all depends, Sir, upon whether I embrace your
principles or your mistress."

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005