June 2005 - U-Boot

[U-Boot-Users] tool to create environment on host?
by Bob Peterson 08 Jun '05

08 Jun '05

Hi All U-Booters, I have written a simple u-boot environment modifying tool that you guys may find useful. (Attached). The tool is essential for our company since our devices often get to me all packaged up and the console serial port assigned to u-boot is physically inaccessible. The flash chips are pre-burned with our initial values, defining the device as host ppc1 with a fixed mac address and ip address, but we're often called upon to change those values after the fact. Therefore, my tool is designed to switch a device's hostname, mac address, and ip address in several places in the u-boot environment. For example, to change a device called ppc1 to ppc4, I can simply do something like this: ssh ppc1 envtool 4 To print your current values for hostname, ip and mac address, I do: envtool -print To print all u-boot variables, I do: envtool -printenv I'm not claiming this tool is perfect, nor even elegant. It is simple and effective, and I'm stilling making tweaks here and there. WARNING: The tool relies heavily upon the assumption that the u-boot environment variables are being stored in /dev/mtdblock1. That's how I have the kernel for my icecube-based board set up. To compile for icecube, do this: ppc_6xx-gcc -o envtool envtool.c Regards, Bob Peterson Advanced Communication Design

3 2

RE: [U-Boot-Users] Custom Board configuration
by Fillod Stephane 08 Jun '05

08 Jun '05

David Grab wrote: >I actually have access to DDRAM, Flash and RTC over BDM Interface. So now i >need a minimal configuration for booting with u-boot. Is there anywhere a >guide or some information what i have to do?! README ? Cheers, -- Stephane

1 0

[U-Boot-Users] is there a bug in cfi_flash.c
by Yusuf Ibrahim Ozkok 08 Jun '05

08 Jun '05

Hi, There might be a bug in the code for reading status register in cfi_flash driver. In the function "flash_isset" it's directly read as reading from memory. But in intel's data sheet (for 28F640C3T) reading status register is described as below. Read Status Register The status register indicates the status of device operations, and the success/failure of that operation. The Read Status Register (0x70) command causes subsequent reads to output data from the status register until another command is issued. To return to reading from the array, issue a Read Array (0xFF) command. So before reading for SR, "Read Status Register" (0x70) command must be written to the flash. But I think this driver is beeing used by several boards. So if this driver is tested and it's working, I should be missing something? What am I missing? Thank you. Yusuf Software Eng. - Aselsan Inc. ###################################################################### Dikkat: Bu elektronik posta mesaji kisisel ve ozeldir. Eger size gonderilmediyse lutfen gondericiyi bilgilendirip mesaji siliniz. Firmamiza gelen ve giden mesajlar virus taramasindan gecirilmekte, guvenlik nedeni ile kontrol edilerek saklanmaktadir. Mesajdaki gorusler ve bakis acisi gondericiye ait olup Aselsan A.S. resmi gorusu olmak zorunda degildir. ###################################################################### Attention: This e-mail message is privileged and confidential. If you are not the intended recipient please delete the message and notify the sender. E-mails to and from the company are monitored for operational reasons and in accordance with lawful business practices. Any views or opinions presented are solely those of the author and do not necessarily represent the views of the company. ######################################################################

2 1

RE: [U-Boot-Users] PPC440GX reset command doesn't work
by Mészáros Lajos 08 Jun '05

08 Jun '05

The RESET pin is pulled down during internal reset. I know only the 8xx and 82xx family but IMHO the 440 is (should be) the same. The answer IS buried somewhere in the manuals. Ludwig ... > > Howard, Marc wrote: > > Try putting a scope/logic analyzer on your SYSRESET* line > to see if it > > is getting pulled down when you try to reset from U-Boot. > > Good point. But shouldn't the core and chip level reset still > function, > independent of the external reset line? The answer might be buried > somewhere in the PPC440 tech manuals. > > I might also talk to our hardware guys about this. > ...

1 0

RE: [U-Boot-Users] PPC440GX reset command doesn't work
by Howard, Marc 07 Jun '05

07 Jun '05

Try putting a scope/logic analyzer on your SYSRESET* line to see if it is getting pulled down when you try to reset from U-Boot. Marc W. Howard > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf > Of Andrew Wozniak > Sent: Tuesday, June 07, 2005 10:48 AM > To: tsawyer+u-boot(a)sandburst.com > Cc: U-Boot mailing list > Subject: Re: [U-Boot-Users] PPC440GX reset command doesn't work > > Travis B. Sawyer wrote: > > Andrew Wozniak wrote: > > > >> Andrew Wozniak wrote: > >> > >>> We have a custom PPC440GX board running a ported version > of U-Boot based > >>> on the OCOTEA codebase. Most U-Boot commands are working > - life is good. > >>> > > <SNIP> > > > >>> Just wondering if anyone else with a PPC440 target had any special > >>> modifications to make 'reset' work. > >> > >> > > Nope, it just works, on 3 different 440gx targets I have. The XES > > XPedite1000, the Ocotea, and our custom hardware... > > hmmm.... will have to investigate further. > > Could our problem be related to how our PPC is configured from serial > eeprom? Or might is be that DBCR (or some other control register) is > misconfigured - disallowing a "system reset"? > > Thanks for confirming proper 'reset' operation as currently > implemented. > > > > > -travis > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far > can you shotput > a projector? How fast can you ride your desk chair down the > office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users >

2 1

[U-Boot-Users] PPC440GX reset command doesn't work
by Andrew Wozniak 07 Jun '05

07 Jun '05

We have a custom PPC440GX board running a ported version of U-Boot based on the OCOTEA codebase. Most U-Boot commands are working - life is good. Except for the 'reset' command. The do_reset() source code at cpu/ppc4xx/cpu.c appears to be the function for doing the reset via the PPC "debug control register". The PPC manual shows that a cpu reset is possible thru this register, but I'm a PPC assembly newbee and need to figure it out the macros in the cpu.c source code. Just wondering if anyone else with a PPC440 target had any special modifications to make 'reset' work. Thank you.

2 3

[U-Boot-Users] help for cfi_flash
by Yusuf Ibrahim Ozkok 07 Jun '05

07 Jun '05

Hi all, I'm in trouble with cfi_flash driver. Can you please help me? We have ported u-boot to our custom MPC8245 board, except the flash driver. Now I'm trying to use cfi_flash driver of u-boot. But until now (with more then a week of work) I couldn't succedded. So I need some help!!! We have an Intel 28F640C3T flash on our custom MPC8245 board. Four flash chips are connected to 64 bit address bus. Since our flash chip supports CFI, I decided to use cfi driver, was it a wrong choice! I have seen that there were several patches for cfi_flash driver in u-boot lists. Most of them were added to u-boot1.1.2 but as seen there were still discussions on cfi_flash after the relaese of ver 1.1.2. I stated out my problem below. Can you point out me a way. What should I try after all? The problem is; When I boot with u-boot, flash initialization is completed. I can read the flash, but the problem is I can't erase, prog, or protect/uprotect flash. the command "protect off ff000000 ff03ffff" results with "flash is busy:1" warning messages. And obviously I can't erase or prog before successfully unprotect the flash. After this brief describtion of my problem I want to list below, what I have done, and clues I obtained; I want to state out that this board is also being used with vxworks. And vxworks flash driver works well. So there shouldn't be any hardware problem. Our flash addressing is divided into two regions. first 16M is connected to 0xff000000 and other 16M is connected to 0x70000000. In vxworks second half of the flash is being used after PCI initialization. In u-boot we are aiming to use the first 16M for the first time. I have defined required definitions for the CFI flash in our board configuration header file such as; #define CFG_FLASH_CFI 1 /* Flash is CFI conformant */ #define CFG_FLASH_CFI_DRIVER 1 /* Use the common driver */ #define CFG_FLASH_BASE 0xFF000000 #define CFG_ENV_IS_IN_FLASH 0 #define CFG_FLASH_PROTECTION #define CFG_MAX_FLASH_BANKS 1 /* max number of memory banks */ #define CFG_MAX_FLASH_SECT 127+8 /* max number of sectors on one chip */ /*there are 127 boot blocks, 128th block has 8 parameter blocks.*/ #define CFG_FLASH_BANKS_LIST {CFG_FLASH_BASE } I have defined CFG_FLASH_PROTECTION because when I dive into the u-boot code I recognized that without defining this lag flash is not unprotected actually, but only a soft protection mechanism is employed. Output of "fli" is below; U-Boot 1.1.2 (Jun 7 2005 - 14:20:26) CPU: MPC8245 Revision 1.4 at 349.999 MHz: 16 kB I-Cache 16 kB D-Cache Board: akb8245 8245 Unity ##Test not implemented yet## I2C: ready DRAM: 64 MB FLASH: 32 MB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: i82559#0 => => fli Bank # 1: CFI conformant FLASH (64 x 16) Size: 32 MB in 135 Sectors Erase timeout 8192 ms, write timeout 0 ms, buffer write timeout 1 ms, buffer si ze 1 Sector Start Addresses: FF000000 (RO) FF040000 (RO) FF080000 (RO) FF0C0000 (RO) FF100000 (RO) FF140000 (RO) FF180000 (RO) FF1C0000 (RO) FF200000 (RO) FF240000 (RO) FF280000 (RO) FF2C0000 (RO) FF300000 (RO) FF340000 (RO) FF380000 (RO) FF3C0000 (RO) FF400000 (RO) FF440000 (RO) FF480000 (RO) FF4C0000 (RO) FF500000 (RO) FF540000 (RO) FF580000 (RO) FF5C0000 (RO) FF600000 (RO) FF640000 (RO) FF680000 (RO) FF6C0000 (RO) FF700000 (RO) FF740000 (RO) FF780000 (RO) FF7C0000 (RO) FF800000 (RO) FF840000 (RO) FF880000 (RO) FF8C0000 (RO) FF900000 (RO) FF940000 (RO) FF980000 (RO) FF9C0000 (RO) FFA00000 (RO) FFA40000 (RO) FFA80000 (RO) FFAC0000 (RO) FFB00000 (RO) FFB40000 (RO) FFB80000 (RO) FFBC0000 (RO) FFC00000 (RO) FFC40000 (RO) FFC80000 (RO) FFCC0000 (RO) FFD00000 (RO) FFD40000 (RO) FFD80000 (RO) FFDC0000 (RO) FFE00000 (RO) FFE40000 (RO) FFE80000 (RO) FFEC0000 (RO) FFF00000 (RO) FFF40000 (RO) FFF80000 (RO) FFFC0000 (RO) 00000000 00040000 00080000 000C0000 00100000 00140000 00180000 001C0000 00200000 00240000 00280000 002C0000 00300000 00340000 00380000 003C0000 00400000 00440000 00480000 004C0000 00500000 00540000 00580000 005C0000 00600000 00640000 00680000 006C0000 00700000 00740000 00780000 007C0000 00800000 00840000 00880000 008C0000 00900000 00940000 00980000 009C0000 00A00000 00A40000 00A80000 00AC0000 00B00000 00B40000 00B80000 00BC0000 00C00000 00C40000 00C80000 00CC0000 00D00000 00D40000 00D80000 00DC0000 00E00000 00E40000 00E80000 00EC0000 00F00000 00F40000 00F80000 00FC0000 00FC8000 00FD0000 00FD8000 00FE0000 00FE8000 00FF0000 00FF8000 => I have modified the tout in flash_status_check(), because it was too long!!! And although the "tout" is passed as a parameter, it's not used. (I thing this chance is given as a patch previously) - if (get_timer (start) > info->erase_blk_tout * CFG_HZ) { + if (get_timer (start) > tout) { output of the protect command; =>protect off ff000000 ff03ffff flash_is_busy: 1 . . . flash_is_busy: 1 flash_is_busy: 1 long addr is at ff000000 info->portwidth = 8 addr[0] = 0x27 addr[1] = 0x5 addr[2] = 0x19 addr[3] = 0x56 addr[4] = 0x55 addr[5] = 0x2d addr[6] = 0x42 addr[7] = 0x6f addr[8] = 0x6f addr[9] = 0x74 addr[a] = 0x20 addr[b] = 0x31 addr[c] = 0x2e addr[d] = 0x31 addr[e] = 0x2e addr[f] = 0x31 addr[10] = 0x20 addr[11] = 0x28 addr[12] = 0x4d addr[13] = 0x61 addr[14] = 0x79 addr[15] = 0x20 addr[16] = 0x20 addr[17] = 0x33 addr[18] = 0x20 addr[19] = 0x32 addr[1a] = 0x30 addr[1b] = 0x30 addr[1c] = 0x35 addr[1d] = 0x20 addr[1e] = 0x2d addr[1f] = 0x20 Flash unprotect timeout at address ff000000 data 316f2033 fwrite addr ff000000 cmd ff 00ff00ff00ff00ff 64 bit x 16 bit is= cmd 80(Ç) addr ff000000 is= 27051956552d426f 0080008000800080 Flash unprotect error at address ff000000 fwrite addr ff000000 cmd ff 00ff00ff00ff00ff 64 bit x 16 bit .Un-Protected 1 sectors => Thank you very much. Yusuf. Software Eng. - Aselsan Inc. ###################################################################### Dikkat: Bu elektronik posta mesaji kisisel ve ozeldir. Eger size gonderilmediyse lutfen gondericiyi bilgilendirip mesaji siliniz. Firmamiza gelen ve giden mesajlar virus taramasindan gecirilmekte, guvenlik nedeni ile kontrol edilerek saklanmaktadir. Mesajdaki gorusler ve bakis acisi gondericiye ait olup Aselsan A.S. resmi gorusu olmak zorunda degildir. ###################################################################### Attention: This e-mail message is privileged and confidential. If you are not the intended recipient please delete the message and notify the sender. E-mails to and from the company are monitored for operational reasons and in accordance with lawful business practices. Any views or opinions presented are solely those of the author and do not necessarily represent the views of the company. ######################################################################

2 1

[U-Boot-Users] Booting from serial flash?
by Hoda 07 Jun '05

07 Jun '05

Hi everyone, I was wondering if anyone can help me on this matter: does the U-boot support loading solely from serial flash or nand flash (i.e. no other flash is available)? If so, which of the boards support that. I've been digging into the U-Boot files and I found support for compact flash but it exists along with another flash memory, where as I need a bootloader running with only compact flash. Thanks, Hoda

2 1

[U-Boot-Users] To Board B2's author
by hai tan 07 Jun '05

07 Jun '05

I want to use u-boot as my board loarder, refering ro my board hardware, I select B2 as my target to modify. Now I put up my hardware configuration(flash:SST39VF160;SDRAM:H57V65160B; MCPU: s3c44b0).The problem is that which file should modify and how to do it. at first I want to the l less change. Best regard. tanhai _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 0

[U-Boot-Users] [newbie] U-boot linker script
by Srivatsan CR 07 Jun '05

07 Jun '05

Hi all, As part of understanding of U-Boot, I was looking at customizing the U-Boot linker scripts (With the help of "Using ld" from GNU) file as follows: (TEXT_BASE = 0x01000000) a) Changed the line in u-boot.lds from ". = + SIZEOF_HEADER" to ". = 0x1010000 + SIZEOF_HEADER b) Compared the map file with the change and without the change, it is seen that there is no change in the files except the location pointer address. c) Changed the line in u-boot.lds from ".text : { cpu/mpc8260/start.o (.text) *(.text) *(.fixup) *(.got1) . = ALIGN(16); *(.rodata) *(.rodata1) *(.rodata.str1.4) } to ".text . : { cpu/mpc8260/start.o (.text) *(.text) *(.fixup) *(.got1) . = ALIGN(16); *(.rodata) *(.rodata1) *(.rodata.str1.4) }" d) Compared the map file with the change and without the change, it is seen that there is no change in the files. Shouldn't the text be relocated to the location pointer address? I am going wrong somewhere in my understanding. Can someone put me in the right direction? Thanks. With Regards, C.R.Srivatsan

1 0