July 2006 - U-Boot

Re: [U-Boot-Users] [DNX#2006071142000047] [DNX#2006071842000016] [patch] Adde [...]
by DENX Support System 20 Jul '06

20 Jul '06

Hello list, inside the automatic U-Boot patch tracking system a follow up to [DNX#2006071142000047] was entered through the web interface: <snip> > > Also, I consider it a very bad ide to hard-wire MAC and IP addreses > > in the board config file. And pre-defining constants like "unknown" > > for hostname, "/nfsroot" for rootpath or "your.uImage" for bootfile > > is, well, let's say not very helpful. If there are no useful common > > setttings it is better NOT to set such variables at all. > I thought that "hard-wire MAC and IP addresses in the board config > file" were just compiled into default environmental variables, not > hard-wired. > > Would it then be appropriate to do something like this: > #if 0 /* user option to compile with default network values */ > Default ip settings > Hostname, bootfile, rootpath constants > #endif > So that the *option* of setting up default settings is given to the > users in case that makes sense for their applications? > > > Finally, I recommend to use "${...}" variable syntax in all your > > definitions, as this makes it possible to switch command line parsers > > without need to change the environment definitions. > That is a valuable point. I will do this. > > > > * Please keep lists sorted (like board names in MAKEALL) > Of course. Additionally, I just changed the 8xx section from columns to > rows so that they would compile in the correct order now. > > -JM </snip> Your U-Boot support team

1 0

Re: [U-Boot-Users] [DNX#2006071842000016] [patch] Added support for Embedded [...]
by Jeff Mann 20 Jul '06

20 Jul '06

> Also, I consider it a very bad ide to hard-wire MAC and IP addreses > in the board config file. And pre-defining constants like "unknown" > for hostname, "/nfsroot" for rootpath or "your.uImage" for bootfile > is, well, let's say not very helpful. If there are no useful common > setttings it is better NOT to set such variables at all. I thought that "hard-wire MAC and IP addresses in the board config file" were just compiled into default environmental variables, not hard-wired. Would it then be appropriate to do something like this: #if 0 /* user option to compile with default network values */ Default ip settings Hostname, bootfile, rootpath constants #endif So that the *option* of setting up default settings is given to the users in case that makes sense for their applications? > Finally, I recommend to use "${...}" variable syntax in all your > definitions, as this makes it possible to switch command line parsers > without need to change the environment definitions. That is a valuable point. I will do this. > * Please keep lists sorted (like board names in MAKEALL) Of course. Additionally, I just changed the 8xx section from columns to rows so that they would compile in the correct order now. -JM

1 0

[U-Boot-Users] uboot script parameters.
by Leonid 20 Jul '06

20 Jul '06

Hi: Couple questions regarding u-boot scripts: 1) Is it possible to create proprietary u-boot script which takes parameters (like bash for instance): setenv getkernel tftp 2000000 \$1\/uImage where I used $1 for 1st parameter like in bash (u-boot may have different notation). Then later I can run my script with arbitrary parameter: run getkernel /images 2) Looks like u-boot doesn't support nested substitution of script parameters. For instance: => setenv sw_ver 1.0.10 => setenv image_path rel\/\$(sw_ver) => printenv image_path image_path=rel/$(sw_ver) => Am I doing something wrong? Thanks, Leonid.

2 3

[U-Boot-Users] No serial output from mips/au1550
by mitsy 20 Jul '06

20 Jul '06

I'm using BDI2000 to debug my version of u-boot, which is still under development. I can step through the code via telnet with bdi, but I'm not seeing any output on serial port when it's supposed to be writing stuff out. The only time I see anything on the serial console is when I reset the target, before running anything. It spits put some garbage. Within board_init_f(), both init_baudrate and serial_init seem to be running fine. Has anybody experienced something similar to this? If so, what am I missing to make it work? TIA!

4 3

Re: [U-Boot-Users] [Retrieved] No serial output from mips/au1550
by Jeff Mann 19 Jul '06

19 Jul '06

"It spits put some garbage" I know this sounds trivial but recheck that you are using the right serial UART and baud rate. "but I'm not seeing any output on serial port when it's supposed to be writing stuff out" Also check that the TTL level to RS-232 logic level transceiver is enabled (the MAX232 or equivalent). Also, look at the uart buffer in memory and make sure u-boot gets that far and sends stuff to the UART. -JM

1 0

[U-Boot-Users] MPC8548 PCIe Support
by Steve Williams 19 Jul '06

19 Jul '06

Hi I wonder if anybody has any views as to what work is involved in supporting the PCIe interface of the (Freescale) MPC85xx's that have this interface. From first look at the data book I wonder if the PCIe interface is in fact compatible enough with the standard PCI interface to allow the exiting code to work correctly provided that the address and data register addresses (the two registers used to initiate a config cycle) for the PCIe interface are used. In my case I am porting u-boot to custom MPC8548 hardware that has a custom, fixed PCIe peripheral on the PCIe bus. I think I can kludge things for this device if needed but it would be nice to do it properly and feed the results back to the group. Any comments/views would be much appreciated. Regards Steve Williams

1 0

Re: [U-Boot-Users] [DNX#2006071942000014] [patch] add-support-for-new-tqm5200 [...]
by DENX Support System 19 Jul '06

19 Jul '06

Hello list, inside the automatic U-Boot patch tracking system a new ticket [DNX#2006071942000014] was created: <snip> > In message > <47F3F98010FF784EBEE6526EAAB078D1024F8172(a)tq-mailsrv.tq-net.de> you > wrote: > > > > * Add support for new TQM5200 revisions > > Patch by Martin Krause, 7 Jul 2006 > > Applied, thanks. > > 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 > "No matter where you go, there you are..." - Buckaroo Banzai </snip> Your U-Boot support team

1 0

Re: [U-Boot-Users] [DNX#2006071942000014] [ [...]
by U-Boot patch tracking system 19 Jul '06

19 Jul '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#2006071942000014]. Your U-Boot support team Powered by OTRS (http://otrs.org/)

1 0

[U-Boot-Users] Patch approvation procedure
by Marco Cavallini 19 Jul '06

19 Jul '06

Hi, Just for curiosity I'd like to know (and understand) what is the patch approvation procedure. For example I posted a PXA270 MAINSTONE patch on 9/3/06 and then Wolfgang added it with the new system on 1/4/06 [DNX#2006040142000295] Which are the requirements for approvation and subsequent insertion in the development tree ? TIA -- Marco Cavallini Koan s.a.s. - Bergamo - ITALIA Embedded and Real-Time Software Engineering Tel. +39-(0)35-255.235 - Fax +39-178-223.9748 www.KoanSoftware.com | www.KaeilOS.com

3 5

[U-Boot-Users] [patch] add-support-for-new-tqm5200-revisions.patch
by Martin Krause 19 Jul '06

19 Jul '06

CHANGELOG: * Add support for new TQM5200 revisions Patch by Martin Krause, 7 Jul 2006 - Support for TQM5200S (short version of the module without SM501 graphic controller) - Support for modules with 'N' type S29GL128N Spansion flashes. Because the new flashes have a doubled sector size, the flash layout had to be modified. - Support for MPC5200B cpu (mostly support for the second SDRAM bank)

2 1