• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / U-Boot stuff / Re: boot menu or similar? for u-boot on: April 14, 2009, 11:43:36 AM
I've configured something like a multiboot on my plug.  Take a look at the post here : http://openplug.org/plugforum/index.php?topic=36.msg264#msg264

There is no way (that I know of) to actually create and display a bootmenu, but you can get into the U-Boot environment and execute a 'run boot_sd' or 'run boot_nfs' with the way I have it configured.  If you could find a method to stop autoboot and run a few echo commands after initialization I suppose it would work as a makeshift bootmenu but I have not seen such functionality in the documentation.  However you will probably want to leave autoboot enabled and a default bootcmd set, otherwise you will need the console connected everytime the plug boots.
2  Hardware and U-Boot firmware / U-Boot stuff / Re: u-boot Example Settings To Easily Switch Between TFTP/NFS and NAND on: April 14, 2009, 11:34:39 AM
@mteel : thanks for your post, I've taken your settings, modified and expanded slightly to add booting from SD.  Perhaps someone will find it of use:

Code:
set console 'console=ttyS0,115200 mtdparts=nand_mtd:0x00100000@0x00000000(uBoot)ro,0x00400000@0x00100000(uImage),0x1fb00000@0x00500000(rootfs)'

set boottftp 'tftpboot 0x2000000 $(image_name)'
set bootargs_nfs 'root=/dev/nfs rw'
set boot_nfs 'run boottftp;setenv bootargs $(console) $(bootargs_nfs) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x2000000'

set bootnand 'nand read.e 0x2000000 0x00100000 0x00500000'
set bootargs_nand 'root=/dev/mtdblock2 rw'
set boot_nand 'run bootnand;setenv bootargs $(console) $(bootargs_nand) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x2000000'

set bootargs_sd 'root=/dev/mmcblk0p1 rw'
set boot_sd 'run bootnand;setenv bootargs $(console) $(bootargs_sd) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x2000000'

set bootcmd 'run boot_sd;'

mtdparts are configured for a 4mb uImage size (and loading rootfs @ 5mb), using this one may need to adjust the numbers to match their environment.

3  Linux Stuff / Kernel / Re: "Bad Magic Number" on: April 14, 2009, 11:20:06 AM
I believe another user posted that a new uImage release (040309 or something) will fit without a problem, although I have not tried it yet myself.  However, it's probably not a bad idea playing around with mtdparts thought just to get a better idea of how it works.
4  Linux Stuff / Kernel / Re: Problems reflashing UImage, bad blocks on: April 14, 2009, 11:15:36 AM
My plug also has a number of bad blocks as well:

Code:
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 320 at 0x02800000
Bad eraseblock 2240 at 0x11800000
Bad eraseblock 2241 at 0x11820000
Bad eraseblock 2242 at 0x11840000
Bad eraseblock 2243 at 0x11860000
Bad eraseblock 2244 at 0x11880000
Bad eraseblock 2290 at 0x11e40000

 * Loading hardware drivers...                                                  end_request: I/O error, dev mtdblock0, sector 0
Buffer I/O error on device mtdblock0, logical block 0
end_request: I/O error, dev mtdblock0, sector 8
Buffer I/O error on device mtdblock0, logical block 1
end_request: I/O error, dev mtdblock0, sector 16
Buffer I/O error on device mtdblock0, logical block 2
end_request: I/O error, dev mtdblock0, sector 24
Buffer I/O error on device mtdblock0, logical block 3
end_request: I/O error, dev mtdblock0, sector 0
Buffer I/O error on device mtdblock0, logical block 0

My question is given these are on mtdblock0, if they keep growing wouldn't it eventually corrupt the uBoot image?  Oh and @Blazer, I noticed the erasesize as 2MB for mine as well:

Code:
root@sheeva:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uBoot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "rootfs"

Pages: [1]