In many cases environment variables need access to the U-Boot CONFIG
variables to select different options. Enable this so that the environment
scripts can be as useful as the ones currently in the board config files.
Signed-off-by: Simon Glass
---
Changes in v3:
- Define __UBOOT_CONFIG__ when co
This seems more intuitive that the current #define way of doing things.
The resulting code is shorter, avoids the quoting and line continuation
pain, and also improves the clumsy way that stdio variables are created:
#ifdef CONFIG_VIDEO_TEGRA
#define STDOUT_LCD ",lcd"
#else
#define STDOUT_LCD
Adjust the code for these commands so that they work on sandbox.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Add new patch to get 'env import/export' working on sandbox
common/cmd_nvedit.c | 31 ++-
1 file changed, 18 insertions(+), 13 deletio
In the case where an environment variable spans multiple lines, we should
use run_command_list() so that all lines are executed. This shold be
backwards compatible with existing behaviour for existing scripts.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Add new patch to ad
At present U-Boot environment variables, and thus scripts, are defined
by CONFIG_EXTRA_ENV_SETTINGS. It is painful to add large amounts of text
to this file and dealing with quoting and newlines is harder than it
should be. It would be better if we could just type the script into a
text file and ha
(Note that Wolfgang is looking at a way of adjusting the environment
within a U-Boot binary - this series could fit with that but aims to
improve the creation of the initial default environment).
At present U-Boot environment variables, and thus scripts, are defined
by CONFIG_EXTRA_ENV_SETTINGS. I
Hi,
On Fri, Oct 25, 2013 at 6:11 PM, Laszlo Papp wrote:
> Ping?
>
>
> On Thu, Oct 24, 2013 at 6:29 PM, Laszlo Papp wrote:
>
>> Hi,
>>
>> is it possible from within a running u-boot session?
>>
>> The use case is that I would like to make a screenshot, but without the
>> proprietary name people m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/24/2013 04:22 PM, Javier Martinez Canillas wrote:
> On Thu, Oct 17, 2013 at 6:30 AM, Javier Martinez Canillas
> wrote:
>> From: Javier Martinez Canillas
>>
>> There seems to be a naming convention for the configuration
>> files for boards using
Thanks For reply, i check DDR configuration using Code warrior, and
successfully getting read/write from DDR. I use the following configuration
in code warrior and same in u-boot...
writemem.l 0xf8006000 0x001f # CS0_BNDS writemem.l 0xf8006080
0x80914102 # CS0_CONFIG writemem.l0x
Ping?
On Thu, Oct 24, 2013 at 6:29 PM, Laszlo Papp wrote:
> Hi,
>
> is it possible from within a running u-boot session?
>
> The use case is that I would like to make a screenshot, but without the
> proprietary name people may have set ...
>
> Cheers,
> Laszlo
>
It is probably because your DDR wasn't initialized correctly. You can
try to dump all DDR registers and check if anyone is suspicious. You can
also override any register before enabling the controller.
You may also add some memory test before relocation.
York
On 10/25/2013 06:38 AM, Ashish Kheta
Haijun Zhang wrote on 10/24/2013 08:54:42 PM:
> struct mmc should be clear to all '0' after malloc to avoid
> unexpect variable value.
>
> Like mmc->has_init = xxx.
> In this case mmcinfo will believe the card had been initialized before
> and skip the initialization.
>
> Test on P5040 and T424
All,
This issue has since been resolved. I sent this email yesterday morning
and since this was my first post to u-boot mailing list I needed
moderator approval.
This issues has since been resolved by applying Haijun Zhang's patch:
[PATCH 1/2] esdhc: memset mmc struct before putting into use
From: Hardik Patel
Signed-off-by: Hardik Patel
---
include/configs/omap4_common.h |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h
index e9f2383..9aa4030 100644
--- a/include/configs/omap4_common.h
+++
From: Hardik Patel
This patch adds Elpida DDR2 RAM support for Pandaboard-ES Rev-B3 board.Enable
automatic sdram detection in pandaboard defconfig, so that Elpida DDR2 RAM gets
detected on Pandaboard-ES Rev-B3 board. We verified that u-boot works on
Panadaboard-ES Rev-B2 board with this patch.
On Thu, Oct 24, 2013 at 6:18 AM, matti kaasinen
wrote:
> Hi!
>
> Im working on beaglebone variant board - basically the same as beaglebone
> but with NAND flash on board with am33x processor.
>
> Ubifs works fine when I access it purely from Linux (formatting, making
> ubifs volume etc.). However,
I was able to get SD Card booting for P2041RDB working correctly with
U-Boot 2013.07. However, today I was attempting to move to 2013.10, and
I'm having issues booting from the SD Card. Specifically issues with
U-Boot not reading my FMan firmware binary file on the SD Card.
NOTE: all of the fol
hii I am using MPC8641D based custom board for evaluation purpose. I am
using minimal configuration for this board i.e. only FLASH and DDR
initialisation. when I compiled U-boot in debug mode its printing
addresses, i check for those addresses and found that it is unable to
relocate itself to DDR(4
One way is to run a service in one that is not present in the other. For
example, try running an ssh or telnet server in your kernel, but not in
uboot (To my knowledge neither is possible in the bootloader, but I may be
wrong). That way, if you can connect to your board via ssh, then you know
that
On 10/20/2013 09:47 PM, Simon Glass wrote:
> Hi Stephen,
>
> On Wed, Jun 26, 2013 at 1:56 PM, Stephen Warren wrote:
>> On 06/24/2013 02:46 PM, Simon Glass wrote:
>>> At present U-Boot environment variables, and thus scripts, are defined
>>> by CONFIG_EXTRA_ENV_SETTINGS. It is painful to add large
Editing those findings did not help.
In fact I was referring a wrong file in my last message. File README.omap3
refers to is:
arch/arm/include/asm/arch-omap3/omap_gpmc.h
Whereas in my last message I was referring:
arch/arm/include/asm/arch-am33x/omap_gpmc.h
However, there was one mistake also in t
Hi!
I have found that ubifs formatted on Linux (2.8.13) side is not compatible
on u-boot side. Executing ubi part throws tons of ECC error
messages and in fact this same ubifs partition will be found corrupted on
Linux side immediately after this single operation. I have investigated
this issue an
Update T1040QDS naem to Poonam Aggrwal.
Signed-off-by: Priyanka Jain
---
Based on u-boot-mpc85xx/next branch.
boards.cfg |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/boards.cfg b/boards.cfg
index 5e10125..dfe1c59 100644
--- a/boards.cfg
+++ b/boards.cfg
@@ -962,7 +
T1040QDS-D3 has dual-rank DDR:
Micron, MT18KSF51272AZ-1G6 (4GB, x72, CL=10).
Add Raw Timing structure for this DDR.
Typically SPD method is used for getting DDR parameter
and calculating values for various DDR controller registers.
But somentimes it may happen that SPD present on DDR may
24 matches
Mail list logo
