April 2007 - U-Boot

[U-Boot-Users] Cannot boot reliably vxWorks on PPC44x
by Niklaus Giger 04 Apr '07

04 Apr '07

Hi I am trying to boot a vxWorks image (version 6.4) on my Yosemite board (PPC440EP) using the amcc440ep BSP. Booting from a vxWorks bootrom worked without problems. Booting vxWorks from u-boot (more or less git HEAD) failed. After uncommenting in the vxWorks amcc440ep/config.h the following four lines #undef INCLUDE_440X5_DCACHE_RECOVERY #undef INCLUDE_440X5_TLB_RECOVERY #undef INCLUDE_440X5_PARITY_RECOVERY #undef INCLUDE_440X5_TLB_RECOVERY_MAX #undef INCLUDE_440X5_MCH_LOGGER vxWorks boots sometimes if I reset the the board using our BDI. It seems that it never boots after the first reset, but often after the second reset. It never boots without an attached BDI. vxWorks and BDI initialize the TLB quite differently, but the vxWorks startup seems to have already initialised the TLB, but more or less around the time it activates it. Has anybody seen a similar problem? Has anybody successfully booted a vxWorks image on a PPC44x processor? Has anybody an idea where this problem could stem from? (I use the BDI config 4xxep440.cfg from ftp://ftp.denx.de/pub/BDI2000/). BTW, the boot cmd of vxWorks expects a parameter, therefore I think it would make sense to apply a patch like diff --git a/common/cmd_elf.c b/common/cmd_elf.c old mode 100644 new mode 100755 index 0e3d56f..dc4eb27 --- a/common/cmd_elf.c +++ b/common/cmd_elf.c @@ -213,7 +213,7 @@ int do_bootvx (cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]) (char *) bootaddr); printf ("## Starting vxWorks at 0x%08lx ...\n", addr); - ((void (*)(void)) addr) (); + ((void (*)(int)) addr) (2); /* 0 => BOOT_NORMAL 2=> BOOT_CLEAR */ puts ("## vxWorks terminated\n"); return 1; Best regards Niklaus Giger

2 3

[U-Boot-Users] cpu/mpc8xx/i2c.c relocation problem on 880
by DI BACCO ANTONIO - technolabs 04 Apr '07

04 Apr '07

In function i2c_init in file cpu/mpc8xx/i2c.c instruction: iip->iic_rpbase = 0 to disable relocation makes the mpc880 hang. Does anyone agree? Bye, Antonio.

2 1

Re: [U-Boot-Users] PATCH add SMN42 board from Siemens
by Gary Jennejohn 04 Apr '07

04 Apr '07

"Peter Pearse" writes: > > > > -----Original Message----- > > From: u-boot-users-bounces(a)lists.sourceforge.net > > [mailto:u-boot-users-bounces@lists.sourceforge.net] On Behalf > > Of Gary Jennejohn > > Sent: 03 April 2007 15:58 > > To: u-boot-users(a)lists.sourceforge.net > > Subject: [U-Boot-Users] PATCH add SMN42 board from Siemens > > > > Hi, > >= > > The patch is rather large and can be downloaded at > > ftp://ftp.denx.de/pub/patches/SMN42_NEW > > > > The eth.c files for lpc2292sodimm and SMN42 are identical, > > but the driver is very board-specific and cannot be put into > > e.g. drivers. > > Gary > > I stand ready to be corrected, but I thought the way round that > was > > a) move the eth.c to drivers/<unique name>.c > b) add <unique_name>.o to the object list in drivers/Makefile > c) encapsulate the code with #ifdef CONFIG_<UNIQUE_DEF> > d) add #define CONFIG_<UNIQUE_DEF> to the include/configs/<board>.h for > the lpc2292sodimm and SMN42 boards > e) check I haven't missed anything from this list..... > > see e.g drivers/smc91111.c used by DK1C20, DK1S10, EP1C20 etc > > This might still be possible if the lpc2292sodimm and SMN42 eth.c differ > slightly, > using a board specific define..... > Actually, I originally had the driver installed as cpu/arm720t/lpc2292/ \ enc28j60.c with an entry in .../lpc2922/Makefile. Then I though better of it and concluded that it wasn't really CPU-specific and moved it back to the board-specific directories. There's already a CONFIG_ENC28J60 in the driver and the config files, so basically I've already done 50% of what you suggest. I didn't realize that having the define in these files would make the driver suitable to be placed under drivers. But I question whether it's really worth my doing all the work involved with this change (make the change, test that u-boot still compiles and works and then re-roll the patch) to save a few kB in the tree. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde ===================================================================== DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk Office: Kirchenstr. 5, D-82194 Groebenzell, Germany =====================================================================

2 2

Re: [U-Boot-Users] configure to run a xipImage
by Joakim Nordell 04 Apr '07

04 Apr '07

> -----Original Message----- > From: wd(a)denx.de [mailto:wd@denx.de] > To: Joakim Nordell > In message <MLEGLOMOGFHHOOFGOCHAGEBADAAA.tde02003(a)gmail.com> you wrote: > > > > I would like to run a xipImage. I'm sure I have to tell u-boot > that this is the case, but how? > > For the moment I have an xipImage that prints "Magic Bad > Number" when I try to start it. > > This is on PowerPC, I assume? > > An XIP image has the following properties: it is not compressed > (IH_COMP_NONE), and load address is the current start address in > memory (ntohl(hdr->ih_load) == addr); see "common/cmd_bootm.c" lines > 320ff. > No, sorry. It is an Atmel AT91RM9200 (uCRouter) board running u-boot 1.1.1. I have built a linux-2.6.15-xipImage to run in the flash memory. My thought is that the start up time will increase a bit. I have insearted the start address for the kernel within the menuconfig -> boot options. I guess I now have to tell u-boot that the kernel should not be loaded to RAM, and instead run in flash. Is that correct? If so, How can I do that? Greetings Joakim Nordell

2 1

[U-Boot-Users] ECC testing/error injection
by vb 04 Apr '07

04 Apr '07

Gentlemen, browsing the docs in the root directory reveals very little, and the list archives don't seem to be available on sourceforge, so I am asking the questions here. I am trying to enable the ECC feature on an 8541 platform, which uses DDR SDRAM. I noticed that there are config flags available just for that: CONFIG_DDR_ECC and CONFIG_DDR_ECC_CMD, used in a few platforms (my port is based on 1.1.6): # grep CONFIG_DDR_ECC include/configs/*h|grep define include/configs/MPC8349EMDS.h:#define CONFIG_DDR_ECC_CMD /* use DDR ECC user commands */ include/configs/MPC8540ADS.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ include/configs/MPC8541CDS.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ include/configs/MPC8548CDS.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ include/configs/MPC8555CDS.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ include/configs/MPC8560ADS.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ include/configs/MPC8641HPCN.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ include/configs/PM854.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ include/configs/PM856.h:#define CONFIG_DDR_ECC /* only for ECC DDR module */ intersetingly enough, the only platform which has a CLI command to demonstrate ECC functionality (MPC8349EMDS has CONFIG_DDR_ECC_CMD defined) does not have CONFIG_DDR_ECC defined. I moved the CLI command code from board/mpc8349emds/mpc8349emds.c into the common directory and modified it to work with both 83xx and 85xx memory configuration registers' layouts. The thing is that I can't make the ECC errors injection to work, rather, I can't get any ECC errors reported. So, a few questions: - how do I find out if there was any documentation associated with the CLI command implementation contribution in board/mpc8349emds/mpc8349emds.c? - have anyone tested ECC implementation on any 85XX platform which have the flag defined. How did you test it, if so? any input/hints would be highly appreciated, cheers, Vadim

2 2

[U-Boot-Users] [Git push][Microblaze]Please pull u-boot-microblaze.git
by Michal Simek 04 Apr '07

04 Apr '07

[PATH][Microblaze] timer support interrupt controller support flash support ethernet support cache support board information support env support booting image support adding support for Xilinx ML401 commit 76316a318de91f6184e7c22a10e02d275ade2441 commit cfc67116a706fd18b8f6a9c11a16753c5626d689 Hi, I add patch to u-boot-microblaze tree. How to generate this log??? include/asm-blackfin/cpu/cdefBF532.h | 398 ------ Best regards Michal Simek

5 6

[U-Boot-Users] 85xx Custodian Question
by Jon Loeliger 03 Apr '07

03 Apr '07

Wolfgang, I am working on the 8544 DS port, and need to begin releasing that code to the mainline U-Boot tree. Would you like me to: Release this code to you through Andy in the 85xx custodian tree? Or do I have access to push into the 85xx tree as well? Release it to you in the 86xx custodian repository? Perhaps on an 8544 branch? Just send patches to the list and have you apply them? Some other means? Thanks, jdl

2 1

[U-Boot-Users] Where to put semi-common files?
by Jon Loeliger 03 Apr '07

03 Apr '07

Wolfgang, We are needing to introduce the 8544 DS board soon. It's board is essentially identical to the board in the 8641HPCN. Both boards have an FPGA on them that controls carious system parameters and configuraiton parts, including the reset logic that we've already discussed. That FPGA is called "PIXIS" and has support code for it already added to the 8641hpcn's directory. Naturally, we need exactly the same code for the 8544 DS board now too. But it can't be in a shared board directory, nor are the two SoC parts even in the same CPU families. One is 85xx, the other is 86xx. The FPGA isn't really a device for which one might think "driver/", so that likely isn't the right directory either. Perhaps lib_ppc/? Actually, there are other very similar bodies of code that are shared across boards and CPU families (for example, the DDR setup code in spd_sdram.c). Do you have a good place where you would like to see this sort of shared code? It is easy enough to pick up just the parts that are wanted during compilation due to CONFIG options, but we need a directory from which we can share these sources. Recommendations? Thanks, jdl

3 2

[U-Boot-Users] PATCH add SMN42 board from Siemens
by Gary Jennejohn 03 Apr '07

03 Apr '07

Hi, The patch is rather large and can be downloaded at ftp://ftp.denx.de/pub/patches/SMN42_NEW The patch is against a u-boot tree checked out today at 14:35 (GMT+1). Changes: 1) add cpu/arm720t/lpc2292 and include/asm-arm/arch-lpc2292 with files common to ports for the LPC2292. 2) patches to the lpc2292sodimm port reflecting (1). 3) errata fixes to board/lpc2292sodimm/eth.c obtained from Siemens. 4) add board/siemens/SMN42. The eth.c files for lpc2292sodimm and SMN42 are identical, but the driver is very board-specific and cannot be put into e.g. drivers. Signed-off-by: Gary Jennejohn <garyj(a)denx.de> -- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde ===================================================================== DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk Office: Kirchenstr. 5, D-82194 Groebenzell, Germany =====================================================================

2 1

[U-Boot-Users] build u-boot for ns9750dev
by matze 03 Apr '07

03 Apr '07

hi, i'm trying to built u-boot for the ns9750dev board (actually for the softgun simulator). u-boot v1.1.6 contains the file include/configs/ns9750dev and the directory board/ns9750dev , but the makefile doesn't contain the target ns9750dev_config. does this mean that ns9750dev support is still in an experimental phase or is there another way of building it? thanks in advance m. -- Representation of the world, like the world itself, is the work of men; they describe it from their own point of view, which they confuse with the absolute truth (Simone de Beauvoir) .''`. using free software / Debian GNU/Linux | http://debian.org : :' : `. `'` gpg --keyserver keys.indymedia.org --recv-keys B9A88F6F `-

2 1