November 2004 - U-Boot

[U-Boot-Users] Flash memory reading Issue??
by Vikrant_Basotra 15 Nov '04

15 Nov '04

Hi all, I am using ppmc8260 board and flash memory type is strataflash. In order to read the data from the flash memory I am using the function flash_read_long(flash_info_t * info, int sect, uchar offset)" which is defined in the file "board/ppmc8260/strataflash.c" . Can any one tell me precisely what should be the value of the third argument (i.e offset) of the function flash_read_long when we have to read the data from the strataflash. Best Regards, Vikrant Basotra ************************************************************************** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. **************************************************************************

1 0

[U-Boot-Users] uImage's load address and entry point?
by Shawn 15 Nov '04

15 Nov '04

Hi, I have built a uClinux kernel image vmlinux and the header information is dumped here by objdump. I want to make a uImage to let u-boot start linux and am confused about the values of load address and entry point. If the uImage is built from raw binary linux.bin, the load address and entry point should be set to 0. Right? If it is built from vmlinux, the entry point in my case should be 0x00008000, what' should be the load address? Thanks, -Shawn. vmlinux: file format elf32-littlearm Sections: Idx Name Size VMA LMA File off Algn 0 .init 00011000 00008000 00008000 00008000 2**5 CONTENTS, ALLOC, LOAD, CODE 1 .text 0014e7c0 00019000 00019000 00019000 2**5 CONTENTS, ALLOC, LOAD, READONLY, CODE 2 __ex_table 000009b8 001677c0 001677c0 001677c0 2**3 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 __ksymtab 00000000 00168178 00168178 0017f720 2**0 CONTENTS 4 __ksymtab_gpl 00000000 00168178 00168178 0017f720 2**0 CONTENTS 5 __kcrctab 00000000 00168178 00168178 0017f720 2**0 CONTENTS 6 __kcrctab_gpl 00000000 00168178 00168178 0017f720 2**0 CONTENTS 7 .data 0001570c 0016a000 0016a000 0016a000 2**5 CONTENTS, ALLOC, LOAD, DATA 8 .bss 000117d4 0017f720 0017f720 0017f720 2**5 ALLOC 9 .debug_abbrev 00051055 00000000 00000000 0017f720 2**0 CONTENTS, READONLY, DEBUGGING 10 .debug_info 01ab2fc5 00000000 00000000 001d0775 2**0 CONTENTS, READONLY, DEBUGGING 11 .debug_line 00243022 00000000 00000000 01c8373a 2**0 CONTENTS, READONLY, DEBUGGING 12 .debug_pubnames 00011e0c 00000000 00000000 01ec675c 2**0 CONTENTS, READONLY, DEBUGGING 13 .debug_aranges 000035b0 00000000 00000000 01ed8568 2**0 CONTENTS, READONLY, DEBUGGING

2 3

[U-Boot-Users] [PATCH] 5/5 - lpd7a40x flash erase progress
by Paul Ruhland 14 Nov '04

14 Nov '04

CHANGELOG * Patch by Paul Ruhland, 14 November 2004 - add progress output to 'flash_erase()' in 'board/lpd7a40x/flash.c'.

1 0

[U-Boot-Users] [PATCH] 4/5 - lpd7a40x timer CFG_HZ change
by Paul Ruhland 14 Nov '04

14 Nov '04

CHANGELOG * Patch by Paul Ruhland, 14 November 2004 - CFG_HZ now 100 instead of the timer frequency in 'include/configs/lpd7a40x-10.h'. - changes to 'cpu/lh7a40x/interrupts.c': - support using new CFG_HZ value - add timestamp restoral to 'udelay_masked()' allowing 'udelay' to be used with timed loops

1 0

[U-Boot-Users] [PATCH] 3/5 - lpd7a40x rev detect & buffer direction
by Paul Ruhland 14 Nov '04

14 Nov '04

CHANGELOG * Patch by Paul Ruhland, 14 November 2004 - following changes to 'board_init()' in 'board/lpd7a40x/lpd7a40x.c': - cpld revision check - for cpld revisions > 0x34 set gpio pins to set I/O buffers to proper direction - changes to 'doc/README.lpd7a40x' to reflect the card engine version detection and I/O buffer redirection for newer card engines

1 0

[U-Boot-Users] [PATCH] 2/5 - lpd7a40x include consolidation
by Paul Ruhland 14 Nov '04

14 Nov '04

CHANGELOG * Patch by Paul Ruhland, 14 November 2004 - consolidate the lpd7a40x config includes since differences between board/cardengine variants does warant the seperate files. - add 'lpd7a404' to MAKEALL ARM9 board list - toplevel Makefile changed for lpd7a40x to configure for the LPD7A400 or LPD7A404 using the new config includes - add support for all ram configurations. This requires manually editing 'include/configs/lpd7a40x-10.h' and 'board/lpd7a40x/config.mk' prior to building.

1 0

[U-Boot-Users] [PATCH] 1/5 - lpd7a40x register defs
by Paul Ruhland 14 Nov '04

14 Nov '04

This is the first in a series of 5 patches for the lpd7a40x platform. CHANGELOG * Patch by Paul Ruhland, 14 November 2004 - change register definitions for LH7A40X SoC to use the __REG style preferred by the arm linux community

1 0

Re: Re: [U-Boot-Users] u-boot on EP8260 M 1.3
by Nishant Galange 13 Nov '04

13 Nov '04

Thank you. But I had made a pretty silly mistake: I kept HyperTerminal configured at 9600 baud, the default for PlanetCore loader, while u-boot was configured for 115200. Now I can see u-boot (debug build) starting up, but the messages stop at New Stack Pointer is: 03f37f48 Why dosen't the command prompt come up also? Am I missing something? Waiting, Nishant -----Original Message----- From: Jeff Angielski <jangiels(a)speakeasy.net> To: Nishant Galange <nishant.subs(a)myrealbox.com> Date: Thu, 11 Nov 2004 15:06:45 -0500 Subject: Re: [U-Boot-Users] u-boot on EP8260 M 1.3 On Thu, 2004-11-11 at 11:05, Nishant Galange wrote: > I used the standard (unmodified) image of U-Boot for the EP8260 compiled using > the ELDK. Is this configuration valid for revision M 1.3? > CodeWarrior reports that the u-boot image was successfully programmed. However, > nothing appears on the monitor console after power-up. Even the LEDs stop glowing. Did you read the flash manually to verify that u-boot was written ok and that the HRCW was written correctly? More importantly, are you writing both of these things to the correct location? > I also tried to restore the HRCW using the procedure given in the manual: Doesn't the manual assume your are using PlanetCore to configure the HRCW via the PlanetCore command line utility? Did you take that into account? Jeff Angielski The PTR Group

1 0

[U-Boot-Users] RE: Trouble booting uboot on 440GX (ocotea) eval board afterinitial power-up boot
by Howard, Marc 13 Nov '04

13 Nov '04

What works is using a supported flash device. I had swapped out the AMD parts for SST 39VF040. They program like AMDs but the sector sizes are different. Putting in the AMDs and re-flashing U-Boot solved the problem. Thanks to all, Marc W. Howard -----Original Message----- From: David Adair [mailto:dadair@ariodata.com] Sent: Friday, November 12, 2004 3:47 PM To: Howard, Marc Cc: u-boot-users(a)lists.sourceforge.net Subject: RE: Trouble booting uboot on 440GX (ocotea) eval board afterinitial power-up boot > -----Original Message----- > On Thu, Nov 11, 2004 at 06:19:02PM -0800, Howard, Marc wrote: > > Hi, > > > > I've built and installed U-Boot 1.1.2 on an IBM 440GX eval board > > (ocotea). After powering the board I can get the uboot interactive > > prompt. If I type 'reset' or hit the reset button it hangs. I get the > > same results whether or not I use the BDI2000. Doing a power cycle of > > the board is the only way to get back to the prompt. > > > > Is there some reconfiguation U-Boot does that causes the processor boot > > address to change after the initial power-up? Am I missing something > > here? > > You might find more help on the u-boot users list. > > -Matt Does resetting the SDRAM controller help? http://sourceforge.net/mailarchive/forum.php?thread_id=5843422&forum_id= 1289 8

1 0

[U-Boot-Users] EP8260 command prompt does not appear
by Nishant Galange 12 Nov '04

12 Nov '04

Hi all, I am trying boot ep8260 board using u-boot. I have successfully erased the planetcore bootloader and programmed u-boot (debug build) into the flash. The command prompt does not come up, the messages halt at "New Stack Pointer is: 03f37f48". That's exactly the place in u-boot where the code has been relocated to RAM. Can anyone help me - what could be the reason and how to proceed? And also what are the debugging tools we can use to debug? Can the codewarrior with wiretap be used for debugging? As I am fairly new to u-boot, any help will be greatly appreciated. Regards, Nishant

1 0