Assuming you load the kernel to ram with tftp (and that "AppKernel" is
an mtdparts partition in NAND), then you could do:
nand erase.part AppKernel
tftp $load_addr uImage
crc32 $load_addr $filesize
nand write.i $load_addr AppKernel $filesize
nand read.i $load_addr AppKernel $filesize
crc32 $load_
Hi,
Did you use "nand write.i" to write the kernel and "nand read.i" to
read the kernel? the ".i" tells u-boot to skip bad blocks...
No I use "nand read $load_addr AppKernel" cause I didn't know we can use
"nand read.i" - "help nand" doesn't display this information.
I tried "nand read.i" and
id I forget to initialize something ?
BEst regards.
--
Best regards.
Alexandre Gambier
Fte Maximal France SAS
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hello,
Booting using the fdt blob at 0xc0
Uncompressing Kernel Image ... out of func inflateInit2
I backtraced the contents dumped and I found it died in function "inflate" which
is defined in the file of lib/zlib.c and called in the file of lib/gunzip.c.But
after that I don't kno
On 02/11/2011 10:06 AM, Wolfgang Denk wrote:
> Dear Alexandre Gambier,
>
> please do not top post / full quote; please read
> http://www.netmeister.org/news/learn2quote.html
Sorry
> In message<4d54eb92.7080...@ftemaximal.fr> you wrote:
>> I will try to write my own
Hello Andreas,
Thanks for this explanation.
I will try to write my own driver for my board.
Best regards
alex
On 02/10/2011 07:24 PM, Andreas Pretzsch wrote:
> Am Donnerstag, den 10.02.2011, 17:04 +0100 schrieb Alexandre Gambier:
>> Dear Wolfgang,
>>
>> I tried to put s
Dear Wolfgang,
I tried to put some printk in the MTD driver and it seems that the
parse_mtd_partitions function is never called...
I will try to find what's wrong with my kernel configuration.
alex
On 02/10/2011 03:59 PM, Wolfgang Denk wrote:
> Dear Alexandre Gambier,
>
> In me
Hello,
I use U-Boot 1.3.1 with a NOR and a NAND Flash.
I created the following partitions with U-Boot.
device nor0 , # parts = 4
#: namesizeoffset mask_flags
0: U-Boot 0x0008 0x 0
1: Environment 0x000200
Ok.
Thank you very much.
On 02/10/2011 10:48 AM, Wolfgang Denk wrote:
> Dear Alexandre Gambier,
>
> In message<4d539e01.6070...@ftemaximal.fr> you wrote:
>>> waste of memory. You can see that the following sectors are unused
>>> from the 'E' (= empt
Dear Wolfgang,
Thanks for this explanation.
Best regards
Alex
On 02/09/2011 07:50 PM, Wolfgang Denk wrote:
> Dear Alexandre Gambier,
>
> In message<4d52b843.5010...@ftemaximal.fr> you wrote:
>> I'm using u-boot to boot a Linux-based device.
>> I created some MT
Dear Wolfgang,
Thanks for your reply and your help.
On 02/09/2011 07:50 PM, Wolfgang Denk wrote:
>
>> The first sectors #0,1,2,3 are protected and sectors #8,9 (U-Boot
>> environment) are protected.
>> It should be sectors #0,1,2,3,4,5,6,7 and sectors #8,9.
> No, it should not. Only the sectors
ander Stein wrote:
> Hello,
>
> On Wednesday 09 February 2011, 16:52:35 Alexandre Gambier wrote:
>> I'm using u-boot to boot a Linux-based device.
> Which version og u-boot are you running?
>
>> I created some MTD partitions for my NOR and NAND flashes.
>>
>
Hello,
I'm using U-Boot with a NOR and a NAND Flash.
U-Boot is stored into the NOR flash.
The NOR flash is setup as :
0xA000 -> 0xA008 -> 512k -> 8 sectors -> reserved for U-Boot.bin
0xA008 -> 0xA00A -> 128k -> 2 sectors -> reserved for U-Boot
environment
If I use the command `
Hello,
I'm using u-boot to boot a Linux-based device.
I created some MTD partitions for my NOR and NAND flashes.
Here is the configuration:
device nor0 , # parts = 4
#: namesizeoffset mask_flags
0: U-Boot 0x0008 0x
14 matches
Mail list logo
