October 2006 - U-Boot

[U-Boot-Users] debug u-boot using bdi2000
by Reeve Yang 13 Oct '06

13 Oct '06

I'm trying to use bdi2000+gdb to debug u-boot. The image is ROM image on flash, whenever I connect gdb to bdi, I saw execution stops at: _start: /* time t 0 */ li r21, BOOTFLAG_COLD /* Normal Power-On: Boot from FLASH*/ ===>here nop b boot_cold Then though I can set break point, e.g. cpu_init_f, but when continue running break point never stops execution and u-boot just runs by itself. Does it mean I can only debug ram image? does anyone has experience on this could shed some lights? Thanks. - Reeve

4 8

[U-Boot-Users] software FP yada yada yada
by Matt Gessner 13 Oct '06

13 Oct '06

Howdy, I've got a 1.1.2 u-boot that someone else set up and configured, and it builds just fine (it doesn't run yet, but that's a different story). It builds with a 3.4.1 gcc toolchain. I'm building for ARM91RM9200DK. When I got 1.1.4, I get the infamous message about how u-boot needs a software FP whereas my gcc is set up for hardware fp. What I would LIKE to know is why 1.1.2 builds just fine but 1.1.4 does not. Any light you can shed would be appreciated. Thanks, Matt Gessner Avidyne Corp.

6 9

Re: [U-Boot-Users] [DNX#2006040842000022] PATCH: CPC0_PCI init [...]
by U-Boot patch tracking system 13 Oct '06

13 Oct '06

Hi Tolunay, > * (ppc405ep) Add support for board configuration of CPC0_PCI register > This is needed to be able to configure PerWE*/PCI_INT* pin as PerWE* Applied, thanks. And please remember to send your board support code soon, so that the new code will get used. Your Ticket-Team -- Stefan Roese -- DENX Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: support(a)denx.de Powered by OTRS (http://otrs.org/)

1 0

Re: [U-Boot-Users] [DNX#2006040842000013] PATCH: CFG_GPIO0_OR [...]
by U-Boot patch tracking system 13 Oct '06

13 Oct '06

Hi Tolunay, > CHANGELOG: > > * (ppc4xx) Add CFG_GPIO0_OR, CFG_GPIO0_ODR to setup GPIO completely. > - Add configuration of Open Drain GPIO Output selection > - Add configuration of initial value of GPIO output pins Applied, thanks. And please remember to send your board support code soon, so that the new code will get used. Your Ticket-Team -- Stefan Roese -- DENX Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: support(a)denx.de Powered by OTRS (http://otrs.org/)

1 0

[U-Boot-Users] [PATCH] Fix possible uninitialized variable compiler warning.
by Grant Likely 13 Oct '06

13 Oct '06

This patch applies against the u-boot tree at git://www.jdl.com/software/u-boot-86xx.git When CONFIG_OF_FLAG_TREE is set, the compiler complains that 'len' in do_bootm_linux() may be uninitialized. There is no possibility in the current code that len will get used uninitialized, but this fix follows the existing convention of setting both len and data to zero at the same time. Signed-off-by: Grant Likely <grant.likely(a)secretlab.ca> --- common/cmd_bootm.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/common/cmd_bootm.c b/common/cmd_bootm.c index 652d843..af949a3 100644 --- a/common/cmd_bootm.c +++ b/common/cmd_bootm.c @@ -623,7 +623,7 @@ #ifdef CONFIG_OF_FLAT_TREE /* Look for a '-' which indicates to ignore the ramdisk argument */ if (argc >= 3 && strcmp(argv[2], "-") == 0) { debug ("Skipping initrd\n"); - data = 0; + len = data = 0; } else #endif -- 1.4.2.rc2.g822a

5 20

Re: [U-Boot-Users] Can I write to flash using mw command
by bilahari akkiraju 13 Oct '06

13 Oct '06

I did protect off all I have tried the following command sequences but didnt succeed in my objective of writing to and erasing first sector on flash. WRITE COMMAND SEQUENCE: mw ff000555 00AA00AA mw ff0002AA 00550055 mw ff000555 00A000A0 mw ff000000 12345678 SECTOR ERASE COMMAND SEQUENCE: mw ff000555 00AA00AA mw ff0002AA 00550055 mw ff000555 00800080 mw ff000555 00AA00AA mw ff0002AA 00550055 mw ff000000 00300030 Note: I tried mw.b, mw.w, mw.l with appropriate data but didnt succeed. In first place is it possible to write to AMD flash manually like this or shud it be done only programatically. Any one has tried writing to flash this way before ( I could write to Intel strata flash this way). I walked through u-boot code for cfi_flash.c and flash_write() function that is called when cp (copy) command is invoked, the code does the same thing, the only extra thing it does is it polls on data register bits for a certain amount of time (flash erase, write timeout intervals) and also does a reset to bring back device to read array mode mw.w ff000000 00F0 ; reset cmd I have a ppc 8343 processor on board. I am wondering if U-boot that came with my target board has configuration that is preventing me to write to flash (but cp commands works fine with flash). Any one who has same spansion flash chip s29GL064M can try it, I cannot figure out the missing link in the chain, any advise, comments, suggestion will be of great help Thanks, Bilahari --- Wolfgang Denk <wd(a)denx.de> wrote: > In message > <20061005222823.71219.qmail(a)web33206.mail.mud.yahoo.com> > you wrote: > > > > -> I read my board's spec and found out that I > have > > two spansion s29GL064M devices on my board whose > data > > bus is 16-bit wide and address bus is 32-bit wide. > > They are attached as 16-bit devices. > > Then your command sequence was wrong. > > > -> I looked at the data sheet of the spansion > > s29GL64M > > and I am sure I am using the right command > sequences > > (x16 Mode commands) for erase and program. > > No. In 16 bit mode addresses get shifted by one bit, > and your command > word must address both chips, i. e. instead of > > mw.b 0xff000555 0xAA > > you need > > mw FF000AAA 00AA00AA > > > -> How can I check if my memory controller is > > properly configured or not. > > By carefully studying the hardware documentation, > processor User's > manual, chip documentation, etc. Then perform a code > review. > > 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 > Do you suppose the reason the ends of the `Intel > Inside' logo don't > match up is that it was drawn on a Pentium? > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

6 10

Re: [U-Boot-Users] software FP yada yada yada
by Matt Gessner 12 Oct '06

12 Oct '06

> -----Original Message----- > From: u-boot-users-bounces(a)lists.sourceforge.net [mailto:u-boot-users- > bounces(a)lists.sourceforge.net] On Behalf Of Wolfgang Denk > Sent: Thursday, October 12, 2006 4:30 PM > To: Matt Gessner > Cc: u-boot-users(a)lists.sourceforge.net > Subject: Re: [U-Boot-Users] software FP yada yada yada > > In message <131AF8573CF31945B5B11E4201D3F1E142BA28(a)mail3.Avidyne.com> you > wrote: > > > > When I got 1.1.4, I get the infamous message about how u-boot needs a > > software FP whereas my gcc is set up for hardware fp. > > > > What I would LIKE to know is why 1.1.2 builds just fine but 1.1.4 does > > not. > > There have been so many changes between 1.1.2 and 1.1.4 that it's > difficult to tell which specific change causes the problem, but if > you check the "make" output you can clearly see where the problem is > coming from - your compiler fails to provide the required softfloat > routines. Which is kind of funny, since there are not so many ARM > systems with FPU around. > > My recommendation is to fix the toolchain. It certainly does seem odd that it was built with the floating point hardware stuff compiled in, given that the unit has no floating point support. My hands are a bit tied in that I don't have control over the toolchain, but I will bring it up with them. If I have to, I suppose I'll just have to stick with the 1.1.2 build, and figure out how to make it work. > > 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 > I am pleased to see that we have differences. May we together become > greater than the sum of both of us. > -- Surak of Vulcan, "The Savage Curtain", stardate 5906.4 > > ------------------------------------------------------------------------ - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users Thanks for your prompt reply. Regards, Matt Gessner

2 1

Re: [U-Boot-Users] [DNX#2006101242000011] VkAGRA
by U-Boot patch tracking system 12 Oct '06

12 Oct '06

Dear Mr. U. Boot, thank you for your contribution to the U-Boot project. Your e-mail was registered at our system under the ticket number [DNX#2006101242000011]. Please keep this ticket ID string in the subject line of any e-mail replies!!! Your U-Boot support team Powered by OTRS (http://otrs.org/)

1 0

[U-Boot-Users] bactrace use
by alayrac christophe 12 Oct '06

12 Oct '06

Dear Wolfgang I found out that I should not type the 0x before the address from the stdin. Then it works properly. The offset is entered with the 0x prefix on the command line, and negative offset (my case 0x2000000 - 0x3FA9000 = -0x1FA9000) works also. Thank you one more time for your help Bests Regards Chris

1 0

[U-Boot-Users] backtrace question
by alayrac christophe 12 Oct '06

12 Oct '06

Hi all, I'm trying to debug i2c xilinx code to be abble to store environment in EEPROM. My code is stoppped at address 0x3FC1078, the relocation address is 0x3FA9000. The TEXT_BASE address use to build u-boot is 0x2000000. So if i'm not wrong I should use backtrace with the address : 0x2000000 + ( 0x3FC1078 - 0x3FA9000). Is that right? The example in http://www.denx.de/wiki/bin/view/DULG/DecodingUBootCrashDumps sounds strange, and in my case I will have a negative address. I think that there is an error in the example. I'm coming to you beacause the backtrace (download from denx ftp) process start properly but then hang up and did not give any results. alayrac@debian-ca:~/u-boot$ ./backtrace System.map 0x2018078 Reading symbols from System.map Using Address Offset 0x2018078 Any track? Chris

3 3