Re: [U-Boot] Warning due to commit 6a516ef15d79

Hi Lothar, On 12/07/2017 13:44, Lothar Waßmann wrote: > Hi Stefano, > > On Wed, 12 Jul 2017 10:45:21 +0200 Stefano Babic wrote: >> Hi Lothar, >> >> your recent patch : >> >> commit 306dd7dabd6472b8b66ab5106d5a6a516ef15d79 >> Author: Lothar Waßmann >> Date: Tue Jun 27

Re: [U-Boot] Warning due to commit 6a516ef15d79

Hi Stefano, On Wed, 12 Jul 2017 10:45:21 +0200 Stefano Babic wrote: > Hi Lothar, > > your recent patch : > > commit 306dd7dabd6472b8b66ab5106d5a6a516ef15d79 > Author: Lothar Waßmann > Date: Tue Jun 27 15:23:16 2017 +0200 > > net: fec_mxc: fix PHY initialization

[U-Boot] Warning due to commit 6a516ef15d79

Hi Lothar, your recent patch : commit 306dd7dabd6472b8b66ab5106d5a6a516ef15d79 Author: Lothar Waßmann Date: Tue Jun 27 15:23:16 2017 +0200 net: fec_mxc: fix PHY initialization bug with CONFIG_DM_ETH is cause of warnings in several i.MX boards, such as:

Re: [U-Boot] warning: override: reassigning to symbol OF_CONTROL

On Wed, Jul 8, 2015 at 5:05 PM, Bin Meng bmeng...@gmail.com wrote: Hi Simon, I've rebased my git repo on u-boot-x86/master branch and found one warning popped up: $ make crownbay_defconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED

[U-Boot] warning: override: reassigning to symbol OF_CONTROL

Hi Simon, I've rebased my git repo on u-boot-x86/master branch and found one warning popped up: $ make crownbay_defconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

On 11/26/2014 04:34 AM, Laurentiu Tudor wrote: Hi Jocke, York, Sorry for the late reply. I didn't noticed the thread in time. You need this patch: https://patchwork.ozlabs.org/patch/411910/ Great, I guess this will hit upstream any day now? I'm thinking York will pick it up in one of

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

York Sun york...@freescale.com wrote on 2014/12/01 18:26:21: On 11/26/2014 04:34 AM, Laurentiu Tudor wrote: Hi Jocke, York, Sorry for the late reply. I didn't noticed the thread in time. You need this patch: https://patchwork.ozlabs.org/patch/411910/ Great, I guess this will

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

On 12/01/2014 10:31 AM, Joakim Tjernlund wrote: York Sun york...@freescale.com wrote on 2014/12/01 18:26:21: On 11/26/2014 04:34 AM, Laurentiu Tudor wrote: Hi Jocke, York, Sorry for the late reply. I didn't noticed the thread in time. You need this patch:

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

Laurentiu Tudor b10...@freescale.com wrote on 2014/11/25 09:49:22: On 11/24/2014 06:57 PM, York Sun wrote: On 11/23/2014 11:30 PM, Joakim Tjernlund wrote: York Sun york...@freescale.com wrote on 2014/10/24 18:02:03: On 10/24/2014 08:39 AM, Joakim Tjernlund wrote: Booting my t1042 I

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

On 11/26/2014 10:55 AM, Joakim Tjernlund wrote: Laurentiu Tudor b10...@freescale.com wrote on 2014/11/25 09:49:22: On 11/24/2014 06:57 PM, York Sun wrote: On 11/23/2014 11:30 PM, Joakim Tjernlund wrote: York Sun york...@freescale.com wrote on 2014/10/24 18:02:03: On 10/24/2014 08:39 AM,

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

On 11/24/2014 06:57 PM, York Sun wrote: On 11/23/2014 11:30 PM, Joakim Tjernlund wrote: York Sun york...@freescale.com wrote on 2014/10/24 18:02:03: On 10/24/2014 08:39 AM, Joakim Tjernlund wrote: Booting my t1042 I get: Loading Ramdisk to 2e639000, end 2cc4 ... OK Loading Device Tree

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

On 11/23/2014 11:30 PM, Joakim Tjernlund wrote: York Sun york...@freescale.com wrote on 2014/10/24 18:02:03: On 10/24/2014 08:39 AM, Joakim Tjernlund wrote: Booting my t1042 I get: Loading Ramdisk to 2e639000, end 2cc4 ... OK Loading Device Tree to 03fe4000, end 03fffd45 ... OK WARNING

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

York Sun york...@freescale.com wrote on 2014/10/24 18:02:03: On 10/24/2014 08:39 AM, Joakim Tjernlund wrote: Booting my t1042 I get: Loading Ramdisk to 2e639000, end 2cc4 ... OK Loading Device Tree to 03fe4000, end 03fffd45 ... OK WARNING Could not get liodn of node /pcie@ffe24:

[U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

Booting my t1042 I get: Loading Ramdisk to 2e639000, end 2cc4 ... OK Loading Device Tree to 03fe4000, end 03fffd45 ... OK WARNING Could not get liodn of node /pcie@ffe24: FDT_ERR_NOTFOUND WARNING Could not get liodn of node /pcie@ffe25: FDT_ERR_NOTFOUND WARNING Could not get liodn of

Re: [U-Boot] WARNING Could not get liodn of node /pcie@ffe240000: FDT_ERR_NOTFOUND

On 10/24/2014 08:39 AM, Joakim Tjernlund wrote: Booting my t1042 I get: Loading Ramdisk to 2e639000, end 2cc4 ... OK Loading Device Tree to 03fe4000, end 03fffd45 ... OK WARNING Could not get liodn of node /pcie@ffe24: FDT_ERR_NOTFOUND WARNING Could not get liodn of node

Re: [U-Boot] (WARNING!!! PGP with incorrect signature) Re: [PATCH 03/11] powerpc/ppc4xx: Add fpgad command for dumping gdsys fpga registers

Hi Tom, ... There's checkpatch warning I'm guessing since I can spot some spacing issues. ... Hmm, interesting, it's checkpatch clean. Maybe this tool can still get even more annoying :) Will fix issues asap. Cheers Dirk

Re: [U-Boot] (WARNING!!! PGP with incorrect signature) Re: [PATCH 03/11] powerpc/ppc4xx: Add fpgad command for dumping gdsys fpga registers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/23/2013 05:53 AM, Eibach, Dirk wrote: Hi Tom, ... There's checkpatch warning I'm guessing since I can spot some spacing issues. ... Hmm, interesting, it's checkpatch clean. Maybe this tool can still get even more annoying :) Will fix

[U-Boot] Warning messages in latest u-boot-samsung

Hi Minkyu Kang, I am getting the following warning messages in the latest u-boot-samsung tree. /usr/local/arm/arm-2011.09/bin/arm-none-eabi-ld: warning: /usr/local/arm/arm-2011.09/bin/../lib/gcc/arm-none-eabi/4.6.1/libgcc.a(bpabi.o) uses variable-size enums yet the output is to use 32-bit

Re: [U-Boot] Warning messages in latest u-boot-samsung

Hi Rajeshwari, On Tue, 2 Apr 2013 11:58:42 +0530, Rajeshwari Birje rajeshwari.bi...@gmail.com wrote: Hi Minkyu Kang, I am getting the following warning messages in the latest u-boot-samsung tree. /usr/local/arm/arm-2011.09/bin/arm-none-eabi-ld: warning:

Re: [U-Boot] Warning messages in latest u-boot-samsung

Hi Albert, I am building for Samsung SMDK5250 and toolchain I use is arm-2011.09. Is it the issue with my toolchain. Regards, Rajeshwari Shinde On Tue, Apr 2, 2013 at 1:30 PM, Albert ARIBAUD albert.u.b...@aribaud.net wrote: Hi Rajeshwari, On Tue, 2 Apr 2013 11:58:42 +0530, Rajeshwari Birje

Re: [U-Boot] Warning messages in latest u-boot-samsung

Hi Rajeshwari, (pleale avoid top-posting, and quote only what is necessary to understand your answer) On Tue, 2 Apr 2013 15:00:55 +0530, Rajeshwari Birje rajeshwari.bi...@gmail.com wrote: Hi Albert, I am building for Samsung SMDK5250 and toolchain I use is arm-2011.09. Is it the issue with

Re: [U-Boot] Warning messages in latest u-boot-samsung

On 02/04/13 18:50, Albert ARIBAUD wrote: Hi Rajeshwari, (pleale avoid top-posting, and quote only what is necessary to understand your answer) On Tue, 2 Apr 2013 15:00:55 +0530, Rajeshwari Birje rajeshwari.bi...@gmail.com wrote: Hi Albert, I am building for Samsung SMDK5250 and

Re: [U-Boot] Warning messages in latest u-boot-samsung

Hi Albert and Minkyu Thank you for your inputs Will recheck my compiler. Thanks and Regards, Rajeshwari Shinde. On Tue, Apr 2, 2013 at 3:24 PM, Minkyu Kang mk7.k...@samsung.com wrote: On 02/04/13 18:50, Albert ARIBAUD wrote: Hi Rajeshwari, (pleale avoid top-posting, and quote only what

Re: [U-Boot] WARNING: Caches not enabled on openrd based board

-Original Message- From: u-boot-boun...@lists.denx.de [mailto:u-boot- boun...@lists.denx.de] On Behalf Of Alex Zeffertt Sent: 17 August 2012 16:47 To: u-boot@lists.denx.de Subject: [U-Boot] WARNING: Caches not enabled on openrd based board Hi U-Booters, I get the following

Re: [U-Boot] WARNING: Caches not enabled on openrd based board

Am 17.08.2012 13:16, schrieb Alex Zeffertt: I get the following warning when I boot our openrd based board: U-Boot 2012.07 (Aug 17 2012 - 10:45:29) OpenRD-Base SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 512 MiB The warning tells you that the plaform has no

[U-Boot] WARNING: Caches not enabled on openrd based board

Hi U-Booters, I get the following warning when I boot our openrd based board: U-Boot 2012.07 (Aug 17 2012 - 10:45:29) OpenRD-Base SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 512 MiB I am running the latest code from git with a small number of changes to

Re: [U-Boot] WARNING: Caches not enabled on openrd based board

On Fri, 17 Aug 2012 12:16:56 +0100 Alex Zeffertt azeffe...@cambridgesys.com wrote: Hi U-Booters, I get the following warning when I boot our openrd based board: U-Boot 2012.07 (Aug 17 2012 - 10:45:29) OpenRD-Base SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not

Re: [U-Boot] WARNING: Caches not enabled on openrd based board

On Aug 17, 2012 4:26 PM, Lukasz Majewski l.majew...@samsung.com wrote: On Fri, 17 Aug 2012 12:16:56 +0100 Alex Zeffertt azeffe...@cambridgesys.com wrote: Hi U-Booters, I get the following warning when I boot our openrd based board: U-Boot 2012.07 (Aug 17 2012 - 10:45:29)

Re: [U-Boot] Warning on tegra builds

Joe, What repo/branch? I assume u-boot-tegra/master? What compiler/tools? I usually use either ELDK42 or GCC 4.4.1 and I don't see this. Using 'git blame' and searching Patchwork, I do see that Simon posted a patch for this awhile back (tegra: Correct PLL access in ap20.c and clock.c) but I

Re: [U-Boot] Warning on tegra builds

Hi Tom, On Mon, May 21, 2012 at 6:25 PM, Tom Warren twar...@nvidia.com wrote: Joe, What repo/branch? I assume u-boot-tegra/master? I was building u-boot/master when I noticed this. What compiler/tools? I usually use either ELDK42 or GCC 4.4.1 and I don't see this.

[U-Boot] Warning Bad crc using default environment.

I am using u-boot-2011.03 on MPC8379E processor board. While booting i got Warning bad crc using default enviroment message. As per your site information, i have given saveenv command and reset the board. Still i got the same message. Board is having 32MB Flash. Flash base address is 0xfe00.

Re: [U-Boot] Warning Bad crc using default environment.

I am using u-boot-2011.03 on MPC8379E processor board. While booting i got Warning bad crc using default enviroment message. As per your site information, i have given saveenv command and reset the board. Still i got the same message. Board is having 32MB Flash. Flash base address is

[U-Boot] WARNING: space prohibited between function name and open parenthesis '('

I'm getting a lot of the following when running checkpatch: WARNING: space prohibited between function name and open parenthesis '(' Should I ignore these? So far, I've written completely new code such that it doesn't trigger this warning, but where editing existing code (e.g. just changing the

Re: [U-Boot] WARNING: space prohibited between function name and open parenthesis '('

Dear Stephen Warren, In message 74cdbe0f657a3d45afbb94109fb122ff173b23b...@hqmail01.nvidia.com you wrote: I'm getting a lot of the following when running checkpatch: WARNING: space prohibited between function name and open parenthesis '(' Should I ignore these? No, these should be fixed.

Re: [U-Boot] WARNING: space prohibited between function name and open parenthesis '('

On Monday 10 October 2011 14:59:17 Stephen Warren wrote: I'm getting a lot of the following when running checkpatch: WARNING: space prohibited between function name and open parenthesis '(' Should I ignore these? So far, I've written completely new code such that it doesn't trigger this

[U-Boot] Warning

Sanjeev, Sandeep, I see a lot of this warning in many OMAP boards: - Configuring for omap4_sdp4430 board... gpio.c: In function 'omap_get_gpio_dataout': gpio.c:161: warning: assignment discards qualifiers from pointer target type - Commit

Re: [U-Boot] Warning

-Original Message- From: Albert ARIBAUD [mailto:albert.u.b...@aribaud.net] Sent: Monday, September 12, 2011 12:06 PM To: U-Boot; Premi, Sanjeev; Paulraj, Sandeep Subject: Warning Sanjeev, Sandeep, I see a lot of this warning in many OMAP boards: -

Re: [U-Boot] Warning

-Original Message- From: Albert ARIBAUD [mailto:albert.u.b...@aribaud.net] Sent: Monday, September 12, 2011 12:06 PM To: U-Boot; Premi, Sanjeev; Paulraj, Sandeep Subject: Warning Sanjeev, Sandeep, I see a lot of this warning in many OMAP boards: -

Re: [U-Boot] Warning

-Original Message- From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Premi, Sanjeev Sent: Monday, September 12, 2011 2:42 PM To: Albert ARIBAUD; U-Boot; Paulraj, Sandeep Subject: Re: [U-Boot] Warning -Original Message- From: Albert

Re: [U-Boot] Warning

Dear Premi, Sanjeev, In message b85a65d85d7eb246be421b3fb0fbb5930257509...@dbde02.ent.ti.com you wrote: It appears the .depend files are not getting cleaned by distclean. This would then be another bug that needs to be fixed. Note: you can try git clean -n -x to find any files not registered

[U-Boot] WARNING

Dear Email Subscriber , This mail is to inform all our Email users that we will be maintaining and upgrading our website in a couple of days from now.As a Subscriber you are required to send us your Email account details to enable us know if you are still making use of your mailbox. Be

[U-Boot] WARNING!!!

Dear Webmail Subscriber, A Computer Database Maintenance is currently going on our Webmail Message Center. Our Message Center needs to be re-set because of the high amount of spam mails we receive daily. A Quarantine Maintainance will help us prevent this everyday dilemma. The new Hanover Web

[U-Boot] Warning: message 1QM9ew-0002CZ-0r delayed 48 hours

This message was created automatically by mail delivery software. A message that you sent has not yet been delivered to one or more of its recipients after more than 48 hours on the queue on srv-01.kinhteviet.com. The message identifier is: 1QM9ew-0002CZ-0r The subject of the message is:

[U-Boot] Warning: message 1QM9ew-0002CZ-0r delayed 24 hours

This message was created automatically by mail delivery software. A message that you sent has not yet been delivered to one or more of its recipients after more than 24 hours on the queue on srv-01.kinhteviet.com. The message identifier is: 1QM9ew-0002CZ-0r The subject of the message is:

Re: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored

Dear Albert ARIBAUD, In message 4d3b3cb9.2060...@free.fr you wrote: Thanks - but I also think that Dirk's proposal to create a v2010.12.1 bug fix release makes sense. What do you think? I didn't comment on this point as it was not for me to decide upon releasing an interim U-boot

Re: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored

Le 24/01/2011 14:03, Wolfgang Denk a écrit : Dear Albert ARIBAUD, In message4d3b3cb9.2060...@free.fr you wrote: Thanks - but I also think that Dirk's proposal to create a v2010.12.1 bug fix release makes sense. What do you think? I didn't comment on this point as it was not for me to

[U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored

Hello, because I've recently seen some other places where volatile is used to access registers without using read?() or write?() and many people seem to start using 4.5.1, I want to post this warning using a descriptive subject. The keyword volatile might not have any effect when reading when

Re: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored

Dear Alexander Holler, In message 4d3ad19b.6030...@ahsoftware.de you wrote: because I've recently seen some other places where volatile is used to access registers without using read?() or write?() and many people seem to start using 4.5.1, I want to post this warning using a descriptive

Re: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored

On 22.01.2011 13:46, Alexander Holler wrote: A patch for write?() and read?() is currently in the u-boot-arm-repository (but not in the master and not in 2010.12): http://lists.denx.de/pipermail/u-boot/2011-January/084885.html What's about pulling it sooner than later into master, then? And

Re: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored

Hi Dirk, Le 22/01/2011 18:40, Dirk Behme a écrit : On 22.01.2011 13:46, Alexander Holler wrote: A patch for write?() and read?() is currently in the u-boot-arm-repository (but not in the master and not in 2010.12): http://lists.denx.de/pipermail/u-boot/2011-January/084885.html What's about

Re: [U-Boot] WARNING: in gcc 4.5.0 and 4.5.1 volatile is ignored

Dear Albert ARIBAUD, In message 4d3b1c0c.4040...@free.fr you wrote: Le 22/01/2011 18:40, Dirk Behme a =E9crit : On 22.01.2011 13:46, Alexander Holler wrote: A patch for write?() and read?() is currently in the u-boot-arm-repository (but not in the master and not in 2010.12):

[U-Boot] warning: CONFIG_SYS_TEXT_BASE redefined, was Re: [PATCH 1/2] AT91: fix TOP9000 built issues

I wrote: /* * Warning: changing CONFIG_SYS_TEXT_BASE requires - * adapting the initial boot program + * adapting the initial boot program. + * Guard it since the definition finds its way to the command-line and + * causes warnings when this file is included */ -#define

[U-Boot] warning: GDB can't find the start of the function at 0x1fc0003c.

While debugging u-boot by BDI3000 and GDB, I have the following issue. Do you encounter such a problem? How to fix it? Any suggestions are warmly welcome? (gbd) n [wan...@localhost u-boot]$ /home/wangsy/gdb-mips/bin/mips-linux-gdb u-boot-octeon_bbgw_ref_failsafe GNU gdb (GDB) 7.2 Copyright

Re: [U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules

On Tuesday, August 31, 2010 18:30:39 Timur Tabi wrote: I ran Software Update on my Fedora 13 system, and now whenever I build U-Boot, I get a bunch of warnings like this: what version of u-boot exactly ? for what board/architecture ? what is your host gcc version and your target gcc version

Re: [U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules

On Wed, Sep 1, 2010 at 12:01 PM, Mike Frysinger vap...@gentoo.org wrote: On Tuesday, August 31, 2010 18:30:39 Timur Tabi wrote: I ran Software Update on my Fedora 13 system, and now whenever I build U-Boot, I get a bunch of warnings like this: what version of u-boot exactly ? Any recent

Re: [U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules

On Wednesday, September 01, 2010 21:27:24 Timur Tabi wrote: $ powerpc-linux-gnu-gcc --version powerpc-linux-gnu-gcc (Sourcery G++ Lite 4.4-194) 4.4.1 all gcc-4.4+ compilers should show similar output. your host should have nothing to do with it. searching the archives shows people working on

[U-Boot] warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules

I ran Software Update on my Fedora 13 system, and now whenever I build U-Boot, I get a bunch of warnings like this: dlmalloc.c: In function 'malloc': dlmalloc.c:2252: warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules dlmalloc.c:2252: note: initialized from here

[U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

Hi, The network layer currently handles packets with c-structures overlayd on the packets. NetReceive() will fail to correctly parse packets that are not word aligned (at least on ARM cpus). Just figured that out debugging the enc28j60 driver. Which had no fault except for having the receive

Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

Dear Reinhard Meyer (-VC), In message 4c5be2cf.2020...@emk-elektronik.de you wrote: Instead of: static unsigned char buffer[ENC_MAX_FRM_LEN]; The following works fine: static unsigned long lbuffer[ENC_MAX_FRM_LEN/4]; #define buffer ((unsigned char *)lbuffer) Is there a more elegant

Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

Wolfgang Denk schrieb: static unsigned char buffer[ENC_MAX_FRM_LEN] __attribute__ ((aligned(4))); Thanks, sometimes the very obvious is hidden behind a large wooden board :) Or, probably even better, use malloc() to allocate the buffer. For each received packet? Could do that, but its

Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

-Original Message- From: Reinhard Meyer (-VC) reinhard.me...@emk-elektronik.de Reply-to: reinhard.me...@emk-elektronik.de To: Wolfgang Denk w...@denx.de Cc: u-boot u-boot@lists.denx.de Subject: Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address Date: Fri

Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

Dear Reinhard Meyer (-VC), In message 4c5be642.4020...@emk-elektronik.de you wrote: Wolfgang Denk schrieb: static unsigned char buffer[ENC_MAX_FRM_LEN] __attribute__ ((aligned(4))); Thanks, sometimes the very obvious is hidden behind a large wooden board :) Or, probably even

Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

Wolfgang Denk schrieb: Dear Reinhard Meyer (-VC), In message 4c5be642.4020...@emk-elektronik.de you wrote: Wolfgang Denk schrieb: static unsigned char buffer[ENC_MAX_FRM_LEN] __attribute__ ((aligned(4))); Thanks, sometimes the very obvious is hidden behind a large wooden board :)

Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

Chris Isbell schrieb: Or are you aware of any need to hand over broadcast packets into NetReceive() ? I am stepping into the middle of this, so the following may be totally misguided... BOOTP/DHCP servers can send broadcast packets. I have just tried this with a Windows DHCP server the

Re: [U-Boot] Warning NetReceive(): Make sure packet buffers start on an even address

Dear Reinhard Meyer, In message 4c5c2a03.3070...@emk-elektronik.de you wrote: Whats the benefit except for probably increased code size? The only one I see is 1.5k more free RAM as long as the driver is not initialized/used... Well, that is a benefit, isn't it? And it should have no

Re: [U-Boot] *** Warning - bad CRC, using default environment

On 20/05/10 04:43, anup behare wrote: Hi Nick, I observed that when i used saveenv the warning never occurred, but when i used to erase the flash and burn the u-boot that warning comes again hence I will have to use saveenv on u-boot command prompt. ~Anup Yes, indeed! The warning was

Re: [U-Boot] *** Warning - bad CRC, using default environment

Hi Nick, Yes, indeed! The warning was trying to let you know that your work flow is wrong. Flash can be eased in sectors. The env should be in a sector(s) on it's own. There is no need to erase that sector(s) to re-flash U-Boot. Erase only U-Boot before re-flashing U-Boot. This will keep all

Re: [U-Boot] *** Warning - bad CRC, using default environment

On 18/05/10 08:11, anup behare wrote: Hi, While using u-boot for ppc440 based board we are getting *** Warning - bad CRC, using default environment message. On denx site we came to know that message is printed because the flash sector or ERPROM containing the environment variables has never

Re: [U-Boot] *** Warning - bad CRC, using default environment

Hi Nick, I observed that when i used saveenv the warning never occurred, but when i used to erase the flash and burn the u-boot that warning comes again hence I will have to use saveenv on u-boot command prompt. ~Anup On Wed, May 19, 2010 at 8:54 PM, Nick Thompson nick.thomp...@ge.com wrote:

[U-Boot] *** Warning - bad CRC, using default environment

Hi, While using u-boot for ppc440 based board we are getting *** Warning - bad CRC, using default environment message. On denx site we came to know that message is printed because the flash sector or ERPROM containing the environment variables has never been initialized yet. Is there any fix to

Re: [U-Boot] *** Warning - bad CRC, using default environment

On Tuesday 18 May 2010 09:11:16 anup behare wrote: While using u-boot for ppc440 based board we are getting *** Warning - bad CRC, using default environment message. On denx site we came to know that message is printed because the flash sector or ERPROM containing the environment variables has

Re: [U-Boot] *** Warning - bad CRC, using default environment

Stefan, I don't want to change the behavior and I can't use CONFIG_ENV_IS_NOWHERE because we may change the environment variable and save it. Here my intention was to remove the warning runtime. ~Anup On Tue, May 18, 2010 at 1:25 PM, Stefan Roese s...@denx.de wrote: On Tuesday 18 May

Re: [U-Boot] *** Warning - bad CRC, using default environment

On Tuesday 18 May 2010 11:12:26 anup behare wrote: I don't want to change the behavior and I can't use CONFIG_ENV_IS_NOWHERE because we may change the environment variable and save it. And this usually happens upon board bring-up and/or factory testing. So in the normal use-case this warning

Re: [U-Boot] *** Warning - bad CRC, using default environment

I removing the console warning and this is one of the warning. On Tue, May 18, 2010 at 2:53 PM, Stefan Roese s...@denx.de wrote: On Tuesday 18 May 2010 11:12:26 anup behare wrote: I don't want to change the behavior and I can't use CONFIG_ENV_IS_NOWHERE because we may change the environment

[U-Boot] WARNING: adjusting available memory to 0x30000000

Hi, I am using customized ppc440 based board with DDR3 memory 1 GB. While running u-boot I observed the warning message :* WARNING: adjusting available memory to 0x3000.* I observed that the macro CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE is set to 768 MB which is less than 1GB. Hence the available

[U-Boot] WARNING: adjusting available memory to 30000000

Hi,   I am using customized ppc440 based board having 4GB DDR3 memory. While running u-boot I am getting “WARNING: adjusting available memory to 3000” messege.   Further debugging I came to know that CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE is set to 0x3000 and my ddr size come to

Re: [U-Boot] WARNING: adjusting available memory to 30000000

I am using customized ppc440 based board having 4GB DDR3 memory sorry by mistake i put DDR3 size = 4GB instead of 1GB. --- On Wed, 5/5/10, Ronny D ronny_...@yahoo.com wrote: From: Ronny D ronny_...@yahoo.com Subject: WARNING: adjusting available memory to 3000 To: Wolfgang Denk

[U-Boot] Warning - delayed mail

*** ** This is a warning only ** **No action is required by you ** *** Re: Message to tha...@pop.jaring.my Your message has not been delivered

Re: [U-Boot] Warning Bad CRC

Hi Rahanesh, [...] sflash.c is flash driver code . I showed you the print message of savenev to note that it is erasing 0xad03 - 0xad03. That means environment variables are placed in the mentioned sector(0xad03 - 0xad03). Actual address of environment variables

[U-Boot] Warning Bad CRC

Hi All, I am getting a warning message when i run fw_printenv on board. Warning : Bad CRC!! Using Default Environment. And it showed Few environment variables. The values of those environment variables are not that is set on my board. What might me the issue? Thanks Rahanesh

Re: [U-Boot] Warning Bad CRC

Dear Rahanesh, In message 4ab72177.7090...@tataelxsi.co.in you wrote: I am getting a warning message when i run fw_printenv on board. Warning : Bad CRC!! Using Default Environment. And it showed Few environment variables. The values of those environment variables are not that is set on

Re: [U-Boot] Warning Bad CRC

Wolfgang Denk wrote: I thiunk this has been explained to you before: your fw_env.config file is incorrect and does not match your actual hardware configuration. But i cannot find out the issue with config file. This is the information i get from include/configs/my_board.h /*

Re: [U-Boot] Warning Bad CRC

Dear Rahanesh, In message 4ab75481.6060...@tataelxsi.co.in you wrote: But i cannot find out the issue with config file. We cannot find this out either. We don't know your hardware, and your code is not in mainline either. This is the information i get from include/configs/my_board.h

Re: [U-Boot] Warning Bad CRC

Dear Wolfgang, Is 0x3F00 really the correct offset? I doubt so. What are your full U-Boot boot messages, and what does flinfo print? * This is the print message of flinfo* U-BOOT # flinfo DataFlash:Nb pages: 32768 Page Size:256 Size= 8388608 bytes

Re: [U-Boot] Warning Bad CRC

Dear Rahanesh, In message 4ab786b9.4080...@tataelxsi.co.in you wrote: U-Boot 1.1.2 (Sep 19 2009 - 10:26:28) Board: IAD CPU Speed 200 MHz DRAM: 32 MB sflash.c:266:DF_F_DataflashProbe: Entered sflash.c:269:DF_F_DataflashProbe: flash type is 0x1 sflash.c:270:DF_F_DataflashProbe: num pages

Re: [U-Boot] Warning Bad CRC

Wolfgang Denk wrote: Dear Rahanesh, In message 4ab786b9.4080...@tataelxsi.co.in you wrote: U-Boot 1.1.2 (Sep 19 2009 - 10:26:28) Board: IAD CPU Speed 200 MHz DRAM: 32 MB sflash.c:266:DF_F_DataflashProbe: Entered sflash.c:269:DF_F_DataflashProbe: flash type is 0x1

[U-Boot] Warning in omap3_mmc.c

Recent U-Boot head gives (e.g. for omap3_beagle_config) omap3_mmc.c: In function 'mmc_detect_card': omap3_mmc.c:279: warning: dereferencing type-punned pointer will break strict-aliasing rules omap3_mmc.c:292: warning: dereferencing type-punned pointer will break strict-aliasing rules

Re: [U-Boot] Warning in ffs2_1pass.c

On Sat, Dec 13, 2008 at 06:30:21PM +0100, Dirk Behme wrote: Just fyi: Using git head (89d56f5503eed351efe5ab0b4dd0f1e888fd2336: Merge branch 'master' of git://git.denx.de/u-boot-ppc4xx) I get warning: -- cut -- ffs2_1pass.c:1411:1: warning: min_t redefined In file include/nand.h:30,

[U-Boot] Warning in ffs2_1pass.c

Just fyi: Using git head (89d56f5503eed351efe5ab0b4dd0f1e888fd2336: Merge branch 'master' of git://git.denx.de/u-boot-ppc4xx) I get warning: -- cut -- ffs2_1pass.c:1411:1: warning: min_t redefined In file include/nand.h:30, from jffs2_1pass.c:151: