November 2005 - U-Boot

[U-Boot-Users] does this situation can assert to be a hardware problem?
by zhuzhenhua 25 Nov '05

25 Nov '05

in the u-boot, when run into board_init_r(lib_mips/board.c), sometimes it stop at the call of mem_malloc_init, sometimes it stop at the call of env_relocate. does it means it maybe caused by hardware or uncorrect sdram init?, it can not be the software ploblem of the board.c file? when i used the bdi2000 to debug in, i found at the call of mem_malloc_init "lw t9,8(gp)" , if i set a breadpoint at "addiu t9,t9,1552", the t9 is not the correct value ,but in gp+8 is still a correct value and if a set a breakpoint before "lw t9,8(gp)" at anywhere after in_ram, the t9 can get the correct value, so it can run the mem_malloc_init, and run to hang at env_relocate as follow is the dissamble file bfc00b80 <board_init_r>: ...... bfc00c90: 8f990008 lw t9,8(gp) //to call mem_malloc_init bfc00c94: 00000000 nop bfc00c98: 27390610 addiu t9,t9,1552 bfc00c9c: 0320f809 jalr t9 bfc00ca0: 00000000 nop as follow is the printf info of two different reset and go situation U-Boot 1.1.3 (Nov 23 2005 - 19:23:54) checkboard Board: ACT213X (CPU Speed 0 MHz) DRAM: 32 MB Top of RAM usable for U-Boot at: a2000000 Reserving 146k for U-Boot at: a1fd8000 Reserving 192k for malloc() at: a1fa8000 Reserving 44 Bytes for Board Info at: a1fa7fd4 Reserving 36 Bytes for Global Data at: a1fa7fb0 Reserving 128k for boot params() at: a1f87fb0 Stack Pointer at: a1f87f98 before gd->bd operation! U-Boot 1.1.3 (Nov 23 2005 - 19:23:54) checkboard Board: ACT213X (CPU Speed 0 MHz) DRAM: 32 MB Top of RAM usable for U-Boot at: a2000000 Reserving 146k for U-Boot at: a1fd8000 Reserving 192k for malloc() at: a1fa8000 Reserving 44 Bytes for Board Info at: a1fa7fd4 Reserving 36 Bytes for Global Data at: a1fa7fb0 Reserving 128k for boot params() at: a1f87fb0 Stack Pointer at: a1f87f98 before gd->bd operation! after memmalloc! binrelocate Best Regards zhuzhenhua

2 2

[U-Boot-Users] Question about MPC8349
by Yogesh Patel 24 Nov '05

24 Nov '05

I want to find out how the console address is set for the MPC8349ads board. Basically there are lot of defines in immap_8349.h file, and for duart there is a structure defined. Want to know where all the fields are set. Thanks Pat __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

Re: Re: [U-Boot-Users] A question about initialization of SDRAM
by 蔡潋滟 24 Nov '05

24 Nov '05

Thanks for your reply! I had tried several different version of ppc_8xx-gcc to build the same u-boot.Only version 3.2.1 works ok. All the others(3.2.2, 3.3.1 and 3.3.3) have the problem that I have said before. So I think that maybe there is something different between these versions of gcc. Would you please explain it to me? Thanks a lot. >>In message <Tx948882797899.26592(a)send2.inner-21cn.com> you wrote: >>> >>> I am trying to use ELDK to make a u-boot on the board with MPC852T. >> >>"the board with MPC852T"? There is many such boards, most of them differnt. >> >>> There is declaration of rtx in cpu/mpc8xx/fec.c: >>... >>> static RTXBD *rtx = NULL; >>... >>> I think that "rtx" should be NULL at the first time fec_init() is entered,so the rtx will be given the value. >>> but after the ELDK make the u-boot, "rtx" isn't NULL at the first time fec_init() is entered, it is 0xffffffff. >> >>What makes you think so? The code is running perfectly fine on many >>boards. Which specific problem do you see? >> >>> Before the word "memctl->memc_mbmr = 0xD0924114" in the function initdram, rtx is NULL(0x0),but after that it >>> is 0xffffffff. Part of the fuction initdram is below: >> >>Looks as if there was a bug in the SDRAM init sequence for your board. >> >>> I wonder what happens in "memctl->memc_mbmr = 0xD0924114;",would you please explain it to me ? Thanks! >> >>Please see the processor's User's Manual; read the memory controller >>section. >> >>Best regards, >> >>Wolfgang Denk >> >>-- >>Software Engineering: Embedded and Realtime Systems, Embedded Linux >>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de >>WARNING: This Product Attracts Every Other Piece of Matter in the >>Universe, Including the Products of Other Manufacturers, with a Force >>Proportional to the Product of the Masses and Inversely Proportional >>to the Distance Between Them. >> > >= = = = = = = = = = = = = = = = = = = = > > = = = = = = = = = = = = = = = = = = = = 　　　　　　　　致礼！　　　　　　　　蔡潋滟　　　　　　　　killercai(a)21cn.com 　　　　　　　　　　2005-11-24

2 1

Re: [U-Boot-Users] u-boot 1.1.2 and atoi in exports not working
by Wolfgang Denk 24 Nov '05

24 Nov '05

Dear John, in message <6a7ac2300511240637p1b281106k2849ac3bb5a96715(a)mail.gmail.com> you wrote: > > > What makes you think atoi() is available in U-Boot? > > I see all these other routines using it. I figured I could use it as well. ie. Be careful! Just running "grep" does not mean anything. You have to check on which #ifdef's these lines depend. > common/hush.c:104:#include <stdlib.h> /* getenv, atoi */ > common/hush.c:606: exit (atoi(child->argv[1])); > common/hush.c:803: n=atoi(child->argv[1]); > common/hush.c:2667: num=atoi(o->data); For example, the hush shell is a port from the busybox project, and was changed only in the minimal necessary way. And if you look for example at common/hush.c:104:#include <stdlib.h> /* getenv, atoi */ you should check the context: ... 100 #ifdef CFG_HUSH_PARSER 101 #ifndef __U_BOOT__ 102 #include <ctype.h> /* isalpha, isdigit */ 103 #include <unistd.h> /* getpid */ 104 #include <stdlib.h> /* getenv, atoi */ ... Note the "#ifndef __U_BOOT__" part! > tools/mpc86x_clk.c:205: xin = atoi(argv[1]); > tools/mpc86x_clk.c:206: want_gclk2 = atoi(argv[2]); > tools/mpc86x_clk.c:208: ppm = atoi(argv[3]); > tools/ncb.c:14: port = atoi (argv[1]); Also, tools/ are tools that are running on the host system - they don't have anything in common with U-Boot code. Summary: there is no atoi() in U-Boot. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de In an organization, each person rises to the level of his own incom- petency - The Peter Principle

1 0

[U-Boot-Users] Patch for support of i3micro mood300 (MIPS/au1550)
by jakob.sandgren＠i3micro.com 24 Nov '05

24 Nov '05

Hi, Attached is a patch that will enable support for the i3micro Set Top Box "mood300". Most of the files changes is in boards/i3micro, but there is some other changes in the generic mips code (add calls to nand init, etc). The development has been done by Leif Lindholm, but I will now maintain this code at i3micro. The patch applies cleanly against git head. CHANGELOG entry: Add support for i3micro mood300 Set Top Box. Best Regards, Jakob Sandgren i3 micro technology

1 0

[U-Boot-Users] Moving u-boot location in ram to do full mem-test?
by Martin Egholm Nielsen 24 Nov '05

24 Nov '05

Hi, I'm using "mtest" to test the sdram somewhat, but parts of the ram is ofcourse left untested doing so - due to stack- and u-boot positioning. Enabling DEBUG'ing I narrowed in the plausible test segment into something like: => mtest 1090 3f8af37 where the last value is based on the information: Top of RAM usable for U-Boot at: 04000000 Reserving 208k for U-Boot at: 03fcb000 Reserving 256k for malloc() at: 03f8b000 Reserving 128 Bytes for Board Info at: 03f8af80 Reserving 48 Bytes for Global Data at: 03f8af50 Stack Pointer at: 03f8af38 New Stack Pointer is: 03f8af38 Now running in RAM - U-Boot at: 03fcb000 FLASH: [flash_init, 771] Entering ... [flash_init, 772] flash_info = 0x03FFEB20 ... U-Boot relocated to 03fcb000 and the first from manual testing. So, I would like to make a new u-boot binary that offered me the possibility to test the first part - from "0x0" to "0x108F" and from "0x3f8af37" to "0x3ffffff". I've scanned my board-header to see if any of these addresses are directly present there, but without luck. The nearest I get to something that smells of the lower boundary, is the value of "CFG_INIT_RAM_ADDR" and "CFG_OCM_DATA_SIZE" both having the value 0x1000. Any clues? BR, Martin Egholm

2 10

[U-Boot-Users] u-boot 1.1.2 and atoi in exports not working
by John Davis 24 Nov '05

24 Nov '05

Hello I am trying to use atoi in my code. I can not get the image to link properly when i try to add it. Here is my setup. Addded to include/_exports.h EXPORT_FUNC(atoi) Added to include/exports.h int atoi(const char *); Added to common/exports.c gd->jt[XF_atoi] = (void *)atoi; But when I do the make of u-boot, I get : /gcc-lib/ppc-linux/3.3.3/pic -lgcc --end-group \ -Map u-boot.map -o u-boot common/libcommon.a(exports.o)(.got2+0x20): In function `jumptable_init': /home/davis/progs/c/u-boot-1.1.2/common/exports.c:14: undefined reference to `atoi' make: *** [u-boot] Error 1 However, I did the same thing for get_dcr and set_dcr and it worked. Please advise, JD

2 1

Re: [U-Boot-Users] Re: where is the interrupt vectors?
by KokHow Teh 24 Nov '05

24 Nov '05

>In message <1132812293.2550.20.camel@PC6> you wrote: >> >> Thank you for your reply ,but I think you misunderstood my question. >No, it is you who does not understand. >> What I said is the extern interrupts, and now I have know that U-BOOT is >> no support the interrupts, so it doesn't need the vectors. >You are wrong. You can use interrupts in U-Boot. There is even code >in the examples directory which does so. and here are the external interrupts: ./74xx_7xx/interrupts.c:62:external_interrupt(struct pt_regs *regs) ./74xx_7xx/interrupts.c:64: puts("external_interrupt (oops!)\n"); ./74xx_7xx/start.S:122: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt) ./mpc5xx/interrupts.c:75:void external_interrupt (struct pt_regs *regs) ./mpc5xx/start.S:208: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt) ./mpc5xxx/interrupts.c:48:external_interrupt(struct pt_regs *regs) ./mpc5xxx/interrupts.c:50: puts("external_interrupt (oops!)\n"); ./mpc5xxx/start.S:206: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt) ./mpc8220/interrupts.c:47:void external_interrupt (struct pt_regs *regs) ./mpc8220/interrupts.c:49: puts ("external_interrupt (oops!)\n"); ./mpc8220/start.S:167: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt) ./mpc824x/interrupts.c:56:void external_interrupt (struct pt_regs *regs) ./mpc824x/start.S:218: STD_EXCEPTION(EXC_OFF_EXTERNAL, ExtInterrupt, external_interrupt) ./mpc8260/interrupts.c:177:void external_interrupt (struct pt_regs *regs) ./mpc8260/start.S:277: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt) ./mpc83xx/interrupts.c:54:void external_interrupt (struct pt_regs *regs) ./mpc83xx/start.S:219: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt) ./mpc8xx/interrupts.c:68:void external_interrupt (struct pt_regs *regs) ./mpc8xx/start.S:222: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt) ./nios/interrupts.c:103:void external_interrupt (struct pt_regs *regs) ./nios/traps.S:318: * The default handler passes control to external_interrupt(). So trap ./nios/traps.S:323: * external_interrupt(). This lets the underflow and overflow handlers ./nios/traps.S:398: pfx %hi(external_interrupt@h) ./nios/traps.S:399: movi %o1, %lo(external_interrupt@h) ./nios/traps.S:400: pfx %xhi(external_interrupt@h) ./nios/traps.S:401: movhi %o1, %xlo(external_interrupt@h) ./nios2/exceptions.S:83: movhi r3, %hi(external_interrupt) ./nios2/exceptions.S:84: ori r3, r3, %lo(external_interrupt) ./nios2/interrupts.c:121:void external_interrupt (struct pt_regs *regs) ./ppc4xx/interrupts.c:199:void external_interrupt(struct pt_regs *regs) ./ppc4xx/interrupts.c:222:} /* external_interrupt CONFIG_440GX */ ./ppc4xx/interrupts.c:226:void external_interrupt(struct pt_regs *regs) ./ppc4xx/start.S:783: STD_EXCEPTION(0x500, ExtInterrupt, external_interrupt)

2 1

[U-Boot-Users] get_dcr and set_dcr in loadable apps
by John Davis 24 Nov '05

24 Nov '05

Hello I am trying to use get_dcr and set_dcr in my examples/app.c code. I added g/set_dcr to exports.h and _exports.h. but I get a lock up when I call them. Any idea how to access these functions from loadable apps? JD

2 2

[U-Boot-Users] Re: where is the interrupt vectors?
by terry 24 Nov '05

24 Nov '05

> Subject: Re: [U-Boot-Users] where is the interrupt vectors? > To: u-boot-users(a)lists.sourceforge.net > From: "KokHow Teh" <KokHow.Teh(a)marconi.com> > Date: Thu, 24 Nov 2005 11:32:24 +0800 > > > > > >I want to support some perpherals which need use the I/O pins of INT. > >And it need to be allocated the vectors, depending on the INT ports. > >How does u-boot support this, and where I can find it? > > Depending on your CPU architecture, interrupt/exception vectors are setup > in start.S > Thank you for your reply ,but I think you misunderstood my question. What I said is the extern interrupts, and now I have know that U-BOOT is no support the interrupts, so it doesn't need the vectors. regards Terry

2 2