January 2006 - U-Boot

[U-Boot-Users] SDRAM problem
by ronen ronen 26 Jan '06

26 Jan '06

3 2

[U-Boot-Users] Passing board info from uboot to linux
by Mustafa Çayır 26 Jan '06

26 Jan '06

hi, 1- when linux image is zImage, there is no boot parameter passing from bootloader(DINK32 or customer firmware) to kernel and bootloader integrated into linux image. In this situation, is linux kernel start at point linux/arch/ppc/kernel/haed.S - _start start up code ? 2- when linux image is uImage, how do u-boot pass board info data structure to linux kernel? where is linux kernel starting point in linux sources? Best Regards, Mustafa

2 1

[U-Boot-Users] [PATCH] Fixing 'pci' command output
by KRONSTORFER Horst 26 Jan '06

26 Jan '06

hi! currently a series of 'pci_bus_to_hose() failed' messages are printed when pciinfo() is called with a invalid (out-of-bounds) bus number. this patch fixes the output of the 'pci' command by *) checking that the given bus number is actually a number *) checking that the given bus number is not out-of-bounds before doing a scan *) printing 'pci_bus_to_hose() failed' only when DEBUG is defined Signed-off-by: Horst Kronstorfer <hkronsto <at> frequentis.com> CHANGELOG * Fixing 'pci' command output: Patch by Horst Kronstorfer, 26 Jan 2006 diff --git a/common/cmd_pci.c b/common/cmd_pci.c index 4508546..e0e166c 100644 --- a/common/cmd_pci.c +++ b/common/cmd_pci.c @@ -71,6 +71,11 @@ void pciinfo(int BusNum, int ShortPCILis unsigned short VendorID; pci_dev_t dev; + if (pci_bus_to_hose(BusNum) == NULL) { + printf("Error: bus no. %d does not exist\n", BusNum); + return; + } + printf("Scanning PCI devices on bus %d\n", BusNum); if (ShortPCIListing) { @@ -511,9 +516,17 @@ int do_pci (cmd_tbl_t *cmdtp, int flag, if (argv[argc-1][0] == 'l') { value = 0; argc--; + } else if (argv[argc-1][0] == 's') + argc--; + if (argc > 1) { + char *endp; + bdf = simple_strtoul(argv[1], &endp, 16); + if (*endp != '\0') { + printf("Error: \`%s\' is not a valid " + "bus no.\n", argv[1]); + return 0; + } } - if (argc > 1) - bdf = simple_strtoul(argv[1], NULL, 16); } pciinfo(bdf, value); return 0; diff --git a/drivers/pci.c b/drivers/pci.c index 5360030..34b4055 100644 --- a/drivers/pci.c +++ b/drivers/pci.c @@ -142,7 +142,7 @@ struct pci_controller *pci_bus_to_hose ( if (bus >= hose->first_busno && bus <= hose->last_busno) return hose; - printf("pci_bus_to_hose() failed\n"); + debug("pci_bus_to_hose() failed\n"); return NULL; }

1 0

[U-Boot-Users] SPI support in U-boot
by Vladimir Gurevich 26 Jan '06

26 Jan '06

Hello, It looks like the basic SPI I/O function, spi_xfer() has two different prototypes in U-boot. 1. in common/soft_spi.c, include/spi.h and cpu/nio/spi.c it is declared as int spi_xfer(spi_chipsel_type chipsel, int bitlen, uchar *dout, uchar *din) 2. in SPI drivers for MPC CPUs (cpu/mpc{8xx, 8260, 5xxx}/spi.c) it is declared as ssize_t spi_xfer (size_t count) The code for "sspi" command (do_spi()) definitely uses the first prototype. Subsequently it doesn't work on the above mentioned CPUs (unless you use software SPI implementation). On the other hand, the code for the "eeprom" command, which is another way to access an SPI EEPROM uses functions spi_read() and spi_write, which are implemented only in cpu/mpc{8xx, 8260, 5xxx}/spi.c. However, these functions are very basic. Fore example they do not allow you to control SPI chip select. Can someone tell me what is going on. Is it that MPC drivers became outdated and should be modified? How do other people use them then? Or I am simply missing something? Thanks, Vladimir

2 4

RE: [U-Boot-Users] IXP425 processor
by Martijn de Gouw 26 Jan '06

26 Jan '06

> -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Frank > Sent: woensdag 25 januari 2006 3:23 > To: u-boot-users(a)lists.sourceforge.net > Subject: [U-Boot-Users] IXP425 processor > > Does the EDK4.0 cross toolchain support the IXP425 Xscale > processor? > Yes, use the arm toolchain Regards, martijn

4 8

RE: [U-Boot-Users] boot linux from memory
by Xuezhang Dong 25 Jan '06

25 Jan '06

Later on, I moved the image to NOR Flash, and it is OK to boot the image now. But I still confused by the compression. > Image Type: ARM Linux Kernel Image (uncompressed) Does this means the kernel is uncompressed? Also, in case I want to load an image to memory and run directly, I must use the XIP kernel build in Linux? I can understand that bootm will recognize the uImage format and load the content to another memory by strip off the header, but in case I want to run it directly, what happened to the 40 bytes header in the uImage format? Is this XIP related again? Sorry for so many questions, I think I misunderstanding something about booting sequence, thanks in advance for any help. Regards. Xuezhang. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Andreas Schweigstill Sent: Wednesday, January 25, 2006 2:19 AM To: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] boot linux from memory Dear Xuezhang Dong! Xuezhang Dong schrieb: > If I try to boot from 06008000, I got following: > BRCM5001 # bootm 06008000 > ## Booting image at 06008000 ... > Image Name: Linux-2.6.15 > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 655784 Bytes = 640.4 kB > > Load Address: 06008000 > Entry Point: 06008000 > Verifying Checksum ... OK > XIP Kernel Image ... OK The compressed image and the Linux kernel to be executed may not overlap. In your configuration both will be at address 0x06008000. After decompression memory can be reused, so usually the compressed image would be loaded to something like 0x06200000 or 0x06800000. With best regards Andreas Schweiigstill -- Dipl.-Phys. Andreas Schweigstill Schweigstill IT | Embedded Systems Schauenburgerstraße 116, D-24118 Kiel, Germany Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436 Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

RE: [U-Boot-Users] IXP425 processor
by Martin Krause 25 Jan '06

25 Jan '06

u-boot-users-admin(a)lists.sourceforge.net wrote on : > On Wednesday 25 January 2006 16:27, Martijn de Gouw wrote: > > > Does the EDK4.0 cross toolchain support the IXP425 Xscale > > > processor? > > > > Yes, use the arm toolchain > > I am afraid, but ELDK 4.0 doesn't have an arm toolchain right now. > Might come in a future release. But the ELDK 3.1.1 has an arm > toolchain which can be used for ARM U-Boot ports. Oh? I just installed ELDK 4.0 for arm (the arm-2006-01-16.iso) and did a MAKEALL for an arm board (cmc_pu2). There was a bunch of new compiler warnings, but nevertheless I got an u-boot.bin image. A not working image, though :( Regards, Martin

2 1

[U-Boot-Users] [PATCH] Integrator AP PCI configuration crash
by Jean-Paul Saman 25 Jan '06

25 Jan '06

Patch by Jean-Paul Saman, 17 Jan 2006. Enabling CONFIG_PCI for the ARM Integrator AP board makes u-boot crash on pci-configuration. The attached patch fixes the crash, but not the pci device discovery. There are no PCI devices seen on the bus for this board. The patch is made tested and generated against current git HEAD archive. CHANGELOG: * Fix crash on PCI in pci_integratorap_read_dword() due to unalligned read Kind greetings, Jean-Paul Saman Philips Semiconductors CTO/RTG Philips HighTech Campus, building WDA 3.29 Professor van den Holstlaan 4 5655 AA Eindhoven tel: +31 (0)40 27 45131

1 0

RE: [U-Boot-Users] recieving network packets ?
by Eisenhut, Daniel (GE Healthcare) 25 Jan '06

25 Jan '06

John, > Hi, > I uboot - i want to recieve network packets. I wrote a small > program using the code available in uboot. > However its not working ?. Can anyone point me where i am going wrong ?. I've tried that method before and you'll run into nothing but trouble. Just use what is already there! Attached is a small patch against u-boot-1.1.1 (I know, it's old) for net.[ch] to add a "Custom Protocol" (maybe not the best name) that you can use. Also attached is a "send_message.c" file that I have in my board directory with which you can use as an example of how to use it. This is all still a work in progress... I'm working on custom MPC860 based hardware which contains multiple independent processors that communicate via ethernet (done for legacy reasons). This code is used to communicate status from startup and stand-alone test applications that get run. Dan

1 0

[U-Boot-Users] Standalone application vs. command
by do 25 Jan '06

25 Jan '06

Hello, When should I write some routines for custom board as a standalone u-boot program and when as a u-boot command. What are differences between writing standalone applications and commands? Best regards!

2 1