April 2004 - U-Boot

[U-Boot-Users] [PATCH] support for CF/IDE on PCMCIA for PXA25X
by Christian Pell 13 Aug '05

13 Aug '05

Hi, I tried this with some different CFs with FAT file-systems on them. There is a README in the patch itself that goes in documentation directory. Bye, -- Christian Pellegrin <chri(a)ascensit.com>, <c.pellegrin(a)eurotech.it>, <chri(a)infis.univ.ts.it>, <c.pellegrin(a)exadron.com>

4 8

[U-Boot-Users] mkimage for DOS
by Dave Westwood 10 Jun '05

10 Jun '05

long shot really, but does anyone have a working executable mkimage for DOS or a dos window in windows (don't flame me for using windows !!)

2 1

[U-Boot-Users] Environment in flash rather than EEProm
by Andy Hawkins 11 Feb '05

11 Feb '05

Hi all I'm using a PPChameleonEVB, and am trying to move the u-boot environment into flash. I've modified the include/configs/PPChameleon.h file as follows: #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_ADDR 0xFFFFA000 #define CFG_ENV_OFFSET (CFG_ENV_ADDR - 0xFFFC0000) #define CFG_ENV_SIZE 0x2000 I've added some debugging into the section where it reads the environment, and I'm seeing the following: U-Boot 1.0.2-adh-2004/03/29 (Mar 30 2004 - 13:40:38) CPU: IBM PowerPC 405EP Rev. B at 133.333 MHz (PLB=133, OPB=66, EBC=33 MHz) IIC Boot EEPROM disabled PCI async ext clock used, internal PCI arbiter enabled 16 kB I-Cache 16 kB D-Cache Board: ### No HW ID - assuming PPChameleonEVB I2C: ready DRAM: 32 MB Top of RAM usable for U-Boot at: 02000000 Reserving 189k for U-Boot at: 01fd0000 Reserving 256k for malloc() at: 01f90000 Reserving 128 Bytes for Board Info at: 01f8ff80 Reserving 48 Bytes for Global Data at: 01f8ff50 Stack Pointer at: 01f8ff38 New Stack Pointer is: 01f8ff38 Now running in RAM - U-Boot at: 01fd0000 FLASH: 4 MB env_relocate[204] offset = 0x2010000 env_relocate[216] embedded ENV (before reloc) at fffd9474 env_relocate[218] embedded ENV (after reloc) at 01fe9474 U-Boot relocated to 01fd0000 NAND:Probing at 0xff000000 32 MB ### main_loop entered: bootdelay=5 ### main_loop: bootcmd="<UNDEFINED>" => As you can see, the address of the environment before relocation is 0xfffd9474. Shouldn't this be 0xFFFFA000? Is there anything else I need to do to force the location of the environment into the required place? It looks like the address of the environment is based on the location of the 'environment' variable in common/environment.c. Do I need to change the LD script to force this variable to a certain location? If so, can anyone help with what I need to do (I'm not familiar with LD scripts yet). Many thanks. Andy

3 7

[U-Boot-Users] Binary file cat
by Adam Bezanson 03 Aug '04

03 Aug '04

Hi, I have ported u-boot to my arm920t based system. I have a unique situation in that my processor requires a binary header to be placed In front of u-boot.bin before it is burnt into flash. If the processor doesn't find this header in flash it will not boot out of flash. Currently I have the header file as a separate file in the root directory and when I finish a new compile I have a shell script which Simply does a 'cat header.bin u-boot.bin > out.bin'. I'd like to get away from this and add it to the Makefiles so for my board I don't have to run this script every time. Before I go editing a top-level Makefile, I wanted to ask for advice on how I should go About doing this? Anything I can do in my board-specific directory would make me feel better. Suggestions? Thanks, Adam

3 6

[U-Boot-Users] [patch] MicroBlaze port of U-Boot
by Yasushi SHOJI 28 Jun '04

28 Jun '04

Hello all, Here is a patch against the current CVS for microblaze port of u-boot. I does nothing but boot itself, but this can be a start. Suggestions, thoughts, and comments are welcome, of course. best regards, -- yashi

3 7

[U-Boot-Users] [PATCH] OMAP730 Perseus2 support
by Dave Peverley 07 Jun '04

07 Jun '04

Hi all, I'm pleased to submit back to the list this patch for the OMAP730 Perseus2 board. The patch adds support for the OMAP730 Perseus2 board. For detailed information, see the doc/README.omap730p2 text file contained in the patch. The patch itself was created against the CVS repository tag "U-Boot-1_1_0" using the command : diff -purN u-boot u-boot-omap730p2 > u-boot-1.1.0-omap730p2.patch Changelog Entry : * Patch by Dave Peverley, 29th Apr 2004: Added support for OMAP730 Perseus2 Development board CREDITS Entry : N: Dave Peverley E: dpeverley(a)mpc-data.co.uk W: http://www.mpc-data.co.uk D: OMAP730 P2 board support All comments and feedback welcome. Best Wishes, Dave Peverley --------------------------------------------------------------------------- Dave Peverley, Software Engineer, MPC Data Limited. Phone : [+44] (0) 1225 868 228 Web : http://www.mpc-data.co.uk

2 2

[U-Boot-Users] [RFC] NAND Flash
by Pantelis Antoniou 07 Jun '04

07 Jun '04

Hello there. As you remember earlier I have sent a small patch for the NAND portion of u-boot. This forced me to really take a hard look at the code and really evaluate it. The big problem with the code as it is its its tendancy not to account properly for errors which are not only probable but certain during the life of the device. For example the current code cannot boot reliably from NAND and the read and write routines are also unreliable. It's basic assumption made that you can read/write from the NAND at any position is false. This is impossible because of the bad blocks that may force you to skip a bad sector. I'm currently in the process of rewritting to actually make it work reliably. I can keep backwards compatibility with the old code but you can only use it at your own risk. I'm asking for any people currently working with NAND to comment on the following points: 1. Do you read and write the NAND at arbitrary offsets? That means not in page boundaries. 2. Do you use the NAND boot command? It can be replaced by a copy and bootm sequence. 3. Do you use it as a raw device without employing ECC? Do you understand the implications? 4. What kind of filesystem do you use? JFFS2 & YAFS have different OOB placement of ECC and status bits? 5. What kind of bad block management options would you like? I'm thinking of implementing a bad block detection mechanism which would erase and test the whole chip for any bad blocks. Another command could also utilise ECC to detect borderline working pages and relocate them to avoid a permanent failure. Awaiting your input... Regards Pantelis

2 2

[U-Boot-Users] New NAND code draft
by Pantelis Antoniou 07 Jun '04

07 Jun '04

Hi there In the attached patch you can see the progress of my work in the NAND rewrite. This is not suitable for inclusion yet. Things that work now: 1. Correct handling of bad blocks. 2. NAND boot works 3. Updated to latest MTD snapshot. 4. Direct to NAND tftp/nfs support. Things that are probably borked: 1. Multiple chip support (I don't have such hardware available and the previous code was kinda of unclear. 2. Since there is DOC support in u-boot that utilizes the old code and definitions I left the linux/mtd/nand.h header in place, and created a new mtd_nand.h header for the new stuff. 3. JFFS2 support although there is probably b0rken. 4. The read.xxx/write.xxx support is just not there yet. I would appreciate it if you could take a look and report back to me. Regards Pantelis

2 1

[U-Boot-Users] MPC8xx FADS Board Flash Chip Select
by Alan J. Luse 07 Jun '04

07 Jun '04

The setting of the Flash chip select extent on MPC8xx FADS boards (board/fads/flash.c) is too big by a factor of 2. A board with 2 Mbytes will have its chip select set to allocate a region of 4 Mbytes. * Patch by Alan J. Luse, 29 Apr 2004: Flash chip-select (OR0) option register was being set incorrectly to twice the available Flash for FADS boards. Alan J. Luse Embedded Systems Engineer Time America, Inc. 51 West Third Street, Suite 310 Tempe, AZ 85281 Voice: (480) 296-0408 Fax: (480) 296-0444

2 1

[U-Boot-Users] MII Speed & Duplex Readback
by Alan J. Luse 07 Jun '04

07 Jun '04

The MII PHY utility (common/miiphyutil.c) does not report network speed and duplex mode properly if auto-negotiate is not enabled. The attached patch checks if auto-negotiate is enabled and looks in the proper registers based on that bit to return speed and duplex values. * Patch by Alan J. Luse, 29 Apr 2004: Report MII network speed and duplex setting properly when auto-negotiate is not enabled. Alan J. Luse Embedded Systems Engineer Time America, Inc. 51 West Third Street, Suite 310 Tempe, AZ 85281 Voice: (480) 296-0408 Fax: (480) 296-0444

2 1