• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 2 3 [4] 5 6 7
Author Topic: new uboot version 3.4.25  (Read 53023 times)
monkeyhybrid
Newbie
*

Karma: 1
Posts: 16


View Profile
« Reply #45 on: December 30, 2009, 05:07:52 AM »

Thanks pingtoo!

I ran into this problem this morning whilst setting up my first Sheeva plug, preparing it for Debian Squeeze. Your patched version worked a treat!
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #46 on: December 30, 2009, 12:44:38 PM »

I also can confirm that the patch fixed the mismatch between SD and USB found in 3.4.27.
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #47 on: December 30, 2009, 01:50:38 PM »

I also can confirm that the patch fixed the mismatch between SD and USB found in 3.4.27.
Thanks. BTW, Did you got my patch file yet?
Logged

Good Luck Smiley

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #48 on: December 30, 2009, 11:37:56 PM »

Quote
Thanks. BTW, Did you got my patch file yet?
Yes I did and tested it patched against 3.4.27
Logged

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #49 on: January 01, 2010, 10:11:33 AM »

Hi pingtoo and rooster.

I have been doing so more testing with the patched version of uboot 3.4.27 and my 8GB Kingston class 6 card.

I cleared the card completely... and reformatted with ext2fs.

I untarred  a Debian root file system from M Gilespie (sp?) on it.

I cross compiled a new uImage, and installed it in /boot on the card.

When I tried to ext2load /boot/uImage  or ext2ls mmc 0:1 /boot  uboot returned an empty directory !!!  HOWEVER ext2ls mmc 0:1 /dev returned a list of the contents Huh?

Looking through this forum I found this entry,  (actually to rooster!):-

http://plugcomputer.org/plugforum/index.php?topic=307.msg3117#msg3117

Which describes my problem exactly.

So I moved uImage from /boot  to / on the card and booted manually thus:-
Quote
set bootargs 'console=ttyS0,115200 ro root=/dev/mmcblk0p1 rootdelay=3'
mmcinit
ext2load mmc 0 0x800000 /uImage
bootm 0x800000

This worked OK and loaded and booted my new kernel which runs OK.

The number of manual mmcinits I give do not make any difference.

Now the problem is that the only difference between ext2load working and not working is a new ext2fs using the same command,  untarring the same root file system, but installing a new kernel,  which will be slightly different in size on the SAME SDHC card.

Now  a further interesting observation.

I tried an ext2ls on /boot   failed
                              /dev     returned contents OK
                              /etc      failed

When I put the card in a reader on my Linux box, and did a ls -la on  /boot , /dev, and /etc, I found that there was a difference,  /boot and /etc contents had NO alpha bit set and failed to list, all the files and directories in /dev had the ALPHA character of the permision set thus:-
Quote
debsilch:/mnt/plug# ls -la dev
total 16
drwxr-xr-x  4 root root     4096 2010-01-01 16:36 .
drwxr-xr-x 21 root root     4096 2010-01-01 16:32 ..
crw-rw----  1 root video 10, 175 2009-12-03 12:35 agpgart
crw-rw----  1 root audio 14,   4 2009-12-03 12:35 audio
crw-rw----  1 root audio 14,  20 2009-12-03 12:35 audio1
crw-rw----  1 root audio 14,  36 2009-12-03 12:35 audio2
crw-rw----  1 root audio 14,  52 2009-12-03 12:35 audio3
crw-rw----  1 root audio 14,   7 2009-12-03 12:35 audioctl
crw-------  1 root tty    5,   1 2009-12-03 12:34 console
lrwxrwxrwx  1 root root       11 2010-01-01 15:27 core -> /proc/kcore
crw-rw----  1 root audio 14,   3 2009-12-03 12:35 dsp
crw-rw----  1 root audio 14,  19 2009-12-03 12:35 dsp1
crw-rw----  1 root audio 14,  35 2009-12-03 12:35 dsp2
crw-rw----  1 root audio 14,  51 2009-12-03 12:35 dsp3
lrwxrwxrwx  1 root root       13 2010-01-01 15:27 fd -> /proc/self/fd
crw-rw-rw-  1 root root   1,   7 2009-12-03 12:34 full
prw-------  1 root root        0 2009-12-03 12:35 initctl
crw-r-----  1 root kmem   1,   2 2009-12-03 12:34 kmem
srw-rw-rw-  1 root root        0 2010-01-01 16:36 log
brw-rw----  1 root disk   7,   0 2009-12-03 12:34 loop0
brw-rw----  1 root disk   7,   1 2009-12-03 12:34 loop1
brw-rw----  1 root disk   7,   2 2009-12-03 12:34 loop2
brw-rw----  1 root disk   7,   3 2009-12-03 12:34 loop3
brw-rw----  1 root disk   7,   4 2009-12-03 12:34 loop4
brw-rw----  1 root disk   7,   5 2009-12-03 12:34 loop5
brw-rw----  1 root disk   7,   6 2009-12-03 12:34 loop6
brw-rw----  1 root disk   7,   7 2009-12-03 12:34 loop7
crw-r-----  1 root kmem   1,   1 2009-12-03 12:34 mem
crw-rw----  1 root audio 35,   0 2009-12-03 12:35 midi0
crw-rw----  1 root audio 14,   2 2009-12-03 12:35 midi00
crw-rw----  1 root audio 14,  18 2009-12-03 12:35 midi01
crw-rw----  1 root audio 14,  34 2009-12-03 12:35 midi02
crw-rw----  1 root audio 14,  50 2009-12-03 12:35 midi03
crw-rw----  1 root audio 35,   1 2009-12-03 12:35 midi1
crw-rw----  1 root audio 35,   2 2009-12-03 12:35 midi2
crw-rw----  1 root audio 35,   3 2009-12-03 12:35 midi3
crw-rw----  1 root audio 14,   0 2009-12-03 12:35 mixer
crw-rw----  1 root audio 14,  16 2009-12-03 12:35 mixer1
crw-rw----  1 root audio 14,  32 2009-12-03 12:35 mixer2
crw-rw----  1 root audio 14,  48 2009-12-03 12:35 mixer3
crw-rw----  1 root audio 31,   0 2009-12-03 12:35 mpu401data
crw-rw----  1 root audio 31,   1 2009-12-03 12:35 mpu401stat
crw-rw-rw-  1 root root   1,   3 2009-12-03 12:34 null
crw-r-----  1 root kmem   1,   4 2009-12-03 12:34 port
crw-rw-rw-  1 root tty    5,   2 2009-10-04 21:23 ptmx
drwxr-xr-x  2 root root     4096 2009-12-03 12:35 pts
lrwxrwxrwx  1 root root        4 2010-01-01 15:26 ram -> ram1
brw-rw----  1 root disk   1,   0 2009-12-03 12:34 ram0
brw-rw----  1 root disk   1,   1 2009-12-03 12:34 ram1
brw-rw----  1 root disk   1,  10 2009-12-03 12:34 ram10
brw-rw----  1 root disk   1,  11 2009-12-03 12:34 ram11
brw-rw----  1 root disk   1,  12 2009-12-03 12:34 ram12
brw-rw----  1 root disk   1,  13 2009-12-03 12:34 ram13
brw-rw----  1 root disk   1,  14 2009-12-03 12:34 ram14
brw-rw----  1 root disk   1,  15 2009-12-03 12:34 ram15
brw-rw----  1 root disk   1,  16 2009-12-03 12:34 ram16
brw-rw----  1 root disk   1,   2 2009-12-03 12:34 ram2
brw-rw----  1 root disk   1,   3 2009-12-03 12:34 ram3
brw-rw----  1 root disk   1,   4 2009-12-03 12:34 ram4
brw-rw----  1 root disk   1,   5 2009-12-03 12:34 ram5
brw-rw----  1 root disk   1,   6 2009-12-03 12:34 ram6
brw-rw----  1 root disk   1,   7 2009-12-03 12:34 ram7
brw-rw----  1 root disk   1,   8 2009-12-03 12:34 ram8
brw-rw----  1 root disk   1,   9 2009-12-03 12:34 ram9
crw-rw-rw-  1 root root   1,   8 2009-12-03 12:34 random
crw-rw----  1 root audio 35,  64 2009-12-03 12:35 rmidi0
crw-rw----  1 root audio 35,  65 2009-12-03 12:35 rmidi1
crw-rw----  1 root audio 35,  66 2009-12-03 12:35 rmidi2
crw-rw----  1 root audio 35,  67 2009-12-03 12:35 rmidi3
crw-rw----  1 root audio 14,   1 2009-12-03 12:35 sequencer
drwxr-xr-x  3 root root     4096 2009-12-03 12:36 shm
crw-rw----  1 root audio 35, 128 2009-12-03 12:35 smpte0
crw-rw----  1 root audio 35, 129 2009-12-03 12:35 smpte1
crw-rw----  1 root audio 35, 130 2009-12-03 12:35 smpte2
crw-rw----  1 root audio 35, 131 2009-12-03 12:35 smpte3
crw-rw----  1 root audio 14,   6 2009-12-03 12:35 sndstat
lrwxrwxrwx  1 root root        4 2010-01-01 15:26 stderr -> fd/2
lrwxrwxrwx  1 root root        4 2010-01-01 15:26 stdin -> fd/0
lrwxrwxrwx  1 root root        4 2010-01-01 15:26 stdout -> fd/1
crw-rw-rw-  1 root tty    5,   0 2009-12-03 12:34 tty
crw-------  1 root tty    4,   0 2009-12-03 12:34 tty0
crw-------  1 root tty    4,   1 2009-12-03 12:34 tty1
crw-------  1 root tty    4,   2 2009-12-03 12:34 tty2
crw-------  1 root tty    4,   3 2009-12-03 12:34 tty3
crw-------  1 root tty    4,   4 2009-12-03 12:34 tty4
crw-------  1 root tty    4,   5 2009-12-03 12:34 tty5
crw-------  1 root tty    4,   6 2009-12-03 12:34 tty6
crw-------  1 root tty    4,   7 2009-12-03 12:35 tty7
crw-------  1 root tty    4,   8 2009-12-03 12:35 tty8
crw-------  1 root tty    4,   9 2009-12-03 12:35 tty9
crw-rw-rw-  1 root root   1,   9 2009-12-03 12:34 urandom
prw-r-----  1 root adm         0 2010-01-01 16:57 xconsole
crw-rw-rw-  1 root root   1,   5 2009-12-03 12:34 zero


Whereas the failing directory /etc looks like:-
Quote
debsilch:/mnt/plug# ls -la etc
total 428
drwxr-xr-x 42 root root    4096 2010-01-01 16:36 .
drwxr-xr-x 21 root root    4096 2010-01-01 16:32 ..
-rw-r--r--  1 root root    2986 2009-12-03 12:35 adduser.conf
-rw-r--r--  1 root root      44 2009-12-03 12:33 adjtime
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 alternatives
drwxr-xr-x  4 root root    4096 2009-12-03 12:36 apt
-rw-r--r--  1 root root    1453 2008-05-13 16:49 bash.bashrc
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 bash_completion.d
-rw-r--r--  1 root root     332 2009-01-04 16:12 bindresvport.blacklist
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 calendar
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 cron.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:36 cron.daily
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 cron.hourly
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 cron.monthly
-rw-r--r--  1 root root     724 2008-09-28 12:07 crontab
drwxr-xr-x  2 root root    4096 2009-12-03 12:36 cron.weekly
-rw-r--r--  1 root root      54 2009-12-03 12:37 crypttab
-rw-r--r--  1 root root    2969 2008-10-12 18:07 debconf.conf
-rw-r--r--  1 root root       6 2009-08-30 21:01 debian_version
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 default
-rw-r--r--  1 root root     600 2008-08-10 22:35 deluser.conf
drwxr-xr-x  4 root root    4096 2009-12-03 12:36 dhcp3
drwxr-xr-x  3 root root    4096 2009-12-03 12:35 dpkg
-rw-r--r--  1 root root       0 2009-12-03 12:35 environment
-rw-r--r--  1 root root      37 2009-12-03 12:33 fstab
-rw-r--r--  1 root root    2689 2009-01-04 16:15 gai.conf
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 groff
-rw-r--r--  1 root root     487 2009-12-03 12:37 group
-rw-------  1 root root     476 2009-12-03 12:35 group-
-rw-r-----  1 root shadow   406 2009-12-03 12:37 gshadow
-rw-------  1 root root     398 2009-12-03 12:35 gshadow-
-rw-r--r--  1 root root       9 2006-08-07 18:14 host.conf
-rw-r--r--  1 root root       7 2009-12-03 12:36 hostname
-rw-r--r--  1 root root      37 2009-12-03 12:36 hosts
-rw-r--r--  1 root root     579 2009-12-03 12:36 hosts.allow
-rw-r--r--  1 root root     878 2009-12-03 12:36 hosts.deny
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 init.d
-rw-r--r--  1 root root    1307 2009-12-03 12:36 inittab
-rw-r--r--  1 root root    1723 2009-01-14 11:19 inputrc
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 iproute2
-rw-r--r--  1 root root      28 2009-08-31 04:45 issue
-rw-r--r--  1 root root      21 2009-08-31 04:45 issue.net
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 keys
-rw-r--r--  1 root root    7335 2009-12-03 12:37 ld.so.cache
-rw-r--r--  1 root root      34 2009-12-03 12:34 ld.so.conf
drwxr-xr-x  2 root root    4096 2009-12-03 12:34 ld.so.conf.d
-rw-r--r--  1 root root     118 2009-12-03 12:35 localtime
-rw-r--r--  1 root root   10879 2008-11-22 20:16 login.defs
-rw-r--r--  1 root root     599 2008-10-08 16:53 logrotate.conf
drwxr-xr-x  2 root root    4096 2009-12-03 12:36 logrotate.d
drwxr-xr-x  2 root root    4096 2008-08-18 22:34 lsb-base
-rw-r--r--  1 root root    4630 2009-01-25 03:27 manpath.config
-rw-r--r--  1 root root     803 2008-10-13 06:06 mke2fs.conf
drwxr-xr-x  3 root root    4096 2009-12-03 12:35 modprobe.d
-rw-r--r--  1 root root     248 2009-12-03 12:35 modules
lrwxrwxrwx  1 root root      13 2010-01-01 15:27 motd -> /var/run/motd
-rw-r--r--  1 root root     286 2009-12-03 12:35 motd.tail
-rw-r--r--  1 root root     297 2010-01-01 16:36 mtab
-rw-r--r--  1 root root    7672 2008-08-26 17:31 nanorc
drwxr-xr-x  6 root root    4096 2009-12-03 12:36 network
-rw-r--r--  1 root root      60 2009-12-03 12:35 networks
lrwxrwxrwx  1 root root      28 2010-01-01 15:27 nologin -> /var/lib/initscripts/nologin
-rw-r--r--  1 root root     475 2006-08-28 17:33 nsswitch.conf
drwxr-xr-x  2 root root    4096 2009-12-03 12:33 opt
-rw-r--r--  1 root root     552 2009-03-17 23:58 pam.conf
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 pam.d
-rw-r--r--  1 root root     811 2009-12-03 12:37 passwd
-rw-------  1 root root     811 2009-12-03 12:37 passwd-
-rw-r--r--  1 root root     475 2006-10-28 14:42 profile
-rw-r--r--  1 root root    2626 2008-08-28 03:00 protocols
-rw-------  1 root root       0 2009-12-03 12:35 .pwd.lock
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rc0.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rc1.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rc2.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rc3.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rc4.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rc5.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rc6.d
-rwxr-xr-x  1 root root     306 2009-12-03 12:35 rc.local
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 rcS.d
-rw-r--r--  1 root root      55 2010-01-01 16:36 resolv.conf
-rwxr-xr-x  1 root root     268 2008-04-17 14:22 rmt
-rw-r--r--  1 root root     887 2008-08-28 03:00 rpc
-rw-r--r--  1 root root    2565 2009-02-08 04:00 rsyslog.conf
drwxr-xr-x  2 root root    4096 2009-02-08 04:13 rsyslog.d
-rw-r--r--  1 root root    1287 2008-11-22 20:16 securetty
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 security
-rw-r--r--  1 root root   18480 2008-08-28 03:00 services
-rw-r-----  1 root shadow   563 2009-12-03 12:37 shadow
-rw-------  1 root root     563 2009-12-03 12:37 shadow-
-rw-r--r--  1 root root     155 2009-12-03 12:35 shells
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 skel
drwxr-xr-x  2 root root    4096 2009-12-03 12:37 ssh
-rw-r--r--  1 root root    2275 2009-01-11 22:11 sysctl.conf
drwxr-xr-x  2 root root    4096 2009-01-11 22:11 sysctl.d
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 terminfo
-rw-r--r--  1 root root       8 2009-12-03 12:35 timezone
drwxr-xr-x  3 root root    4096 2008-04-29 05:39 udev
drwxr-xr-x  2 root root    4096 2009-12-03 12:35 vim
-rw-r--r--  1 root root    4221 2008-09-08 06:03 wgetrc
drwxr-xr-x  4 root root    4096 2009-12-03 12:37 X11

I cannot think of any reason why the alpha character ( which stands for b block c charc d directory etc etc), should have any effect on making the ext2ls work correctly!

I can only conclude that there is STILL something very flakey with U-boot, even the much improved patched version 3.4.27

regards

Patrick
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #50 on: January 01, 2010, 12:30:46 PM »

Hi superpet,

If I read your description correctly you said for the same file system when it read from normal linux machine the read out also partial failed. Am I correct? If I do then I think this is a problem in the rootfs tar you untarred to your newly created ext2 file system. it most have some sort of security setting prevent normal ls read the directory entries. I am not familiar the linux security setup so I can only guess. Other possibility is the newly created file system is not ext2. one way to work around this could be untarred the rootfs tar into a normal linux box's file system, run some command to turn off the magic security setting then re-copy it back to SD card.

I will do some research the Debian root fs you download to check. please post the URL you use to download to help verify later.
Logged

Good Luck Smiley

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #51 on: January 01, 2010, 04:10:13 PM »

hi pingtoo,

No  you mis-understand me.  Please re read my previous reply, and this reply, to clarify.

ALL  my problems are with u-boot and the rfs.

I have no problems reading /boot/uImage with the sdhc card mounted using a card reader on my linux m/c.

The directories /boot, /etc, and /dev have exactly the same owners.

Using ext2ls from u-boot,  /boot/ and /etc appear empty, but /dev returns a list of files

The only diff in owner and permissions is that the first digit of the permissions, (d,p,b,c etc) is null in the failing directories file contents and are used in all the files and directories in  /dev.

OF COURSE THE FILE SYSTEM IS EXT2!!!!!  I am using a single 8gb ext2 partition on my sdhc card.

If I move uImage from inside /boot and put it in the root (/uImage) then i can boot it using ext2load and run my deb system OK, from the sdhc card, including a fsck of the ext2fs on bootup!

All files list ok using linux pc. (see included listings in previous post).

Read the same problem from the other poster, I included a pointer.

cheers

Patrick
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #52 on: January 01, 2010, 10:51:51 PM »

superpat, your problem sounds similar to what I have experienced on my plug.  I am running the uBoot from the alpha-6 installer (3.4.16).  I'm also running an ext2fs on an SDcard here, and booting from the card.  What I discovered is that the uBoot is unable to read about one out of every ten files on the SDcard's file system.  You can use the ext2ls command to determine if a particular file is readable or not:  The file will show up as zero length when it should not be if uBoot cannot read it.

My workaround is to copy the currently bootable kernels (uImage files) to the root of the FS, and retain the old images until I can verify that the uBoot is happy with the new ones.  Then I boot directly from /uImage.  In the rare event that the uBoot can't load the image, I boot back to one of the old kernels temporarily, and then simply make a new copy of the "bad" image:

Code:
# mv /uImage /uImage.bad
# cp /uImage.bad /uImage

and try booting from the new kernel again, which almost always works.  The readability problem is consistent:  Once the uBoot can successfully load the uImage, it appears to consistently be able to do so.

I'm fairly sure the underlying problem is a bug in the ext2 code in the uBoot, one that I hoped had been corrected in one of the more recent loads, but which apparently has not been.  It may depend on the type of SDcard -- maybe some work better than others -- I don't have enough data points to know.  In any event, I view it as a nuisance item that only comes into play when upgrading kernels, and which may be worked-around by copying the "bad" uImage to another file.

One final comment:  If it is the /boot directory that is itself unreadable, you'll never be able to boot from any uImage therein.  I suspect you could create another directory, copy the contents from the old /boot to the new one, remove the old /boot, and then rename the new one to be /boot.

Good luck!
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #53 on: January 02, 2010, 07:37:20 AM »

hi pingtoo,

No  you mis-understand me.  Please re read my previous reply, and this reply, to clarify.

ALL  my problems are with u-boot and the rfs.

I have no problems reading /boot/uImage with the sdhc card mounted using a card reader on my linux m/c.

The directories /boot, /etc, and /dev have exactly the same owners.

Using ext2ls from u-boot,  /boot/ and /etc appear empty, but /dev returns a list of files

The only diff in owner and permissions is that the first digit of the permissions, (d,p,b,c etc) is null in the failing directories file contents and are used in all the files and directories in  /dev.

OF COURSE THE FILE SYSTEM IS EXT2!!!!!  I am using a single 8gb ext2 partition on my sdhc card.

If I move uImage from inside /boot and put it in the root (/uImage) then i can boot it using ext2load and run my deb system OK, from the sdhc card, including a fsck of the ext2fs on bootup!

All files list ok using linux pc. (see included listings in previous post).

Read the same problem from the other poster, I included a pointer.

cheers

Patrick
Thanks for clarification my question. I will give it a try to see if I can fix this. In the mean time if this is really trouble you, may I suggest you try to format your SD in to two partitions, one small partition in small size (less then 2GB) to hold your kernel/initrd and second partition use reminding part of SD to hold the rest of RFS. or keep kernel/initrd in / of your SD as workaround.

English is not my first language, some time I would misunderstand what people said, So I always want to confirm my understanding using my own expression to make sure there is no mistake. Because your post include the portion show everything seems be normal so I am not able to be sure where the problem really is. In your post you have describe the booting sequence will however you did not post your command used to format the SD card so I can not tell how it is done so I need to confirm with you. (You know there is many pro who make obvious mistake because those mundane thing right) Cheesy
Logged

Good Luck Smiley

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #54 on: January 02, 2010, 09:06:36 AM »

Hi superpet,

I need to see the output of the error condition. I search around internet (google) no one else report similar problem. I check the uboot code there is no clear indication of fix to specific of this problem.
Logged

Good Luck Smiley

fun
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #55 on: January 02, 2010, 09:27:05 AM »

mmc_block_read() uses ulong to specify address. I think it can't access >4GB area.
(see u-boot-3.4.27/board/mv_feroceon/USP/sdio/mmc.c)
Logged

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #56 on: January 04, 2010, 04:04:17 AM »

@pingtoo,

I am sorry for the delay in replying, I have had to visit relatives for the weekend.

I apologise that I was not clear in my English to you, I will try to keep it more straightforward in future.

Regarding your request for error printouts,   unforunately there are not any of much use.

U-Boot ether works OK  or returns no output when it fails.  Trying a ext2ls,  if it fails, just returns to  the uboot prompt

when trying to execute:-

set bootargs 'console=ttyS0,115200 ro root=/dev/mmcblk0p1 rootdelay=1'
mmcinit
ext2load mmc 0 0x800000 /boot/uImage

uboot reports  0 bytes read and returns to uboot prompt

The post from "restamp" just above in this thread, sums it up very well!

Thanks again to everyone who are working to make u-boot more solid!

regards

Patrick
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #57 on: January 04, 2010, 08:03:23 AM »

@superpat,

No problem at all, I just want to make clear communication.

So do you wish to further the debugging process? The reason I am asking is because I can not reproduce this problem, so any debug activity will heavily depend on you. This will mostly inconvenient you. As right now I presume your have workaround in place so you are not stuck.

If you wish to further pursue this I can produce a version of u-boot have debug code surrounding the ext2 code to understand where is the root of problem. However since right now everybody is back to normal work schedule I can only work at after hours it may take me a day or two to make the debug code. BTW I may have a way to produce the debug version that you can test without flush it to NAND every time, but I need to test that one first. Wink
Logged

Good Luck Smiley

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #58 on: January 04, 2010, 04:09:23 PM »

Hi pingtoo,

I will be very happy to test any debug versions or experiments you want me to try.

Just say what you want me to do, 

cheers

Patrick
Logged

pingtoo
Sr. Member
****

Karma: 15
Posts: 318


View Profile
« Reply #59 on: January 04, 2010, 08:01:07 PM »

Hi pingtoo,

I will be very happy to test any debug versions or experiments you want me to try.

Just say what you want me to do, 

cheers

Patrick
OK, here is a debug version of u-boot, I didn't do much other enable DEBUG symbol, this will at lease give us a begin to see how the code work in your environment. following is how you should load this test u-boot,
Code:
Marvell>>ext2load mmc 0 0x01600000 /ext2-debug-u-boot.bin

474076 bytes read
Marvell>> go 0x01600000
## Starting application at 0x01600000 ...
and this what should be showing.
Code:
Marvell>> ext2load mmc 0 0x01600000 /ext2-debug-u-boot.bin

474076 bytes read
Marvell>> go 0x01600000
## Starting application at 0x01600000 ...

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

U-Boot 1.1.4 (Jan  4 2010 - 21:45:00) Marvell version: 3.4.27

U-Boot code: 01600000 -> 0167FFF0  BSS: -> 016CFEE0

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 24M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (24M - 23M): 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>> version

U-Boot 1.1.4 (Jan  4 2010 - 21:45:00) Marvell version: 3.4.27 - pingtoo ext2 testing.01
Marvell>> mmcinit
SD found. Card desciption is:
Manufacturer:       0x27, OEM "PH"
Product name:       "SD02G", revision 2.0
Serial number:      2085621231
Manufacturing date: 10/2007
CRC:                0x00, b0 = 0
Marvell>> ext2ls mmc 0
 <2, 0, 204>
revision_level = 0x1, inode_size = 0x80
ext2fs read inode 1
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 0 blkoff 1
 <522, 128, 128>
ext2fs_read_block 00000204
 <1032, 0, 8>
ext2fs_read_block 00000204
 <1032, 8, 1>
iterate >.<
ext2fs read inode 1
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 0 blkoff 1
 <522, 128, 128>
<DIR>       1024 .
ext2fs_read_block 00000204
 <1032, 12, 8>
ext2fs_read_block 00000204
 <1032, 20, 2>
iterate >..<
ext2fs read inode 1
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 0 blkoff 1
 <522, 128, 128>
<DIR>       1024 ..
ext2fs_read_block 00000204
 <1032, 24, 8>
ext2fs_read_block 00000204
 <1032, 32, 10>
iterate >lost+found<
ext2fs read inode 10
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 1 blkoff 2
 <524, 256, 128>
<DIR>      12288 lost+found
ext2fs_read_block 00000204
 <1032, 44, 8>
ext2fs_read_block 00000204
 <1032, 52, 6>
iterate >uImage<
ext2fs read inode 11
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 1 blkoff 3
 <524, 384, 128>
         1142988 uImage
ext2fs_read_block 00000204
 <1032, 60, 8>
ext2fs_read_block 00000204
 <1032, 68, 10>
iterate >uInitramfs<
ext2fs read inode 12
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 1 blkoff 4
 <525, 0, 128>
         2980057 uInitramfs
ext2fs_read_block 00000204
 <1032, 80, 8>
ext2fs_read_block 00000204
 <1032, 88, 18>
iterate >testing-u-boot.bin<
ext2fs read inode 13
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 1 blkoff 5
 <525, 128, 128>
          474076 testing-u-boot.bin
ext2fs_read_block 00000204
 <1032, 108, 8>
ext2fs_read_block 00000204
 <1032, 116, 21>
iterate >ext2-debug-u-boot.bin<
ext2fs read inode 14
ext2fs read blockgroup
 <4, 0, 32>
ext2fs read inode blkno 1 blkoff 6
 <525, 256, 128>
          474076 ext2-debug-u-boot.bin
Marvell>>
You can replace the mmc to usb or over /tftp. If I remember correct you indicate it seems to be work most reliable when it is in / directory.

Please post the output of all commands you tested. Please note, there is no fixes included in this code, this just merely give me a way to understand what happen in your environment.

* ext2-debug-u-boot.bin (462.96 KB - downloaded 208 times.)
Logged

Good Luck Smiley

Pages: 1 2 3 [4] 5 6 7
Print
Jump to: