Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Thu Nov 23, 2017 12:22 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 17 posts ]  Go to page 1 2 Next
Author Message
 Post subject: u-boot checksum bad?
PostPosted: Fri Oct 06, 2006 3:56 pm 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
I got finally got u-boot built. I tried out the RAM build, but got
'checksum bad' on the console four times. I didn't type anything,
it proactively told me there was a problem.

I tried the prebuilt .bin from nas-central.org (HG), but I couldn't
even get a nc connection with that one.

Any help?


Code:
[eldk@nexus u-boot-1.1.4]$ board/linkstation/nc.sh 192.168.11.150 
Connection to 192.168.11.150 6666 port [udp/*] succeeded!
 
U-Boot 1.1.4 LiSt 2.1.0 (Oct  7 2006 - 00:30:00) LinkStation HG / KuroBox HG
stdin :   nc
stdout:   nc
stderr:   nc
IDE:   Bus 0: OK
  Device 0: Model: SAMSUNG HD300LD Firm: WK100-12 Ser#: SXXXXXXXXXX
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
Boot in 07 seconds ('s' to stop)...
=> checksum bad
checksum bad
checksum bad
checksum bad
 
=> flinfo
 
Bank # 1: Flash chip: STMICRO M29W324DB
 
CFI Query Results:
Primary Vendor Command Set: 0x0002 (AMD/Fujitsu Standard)
Primary Algorithm Table at 0x0040
Alternate Vendor Command Set: 0x0000 (None)
No Alternate Algorithm Table
Vcc Min.: 2.7 V
Vcc Max.: 3.6 V
Vpp Min.: 11.5 V
Vpp Max.: 12.5 V
Typical byte/word write timeout: 16 us
Maximum byte/word write timeout: 256 us
Full buffer write not supported
Typical block erase timeout: 1024 ms
Maximum block erase timeout: 8192 ms
Chip erase not supported
Device size: 0x400000 bytes (4 MiB)
Flash Device Interface description: 0x0002
  - x8 / x16 via BYTE# with asynchronous interface
Max. bytes in buffer write: 1
Number of Erase Block Regions: 2
 
Actual values used by U-Boot:
Word   write timeout:      2 ms
Buffer write timeout:      2 ms
Sector erase timeout:   8192 ms
 


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Fri Oct 06, 2006 4:02 pm 
Offline
Site Admin
User avatar

Joined: Tue Jul 12, 2005 11:26 am
Posts: 3701
Location: JAPAN
The bad checksum is as a result of you not using the reserved area for storing env variables (saveenv) that override those values set during compilation. It is not an error.

_________________
LS used as PVR and streaming source


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Fri Oct 06, 2006 9:17 pm 
Offline
Developer

Joined: Sat Aug 19, 2006 4:53 pm
Posts: 187
Location: United Kingdom (Great Britain)
In fact the message "checksum bad" is from the network layer saying that it received a bad packet and it is discarding it. Harmless, but it shows that your network is a little bit shaky. Maybe loose cable or poor quality cable.
Your RAM build seems to work just fine and the flash chip is the same as the one in my LS-HG. In my view, you can now build the ROM version and flash it.


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Fri Oct 06, 2006 11:16 pm 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
linuxnotincluded wrote:
Harmless, but it shows that your network is a little bit shaky. Maybe loose cable or poor quality cable.

I'm running gigabit over Cat. 5e equipment. I'll swap it back and see if it's better.

linuxnotincluded wrote:
In my view, you can now build the ROM version and flash it.

Woohoo! I feel like I've received a blessing! Thanks for the assurance.


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sat Oct 07, 2006 7:33 am 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
hsum wrote:
I'll swap it back and see if it's better.

I'm still getting those 'checksum bad' on the console using fast ethernet. Maybe I have some bad cables somewhere.

linuxnotincluded wrote:
U-Boot will attempt to load the ROM build from the directory share/u-boot/ on the third partition of the hard drive

I'm trying to flash it. Unfortunately, I don't have a 3rd partition and neither will anyone with a stock LS, right? Does this mean that the preferred method won't be used by most people? Is flashing from Linux that bad?

I think include/configs/linkstation.h:167 defines which partition to get the UBFILE from:
Code:
    "ubpart=0:3\0"


Is it safe for me to change this from 3 to 1 and rebuild?


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sat Oct 07, 2006 8:09 am 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
It looks like ubpart is an environmental variable and it could/needs to be changed in the runtime environment in order to flash.

Was this intended as a safety measure?

thanks.


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sat Oct 07, 2006 9:07 am 
Offline
Developer

Joined: Sat Aug 19, 2006 4:53 pm
Posts: 187
Location: United Kingdom (Great Britain)
hsum wrote:
I don't have a 3rd partition and neither will anyone with a stock LS, right?

Wrong. Everyboy has the third partition, /dev/hda3. It is mounted on /mnt. And you are looking at the wrong configuration variable. ubpart is used to load and flash a ROM build from a RAM build.

In the standard configuration, U-Boot attempts to load the file boot/vmlinux.UBoot from the first hard disk partition, /dev/hda1. The partition and file name are stored in the environment variables "hdpart" and "hdfile" respectively. Note that the name of the file can be a symbolic link. Some of the precompiled binaries have changed the file name to "uImage" but if you compiled U-Boot yourself, this is not the case.


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sat Oct 07, 2006 9:34 am 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
My mistake, I rebooted into /dev/hda1 root.../mnt is on /dev/hda3

Unfortunately, uboot isn't able to find my partition table.
Code:
=> run upgrade 
Loading 0:3:share/u-boot/u-boot-hg.flash.bin
Error (no IRQ) dev 0 blk 0: status 0xd0
** Can't read partition table on 0:0 **
** Bad partition 3 **


Any suggestions? thanks again.


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sat Oct 07, 2006 3:56 pm 
Offline
Developer

Joined: Sat Aug 19, 2006 4:53 pm
Posts: 187
Location: United Kingdom (Great Britain)
It appears that your hard disk is not responding which is strange given your first post:
Code:
IDE:   Bus 0: OK 
  Device 0: Model: SAMSUNG HD300LD Firm: WK100-12 Ser#: SXXXXXXXXXX
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
Please note that the message "no IRQ" can be misleading. U-Boot doesn't use interrupts with the exception of the decrementer interrupt. The message is about U-Boot not receiving a response from the hard disk within the timeout period.

Reload the RAM build, press 's' to stop the boot process and try:
Code:
=> ext2ls ide 0:1 /
to list the contents of /dev/hda1:/ and
Code:
=> ext2ls ide 0:3 share/u-boot
to list the contents of /dev/hda3:/share/u-boot

If the above commands work, the "upgrade" command should work too.


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sat Oct 07, 2006 10:45 pm 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
linuxnotincluded wrote:
ext2ls ide 0:1 /

works - no problem.

linuxnotincluded wrote:
ext2ls ide 0:3 share/u-boot

no good.

Code:
=> ext2ls ide 0:3 share/u-boot 
Error (no IRQ) dev 0 blk 381416090: status 0x51
 ** ext2fs_devread() read error - last part
=> ext2ls ide 0:3 share
<DIR>       4096 .
<DIR>       4096 ..
Error (no IRQ) dev 0 blk 381416090: status 0x51
 ** ext2fs_devread() read error - last part
=> ext2ls ide 0:3 /
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 share
<DIR>       4096 share-mac
<DIR>       4096 spool
<DIR>       4096 backups
<DIR>       4096 usr
<DIR>       4096 tmp
<DIR>       4096 ftp


Code:
root@HD-HGLAN1A6:/mnt# ls -l share/u-boot 
total 176
-rw-r--r--    1 root     root       174664 Oct  7 07:45 u-boot-hg.flash.bin


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sun Oct 08, 2006 11:33 am 
Offline
Developer

Joined: Sat Aug 19, 2006 4:53 pm
Posts: 187
Location: United Kingdom (Great Britain)
hsum wrote:
Error (no IRQ) dev 0 blk 381416090: status 0x51

The status show an error in the disk read operation (bit 0 is set).
hsum wrote:
Error (no IRQ) dev 0 blk 0: status 0xd0

The status shows a timeout (bit 7 is set).

You seem to have a problem sector or a faulty cable. U-Boot doesn't retry the disk operations where Linux does. Check the kernel log for disk errors.
Try to read the problem sector using the "ide" command. Remember that U-Boot treats all input as hex, so 381416090 = 0x16BBF29A.
Code:
ide read 800000 16BBF29A 1


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sun Oct 08, 2006 4:07 pm 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
I switched to directly connecting the HG to my machine - no more checksum errors.

/var/log/messages didn't have any errors - at least not disk related.

Unfortunately, there is still a problem reading my disk:

Code:
=> ide read 800000 16BBF29A 1 
 
IDE read: device 0 block # 381416090, count 1 ... Error (no IRQ) dev 0 blk 381416090: status 0xd0
0 blocks read: ERROR


Is this an unrecoverable error?


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sun Oct 08, 2006 4:09 pm 
Offline
Site Admin
User avatar

Joined: Tue Jul 12, 2005 11:26 am
Posts: 3701
Location: JAPAN
Have you tried re-formatting this partition? you are getting too many sector errors.

_________________
LS used as PVR and streaming source


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sun Oct 08, 2006 5:32 pm 
Offline
Regular Member

Joined: Sat Dec 03, 2005 7:29 am
Posts: 106
lb_worm wrote:
Have you tried re-formatting this partition?


Pure genius! I tried fsck, but mkfs.ext2 -j is really what I needed.
Temporarily unlinking /usr was the only potential problem.

U-Boot is installed. Thank you both!

Code:
Connection to 192.168.11.150 6666 port [udp/*] succeeded! 
 
U-Boot 1.1.4 LiSt 2.1.0 (Oct  7 2006 - 00:30:00) LinkStation HG / KuroBox HG
stdin :   nc
stdout:   nc
stderr:   nc
IDE:   Bus 0: OK
  Device 0: Model: SAMSUNG HD300LD Firm: WK100-12 Ser#: SXXXXXXXXXX
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 286168.1 MB = 279.4 GB (586072368 x 512)
Boot in 09 seconds ('s' to stop)...
=> ext2ls ide 0:3 share/u-boot
<DIR>       4096 .
<DIR>       4096 ..
          174664 u-boot-hg.flash.bin
=> run upgrade
Loading 0:3:share/u-boot/u-boot-hg.flash.bin
 
174664 bytes read
Un-Protected 3 sectors
 
Flash erase: first = 55 @ 0xfff00000
             last  = 57 @ 0xfff20000
Flash erase: Done
Erased 3 sectors
Copy to Flash... done
Total of 174664 bytes were the same


Top
   
 Post subject: Re: u-boot checksum bad?
PostPosted: Sun Oct 08, 2006 6:23 pm 
Offline
Site Admin
User avatar

Joined: Tue Jul 12, 2005 11:26 am
Posts: 3701
Location: JAPAN
great :) you have finally done it. Welldone.

_________________
LS used as PVR and streaming source


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 17 posts ]  Go to page 1 2 Next

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 8 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited