Hi Sascha,
> 
> 
> > > > > > > 2. Is it possible to do a NAND boot on i.mx27ads board with 
> > > > > > > uboot? 
> If so how can I do it?
> > > > > > 
> > > > > > NAND support (including booting from NAND) has been tested on the
> > > > > > phycore i.MX27 module. So the NAND driver inself is in place, only 
> > > > > > the
> > > > > > board specific bits are missing.. You can use board/pcm038 as a 
> template.
> > > 
> > > 1. Which nand is used on the pcm038 board(vendor, pagesize, bus width)?
> > It's a NAND device: Manufacturer ID: 0x20, Chip ID: 0x36 (ST Micro NAND 
> > 64MiB 
> 1,8V 8-bit)
> > 
> > > 2. Can modify these drivers for the mx27ads which has a samsung, x8, 
> > > 512byte 
> 
> > page, 1Gb... or I have to integrate it totally from scartch?
> > 
> > It should work in principle. All you have to do is to find the bugs ;)
> > I tried it once on my mx27ads but had no luck, but I didn't investigate
> 
> I modified the imx27ads/* for nand boot as in pcm038 and the 
> drivers/nand/nand_base.c *maf_id and dev_id. Then it boots succesfully for 
> the 
> Samsung NAND on the ADS board.
> 
>  
> U-Boot 2.0.0-rc5-git (Sep 23 2008 - 11:14:46)
> Board: Freescale i.MX27 ADS
> NAND device: Manufacturer ID: 0xec, Chip ID: 0x79 (Samsung NAND 128MiB 3,3V 
> 8-bit)
> Scanning device for bad blocks
> Bad eraseblock 6037 at 0x05e54000
> Using environment in NAND Flash
> chip id: [1,882,1,01d]
> mpll:    398998U-Boot 2.0.0-rc5-git (Sep 23 2008 - 11:14:46)
> envfs: wrong magic on /dev/env0
> 000 Hz
> spll:    240000000 Hz
> arm:      132999333 Hz
> perclk1:  66499666 Hz
> perclk2:  66499666 Hz
> perclk3:  66499666 Hz
> perclk4:  66499666 Hz
> clkin26:  26000000 Hz
> ahb:      66499666 Hz
> ipg:      33249833 Hz
> Malloc space: 0xa7b00000 -> 0xa7f00000 (size  4 MB)
> Stack space : 0xa7af8000 -> 0xa7b00000 (size 32 kB)
> envfs: wrong magic on /dev/env0
> Q>> Where can I specify my NAND/NOR/RAM details(size, sectors...) so that I 
> can 
> alter the configuration files. (In the previous version it was 
> include/config/.h. Now all those files seems to be empty.)
> 

Q>>Why does the wrong magic on /dev/env0 happen? How to correct this?

 
Q>> How can I store uImage and the rootfilesystem on the NAND? Are there any 
commands for this?

> 
> I make a uImage with the following commands.
> #/opt/OSELAS.Toolchain-1.1.1/arm-v4t-linux-gnueabi/gcc-4.1.2-glibc-2.5-kernel-2.6.18/bin/arm-v4t-linux-gnueabi-objcopy
>  
> -O binary -R .note -R .comment -S vmlinux linux.bin
> #gzip -9 linux.bin
> #mkimage -A arm -O linux -T kernel -C gzip -a 0xA0008000 -e 0xA0008000 -n 
> "Linux 
> kernel image" -d linux.bin.gz uImage
> 
> Once the boot happens the following error messages come:
>  
> Hit any key to stop autoboot:  3 2 1
> phy0: Link is up - 100/Full
> TFTP from server 199.63.38.20; our IP address is 199.63.38.113
> Filename 'uImage'.
> Loading: *#################################################################
>      ###############################T ###############################T ###
>      ########################################error frame: 0xa7b02468 
>0x00000884
> T ########################T error frame: 0xa7b02480 0x00000804
> T ##############T T ####################################################
> ######################error frame: 0xa7b023c0 0x00000890
> T #############error frame: 0xa7b02318 0x00000884
> T #error frame: 0xa7b02498 0x00000890
> T ########################
> done
> Bytes transferred = 1634718 (18f19e hex)
>    Image Name:  Linux kernel image
>    Created:      2008-09-23  6:50:16 UTC
>    Data Size:    1634654 Bytes =  1.6 MB
>    Load Address: a0008000
>    Entry Point:  a0008000
> OK
> commandline: console=ttymxc0,115200 
> ip=199.63.38.113:199.63.38.20:199.63.38.1:255.255.255.0::: 
> root=/dev/nfs nfsroot=199.63.38.20:/tftpboot/ltib,v3,tcp 
> mtdparts=physmap-flash.0:256k(uboot)ro,128k(ubootenv),1536k(kernel),-(root);
> imx_nand:256k(uboot)ro,128k(ubootenv),1536k(kernel),-(root)
> arch_number: 846
> Unimplemented compression type 1
> handler returned!
> uboot:/ 

Q>> Why is the tftp download breaking?
> 
> Q>>I compress the linux image using gzip. Does'nt this version of uboot 
> support 
> gzip (because it says unimplemented compression type) or am I missing out 
> something here?

I had not included the zlib support.. Once included the linux boots through 
tftp and nfs.

> 
Q>> How to enable GDB support in uboot?
> 
> 
Thanks and regards,
Tiju



      Add more friends to your messenger and enjoy! Go to 
http://in.messenger.yahoo.com/invite/


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

Reply via email to