Re: [U-Boot] [PATCH] TQM5200 HIGHBOOT Makefile patch
On Sun, 7 Sep 2008 01:10:15 +0200 Wolfgang wrote:
Dear Pedro Luis D. L.,
In message [EMAIL PROTECTED] you wrote:
I don't know the normal procedure, if I should send the patch to Wolfgang o=
r someone else, but I found a problem with Makefile and TQM5200 HIGHBOOT co=
nfig in Makefile. I think this problem is also in previous versions since t=
qm boards where moved under tqc folder.
Please use a line length not longer than some 70+ characters.
Sorry, you told me before and I forgot. I use web email and can not
change this option, so I have to do it manually.
The patch is:
--- a/Makefile 2008-09-04 14:55:05.0 +0200
+++ b/Makefile 2008-09-04 14:56:14.0 +0200
@@ -755,7 +755,7 @@
echo #define CONFIG_TQM5200_B
$(obj)include/config.h ; \
}
@[ -z $(findstring HIGHBOOT,$@) ] || \
- { echo TEXT_BASE =3D
0xFFF0$(obj)board/tqm5200/config.tmp ; \
+ { echo TEXT_BASE =3D
0xFFF0$(obj)board/tqc/tqm5200/config.tmp ; \
}
@$(MKCONFIG) -n $@ -a TQM5200 ppc mpc5xxx tqm5200 tqc
Please re-submit after adding your Signed-off-by: line (and please
follow the other instructions Detlev sent you).
I'll do it as fast as I can. I can't submit from my office, so I need
to do it from home and had no time these days.
Regards,
Pedro.
_
Llega la nueva temporada. Consulta las nuevas tendencias en MSN Estilo
http://estilo.es.msn.com/moda/___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] FW: Fwd: Problem in writing jffs2 fiesystem
On Mon, 8 Sep 2008 19:51:59 +0530 Navin wrote: Hi all, I am running u-b00t-1.6.6 on custom at91sam9263 board. Are you sure it is u-boot-1.6.6? The latest u-boot in repository is 1.3.4. Now i am able to boot, jffs2 filesystem with linux-2.6.20 kernel. but the procedure i am using to burn is jffs2 is : 1)boot the linux kernel with ramdisk 2)erase the flash partition using $flasheraseall -j /dev/mtd1 3)writing the image using $nandwrite -p /dev/mtd1 rootfs.jffs2 You should be able to flash the jffs2 file sytem from u-boot. No need to do it from linux. The above procedure works well for me. But when i try writing the jffs2 filesytem in uboot prompt its not booting (kernel panic). In uboot i did this way: 1) tftp 2110 rootfs.jffs2 2)nand write.jffs2 2110 0x20 0x(hex add of displayed by tftp) Which command is nand write.jffs2? Maybe you're using a version which is modified by the board supplier. A normal way to flash it would be: cp.b 2110 $(destiny_addr) $(filesize) Cheers. Pedro L. What is the write of doing this? - Regards, Naveen Juega a las preguntas de Live Quiz con tus contactos de Messenger ¡Empieza ahora! _ ¿Sigue el calor? Consulta MSN El tiempo http://eltiempo.es.msn.com/___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Boot from jffs2 filesystem problem
[Previously posted in the wrong mail list, sorry]
Hello everybody,
I'm finding some problems trying to boot a TQM5200 board using a jffs2 image as
filesystem.
The u-boot version I'm using is 1.3.1 (self compiled) and Linux Kernel 2.6.23.1.
It is possible to boot it with a stored kernel uImage and the oftree in the
flash using a nfs filesystem,
but I can't not boot it using the jffs2 image.
I've read a lot of documentation from denx.de and this is my configuration at
the moment:
mtdparts=mtdparts=TQM5200-0:512k(uboot),256k(environment),3328k(kernel),20m(jffs2),256k(oftree)
bootargs_mtd=setenv bootargs ${bootargs} ${mtdparts}
bootargs_flash=setenv bootargs ${bootargs} root=/dev/mtdblock4 rw
rootfstype=jffs2
(even tried with root=/dev/mtdblock3, I'm not sure if 0 counts or not)
bootargs_base=setenv bootargs console=ttyPSC0,115200
bootcmd_flash=run bootargs_base bootargs_flash bootargs_mtd;bootm fC0C –
fD80
I've defined the partitions myself and double checked the numbers, first
myself, then using the mtdparts command.
The kernel image, oftree, and jffs2 filesystem are stored in the flash.
The problem comes at booting. Even when root=/dev/mtdblock4 rw
rootfstype=jffs2 is passed to the kernel,
it always tries to boot from a Ramdisk image. This is the output when I run
bootcmd_flash command:
= run bootcmd_flash
## Booting image at fc0c ...
Image Name: Linux-2.6.23.1-rt5-pcm030-1trunk
Created: 2008-09-02 11:48:23 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1534856 Bytes = 1.5 MB
Load Address:
Entry Point:
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at ...
Bad Magic Number
It seems to me that U-boot is trying to boot from RAMDisk instead of booting
the kernel, but I'm not sure.
The same kernel is working properly on a phytec board and 1.2.0 U-boot,
so it's not a problem with jffs2 support within the kernel.
Any hint how to boot from jffs2 filesystem? The example in U-Boot documentation
doesn't use oftree and so,
bootm ${kernel_addr} is used, but TQM5200 requieres FDT description to boot
linux as you'll know.
Maybe should I compile the U-boot using some CONFIG_ parameter?
Thanks in advance.
Pedro L. Dominguez.
_
Prueba los prototipos de los últimos en MSN Motor
http://motor.es.msn.com/
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH] TQM5200 HIGHBOOT Makefile patch
Hi,
I don't know the normal procedure, if I should send the patch to Wolfgang or
someone else, but I found a problem with Makefile and TQM5200 HIGHBOOT config
in Makefile. I think this problem is also in previous versions since tqm boards
where moved under tqc folder.
The patch is:
--- a/Makefile 2008-09-04 14:55:05.0 +0200
+++ b/Makefile 2008-09-04 14:56:14.0 +0200
@@ -755,7 +755,7 @@
echo #define CONFIG_TQM5200_B
$(obj)include/config.h ; \
}
@[ -z $(findstring HIGHBOOT,$@) ] || \
- { echo TEXT_BASE = 0xFFF0$(obj)board/tqm5200/config.tmp
; \
+ { echo TEXT_BASE =
0xFFF0$(obj)board/tqc/tqm5200/config.tmp ; \
}
@$(MKCONFIG) -n $@ -a TQM5200 ppc mpc5xxx tqm5200 tqc
Regards,
Pedro.
_
Prueba los prototipos de los últimos en MSN Motor
http://motor.es.msn.com/
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
