[U-Boot-Users] u-boot ...bootup warning bad crc

[U-Boot-Users] u-boot ...bootup warning bad crc

[Siddharth D Tiwari]

Hi all,

I'm trying to boot motorola's FADS823 eval. board with U-boot 0.2.0.
I was successfully able to program the flash with U-boot configured for FADS823  but with the following problem:
As soon as i reset,  the output is as follows and it hangs.....plz. help me in this regards...

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
 .

U-Boot 0.2.0 (Apr  4 2003 - 16:43:01)

CPU:   PPC823ZTnnA at 40 MHz: 2 kB I-Cache 1 kB D-Cache
         *** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: FADS with db MPC823 rev ENG or PILOT
I2C:   ready
DRAM:  (4 MB SDRAM)  8 MB
FLASH:  2 MB
*** Warning - bad CRC, using default environment


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

The output was as above.....
I have no idea where to look for, although i'm looking into the U-boot code.....
I'll be grateful for any help.

rgds,
Sid.

[U-Boot-Users] u-boot ...bootup warning bad crc

[Jerry Van Baren]

The Keys to the Kingdom
-----------------------
Step 1:
   less README

Step 2:
   find . -name "*.[ch]" -exec grep "Warning - bad CRC, using default 
environment" \{\} \; -print

Using the Keys, you will discover it is a warning caused by the fact that 
the environment variable space is invalid and the command "saveenv" will 
fix it.

gvb


At 06:53 PM 4/4/2003 -0500, siddharthdt at myw.ltindia.com wrote:
>Hi all,
>
>I'm trying to boot motorola's FADS823 eval. board with U-boot 0.2.0.
>I was successfully able to program the flash with U-boot configured for 
>FADS823
>but with the following problem:
>As soon as i reset,  the output is as follows and it hangs.....plz. help me in
>this regards...
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>  .
>
>U-Boot 0.2.0 (Apr  4 2003 - 16:43:01)
>
>CPU:   PPC823ZTnnA at 40 MHz: 2 kB I-Cache 1 kB D-Cache
>          *** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
>Board: FADS with db MPC823 rev ENG or PILOT
>I2C:   ready
>DRAM:  (4 MB SDRAM)  8 MB
>FLASH:  2 MB
>*** Warning - bad CRC, using default environment
>
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>The output was as above.....
>I have no idea where to look for, although i'm looking into the U-boot 
>code.....
>I'll be grateful for any help.
>
>rgds,
>Sid.
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: ValueWeb:
>Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
>No other company gives more support or power for your dedicated server
>http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
>_______________________________________________
>U-Boot-Users mailing list
>U-Boot-Users at lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/u-boot-users



**********************************************************************
This e-mail and any files transmitted with it are confidential and may
be legally privileged or otherwise exempt from disclosure under
applicable law. This e-mail and its files are intended solely for
the individual or entity to whom they are addressed and their content
is the property of Smiths Aerospace.  If you are not the intended
recipient, please do not read, copy, use or disclose this communication.
If you have received this e-mail in error please notify the e-mail 
administrator at postmaster at si.com and then delete this e-mail, its
files and any copies.

This footnote also confirms that this e-mail message has been scanned
for the presence of known computer viruses.
***********************************************************************

[U-Boot-Users] u-boot ...bootup warning bad crc

[Marius Groeger]

On Fri, 4 Apr 2003, Jerry Van Baren wrote:

> The Keys to the Kingdom
> -----------------------
> Step 1:
>    less README
>
> Step 2:
>    find . -name "*.[ch]" -exec grep "Warning - bad CRC, using default
> environment" \{\} \; -print

You may find xargs(1) interesting in this context.

> Using the Keys, you will discover it is a warning caused by the fact that
> the environment variable space is invalid and the command "saveenv" will
> fix it.

I think the OP is not (yet) able to type in any input. According to
his problem report, the box just hangs. Unfortunately, I have no real
advice to dispense, either...

> >FADS823
> >but with the following problem:
> >As soon as i reset,  the output is as follows and it hangs.....plz. help me in
> >this regards...

Regards,
Marius

-----------------------------------------------------------------------------
Marius Groeger           SYSGO Real-Time Solutions AG       mgroeger at sysgo.de
Software Engineering     Embedded and Real-Time Software    www.sysgo.de
Voice: +49-6136-9948-0   Am Pfaffenstein 14                 www.osek.de
FAX:   +49-6136-9948-10  55270 Klein-Winternheim, Germany   www.elinos.com

[U-Boot-Users] u-boot ...bootup warning bad crc

[Rune Torgersen]

When U-Boot hangs at this point (or later) it is usually a sign that the
memory map is incorrect and U-Boot is trying to access memory that doesn't
exist (be it Flash or RAM)

Make sure all memory sizes are correct, and on the correct chip-selects.

-----Original Message-----
From: Marius Groeger [mailto:mag at sysgo.de]
Sent: Friday, April 04, 2003 8:33 AM
To: Jerry Van Baren
Cc: siddharthdt at myw.ltindia.com; u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] u-boot ...bootup warning bad crc


On Fri, 4 Apr 2003, Jerry Van Baren wrote:

> The Keys to the Kingdom
> -----------------------
> Step 1:
>    less README
>
> Step 2:
>    find . -name "*.[ch]" -exec grep "Warning - bad CRC, using default
> environment" \{\} \; -print

You may find xargs(1) interesting in this context.

> Using the Keys, you will discover it is a warning caused by the fact that
> the environment variable space is invalid and the command "saveenv" will
> fix it.

I think the OP is not (yet) able to type in any input. According to
his problem report, the box just hangs. Unfortunately, I have no real
advice to dispense, either...

> >FADS823
> >but with the following problem:
> >As soon as i reset,  the output is as follows and it hangs.....plz. help
me in
> >this regards...

Regards,
Marius

----------------------------------------------------------------------------
-
Marius Groeger           SYSGO Real-Time Solutions AG
mgroeger at sysgo.de
Software Engineering     Embedded and Real-Time Software    www.sysgo.de
Voice: +49-6136-9948-0   Am Pfaffenstein 14                 www.osek.de
FAX:   +49-6136-9948-10  55270 Klein-Winternheim, Germany   www.elinos.com


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

[U-Boot-Users] u-boot ...bootup warning bad crc

[Siddharth]

Hi All,

thanx all for ur kind help...the problem was neither due to Memory Mapping nor CRC check...
I tried the same old routine method of debugging, which is the best...
puts( )..
It was all due to the assignment statement in devices_init( ) in devices.c
"gd->flags |= ".....
which is declared using DECLARE_GLOBAL_DATA_PTR in asm/global_data.h

Well as of now i have commented that, and my board seems to boot fine...
But while loading Linux....phew!!! Have a look below...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

:>tftpboot
ARP broadcast 1
ARP broadcast 2
TFTP from server 192.168.6.200; our IP address is 192.168.6.221
Filename 'vmlinuz-2.4.4.n2'.
Load address: 0x100000
Loading: #################################################################
         #################################################################
         #
done
Bytes transferred = 666865 (a2cf1 hex)
:>bootm
## Booting image at 00100000 ...
   Image Name:   Linux 2.4.4 (allfs)
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    666801 Bytes = 651.2 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Now my system hangs.....Any guesses guys....?????
Again, i have already started looking into to Kernel using grep and xargs......thanx to Jerry and Marius ...
thanx again...

adios
Sid.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20030408/fcf366f8/attachment.htm 

[U-Boot-Users] u-boot ...bootup warning bad crc

[Wolfgang Denk]

In message <002b01c2fda0$69bd3f00$a606a8c0@siddharth> you wrote:
> 
> thanx all for ur kind help...the problem was neither due to Memory
> Mapping nor CRC check...
> I tried the same old routine method of debugging, which is the best...
> puts( )..
> It was all due to the assignment statement in devices_init( ) in
> devices.c
> "gd->flags |= ".....
> which is declared using DECLARE_GLOBAL_DATA_PTR in asm/global_data.h

Please understand that this assignment is perfectly  fine  and  works
without a problem on some 100+ other boards.

> Well as of now i have commented that, and my board seems to boot fine...

The important word here is "seems".

> But while loading Linux....phew!!! Have a look below...

Please undo the change you made, go back one step and look  foir  the
_real_ cause of your problem.


Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
The number you have dialed is imaginary. Please divide by 0  and  try
again.

[U-Boot-Users] u-boot ...bootup warning bad crc

[Wolfgang Denk]

repl: bad addresses:
	< <u-boot-users@lists.sourceforge.net>> -- no mailbox in local-part (<)
In message <se930b71.078@EMAIL> you wrote:
> Hi Wolfgang....
> Ur very true in saying that its not the right way of debugging things.
> But ,unfortunately, i'm new to this U-boot.
> Could you please suggest me of what might have gone wrong....i have =
> absolutely no clue....
> Every thing till this stage is working fine & as soon as i assign the =
> value to gd->flags......my system just hangs then n there...
> plz. help me.

Ususally it means that your SDRAM initialization is broken.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Hindsight is an exact science.