• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2 3 ... 7
Author Topic: new uboot version 3.4.25  (Read 58225 times)
rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« on: December 23, 2009, 09:00:11 AM »

new QAed uboot version is ready, following are changes from last version (3.4.23):

  U-boot 3.4.27
  =============
  -) Modified in bootrom header file of 6280 the register values of 0x1620, and sequence of 0x1400. In mvUsb.c modified 0x50420 b[16:14] for 6280.
  -) Updated HAL.
  -) Changed electrical charactaristics of the PEX PHY in mvPex.c.


  U-boot 3.4.26
  =============
  -) Added 6282 option to mv_usb.c hal init function (prior to this addition the USB of the device was not initialized)
  -) Fixed in mvSata.h the device ID of 6282 to 1155 in order to make the integrated SATA controller work.


  U-boot 3.4.25
  =============
  -) Fixed in mv_main.c the initialization of nandEnvBase in order to solve a probel caused to the console variable.


  U-boot 3.4.24
  =============
  -) Fixed in mv_main.c the initialization of nandEnvBase from "" assignment of the env variable which caused wrong display of "" in the mmcinit command to strcpy.
  -) Fixed nand mark bad function in nand_base.c to support non sector aligned addresses.
  -) Changed device number 1155 to 6282
  -) Fixed in nand_base.c the string assignments to nandEcc parameter which caused it to overflow into other strings.


  U-boot 3.4.23
  =============
  -) excluded RD-6281 from audio shut down in mv_main.c.
  -) rolled back the fix in armlinux.c which was made in 3.4.22 (returned to previous state).

* uboot.bin (463.47 KB - downloaded 1443 times.)
Logged

rickyleeb
Newbie
*

Karma: 0
Posts: 35


View Profile
« Reply #1 on: December 23, 2009, 10:49:25 AM »

Just run through installer-v1.0 to run with the new uboot and upon the reboot im greeted with:

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Dec 23 2009 - 13:32:43) Marvell version: 3.4.27

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
SDHC found. Card desciption is:
Manufacturer:       0x02, OEM "TM"
Product name:       "SD16G", revision 3.2
Serial number:      3490581021
Manufacturing date: 11/2007
CRC:                0x00, b0 = 0

2620504 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2620440 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC


[Edit]

Just to check it was the u-boot and not the rootfs and kernal I downgraded the uboot to a older version (3.4.19) and everything works fine.

[/Edit]
Not sure if this is to do with the new uboot or not but thought I would just let you know.
« Last Edit: December 23, 2009, 11:20:22 AM by rickyleeb » Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #2 on: December 23, 2009, 12:04:45 PM »

Thanks for your effort  rooster, however unfortunately same issue here:

Updated from uboot-3.4.23 to .27. So far I could boot both an Ubuntu 9.04 from NAND and a Debian from SD (both with kernel 2.6.32.2 these days).

As with the uboot versions 3.4.24 and 3.4.25 the kernel  from SD is reported to have a "Bad Data CRC".

Luckily it falls back to the kernel in NAND and boots the Ubuntu. Mounting the SD and rewriting the kernel is not mitigating the situation.

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Dec 23 2009 - 13:32:43) Marvell version: 3.4.27

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0

2861324 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.2 (kelly@speedy) (gcc version 4.2.1) #1 PREEMPT Fri Dec 18 22:54:28 MST 2009
[...]
Ubuntu 9.04 debian ttyS0

debian login: root
Password:
Last login: Wed Dec 23 19:31:06 CET 2009 on ttyS0
Linux debian 2.6.32.2 #1 PREEMPT Fri Dec 18 22:54:28 MST 2009 armv5tel
[...]
root@debian:~# mount /dev/mmcblk0p1 /boot
root@debian:/boot# ls -al /boot/
total 5545
drwxr-xr-x  3 root root    1024 Dec 19 12:02 .
drwxr-xr-x 21 root root       0 Dec 19 07:04 ..
drwx------  2 root root   12288 Dec 13 19:09 lost+found
-rw-r--r--  1 root root 2777892 Dec 19 12:00 sheeva-2.6.31.9-uImage
-rw-r--r--  1 root root 2861324 Dec 19 12:00 sheeva-2.6.32.2-uImage
lrwxrwxrwx  1 root root      22 Dec 19 12:02 uImage -> sheeva-2.6.32.2-uImage
root@debian:~# ./README-2.6.32.2 --rootkernel
Downloading files
Extracting modules
Writing kernel to /boot
****************************************************************
 update your bootcmd to load sheeva-2.6.32.2-uImage
 or use a symlink from /boot/sheeva-2.6.32.2-uImage to /boot/uImage
****************************************************************
root@debian:~# ls -al /boot/
total 5545
drwxr-xr-x  3 root root    1024 Dec 19 12:02 .
drwxr-xr-x 21 root root       0 Dec 19 07:04 ..
drwx------  2 root root   12288 Dec 13 19:09 lost+found
-rw-r--r--  1 root root 2777892 Dec 19 12:00 sheeva-2.6.31.9-uImage
-rw-r--r--  1 root root 2861324 Dec 23 19:39 sheeva-2.6.32.2-uImage
lrwxrwxrwx  1 root root      22 Dec 19 12:02 uImage -> sheeva-2.6.32.2-uImage
root@debian:~#reboot

[...]

SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0

2861324 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC


PS: as the issue was introduced with .24 - what of the four changes from .23 may have introduced this behavior!?
« Last Edit: December 23, 2009, 12:07:15 PM by odoll » Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #3 on: December 23, 2009, 01:05:03 PM »

Let me try the 23->27 upgrade myself and see what the issue is, I tried 25->27 and it worked. I think it is related to the ECC 1/4bit settings
Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #4 on: December 23, 2009, 01:14:38 PM »

Puh, though really having no clue want I'm doing here neither understanding the bits and peaces of the boot variables I think I got it working, once!

While I was trying to boot the kernel from NAND but using the RFS from SD I figured that my NAND and SD strings differ at the following part (red):

bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw ip=a.b.c.253:a.b.c.254:a.b.c.1:255.255.255.0:DB88FXX81:eth0:none
bootargs_nand=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=a.b.c.253:a.b.c.254:a.b.c.1:255.255.255.0:DB88FXX81:eth0:none
bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_sd=setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x8000000


Thus I think I changed it to

setenv bootcmd_sd 'setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x800000'

and it worked as I could log into the Debian.

However while trying to make it permanent it's going wrong again.

Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #5 on: December 23, 2009, 01:38:33 PM »

Yes, must be me being mistaken loading the kernel from NAND, but having the RFS running from SD :-(

Marvell>> setenv bootcmd_nand 'setenv bootargs $(bootargs_sd); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
Marvell>> run bootcmd_nand

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.2 (kelly@speedy) (gcc version 4.2.1) #1 PREEMPT Fri Dec 18 22:54:28 MST 2009
[...]
Starting periodic command scheduler: crond.

Debian GNU/Linux 5.0 debian ttyS0

debian login:
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #6 on: December 23, 2009, 02:08:05 PM »

Hi odoll,

I think you already spot your own error Smiley, the ext2load use third parameter as location in memory to load your kernel image and the bootm use first parameter as where to start linux. so if you do
Code:
Marvell>> ext2load mmc 0 0x00800000 /uImage
Marvell>> bootm 0x00800000
this should work.

Good Luck Smiley
Logged

Good Luck Smiley

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #7 on: December 23, 2009, 02:39:14 PM »

Updated from 3.4.25 to 3.4.27 worked perfectly for me from USB.

Many thanks.
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #8 on: December 23, 2009, 05:41:06 PM »

Hi rooster,

3.4.27 does not work for me completely as 3.4.23, for same SD card 3.4.23 work no matter what file system. but for 3.4.27 if the file system type is ext2, the ext2load will read one file then return with a silent error so if the ext2load was embedded in a run command everything after ext2load will not continue. when the file system type is fat the fatload does not return error but it print out
Code:
reading /uImage
curclust: 0x00000000 fatsize=16
Invalid FAT entry
696320 bytes read
reading /uInitramfs
curclust: 0x00000000 fatsize=16
Invalid FAT entry

598016 bytes read
when verify the load image in memory all report BAD CRC. I would like to investigate why this happening, so can you put the 3.4.23 source code back I would like to see how changes affect the mmc code.

Best regards,

Logged

Good Luck Smiley

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #9 on: December 23, 2009, 11:13:09 PM »

here are the sources of 3.4.23

* u-boot-3.4.23.zip (2519.62 KB - downloaded 510 times.)
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #10 on: December 23, 2009, 11:42:00 PM »

Hey ccp,

I tried with my SD (Kingston 16G c4)
Quote
ext2load mmc 0 0x8000000 /uImage
and it loaded fine.
What SD card are you using?
Is the partition ext3 or ext2?

rickyleeb and odol,
Did you get this uboot version working for you after setting the right uboot parameters?
I want to focus on the real issues related to this version.
Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #11 on: December 24, 2009, 04:53:40 AM »

Hi odoll,

I think you already spot your own error Smiley [...]  if you do [...] this should work.
rickyleeb and odol,
Did you get this uboot version working for you after setting the right uboot parameters?

Unfortunately no:

Hit any key to stop autoboot:  0
Marvell>> ext2load mmc 0 0x00800000 /uImage
** Bad partition 1 **
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read
Marvell>> bootm 0x00800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

« Last Edit: December 24, 2009, 04:56:14 AM by odoll » Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #12 on: December 24, 2009, 05:26:08 AM »

BTW: whether bootm 0x00800000 or bootm 0x008000000 makes no difference

Hit any key to stop autoboot:  0
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read
Marvell>> bootm 0x008000000
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC


However with uboot 3.4.23

Marvell>> bubt u-boot-3.4.23.bin
Using egiga0 device
TFTP from server a.b.c.5; our IP address is a.b.c.253
Filename 'u-boot-3.4.23.bin'.
Load address: 0x2000000
Loading: #################################################################
         ############################
done
Bytes transferred = 474596 (73de4 hex)

**Warning**
If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
Override Env parameters? (y/n) n
Erase 0 - 655360 ...
Copy to Nand Flash...
done
Marvell>> reset

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Nov  4 2009 - 12:58:36) Marvell version: 3.4.23

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SDa0000 found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read

Marvell>> bootm 0x00800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.2 (kelly@speedy) (gcc version 4.2.1) #1 PREEMPT Fri Dec 18 22:54:28 MST 2009
Logged

odoll
Full Member
***

Karma: 0
Posts: 148


View Profile
« Reply #13 on: December 24, 2009, 06:14:48 AM »

BTW: whether bootm 0x00800000 or bootm 0x008000000 makes no difference

I'm really getting confused: I find various versions in the Wikis, e.g.

http://www.plugcomputer.org/plugwiki/index.php/U-Boot_Quick_Reference
http://www.plugcomputer.org/plugwiki/index.php/External_Hard_Drives
http://computingplugs.com/index.php/Booting_entirely_off_an_external_USB_device
http://www.cyrius.com/debian/kirkwood/sheevaplug/unpack.html

Or does it depend on whether it's NAND, USB or SD?

However, either a get a "Bad Magic Number" error (bootm 0x00800000)
ot the "Bad Data CRC" error (bootm 0x008000000)
« Last Edit: December 24, 2009, 06:23:50 AM by odoll » Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #14 on: December 24, 2009, 06:23:07 AM »

Hey ccp,

I tried with my SD (Kingston 16G c4)
Quote
ext2load mmc 0 0x8000000 /uImage
and it loaded fine.
What SD card are you using?
Is the partition ext3 or ext2?

rickyleeb and odol,
Did you get this uboot version working for you after setting the right uboot parameters?
I want to focus on the real issues related to this version.
Mine is Kingston 4G and Kingston 2G. the test I perform is on same plug, same SD card, switching between 3.4.23 and 3.4.27 and switching between FAT and EXT2. it is not very consistent in term of error message but always fail.

Thanks for the source code. I will check it out once I am home today.

BTW you only load one image, try to load two different images consecutively see if you will get any error?
Logged

Good Luck Smiley

Pages: [1] 2 3 ... 7
Print
Jump to: