[U-Boot] which u-boot build config to choose for kirkwood?

[U-Boot] which u-boot build config to choose for kirkwood?

[JPT]

Hi,

I finally succeeded in booting my kirkwood board from UART. But this did 
not help. The Netgear uboot 1.1.4 still hangs after loading the network 
hardware. Since I was messing with the uboot-env before it broke, this 
is most likely the cause of the problems.

To access the uboot-env I've got two alternatives I can think of:
- Boot a current mainline U-boot to get the uboot console and access to 
the uboot-env in NAND.

- Boot into (kirkwood?) debug console using the magic bytes. I once 
achieved to get it, but since I don't. And I don't know anything about 
how to use it. (any hints?)
Kirkwood UART boot is integrated into the current mainline uboot, but 
debug console isn't, right?

Well, I decided to build uboot myself. To access uboot env in NAND I 
only need working: CPU, NAND, RAM, UART. Correct?
Could you please give some hints on how to choose the right config?

Most detailed hw info I got from: http://natisbad.org/NAS

CPU:
Marvell 82F6282 SoC (aka ARMADA 300) from Kirkwood family. 
ARMv5TE-compatible
cat /proc/cpuinfo
Processor       : Feroceon 88FR131 rev 1 (v5l)
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1
Hardware        : Feroceon-KW

RAM
2x 128MB DDR3 1333 Hynix H5TQ1G83DFR-H9C @ 533Mhz?

NAND
Hynix H27U1G8F2BTR

UART
integrated into Marvell SoC

I am not sure about this one, and if I need it:
ATMEL AT25F512B-SSH
512 Kilobit SPI flash.


btw, is uboot-env 1.1.4 compatible to recent uboot?


thanks,

Jan

[U-Boot] problem building uboot

[JPT]

Hi,

I decided to just try a random kirkwood config.
but I've got a problem with linking:

$ make all
...
armv5te-gcc  -g  -Os   -fno-common -ffixed-r8 -msoft-float  -D__KERNEL__ 
-DCONFIG_SYS_TEXT_BASE=0x00600000 
-I/home/jan/src/u-boot-2013.01.01/include -fno-builtin -ffreestanding 
-nostdinc -isystem 
/opt/eldk-5.3/armv5te/sysroots/i686-eldk-linux/usr/lib/armv5te-linux-gnueabi/gcc/arm-linux-gnueabi/4.7.2/include 
-pipe  -DCONFIG_ARM -D__ARM__ -marm -mno-thumb-interwork 
-mabi=aapcs-linux -march=armv5te -Wall -Wstrict-prototypes 
-fno-stack-protector -Wno-format-nonliteral -Wno-format-security 
-fstack-usage     -o cache.o cache.c -c
armv5te-ld.bfd -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed   -r -o 
libkirkwood.o  cpu.o dram.o mpp.o timer.o cache.o
armv5te-ld.bfd: unrecognized option '-Wl,-O1'
armv5te-ld.bfd: use the --help option for usage information
make[1]: *** [libkirkwood.o] Fehler 1
make: *** [arch/arm/cpu/arm926ejs/kirkwood/libkirkwood.o] Fehler 2

$ which armv5te-ld.bfd
/opt/eldk-5.3/armv5te/sysroots/i686-eldk-linux/usr/bin/armv5te-linux-gnueabi/armv5te-ld.bfd

$ armv5te-ld.bfd --version
GNU ld (GNU Binutils) 2.22
Copyright 2011 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later 
version.
This program has absolutely no warranty.

now what?

thanks,

Jan



Am 07.04.2013 12:06, schrieb JPT:
> Hi,
>
> Well, I decided to build uboot myself. To access uboot env in NAND I
> only need working: CPU, NAND, RAM, UART. Correct?
> Could you please give some hints on how to choose the right config?

[U-Boot] problem building uboot

[Wolfgang Denk]

Dear JPT,

In message <kjsgvv$o4i$1@ger.gmane.org> you wrote:
> 
> I decided to just try a random kirkwood config.
> but I've got a problem with linking:
...
> armv5te-ld.bfd: unrecognized option '-Wl,-O1'
> armv5te-ld.bfd: use the --help option for usage information

Reading the FAQ [1] might help...

[1] http://www.denx.de/wiki/view/ELDK-5/FrequentlyAskedQuestionsAndAnswers#ELDK_5_3_Known_Issues_and_Workar

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Bus error -- please leave by the rear door.

[U-Boot] Question about Automatic Updates

[TigerLiu at viatech.com.cn]

Hi, experts:
I found an Automatic Updates digest in this web page:
http://www.denx.de/wiki/view/U-Bootdoc/AutomaticUpdates

So, my question is:
1. Can uboot support this feature now?
   I could not find key word "firmware.img" etc in u-boot source code
package.

Best wishes,

[U-Boot] Question about Automatic Updates

[Wolfgang Denk]

Dear TigerLiu at viatech.com.cn,

In message <FE7ADED5C2218B4786C09CD97DC4C49F812619@exchbj02.viatech.com.bj> you wrote:
>
> I found an Automatic Updates digest in this web page:
> http://www.denx.de/wiki/view/U-Bootdoc/AutomaticUpdates
> 
> So, my question is:
> 1. Can uboot support this feature now?

This has been implemented (actually in a number of veriants) for
several boards in U-Boot.

>    I could not find key word "firmware.img" etc in u-boot source code
> package.

Most of this is usually done as shell scripts run by U-Boot. These
scripts are usually proprietary code ant not part of the U-Boot
distribution.

Mainline U-Boot contains all the needed features, and implementing
such an update mechanism is relatively straightforward.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
While most peoples' opinions change, the conviction of their correct-
ness never does.

[U-Boot] Question about Automatic Updates

[Jagan Teki]

Hi,

On Mon, Apr 8, 2013 at 11:00 AM, Wolfgang Denk <wd@denx.de> wrote:
> Dear TigerLiu at viatech.com.cn,
>
> In message <FE7ADED5C2218B4786C09CD97DC4C49F812619@exchbj02.viatech.com.bj> you wrote:
>>
>> I found an Automatic Updates digest in this web page:
>> http://www.denx.de/wiki/view/U-Bootdoc/AutomaticUpdates
>>
>> So, my question is:
>> 1. Can uboot support this feature now?
>
> This has been implemented (actually in a number of veriants) for
> several boards in U-Boot.
>
>>    I could not find key word "firmware.img" etc in u-boot source code
>> package.
>
> Most of this is usually done as shell scripts run by U-Boot. These
> scripts are usually proprietary code ant not part of the U-Boot
> distribution.
>
> Mainline U-Boot contains all the needed features, and implementing
> such an update mechanism is relatively straightforward.

Any README doc for using or creating automation for specific board.
Request for help.

Thanks,
Jagan.

>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> While most peoples' opinions change, the conviction of their correct-
> ness never does.
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] Question about Automatic Updates

[Wolfgang Denk]

Dear Jagan Teki,

In message <CAD6G_RRNUZQWFPrBxVWMmUFax7=e=61P4TF06xWkmTurCx5Jzw@mail.gmail.com> you wrote:
> 
> > Most of this is usually done as shell scripts run by U-Boot. These
> > scripts are usually proprietary code ant not part of the U-Boot
> > distribution.
> >
> > Mainline U-Boot contains all the needed features, and implementing
> > such an update mechanism is relatively straightforward.
> 
> Any README doc for using or creating automation for specific board.
> Request for help.

As mentioned, most of the existing scripts are proprietary code and
not released as part of the U-Boot distribution.

As for the public parts, search for example for auto_update.[ch] in
the source tree...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Unix is like a toll road on which you have to stop every 50  feet  to
pay another nickel. But hey! You only feel 5 cents poorer each time.
                 - Larry Wall in <1992Aug13.192357.15731@netlabs.com>

[U-Boot] build succeeded, what now?

[JPT]

Hi,

Ok, I succeeded in building, used mv88f6281gtw_ge_config.
I cannot find any hints on how to continue in the manual.
So I tried with what I already know or simply guessed.

I added a header to the file u-boot.bin using the netgear provided doimage.

After uploading the image, nothing happens.

I am wondering:
- shouldn't there be a device tree to provide to linux?
- the uboot.bin is 300KiB. the old netgear one was 1,5MiB. How comes?
- is there any way to separate the original rom into pieces like uboot 
binary, device tree, etc?

thanks,

Jan

[U-Boot] how to troubleshoot when u-boot is stuck

[JPT]

I did not succeed trying the "build myself" way yet.
Maybe someone is able to give a hint.

Since I messed with the u-boot-env from linux prompt, u-boot stops right 
after "Net:   egiga0 [PRIME]" which is just before "Hit any key to stop 
autoboot"
Isn't there anything I can do? Anything I can learn from this?


DRAM unknown CAL  tRP = 8 tRAS = 20 tRCD=8
DRAM CS[0] base 0x00000000   size 256MB
DRAM Total size 256MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
Flash:  0 kB
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Switch On !
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0


thanks,

Jan