Re: [U-Boot] question: multiple serial

On 02/24/2011 09:53 PM, Ran Shalit wrote: > Hello, > > I try to understand what is the right way in U-Boot to configure multiple > serials. That is correct. > I use in my board more 3 UART's , one of them is the console. > Should I define config_serial_multi ? Yes > when I did try to do so, I

Re: [U-Boot] [ARM]: File type for u-boot elf file

Le 24/02/2011 14:26, Detlev Zundel a écrit : > Hi sughosh, > >> hi Albert, >> >> On Thu, Feb 24, 2011 at 4:58 PM, Albert ARIBAUDwrote: >> >>> Le 24/02/2011 12:08, sughosh ganu a écrit : >>> >>> I suspect the utility freaks out because it thinks the ELF cannot be made into a binary like

Re: [U-Boot] ARM: Incorrect ROM protection range?

Dear Albert ARIBAUD, In message <4d674d85.40...@free.fr> you wrote: > > All this, of course, if Wolfgang agrees to this suggestion. I fully agree. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-8

Re: [U-Boot] question: multiple serial

Hi Ran, Le 24/02/2011 21:53, Ran Shalit a écrit : > Hello, > > I try to understand what is the right way in U-Boot to configure multiple > serials. I use in my board more 3 UART's , one of them is the console. > Should I define config_serial_multi ? when I did try to do so, I got > "#error No defa

Re: [U-Boot] ARM: Incorrect ROM protection range?

Hi Po-Yu Chuang, Le 25/02/2011 03:41, Po-Yu Chuang a écrit : > Dear Wolfgang and Albert, > > On Fri, Feb 25, 2011 at 4:17 AM, Wolfgang Denk wrote: >> Dear Albert ARIBAUD, >> >> In message<4d66a7cd.9020...@free.fr> you wrote: >>> As far as I can tell, arch/powerpc/lib/board.c , arch/avr

Re: [U-Boot] [PATCH] fsl_esdhc: Correcting esdhc timeout counter calculation

Dear Andy Fleming, In message you wrote: > > Yeah, that took me a while, too. Maybe we should update it to make clear: > > 1) The formula ends up being (2^(13 + timeout))/mmc->trans_speed = (1/4) > seconds > --> 2^(13 + timeout) = mmc->trans_speed/4 > --> 13 + timeout = log2(mmc->trans_speed/4

Re: [U-Boot] [PATCH 0/3] Add support for the MMC device to the vexpress

Dear matt.wad...@linaro.org, > From: Matt Waddel > > These patches add support for the ARM PrimeCell PL180 MultiMedia Interface. > The Versatile Express was the test platform for these changes. > > Matt Waddel (3): >MMC: Max blocks value adjustable >MMC: Add support for PL180 ARM mmc device

Re: [U-Boot] ARM: Incorrect ROM protection range?

Dear Wolfgang and Albert, On Fri, Feb 25, 2011 at 4:17 AM, Wolfgang Denk wrote: > Dear Albert ARIBAUD, > > In message <4d66a7cd.9020...@free.fr> you wrote: >> >> > As far as I can tell, arch/powerpc/lib/board.c , >> > arch/avr32/lib/board.c and examples/standalone/stubs.c actually all >> > mean _

[U-Boot] [PATCH 3/3] ARMV7: Vexpress: Add MMC support

From: Matt Waddel Added the board specific definitions to use the MMCI device. Signed-off-by: Matt Waddel --- board/armltd/vexpress/ca9x4_ct_vxp.c |9 + include/configs/ca9x4_ct_vxp.h |4 2 files changed, 13 insertions(+), 0 deletions(-) diff --git a/board/armltd/ve

[U-Boot] [PATCH 2/3] MMC: Add support for PL180 ARM mmc device

From: Matt Waddel Add support for the ARM PrimeCell MultiMedia Interface - PL180. Ported from original device driver written by ST-Ericsson. Signed-off-by: Matt Waddel --- drivers/mmc/Makefile |1 + drivers/mmc/mmci.c | 452 ++ drivers/mmc

[U-Boot] [PATCH 1/3] MMC: Max blocks value adjustable

From: Matt Waddel The maximum blocks value was hardcoded to 65535 due to a 16 bit register length. The value can change for different platforms. This patch makes the default the current value of 65535, but it is configurable for other platforms. Signed-off-by: Matt Waddel --- drivers/mmc/mmc.

[U-Boot] [PATCH 0/3] Add support for the MMC device to the vexpress

From: Matt Waddel These patches add support for the ARM PrimeCell PL180 MultiMedia Interface. The Versatile Express was the test platform for these changes. Matt Waddel (3): MMC: Max blocks value adjustable MMC: Add support for PL180 ARM mmc device ARMV7: Vexpress: Add MMC support board/

Re: [U-Boot] [PATCH] fsl_esdhc: Correcting esdhc timeout counter calculation

On Thu, Feb 24, 2011 at 3:50 AM, Wolfgang Denk wrote: > Dear Kumar Gala, > > In message <1298537614-20797-1-git-send-email-ga...@kernel.crashing.org> you > wrote: >> >> - Timeout counter value is set as DTOCV bits in SYSCTL register >>   For counter value set as x, >>   Timeout period = (2^(13+x)

Re: [U-Boot] Problem booting on custom board (85xx)

Dear Kevin: The times I have done this it is with a JTAG device, be it a Windriver Probe, BDI or CodeWarrior USB TAP. In all cases the JTAG emulator allows one to set the various register in the chip, especially the DDR registers to get to where one can have *some semblance* of working memory bef

Re: [U-Boot] Problem booting on custom board (85xx)

I am still fighting this DDR issue. Currently, I am trying to get a DDR test to run in uboot before the relocation occurs (in board_init_f). The problem is that if I write code to access memory mapped to DDR, I see no DDR activity on the logic analyzer. Unfortunately it took me a few days of

[U-Boot] USBNET in OMAP (beagleboard)

Hi All, I've searched the mailing list archives and couldn't come up with an answer so I thought I'd try here: Anyone know of any implementations of USBNET in u-boot for OMAP? This feature allows the OMAP, as a USB device (gadget), to do networking over a USB connection with a USB host. Than

[U-Boot] [PATCH] OMAP3 Beagle Pin Mux initialization glitch fix

The below patch reverses the order of two segments in the board file. Output pins need to have their values initialized, before they are exposed to the logic outside the chip. Signed-off-by: Bob Feretich Cc: Wolfgang Denk --- diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c ---

Re: [U-Boot] [PATCH v4 1/4] Refactor do_reset() into board-specific and CPU-specific portions

On Feb 24, 2011, at 13:41, Wolfgang Denk wrote: > In message you wrote: >> >> Perhaps the default should instead be something like this? >> >> __attribute__((__weak__)) int arch_reset(void) >> { >> while(1); >> } > > No. Please don;t implement something that does not do what it is > sup

[U-Boot] question: multiple serial

Hello, I try to understand what is the right way in U-Boot to configure multiple serials. I use in my board more 3 UART's , one of them is the console. Should I define config_serial_multi ? when I did try to do so, I got "#error No default console" though UART2 is defined as console. Could it be t

Re: [U-Boot] ARM: Incorrect ROM protection range?

Dear Albert ARIBAUD, In message <4d66a7cd.9020...@free.fr> you wrote: > > > As far as I can tell, arch/powerpc/lib/board.c , > > arch/avr32/lib/board.c and examples/standalone/stubs.c actually all > > mean __bss_end, as well as all the start.S files, so this seems to be > > consistently used at le

Re: [U-Boot] ARM: Incorrect ROM protection range?

Le 24/02/2011 19:38, Wolfgang Denk a écrit : > Dear Albert ARIBAUD, > > In message<4d6680e4.1070...@free.fr> you wrote: >> >> Do you mean a first commit to turn _end into _bss_end everywhere in >> U-Boot, then a second commit to reintroduce _end and fix the issue with >> monitor protection? Or eve

Re: [U-Boot] [PATCH v4 1/4] Refactor do_reset() into board-specific and CPU-specific portions

Dear "Moffett, Kyle D", In message you wrote: > > Perhaps the default should instead be something like this? > > __attribute__((__weak__)) int arch_reset(void) > { > while(1); > } No. Please don;t implement something that does not do what it is supposed to do. Rather make the pr

Re: [U-Boot] [PATCH v4 1/4] Refactor do_reset() into board-specific and CPU-specific portions

On Feb 23, 2011, at 14:35, Mike Frysinger wrote: > On Wednesday, February 23, 2011 14:28:44 Kyle Moffett wrote: >> +__attribute__((__weak__)) int arch_reset(void) >> +{ >> +return 0; >> +} > > is there any cpu which wouldnt provide arch_reset() ? i dont think it was > possible in the past to

Re: [U-Boot] ARM: Incorrect ROM protection range?

Dear Albert ARIBAUD, In message <4d6680e4.1070...@free.fr> you wrote: > > Do you mean a first commit to turn _end into _bss_end everywhere in > U-Boot, then a second commit to reintroduce _end and fix the issue with > monitor protection? Or even maybe a single commit for both? We should re-chec

[U-Boot] Board [AR71XX] - WNDR3700 u-Boot USB Support *Will donate one to the interested*

Board [AR71XX] - WNDR3700 u-Boot USB Support Hey i have been playing around with the uboot sources NetGear have provided with hope to enable USB Support so i can boot direcly from an USB-Stick. The sources NetGear have provided is based on u-boot-2006-04-06-1725 where they have added basic support

Re: [U-Boot] ARM: Incorrect ROM protection range?

Le 24/02/2011 14:41, Wolfgang Denk a écrit : > Dear Albert ARIBAUD, > > In message<4d66596...@free.fr> you wrote: >> >> Thanks for pointing this out: indeed, _end is actually used as BSS's >> end, not as the image's end -- I did not find any other use of it. >> >> However, not only ARM uses _end:

Re: [U-Boot] ARM: Incorrect ROM protection range?

Dear Albert ARIBAUD, In message <4d66596...@free.fr> you wrote: > > Thanks for pointing this out: indeed, _end is actually used as BSS's > end, not as the image's end -- I did not find any other use of it. > > However, not only ARM uses _end: how do we want to handle the change > overall? Soun

Re: [U-Boot] [ARM]: File type for u-boot elf file

Hi sughosh, > hi Albert, > > On Thu, Feb 24, 2011 at 4:58 PM, Albert ARIBAUD wrote: > >> Le 24/02/2011 12:08, sughosh ganu a écrit : >> >>I suspect the utility freaks out because it thinks the ELF cannot be >>>made into a binary like it would previously, but actually the binary >>>gene

Re: [U-Boot] ARM: Incorrect ROM protection range?

Le 24/02/2011 13:58, Po-Yu Chuang a écrit : > Hi Albert, > > On Thu, Feb 24, 2011 at 7:58 PM, Albert ARIBAUD > wrote: >> Le 24/02/2011 10:39, Wolfgang Denk a écrit : >>> >>> Dear Albert ARIBAUD, >>> >>> In message<4d6611a7.5050...@free.fr>you wrote: >>> In the U-Boot image itself, kn

Re: [U-Boot] ARM: Incorrect ROM protection range?

Hi Albert, On Thu, Feb 24, 2011 at 7:58 PM, Albert ARIBAUD wrote: > Le 24/02/2011 10:39, Wolfgang Denk a écrit : >> >> Dear Albert ARIBAUD, >> >> In message<4d6611a7.5050...@free.fr>  you wrote: >>> >> In the U-Boot image itself, knowing the image size could be achieved >> in >> ARM b

Re: [U-Boot] [ARM]: File type for u-boot elf file

hi Albert, On Thu, Feb 24, 2011 at 4:58 PM, Albert ARIBAUD wrote: > Le 24/02/2011 12:08, sughosh ganu a écrit : > >I suspect the utility freaks out because it thinks the ELF cannot be >>made into a binary like it would previously, but actually the binary >>generation process did not c

Re: [U-Boot] ARM: Incorrect ROM protection range?

Le 24/02/2011 10:39, Wolfgang Denk a écrit : > Dear Albert ARIBAUD, > > In message<4d6611a7.5050...@free.fr> you wrote: >> > In the U-Boot image itself, knowing the image size could be achieved in > ARM by using a general _end symbol that would be set after the last > image output sect

[U-Boot] [PATCHv2 1/2] ARM: OMAP3: Revamp IGEP v2 default configuration

The default IGEP configuration doesn't do anything useful; using some boot.scr search logic like BeagleBoard is much more useful. Signed-off-by: Loïc Minier Signed-off-by: Enric Balletbo i Serra --- include/configs/igep0020.h | 57 1 files changed,

[U-Boot] [PATCHv2 2/2] ARM: OMAP3: Revamp IGEP module default configuration

The default IGEP configuration doesn't do anything useful; using some boot.scr search logic like BeagleBoard is much more useful. Signed-off-by: Enric Balletbo i Serra --- include/configs/igep0030.h | 57 1 files changed, 52 insertions(+), 5 deletio

[U-Boot] [PATCHv2 0/2] ARM: OMAP3: Revamp IGEP default configuration

Hi, This is the second version of patch series to revamp the default configuration for all IGEP boards. The purpose of these patches is use the boot script used in others OMAP3-based boards. Tested on IGEP v2 board and IGEP module. * changes since version 1: * Fix nandboot: should be 'onenand

Re: [U-Boot] [ARM]: File type for u-boot elf file

Le 24/02/2011 12:08, sughosh ganu a écrit : > hi Albert, > > On Thu, Feb 24, 2011 at 4:27 PM, Albert ARIBAUD > wrote: > > Hi Sughosh, > > Le 24/02/2011 11:01, sughosh ganu a écrit : > > Can you please tell me what could have caused this change. I >

Re: [U-Boot] [ARM]: File type for u-boot elf file

hi Albert, On Thu, Feb 24, 2011 at 4:27 PM, Albert ARIBAUD wrote: > Hi Sughosh, > > Le 24/02/2011 11:01, sughosh ganu a écrit : > > Can you please tell me what could have caused this change. I compiled >> u-boot for a powerpc board, and found that the file type in that case is >> 'ELF Executable'

Re: [U-Boot] [PATCH] fsl_esdhc: Correcting esdhc timeout counter calculation

On 02/24/2011 11:37 AM, Kumar Gala wrote: > > On Feb 24, 2011, at 2:53 AM, Kumar Gala wrote: > >> From: Priyanka Jain >> >> - Timeout counter value is set as DTOCV bits in SYSCTL register >> For counter value set as x, >> Timeout period = (2^(13+x))/SD_CLOCK >> >> - As per 4.6.2.2 section of S

Re: [U-Boot] [ARM]: File type for u-boot elf file

Hi Sughosh, Le 24/02/2011 11:01, sughosh ganu a écrit : > hi Albert, > I am facing an issue with generation of AIS signed binaries for > hawkboard. The aisgen utility takes the u-boot elf file as input and > generates a ais binary, which is the file format recognised by the > hawkboard's RBL(rom b

Re: [U-Boot] [PATCH] fsl_esdhc: Correcting esdhc timeout counter calculation

On Feb 24, 2011, at 2:53 AM, Kumar Gala wrote: > From: Priyanka Jain > > - Timeout counter value is set as DTOCV bits in SYSCTL register > For counter value set as x, > Timeout period = (2^(13+x))/SD_CLOCK > > - As per 4.6.2.2 section of SD Card specification v2.00, host should > cofigure t

[U-Boot] [ARM]: File type for u-boot elf file

hi Albert, I am facing an issue with generation of AIS signed binaries for hawkboard. The aisgen utility takes the u-boot elf file as input and generates a ais binary, which is the file format recognised by the hawkboard's RBL(rom bootloader). After the relocation support for ARM, the elf file gene

Re: [U-Boot] [PATCH] fsl_esdhc: Correcting esdhc timeout counter calculation

Dear Kumar Gala, In message <1298537614-20797-1-git-send-email-ga...@kernel.crashing.org> you wrote: > > - Timeout counter value is set as DTOCV bits in SYSCTL register > For counter value set as x, > Timeout period = (2^(13+x))/SD_CLOCK > > - As per 4.6.2.2 section of SD Card specification

Re: [U-Boot] ARM: Incorrect ROM protection range?

Dear Albert ARIBAUD, In message <4d6611a7.5050...@free.fr> you wrote: > > >>> In the U-Boot image itself, knowing the image size could be achieved in > >>> ARM by using a general _end symbol that would be set after the last > >>> image output section, so _end-_start would equal the image size. >

[U-Boot] [PATCH] fsl_esdhc: Correcting esdhc timeout counter calculation

From: Priyanka Jain - Timeout counter value is set as DTOCV bits in SYSCTL register For counter value set as x, Timeout period = (2^(13+x))/SD_CLOCK - As per 4.6.2.2 section of SD Card specification v2.00, host should cofigure timeout period value to minimum 250 msec. - SD_CLOCK = mmc->tr

[U-Boot] Change drive strength of my LPDDR

Hi, I am using a i.MX27 connected to a LPDDR from Micron (se link). I need to lower the drive strength of the memory to half as described at the memory datasheet on page 55 Extended Mode Register ( http://download.micron.com/pdf/datasheets/dram/mobile/512mb_ddr_mobile_sdram_t47m.pdf ) In U-Boot i

[U-Boot] [PATCH] armv7: s5p: pwm driver support

This is common pwm driver of S5P. Signed-off-by: Donghwa Lee Signed-off-by: Kyungmin Park --- arch/arm/cpu/armv7/s5p-common/Makefile |1 + arch/arm/cpu/armv7/s5p-common/pwm.c | 214 +++ arch/arm/include/asm/arch-s5pc1xx/pwm.h | 14 ++ arch/arm/include/as

Re: [U-Boot] ARM: Incorrect ROM protection range?

Le 24/02/2011 08:40, Po-Yu Chuang a écrit : > Hi Heiko, > > On Thu, Feb 24, 2011 at 3:33 PM, Heiko Schocher wrote: >> Albert ARIBAUD wrote: >> The bin length is calculated in arch/arm/lib/board.c, but it seems >> to me not correct ... :-( >> >> in board_init_f(): >> >> gd->mon_len = _bss_end_ofs;