June 2006 - U-Boot

Re: [U-Boot-Users] Using at91 with a different parallel flash, request for help
by Roman Kolesnikov 13 Jun '06

13 Jun '06

Hello everyone, I found the difference (with the help of Koan) in the command list and cycles for the newer Atmel chip. I have a new driver now to access the flash, and it works ok. However, I still have problem with UBoot1.1.4. When I load UBoot originally into flash and run, everything works well. However, when I restart the uboot from flash again, I think uboot overwrites something in the environment variables. My environment variables become corrupt. For instance the very first sign is invalid input, output, and debug settigns on the second start up. When I print the environment variables, I get about 8K of garbage data. I wonder what could be causing my corruption. It only occurs in the environment variables. Roman

4 7

[U-Boot-Users] [PATCH] Added hardware SPI support for MPC8349
by Ben Warren 13 Jun '06

13 Jun '06

Hello, Attached is a patch that adds hardware SPI support for the MPC834x CPU, and as an example, the MPC8349EMDS evaluation board. The only new configuration option is CONFIG_HARD_SPI. Andy Fleming made a good suggestion of putting the driver code in /drivers. I don't think the driver is generic enough at this time (depends heavily on the MPC8349's internal memory map), so for now it's in /cpu/mpc83xx. If future SPI controllers use the same data structures this will be easy to port. CHANGELOG: Added hardware SPI functionality for MPC834x-based boards. Communications over the SPI bus can be performed either through the spi_xfer() function call or via the 'sspi' command which is enabled by CFG_CMD_SPI flag. regards, Ben

1 1

[U-Boot-Users] U-Boot-1.0.0 for PC . . .
by Kiran Jammula 13 Jun '06

13 Jun '06

Hi, I am using U boot with ARM processor Successfully. I want use the U-boot for my Pentium PC instead of GRUB or lilo. Can any one suggest How to ues U-Boot for PC. Thanks in advance,\. Best Regards, Kiran Jammula _________________________________________________________________ NRIs: Still paying for money transfers? Now send Money2India for FREE! http://ads.mediaturf.net/event.ng/Type=click&FlightID=20273&AdID=65990&Targ…

4 3

Re: [U-Boot-Users] How to change MPU frequency in U-Boot?
by phAntOm yAng 13 Jun '06

13 Jun '06

Dear all: Now, I'm working on OMAP5912OSK with U-Boot 1.1.4-gb1d71358-dirty. The message of print_cpuinfo() is: CPU: OMAP1611b at 96.0 MHz (DPLL1=96.0 MHz) But OMAP5912OSK should work on 192MHz. How to let OMAP5912 work on 192MHz during U-Boot phase? I found three reference, but these seem like no direct relationship. 1)OMAP5912OSK Board Support Library ~ti\boards\osk5912\lib\osk5912bsl\osk5912.c /* -------------------------------------------------------------- * * Clocking Parameters after initialization * * DPLL freq: 96 MHz 192 MHz * * Clock mode: Fully Sync Scalable Sync * * ARM freq: 96 MHz 192 MHz * * DSP freq: 96 MHz 192 MHz * * DSPMMU freq:96 MHz 192 MHz * * TC freq: 96 MHz 96 MHz * * LCD freq: 24 MHz 24 MHz * * PER freq: 24 MHz 24 MHz * * -------------------------------------------------------------- */ 2)Linux kernel 2.6.14 include file linux/arch/arm/mach-omap1/clock.h /*--------------------------------------------------------------- * Omap1 MPU rate table *---------------------------------------------------------------*/ static struct mpu_rate rate_table[] = { /* MPU MHz, xtal MHz, dpll1 MHz, CKCTL, DPLL_CTL * NOTE: Comment order here is different from bits in CKCTL value: * armdiv, dspdiv, dspmmu, tcdiv, perdiv, lcddiv */ #if defined(CONFIG_OMAP_ARM_192MHZ) { 192000000, 19200000, 192000000, 0x050f, 0x2510 }, /* 1/1/2/2/8/8 */ { 192000000, 12000000, 192000000, 0x050f, 0x2810 }, /* 1/1/2/2/8/8 */ { 96000000, 12000000, 192000000, 0x055f, 0x2810 }, /* 2/2/2/2/8/8 */ { 48000000, 12000000, 192000000, 0x0baf, 0x2810 }, /* 4/4/4/8/8/8 */ { 24000000, 12000000, 192000000, 0x0fff, 0x2810 }, /* 8/8/8/8/8/8 */ #endif #if defined(CONFIG_OMAP_ARM_168MHZ) { 168000000, 12000000, 168000000, 0x010f, 0x2710 }, /* 1/1/1/2/8/8 */ #endif #if defined(CONFIG_OMAP_ARM_120MHZ) { 120000000, 12000000, 120000000, 0x010a, 0x2510 }, /* 1/1/1/2/4/4 */ #endif #if defined(CONFIG_OMAP_ARM_60MHZ) { 60000000, 12000000, 60000000, 0x0005, 0x2290 }, /* 1/1/1/1/2/2 */ #endif #if defined(CONFIG_OMAP_ARM_30MHZ) { 30000000, 12000000, 60000000, 0x0555, 0x2290 }, /* 2/2/2/2/2/2 */ #endif { 0, 0, 0, 0, 0 }, }; 3)U-Boot DPLL1 setting u-boot/board/omap5912osk/lowlevel_init.S VAL_ARM_CKCTL: .word 0x2000 /* was: 0x3000, now use CLK_REF for timer input */ VAL_DPLL1_CTL: .word 0x2830 Best regards, phantom yang > From: "Stefan Roese" > Don't start working on such an old version of U-Boot. Please use > current top-of-git tree version. Especially for the OMAP5912OSK some > important changes have been incoorporated. -- Get your free email from http://www.sanriotown.com 網炫技術支援

2 1

[U-Boot-Users] Hard SPI driver for 834x
by Ben Warren 12 Jun '06

12 Jun '06

Wolfgang and others, I've developed a hard SPI driver for the MPC834x CPU that I'd like to submit, but have a few questions first. Some background information: Unlike most QUICC-based CPUs before it, the 834x chips has a dedicated SPI controller, instead of using an xCC port and associated DPRAM buffers. There are 32-bit transmit and receive registers that are double-buffered and shifted out/in the MOSI/MISO pins. Other chips in the PowerQUICC II Pro family, such as the 832x and 836x, appear to have a CPM and thus probably work much like the 82xx. Going through the U-boot code, I found two quite different SPI implementations, in addition to a spattering of board-specific code: CONFIG_SPI is very EEPROM-specific, while CONFIG_SOFT_SPI is nice and generic, but is of course bit-banged. My application uses hard SPI, but I want to use U-boot as a hardware debug platform so generic is good. I propose adding CONFIG_HARD_SPI, which does nothing other than #ifdef compile the hard driver. I will then re-use the data structures and commands from CONFIG_SOFT_SPI. My questions: 1. The /cpu directory has 'mpc83xx', while in fact there are at least two groups of chips in this family that have quite different peripherals. Should I put my code here and use #ifdef CONFIG_MPC8349, or start an 'mpc834x' branch? 2. Where is the appropriate place to call 'spi_init()'? In my patch, I've placed it in /lib_ppc/board.c along with 'i2c_init()'. Should it instead go in board code? 3. Should I put changes to README in the same patch, or would you prefer a different one? Patch size should be < 15kB, so size isn't really an issue. 4. More embarassingly, is there a trick to getting new files to show up when calling 'git diff' on the u-boot tree? I've tried 'git-add', committing and various permutations and whatever I do, my new file doesn't show up in the patch. I've tried using 'diff --git', but my version of diff (2.8.1) doesn't seem to support git. regards, Ben

3 2

[U-Boot-Users] [Patch] MCF5282 without preloader
by Jens Scharsig 12 Jun '06

12 Jun '06

This patch adds the MCF5282 support and includes the Zachary P. Landau fec and immap fixes as patch. CHANGELOG: * Patch by Jens Scharsig (BuS Elektronik GmbH & Co. KG), 08 Aug. 2005: Add MCF5282 support (without preloader) relocate ichache_State to ram u-boot can run from internal flash THX to Zachary P. Landau and Wolfgang Denk for help and inspirations. Best regards Jens Scharsig * Patch by Jens Scharsig (BuS Elektronik GmbH & Co. KG), 08 Aug. 2005: Add MCF5282 support (without preloader) relocate ichache_State to ram u-boot can run from internal flash

3 2

[U-Boot-Users] Problems loading ramdisk
by Michael Sprauve 12 Jun '06

12 Jun '06

Hi, I have a very simple and somewhat embarassing question regarding u-boot and loading a ramdisk. I am trying to boot my IXP425 board using a kernel and ramdisk that has been flashed on the board. I have tried following the many suggestions that I have found both on the web, and inside the documentation but still have not had any success. I know the kernel and ramdisk image are good, since I used the same images for booting from Redboot. Below is a snippet of my boot sequence, including the error when trying to mount the ramdisk(initrd) Thanks, Mike ****************************************************** bootm 50040000 50180000 ## Booting image at 50040000 ... Image Name: Snapgear Kernel Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1295376 Bytes = 1.2 MB Load Address: 01600000 Entry Point: 01600000 Verifying Checksum ... OK OK ## Loading Ramdisk Image at 50180000 ... Image Name: Snapgear Ramdisk Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 2264374 Bytes = 2.2 MB Load Address: 00800000 Entry Point: 00800000 Verifying Checksum ... OK Starting kernel ... Uncompressing Linux............................................................. ................................. done, booting the kernel. Linux version 2.6.13.5 (msprauve@Sebring) (gcc version 3.3.2) #34 Tue Jun 6 14:0 3:35 PDT 2006 CPU: XScale-IXP42x Family [690541f1] revision 1 (ARMv5TE) Machine: Intel IXDP425 Development Platform Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x00800000,8M me m=64M@0x00000000 hdc=noprobe hdd=noprobe . . . RAMDISK: Couldn't find valid RAM disk image starting at 0. Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 3

[U-Boot-Users] [Patch] New Board (EB+MCF-EV123 based on Frescale MCF5282)
by Jens Scharsig 12 Jun '06

12 Jun '06

This patch adds the BuS EB+MCF-EV123 Board. Board characteristics: CPU: Frescale MCF5282 RAM: 16MB SDRAM (16 Bit) FLASH: 2MB 16bit external PHY: Inter LXF972 These board is a reference design for future BuS Elektronik consumer boards. I think this patch is helpful for all other MCF528x users. CHANGELOG: * Patch by Jens Scharsig (BuS Elektronik GmbH & Co. KG), 08 Aug. 2005: Add EB+MCF-EV123 board support. includes "[Patch] MCF5282 without preloader" Add m68k Boards to MAKEALL THX to Zachary P. Landau and Wolfgang Denk for help. Best regards, Jens Scharsig * Patch by Jens Scharsig (BuS Elektronik GmbH & Co. KG), 08 Aug. 2005: Add EB+MCF-EV123 board support. includes [Patch] MCF5282 without preloader Add m68k Boards to MAKEALL

2 1

Re: [U-Boot-Users] Question about uboot environment variables and setting uboot in the parallel flash
by Wolfgang Denk 12 Jun '06

12 Jun '06

Hello, in message <448B71A2.70507(a)randrlabs.com> you wrote: > > I wander, if I could ask you a question Wolfgang. Of course you can. You just did. > I am trying to load uboot 1.1.4 directly into a parallel flash on a > board similar to 91rm9200ek. I have written a driver, and the loading to > flash occurs perfect without errors. > However, I have a problem, after the board resets. Once uboot 1.1.4 > loads, it crashes. I believe that the Environment variables are being > saved and overwritten by uboot. I am experiemnting with settings, but I > don't know the solution yet. U-Boot does not automatically write to flash memory, only on behalf of user commands. > Here is what I do: > > Load uboot into ram > Execute uboot from ram > Load uboot into flash This is a different image of U-Boot, one configured correctly (i. e. for booting from flash)? Otherwise see the FAQ: http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarte… > Reboot > Uboot loads to prompt and crashes Well, debug the code. Obviously your port / configuration is broken. > Sorry to bug, but I don't have anywhere else to go, Well, you *also* posted on the mailing list. 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 Syntactic sugar causes cancer of the semicolon. - Epigrams in Programming, ACM SIGPLAN Sept. 1982

1 0

[U-Boot-Users] u-boot porting problem (Execution after code relocated to sdram)
by robinpv 12 Jun '06

12 Jun '06

Hi , In u-boot porting, i am facing a problem. Here after the relocation of the code to the sdram, the code is executed from sdram, at some point we have to do the pci initialization. so we are storing the configuration function in a structure based on the device we want to configure. I am able to detect the device. After dectecting device, when the configuration function if being called, the flash address is loaded and control is jumping it to flash address. At that flash address there is no valid code, but "uboot.dis" disassemble file shows the valid code at that address. Shouldn't the control jump to relocated sdram address of the configuration function ? -------------------------------------------------------------- File: drivers/pci.c In pci_hose_scan_bus() if (cfg) { cfg->config_device(hose, dev, cfg); #ifdef CONFIG_PCI_PNP } else { int n = pciauto_config_device(hose, dev); sub_bus = max(sub_bus, n); #endif -------------------------------------------------------------- In my board related file: static struct pci_config_table pci_tb0286_config_table[] = { { 0x126F, 0x0501, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,PCI_ANY_ID, pci_cfgfunc_config_device, { PCI_ENET0_IOADDR, PCI_ENET0_MEMADDR, PCI_COMMAND_MEMORY | PCI_COMMAND_MASTER }}, { } }; --------------------------------------------------------------- Please provide your feedback on this. Thanks & Regards Robin

2 1