Re: [U-Boot] problem while making kernel up

thanks scott. i loaded my u-boot image to nand flash its fine. and also I need my kernel image and rootfs also in nand flash so that my system should make kernel UP using nand flash. how can i do this using nand flash as we are using only nand flash as boot device. manukumar siganl-networks O

Re: [U-Boot] [PATCH] MMC: MSHCI: Add MSHCI driver

Hi Rajeshwari, On 05/30/2012 10:30 PM, Rajeshwari Birje wrote: > Hi Jaehoon Chung, > > Thank you for comments. > > On Tue, May 29, 2012 at 5:08 PM, Jaehoon Chung wrote: >> Hi Rajeshwari, >> >> i added Some comments. >> >> On 05/25/2012 08:51 PM, Rajeshwari Shinde wrote: >> >>> Add MSHCI driver

[U-Boot] [PATCH] ARM: support for cache coherent allocations

This is a draft implementation of cache coherent memory allocator. This simple implementation just reserves memory area below malloc space and leave it uncached even if data cache is enabled. Allocations are even simpler: code just verifies that we have enough space and increments the offset counte

Re: [U-Boot] [PATCH] arm: Tegra: Use ODMDATA from BCT in IRAM

On 05/30/2012 03:15 PM, Tom Warren wrote: > Walk the BIT and BCT to find the ODMDATA word in the > CustomerData field and put it into Scratch20 reg for > use by kernel, etc. > > Built all Tegra builds OK; Booted on Seaboard and saw > ODMDATA in PMC scratch20 was the same as the value in my > burn-

[U-Boot] [ANNOUNCE] mboot - U-boot clone without blackjack and hookers

Hello. I'm happy to announce a new u-boot clone - I've named it mboot. Please visit https://github.com/ierton/mboot. To see an example of board's initialisation routine, visit [1]. MBOOT bootloader MBOOT is a clone of well known das U-Boot, with reduced functionality. I think, it

[U-Boot] [PATCH] arm: Tegra: Use ODMDATA from BCT in IRAM

Walk the BIT and BCT to find the ODMDATA word in the CustomerData field and put it into Scratch20 reg for use by kernel, etc. Built all Tegra builds OK; Booted on Seaboard and saw ODMDATA in PMC scratch20 was the same as the value in my burn-u-boot.sh file (0x300D8011). NOTE: All flash utilities w

[U-Boot] [PATCH] omap: am33xx: accomodate input clocks other than 24 Mhz

The PLL setup values currently assume a 24 Mhz input clock. This patch uses V_OSCK from the board config file to support boards with different input clock rates. Signed-off-by: Steve Sakoman --- arch/arm/include/asm/arch-am33xx/clocks_am33xx.h | 10 +- 1 files changed, 5 insertions(+)

[U-Boot] [PATCH 3/3] omap: emif: fix bug in manufacturer code test

Code currently tests for <= 0xff. Micron manufacturer code is 0xff, so Micron memory will not be detected! Signed-off-by: Steve Sakoman --- arch/arm/cpu/armv7/omap-common/emif-common.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/arm/cpu/armv7/omap-common/emif-

[U-Boot] [PATCH 2/3] omap: emif: deal with rams that return duplicate mr data on all byte lanes

Some rams (Micron for example) return duplicate mr data on all byte lanes. Users of the get_mr function currently don't deal with this duplicated data gracefully. This patch detects the duplicated data and returns only the expected 8 bit mr data. Signed-off-by: Steve Sakoman --- arch/arm/cpu/a

[U-Boot] [PATCH 1/3] omap: fix compile error in emif-common.c

ext_phy_ctrl_const_base is currently only defined if CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS is set. If not set, the following error occurs: In function `do_sdram_init': | arch/arm/cpu/armv7/omap-common/emif-common.c:985: undefined reference to `ext_phy_ctrl_const_base' Signed-off-by: Steve S

[U-Boot] [PATCH 0/3] omap: fix bugs in automatic emif setup code

While bringing up a new OMAP4 based board I encountered a number of issues when attempting to use the automatic emif setup code. This patch series fixes a compile error and two runtime issues. Tested on the new custom OMAP4 board and Pandaboard Steve Sakoman (3): omap: fix compile error in emi

[U-Boot] [PATCH] tegra: trimslice: fix a couple typos

From: Stephen Warren Fix the .dts file USB unit addresses not to duplicate each-other. Fix the board name string to indicate the vendor is Compulab not NVIDIA. Signed-off-by: Stephen Warren --- board/compulab/dts/tegra2-trimslice.dts |2 +- include/configs/trimslice.h |2 +

Re: [U-Boot] [PATCH 1/3] tegra: add a method to query RAM size from hardware

On 05/30/2012 10:04 AM, Tom Warren wrote: > On Tue, May 29, 2012 at 4:47 PM, Stephen Warren wrote: >> On 05/29/2012 05:19 PM, Tom Warren wrote: >>> On Tue, May 29, 2012 at 3:12 PM, Stephen Warren >>> wrote: On 05/29/2012 03:47 PM, Lucas Stach wrote: > The RAM configuration is set by the

Re: [U-Boot] FDT: Question about embedded fdt enable

On 05/30/2012 08:26 AM, Simon Glass wrote: > Hi Donghwa, > > On Wed, May 30, 2012 at 12:37 AM, Donghwa Lee wrote: ... >> And I have one more question about passing *.dtb to kernel. >> I had make a .dtb binary by using CONFIG_OF_SEPARATE and confirmed >> normally working in u-boot. >> When kernel

Re: [U-Boot] [PATCH V2] tegra: Compulab TrimSlice board support

On 05/30/2012 09:35 AM, Konstantin Sinyuk wrote: > Hi Stephen, > > Thanks for doing this! > We highly appreciate your help. > We (Igor and me) have several comments below... > > > On 05/17/2012 07:03 PM, Stephen Warren wrote: >> diff --git a/board/compulab/dts/tegra2-trimslice.dts >> +usb@

Re: [U-Boot] problem while making kernel up

On 05/30/2012 12:02 AM, Manukumar wrote: > hello, > I was able to solve nand erase and nand write and saveenv. > Now,I am making kernel up and followed below steps.. > > 1) tf 100 uImage_icm_v1.1 > nand erase 0x0020 361483 > nand write 100 0x0020 361483 > > 2) tf c0

Re: [U-Boot] [PATCH 1/3] tegra: add a method to query RAM size from hardware

On Tue, May 29, 2012 at 4:47 PM, Stephen Warren wrote: > On 05/29/2012 05:19 PM, Tom Warren wrote: >> On Tue, May 29, 2012 at 3:12 PM, Stephen Warren >> wrote: >>> On 05/29/2012 03:47 PM, Lucas Stach wrote: The RAM configuration is set by the bootrom to values specified by the BCT. To

Re: [U-Boot] [PATCH V2] tegra: Compulab TrimSlice board support

Hi Stephen, Thanks for doing this! We highly appreciate your help. We (Igor and me) have several comments below... On 05/17/2012 07:03 PM, Stephen Warren wrote: From: Stephen Warren Signed-off-by: Stephen Warren --- v2: Fixed unused variable warnings --- MAINTAINERS

[U-Boot] [PATCH v2 3/4] kw_spi: support spi_claim/release_bus functions

These two function nows ensure that the MPP is configured correctly for the SPI controller before any SPI access, and restore the initial configuration when the access is over. Since the used pins for the SPI controller can differ (2 possibilities for each signal), the used pins are configured wit

[U-Boot] [PATCH v2 4/4] kw_spi: add weak functions board_spi_claim/release_bus

This allows a final, board specific, step in the claim/relase_bus function for the SPI controller, which may be needed for some hardware designs. Signed-off-by: Valentin Longchamp cc: Holger Brunck cc: Prafulla Wadaskar --- drivers/spi/kirkwood_spi.c | 13 - 1 files changed, 12 i

[U-Boot] [PATCH v2 0/4] kirkwood spi_claim/release_bus support

This series adds generic support for the spi_claim/release_bus functions for the kirkwood processors. The implementation was already discussed in another thread following my first board specific submission of the patch. The series adds two functions to the kirkwood mpp code to be able to temporar

[U-Boot] [PATCH v2 2/4] kw_spi: backup and reset the MPP of the chosen CS pin

This was not done before, and in the case of a shared pin (for MPP0 between NF_IO[2] and CSn) this could lead to problems. Signed-off-by: Valentin Longchamp cc: Holger Brunck cc: Prafulla Wadaskar --- drivers/spi/kirkwood_spi.c | 14 ++ 1 files changed, 6 insertions(+), 8 deletio

[U-Boot] [PATCH v2 1/4] kirkwood: add kirkwood_mpp_read function

This function can be used to save current mpp state of all mpp pins given in the mpp_list argument by reading the mpp registers, in the second mpp_saved argument. A later call to kirkwood_mpp_conf function with this saved list will reset the mpp configuration as it was when kirkwood_mpp_read was c

Re: [U-Boot] FDT: Question about embedded fdt enable

Hi Donghwa, On Wed, May 30, 2012 at 12:37 AM, Donghwa Lee wrote: > On Wed, May 23, 2012 at 15:13, Simon Glass wrote: > > > HI Donghwa, > > > > On Wed, May 23, 2012 at 12:39 AM, Donghwa Lee dh09@samsung.com>> wrote: > > > > Dear, Simon Glass > > > > I am preparing device tree in Exyn

[U-Boot] patchwork cleanup

Dear Marek I did few cleanups in patchwork? I will check if further more is needed. Regards.. Prafulla . . . > -Original Message- > From: Marek Vasut [mailto:marek.va...@gmail.com] > Sent: 29 May 2012 20:17 > To: u-boot@lists.denx.de > Cc: Prafulla Wadaskar; Valentin Longchamp; holger.b

Re: [U-Boot] How to debug uboot code on Samsung S5pv210 chip by eclipse and JTAG?

Dear Marek Vasut, In message <201205301309.23163.ma...@denx.de> you wrote: > > > Why would you need to initialize DDR though the JTAG debugger? > > The system has some BootROM, which does the DDR init. But without special > header > in the NAND, the DDR won't be inited ... that was my point ab

Re: [U-Boot] [PATCH] MMC: MSHCI: Add MSHCI driver

Hi Jaehoon Chung, Thank you for comments. On Tue, May 29, 2012 at 5:08 PM, Jaehoon Chung wrote: > Hi Rajeshwari, > > i added Some comments. > > On 05/25/2012 08:51 PM, Rajeshwari Shinde wrote: > >> Add MSHCI driver support and resgister description for same. >> >> Signed-off-by: Alim Akhtar >>

Re: [U-Boot] [PATCH 4/8] mxsboot: stop referring to i.MX28 as this ought to work for all i.MXS SoCs

Dear Marek Vasut, On Wed, May 30, 2012 at 2:49 AM, Marek Vasut wrote: > I'm unhappy about the image generator ;-) > > Ok, now Otavio will probably hate me, but I believe it'd be much more > helpful to > convert mxsboot into part of mkimage (though this is unrelated to this > patch). > And maybe

Re: [U-Boot] How to debug uboot code on Samsung S5pv210 chip by eclipse and JTAG?

Dear Wolfgang Denk, > Dear =?GB2312?B?vOHKrw==?=, > > In message you wrote: > > I have found some tutorials to debug uboot an samsung 2440 and > > 6410 chip by JTAG .I also known I must write a init program or script > > first .But I don't known to debug uboot on S5pv210 and write the init >

Re: [U-Boot] How to debug uboot code on Samsung S5pv210 chip by eclipse and JTAG?

Dear =?GB2312?B?vOHKrw==?=, In message you wrote: >     I have found some tutorials to debug uboot an samsung 2440 and > 6410 chip by JTAG .I also known I must write a init program or script > first .But I don't known to debug uboot on S5pv210 and write the init > DDR script.Anyone gives me a gu

Re: [U-Boot] How to debug uboot code on Samsung S5pv210 chip by eclipse and JTAG?

Dear 坚石, > Oh, I want to use eclipse to debug uboot . All right, I have no experience with eclipse. > And the debugger is OpenOCD. Ok, so you need to connect GDB backend to it somehow. > But I don't known how to establish the enviroment settings to > uboot debugging.Because I shoul

Re: [U-Boot] FDT: Question about embedded fdt enable

On Wed, May 23, 2012 at 15:13, Simon Glass wrote: > HI Donghwa, > > On Wed, May 23, 2012 at 12:39 AM, Donghwa Lee > wrote: > > Dear, Simon Glass > > I am preparing device tree in Exynos SoC and had already tested by using > CONFIG_OF_SEPARATE. But, I co

Re: [U-Boot] R: Re: Question about md output

Wolfgang Denk writes: > Basicly yes, except that the crc32 command does not operate on 32 > bit "words", but on an area of memory (i. e. a number of octets). > Depending on your expectations on endianess etc. this may or may bot > be the same. The "32" in the crc32 command name is just an > indi