* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
@ 2013-01-03 20:56 John Stile
2013-01-03 21:07 ` Wolfgang Denk
0 siblings, 1 reply; 9+ messages in thread
From: John Stile @ 2013-01-03 20:56 UTC (permalink / raw)
To: u-boot
Is it possible to add my kernel to the rootfs partition rather than have
a separate partition?
I am using U-Boot 1.3.4, on a at91sam9g20ek (256Mb Nand, 8Mb Nor), and
use the sam-ba firmware upload tool.
I'd like to put everything on nand, ignore nor, and hold redundant
areas, in perpetration for firmware updates.
My starting point is from the atmel Linux4SAM project:
Nor layout:
Logical address: 0xD0000000
size Address-Range
16895 Area 0: D0000000 to D00041FF (RO) Bootstrap
16895 Area 1: D0004200 to D00083FF Environment
236543 Area 2: D0008400 to D0041FFF (RO) U-Boot
2152687 Area 3: D0042000 to D0251FFF Kernel
6217727 Area 4: D0252000 to D083FFFF FS
Nand layout:
4194304: 0x000000000000-0x000000400000 : "bootstrap/uboot/kernel"
62914560 0x000000400000-0x000004000000 : "rootfs"
201226592 0x000004000000-0x000010000000 : "data"
bootargs:
mem=64M console=ttyS0,115200
mtdparts=atmel_nand:4M(bootstrap/uboot/kernel)ro,60M(rootfs),-(data)
root=/dev/mtdblock1 rw rootfstype=jffs2
bootcmd:
cp.b 0xD0042000 0x22200000 0x0019306C; bootm 0x22200000
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-03 20:56 [U-Boot] is it possilbe to have uboot find the kernel in the file system? John Stile
@ 2013-01-03 21:07 ` Wolfgang Denk
2013-01-04 2:06 ` John Stile
0 siblings, 1 reply; 9+ messages in thread
From: Wolfgang Denk @ 2013-01-03 21:07 UTC (permalink / raw)
To: u-boot
Dear John Stile,
In message <1357246601.7939.128.camel@genx> you wrote:
> Is it possible to add my kernel to the rootfs partition rather than have
> a separate partition?
Yes, it is - assuming you use a storage device and a file system type
supported by U-Boot.
> I am using U-Boot 1.3.4, on a at91sam9g20ek (256Mb Nand, 8Mb Nor), and
> use the sam-ba firmware upload tool.
Oops... v1.3.4 is way over 4 years old. Please consider it hopelessly
obsoleted and completely unsupported.
> I'd like to put everything on nand, ignore nor, and hold redundant
> areas, in perpetration for firmware updates.
For NAND flash, you should use UBI UBIFS (and yes, U-Boot can load
from a UBIFS file system). The first step to this goal is an update
to recent code, though.
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
When in doubt, mumble; when in trouble, delegate; when in charge,
ponder. -- James H. Boren
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-03 21:07 ` Wolfgang Denk
@ 2013-01-04 2:06 ` John Stile
2013-01-04 8:00 ` Wolfgang Denk
0 siblings, 1 reply; 9+ messages in thread
From: John Stile @ 2013-01-04 2:06 UTC (permalink / raw)
To: u-boot
On Thu, 2013-01-03 at 22:07 +0100, Wolfgang Denk wrote:
> Dear John Stile,
>
> In message <1357246601.7939.128.camel@genx> you wrote:
> > Is it possible to add my kernel to the rootfs partition rather than have
> > a separate partition?
>
> Yes, it is - assuming you use a storage device and a file system type
> supported by U-Boot.
>
> > I am using U-Boot 1.3.4, on a at91sam9g20ek (256Mb Nand, 8Mb Nor), and
> > use the sam-ba firmware upload tool.
>
> Oops... v1.3.4 is way over 4 years old. Please consider it hopelessly
> obsoleted and completely unsupported.
>
> > I'd like to put everything on nand, ignore nor, and hold redundant
> > areas, in perpetration for firmware updates.
>
> For NAND flash, you should use UBI UBIFS (and yes, U-Boot can load
> from a UBIFS file system). The first step to this goal is an update
> to recent code, though.
>
> Best regards,
>
> Wolfgang Denk
>
u-boot-2012.10.tar.bz2 does not have support for the at91sam9g20ek
I treid to apply my patches for u-boot-1.3.4, but they are way too old.
Is there a newer patch set?
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-04 2:06 ` John Stile
@ 2013-01-04 8:00 ` Wolfgang Denk
2013-01-04 18:19 ` John Stile
0 siblings, 1 reply; 9+ messages in thread
From: Wolfgang Denk @ 2013-01-04 8:00 UTC (permalink / raw)
To: u-boot
Dear John Stile,
In message <1357265217.7939.131.camel@genx> you wrote:
>
> u-boot-2012.10.tar.bz2 does not have support for the at91sam9g20ek
> I treid to apply my patches for u-boot-1.3.4, but they are way too old.
> Is there a newer patch set?
I see the following board configurations supported in current mainline
code: at91sam9g20ek_nandflash, at91sam9g20ek_dataflash_cs0, and
at91sam9g20ek_dataflash_cs1 . Anything wrong with those?
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
"The whole problem with the world is that fools and fanatics are
always so certain of themselves, but wiser people so full of doubts."
- Bertrand Russell
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-04 8:00 ` Wolfgang Denk
@ 2013-01-04 18:19 ` John Stile
2013-01-04 20:46 ` Jeroen Hofstee
2013-01-04 22:12 ` Wolfgang Denk
0 siblings, 2 replies; 9+ messages in thread
From: John Stile @ 2013-01-04 18:19 UTC (permalink / raw)
To: u-boot
On Fri, 2013-01-04 at 09:00 +0100, Wolfgang Denk wrote:
> Dear John Stile,
>
> In message <1357265217.7939.131.camel@genx> you wrote:
> >
> > u-boot-2012.10.tar.bz2 does not have support for the at91sam9g20ek
> > I treid to apply my patches for u-boot-1.3.4, but they are way too old.
> > Is there a newer patch set?
>
> I see the following board configurations supported in current mainline
> code: at91sam9g20ek_nandflash, at91sam9g20ek_dataflash_cs0, and
> at91sam9g20ek_dataflash_cs1 . Anything wrong with those?
I'm going to have to wrestle with buildroot's uboot configuration or
something... But it would be helpful to know what he build error means.
my buildroot .config sets:
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek"
BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="ftp://ftp.denx.de/pub/u-boot/u-boot-2012.10.tar.bz2"
BR2_TARGET_UBOOT_VERSION="custom"
BR2_TARGET_UBOOT_FORMAT_BIN=y
BR2_TARGET_AT91BOOTSTRAP=y
BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9g20ek"
BR2_TARGET_AT91BOOTSTRAP_DATAFLASH=y
BR2_TARGET_AT91BOOTSTRAP_MEMORY="dataflash"
uboot build error:
>>> uboot custom Configuring
PATH="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/bin:/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin:/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/sbin/:/home/jstile/Komodo-Edit-7/bin:/home/jstile/Komodo-Edit-7/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.4:/usr/games/bin:/home/jstile/bin:/home/jstile/bin" AR="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ar" AS="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-as" LD="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ld" NM="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-nm" CC="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc" GCC="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc" CPP="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-cpp" CXX="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-g++" FC="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gfortran" RANLIB="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ranlib" STRIP="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-strip" OBJCOPY="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-objcopy" OBJDUMP="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-objdump" AR_FOR_BUILD="/usr/bin/ar" AS_FOR_BUILD="/usr/bin/as" CC_FOR_BUILD="/usr/bin/gcc" GCC_FOR_BUILD="/usr/bin/gcc" CXX_FOR_BUILD="/usr/bin/g++" FC_FOR_BUILD="/usr/bin/ld" LD_FOR_BUILD="/usr/bin/ld" CFLAGS_FOR_BUILD="-O2 -I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/include -I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/include" CXXFLAGS_FOR_BUILD="-I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/include -I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/include" LDFLAGS_FOR_BUILD="-L/home/jstile/svn_rmserver/buildroot-2011.11/output/host/lib -L/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/lib -Wl,-rpath,/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/lib" FCFLAGS_FOR_BUILD="" DEFAULT_ASSEMBLER="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-as" DEFAULT_LINKER="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ld" CFLAGS="-pipe -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64" CXXFLAGS="-pipe -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64" LDFLAGS="" FCFLAGS="" PKG_CONFIG="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/pkg-config" PERLLIB="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/lib/perl" STAGING_DIR="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot" CONFIG_NOSOFTFLOAT=1 /usr/bin/make -j2 -C /home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom CROSS_COMPILE=" /home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-" ARCH=arm at91sam9g20ek_config
make[1]: Entering directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
make[1]: Leaving directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
make[1]: Entering directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
make: *** No rule to make target `at91sam9g20ek_config'. Stop.
make[1]: *** [at91sam9g20ek_config] Error 1
make[1]: Leaving directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
make: *** [/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom/.stamp_configured] Error 2
What should the target be?
Maybe my buildroot is also so old it doesn't support the new uboot
configuration syntax?
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-04 18:19 ` John Stile
@ 2013-01-04 20:46 ` Jeroen Hofstee
2013-01-04 22:12 ` Wolfgang Denk
1 sibling, 0 replies; 9+ messages in thread
From: Jeroen Hofstee @ 2013-01-04 20:46 UTC (permalink / raw)
To: u-boot
Hello John,
On 01/04/2013 07:19 PM, John Stile wrote:
> On Fri, 2013-01-04 at 09:00 +0100, Wolfgang Denk wrote:
>> Dear John Stile,
>>
>> In message <1357265217.7939.131.camel@genx> you wrote:
>>> u-boot-2012.10.tar.bz2 does not have support for the at91sam9g20ek
>>> I treid to apply my patches for u-boot-1.3.4, but they are way too old.
>>> Is there a newer patch set?
>> I see the following board configurations supported in current mainline
>> code: at91sam9g20ek_nandflash, at91sam9g20ek_dataflash_cs0, and
>> at91sam9g20ek_dataflash_cs1 . Anything wrong with those?
note the trailing _nandflash, _dataflash_cs0 etc.
> I'm going to have to wrestle with buildroot's uboot configuration or
> something... But it would be helpful to know what he build error means.
>
> my buildroot .config sets:
> BR2_TARGET_UBOOT=y
> BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek"
> BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
> BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="ftp://ftp.denx.de/pub/u-boot/u-boot-2012.10.tar.bz2"
> BR2_TARGET_UBOOT_VERSION="custom"
> BR2_TARGET_UBOOT_FORMAT_BIN=y
> BR2_TARGET_AT91BOOTSTRAP=y
> BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9g20ek"
> BR2_TARGET_AT91BOOTSTRAP_DATAFLASH=y
> BR2_TARGET_AT91BOOTSTRAP_MEMORY="dataflash"
>
> uboot build error:
>>>> uboot custom Configuring
> PATH="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/bin:/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin:/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/sbin/:/home/jstile/Komodo-Edit-7/bin:/home/jstile/Komodo-Edit-7/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.4:/usr/games/bin:/home/jstile/bin:/home/jstile/bin" AR="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ar" AS="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-as" LD="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ld" NM="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-nm" CC="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc" GCC="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-lin
> ux-uclibcgnueabi-gcc" CPP="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-cpp" CXX="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-g++" FC="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-gfortran" RANLIB="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ranlib" STRIP="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-strip" OBJCOPY="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-objcopy" OBJDUMP="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-objdump" AR_FOR_BUILD="/usr/bin/ar" AS_FOR_BUILD="/usr/bin/as" CC_FOR_BUILD="/usr/bin/gcc" GCC_FOR_BUILD="/usr/bin/gcc" CXX_FOR_BUILD="/usr/bin/g++" FC_FOR_BUILD="/usr/bin/ld" LD_FOR_BUILD="/usr/bin/ld" C
> FLAGS_FOR_BUILD="-O2 -I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/include -I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/include" CXXFLAGS_FOR_BUILD="-I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/include -I/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/include" LDFLAGS_FOR_BUILD="-L/home/jstile/svn_rmserver/buildroot-2011.11/output/host/lib -L/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/lib -Wl,-rpath,/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/lib" FCFLAGS_FOR_BUILD="" DEFAULT_ASSEMBLER="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-as" DEFAULT_LINKER="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-ld" CFLAGS="-pipe -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64" CXXFLAGS="-pipe -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64" LDFLAGS="" FCFLAGS="" P
> KG_CONFIG="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/pkg-config" PERLLIB="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/lib/perl" STAGING_DIR="/home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot" CONFIG_NOSOFTFLOAT=1 /usr/bin/make -j2 -C /home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom CROSS_COMPILE=" /home/jstile/svn_rmserver/buildroot-2011.11/output/host/usr/bin/arm-unknown-linux-uclibcgnueabi-" ARCH=arm at91sam9g20ek_config
last word, misses the _nandflash, you should get it there somehow..
> make[1]: Entering directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
> make[1]: Leaving directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
> make[1]: Entering directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
> make: *** No rule to make target `at91sam9g20ek_config'. Stop.
> make[1]: *** [at91sam9g20ek_config] Error 1
> make[1]: Leaving directory `/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom'
> make: *** [/home/jstile/svn_rmserver/buildroot-2011.11/output/build/uboot-custom/.stamp_configured] Error 2
>
> What should the target be?
one of the ones listed in boards.cfg with _config appended, e.g.
at91sam9g20ek_nandflash_config
> Maybe my buildroot is also so old it doesn't support the new uboot
> configuration syntax?
no idea, since I don't use buildroot, but you might get around it by setting
BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_nandflash"
Regards,,
Jeroen
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-04 18:19 ` John Stile
2013-01-04 20:46 ` Jeroen Hofstee
@ 2013-01-04 22:12 ` Wolfgang Denk
2013-01-05 1:25 ` John Stile
1 sibling, 1 reply; 9+ messages in thread
From: Wolfgang Denk @ 2013-01-04 22:12 UTC (permalink / raw)
To: u-boot
Dear John Stile,
In message <1357323597.6335.19.camel@genx.eng.msli.com> you wrote:
>
> > I see the following board configurations supported in current mainline
> > code: at91sam9g20ek_nandflash, at91sam9g20ek_dataflash_cs0, and
> > at91sam9g20ek_dataflash_cs1 . Anything wrong with those?
>
> I'm going to have to wrestle with buildroot's uboot configuration or
> something... But it would be helpful to know what he build error means.
...
> BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek"
I don't know what "BOARDNAME" is exactly supposed to mean here, but
probably this should be one of the configuration names I listed above.
...
> BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9g20ek"
Or this? I have no idea what the difference between BOARDNAME and
BOARD might be...
> BR2_TARGET_AT91BOOTSTRAP_MEMORY="dataflash"
OK, it appears you want one of the at91sam9g20ek_dataflash_csX
configurations...
> make: *** No rule to make target `at91sam9g20ek_config'. Stop.
Well, as mentioned in my previous message, the known config names are
"at91sam9g20ek_nandflash", "at91sam9g20ek_dataflash_cs0", and
"at91sam9g20ek_dataflash_cs1"; plain "at91sam9g20ek" is NOT a known
config name.
> What should the target be?
Depending whether you want to use CS0 or CS1 to address the dataflash
on your board, it should probably be "at91sam9g20ek_dataflash_cs0"
or "at91sam9g20ek_dataflash_cs1".
> Maybe my buildroot is also so old it doesn't support the new uboot
> configuration syntax?
I think it's just misconfigured.
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
I don't see any direct evidence ... but, then, my crystal ball is in
dire need of an ectoplasmic upgrade. :-) -- Howard Smith
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-04 22:12 ` Wolfgang Denk
@ 2013-01-05 1:25 ` John Stile
2013-01-05 1:53 ` Bo Shen
0 siblings, 1 reply; 9+ messages in thread
From: John Stile @ 2013-01-05 1:25 UTC (permalink / raw)
To: u-boot
On Fri, 2013-01-04 at 23:12 +0100, Wolfgang Denk wrote:
> Dear John Stile,
>
> In message <1357323597.6335.19.camel@genx.eng.msli.com> you wrote:
> >
> > > I see the following board configurations supported in current mainline
> > > code: at91sam9g20ek_nandflash, at91sam9g20ek_dataflash_cs0, and
> > > at91sam9g20ek_dataflash_cs1 . Anything wrong with those?
> >
> > I'm going to have to wrestle with buildroot's uboot configuration or
> > something... But it would be helpful to know what he build error means.
> ...
> > BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek"
>
> I don't know what "BOARDNAME" is exactly supposed to mean here, but
> probably this should be one of the configuration names I listed above.
>
> ...
> > BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9g20ek"
>
> Or this? I have no idea what the difference between BOARDNAME and
> BOARD might be...
>
> > BR2_TARGET_AT91BOOTSTRAP_MEMORY="dataflash"
>
> OK, it appears you want one of the at91sam9g20ek_dataflash_csX
> configurations...
>
> > make: *** No rule to make target `at91sam9g20ek_config'. Stop.
>
> Well, as mentioned in my previous message, the known config names are
> "at91sam9g20ek_nandflash", "at91sam9g20ek_dataflash_cs0", and
> "at91sam9g20ek_dataflash_cs1"; plain "at91sam9g20ek" is NOT a known
> config name.
>
> > What should the target be?
>
> Depending whether you want to use CS0 or CS1 to address the dataflash
> on your board, it should probably be "at91sam9g20ek_dataflash_cs0"
> or "at91sam9g20ek_dataflash_cs1".
>
> > Maybe my buildroot is also so old it doesn't support the new uboot
> > configuration syntax?
>
> I think it's just misconfigured.
>
> Best regards,
>
> Wolfgang Denk
>
u-boot-2012.10 build does compile with buildroot's .conf settings
BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_dataflash_cs1"
or
BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_nandflash"
But after writing my ubootEnvtFileDataFlash.bin to NOR with sam-ba
utility (which works with the u-boot-1.3.4), it is not found by the ROM
boot loader, so I'm not sure where to go for help.
I know ROM boot loader executes what ever it finds at NOR start
(0xD0000000) +0x00008400.
Does anyone else use a at91sam uboot-2012 and sam-ba, or have any other
suggestions?
^ permalink raw reply [flat|nested] 9+ messages in thread
* [U-Boot] is it possilbe to have uboot find the kernel in the file system?
2013-01-05 1:25 ` John Stile
@ 2013-01-05 1:53 ` Bo Shen
0 siblings, 0 replies; 9+ messages in thread
From: Bo Shen @ 2013-01-05 1:53 UTC (permalink / raw)
To: u-boot
Hi John Stile,
On 01/05/2013 09:25 AM, John Stile wrote:
>
> u-boot-2012.10 build does compile with buildroot's .conf settings
> BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_dataflash_cs1"
> or
> BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_nandflash"
>
> But after writing my ubootEnvtFileDataFlash.bin to NOR with sam-ba
> utility (which works with the u-boot-1.3.4), it is not found by the ROM
> boot loader, so I'm not sure where to go for help.
>
> I know ROM boot loader executes what ever it finds at NOR start
> (0xD0000000) +0x00008400.
>
> Does anyone else use a at91sam uboot-2012 and sam-ba, or have any other
> suggestions?
Please check the text base of u-boot for at91sam9g20ek.
If you use the old bootstrap, it jump to 0x23f00000 after reading
u-boot, while the v2012.10 u-boot use 0x21f00000 as its text base.
If so, you can change u-boot or bootstrap to keep the two address the same.
Best Regards,
Bo Shen
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-01-05 1:53 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-03 20:56 [U-Boot] is it possilbe to have uboot find the kernel in the file system? John Stile
2013-01-03 21:07 ` Wolfgang Denk
2013-01-04 2:06 ` John Stile
2013-01-04 8:00 ` Wolfgang Denk
2013-01-04 18:19 ` John Stile
2013-01-04 20:46 ` Jeroen Hofstee
2013-01-04 22:12 ` Wolfgang Denk
2013-01-05 1:25 ` John Stile
2013-01-05 1:53 ` Bo Shen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox