Hi,
Today I started to boot my DVEVM from flash and hard disk.
I found the following error:--
----------------------------------------------------------------------------------------------
U-Boot 1.1.4 (Jan 14 2008 - 13:18:38)
U-Boot code: 81080000 -> 81097894 BSS: -> 810A0284
RAM Configuration:
Bank #0: 80000000 256 MB
MY AMD Flash: 16 MB
In: serial
Out: serial
Err: serial
ARM Clock :- 297MHz
DDR Clock :- 162MHz
I2C write: I/O error
I2C read: I/O error
I2C read: I/O error
I2C write: I/O error
Also I am getting error like:
MGC_HdrcServiceUsbStage0 487: V_BUS ERROR??? stopping host (80)
stop_host 386: Stopping due to error 1
MGC_LinuxIsr 1704: irq in error?
After some time I am getting :
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
I am unable to boot . Can anybody tell me what is going wrong . How I can solve
it.
THANKS
MANAS
[EMAIL PROTECTED] wrote: Send Davinci-linux-open-source mailing list
submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Davinci-linux-open-source digest..."
Today's Topics:
1. Mono on Montavista linux with DM355 (Bruno Hansen)
2. RE: problems on testing the shared file system (YangZhijun)
----------------------------------------------------------------------
Message: 1
Date: Tue, 29 Apr 2008 15:07:49 -0300
From: "Bruno Hansen"
Subject: Mono on Montavista linux with DM355
To: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
I'm trying to compile mono for montavista linux and I get the following
error:
arm_v5t_le-gcc ... [Flags for gcc]...
collect2: ld terminated with signal 11 [Segmentation fault]
/opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le/bin/../lib/gcc/armv5tl-montavista-linuxeabi/3.4.3/../../../../armv5tl-montavista-linuxeabi/bin/ld:
make[3]: *** [pedump] Error 1
I'm using the DVSDK (TMS320DM355)
Did anyone compile and use mono on Montavista linux with DM355? Or did
anyone have the same error?
Thanks in advance!
--
Bruno Hansen
msn: [EMAIL PROTECTED]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20080429/0b1533f1/attachment-0001.htm
------------------------------
Message: 2
Date: Wed, 30 Apr 2008 05:07:02 +0800
From: YangZhijun
Subject: RE: problems on testing the shared file system
To:
Message-ID:
Content-Type: text/plain; charset="gb2312"
Hi,
I've run the test again, now do the line wrap correctly
with minicom. But still it does not work. The following is the output
of the console during the boot.
[EMAIL PROTECTED]:~$ minicom
Welcome to minicom 2.2
OPTIONS: I18n
Compiled on Mar 7 2007, 15:10:03.
Port /dev/ttyS0
Press
CTRL-A Z for help on special keys
this is MT29F16G08FAA device
UBL: detected valid U-Boot magic number
UBL: booting to U-Boot
!
U-Boot 1.2.0 (Oct 17 2007 - 15:38:02)
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c,
Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit) Bad block table found at page
524224, version 0x01 Bad block table
found at page 524160, version 0x01
nand_read_bbt: Bad block at 0x09280000
nand_read_bbt: Bad block at 0x14380000
nand_read_bbt: Bad block at 0x2f860000
nand_read_bbt: Bad
!
block at 0x3e260000NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (
Micron NAND 1GiB 3,3V 8-bit)Bad block table found at page 524224, version
0x01Bad block table found at page 524160, version 0x01nand_read_bbt: Bad block
at 0x035e0000nand_read_bbt: Bad block at 0x08c20000nand_read_bbt: Bad block at
0x0a4a0000nand_read_bbt: Bad block at 0x0e6a0000nand_read_bbt: Bad block at
0x10840000nand_read_bbt: Bad block at 0x1d080000nand_read_bbt: Bad block at
0x1ea00000nand_read_bbt: Bad block at 0x263e0000nand_read_bbt: Bad block at
0x2c0e0000nand_read_bbt: Bad block at 0x30020000nand_read_bbt: Bad block at
0x30060000nand_read_bbt: Bad block at 0x300a0000nand_read_bbt: Bad block at
0x300e0000nand_read_bbt: Bad block at 0x30120000nand_read_bbt: Bad block at
0x30160000nand_read_bbt: Bad block at 0x301a0000nand_read_bbt: Bad block at
0x301e0000nand_read_bbt: Bad block at 0x30220000nand_read_bbt: Bad block at
0x30260000nand_read_bbt: Bad block at 0x302a0000nand_read_bbt: Bad block at
0x302e0000nand_read_bbt: Bad block at 0x30320000nand_read_bbt: Bad block
!
at 0x30360000nand_read_bbt: Bad block at 0x303a0000nand_read_bbt: Bad block at
0x303e0000nand_read_bbt: Bad block at 0x30420000nand_read_bbt: Bad block at
0x30460000nand_read_bbt: Bad block at 0x304a0000nand_read_bbt: Bad block at
0x304e0000nand_read_bbt: Bad block at 0x30520000nand_read_bbt: Bad block at
0x30560000nand_read_bbt: Bad block at 0x305a0000nand_read_bbt: Bad block at
0x305e0000nand_read_bbt: Bad block at 0x30620000nand_read_bbt: Bad block at
0x30660000nand_read_bbt: Bad block at 0x306a0000nand_read_bbt: Bad block at
0x306e0000nand_read_bbt: Bad block at 0x30720000nand_read_bbt: Bad block at
0x30760000nand_read_bbt: Bad block at 0x307a0000nand_read_bbt: Bad block at
0x307e0000nand_read_bbt: Bad block at 0x30820000nand_read_bbt: Bad block at
0x30860000nand_read_bbt: Bad block at 0x308a0000nand_read_bbt: Bad block at
0x308e0000nand_read_bbt: Bad block at 0x30920000nand_read_bbt: Bad block at
0x30960000nand_read_bbt: Bad block at 0x309a0000nand_read_bbt: Bad block
!
at 0x309e0000nand_read_bbt: Bad block at 0x30a20000nand_read_bbt: Bad
block at 0x30a60000nand_read_bbt: Bad block at 0x30aa0000nand_read_bbt: Bad
block at 0x30ae0000nand_read_bbt: Bad block at 0x30b20000nand_read_bbt: Bad
block at 0x30b60000nand_read_bbt: Bad block at 0x30ba0000nand_read_bbt: Bad
block at 0x30be0000nand_read_bbt: Bad block at 0x33ac00002048 MiBIn:
serialOut: serialErr: serialARM Clock :- 216MHzDDR Clock :- 171MHzHit any
key to stop autoboot: 0 DM355 EVM #
I then enter the environment variables, boot it but it does not work, and the
bdinfo show the board does not get an IP.
DM355 EVM # setenv nfshost 192.168.1.207DM355 EVM # setenv rootpath
/home/zyang1/workdir/filesysDM355 EVM # setenv bootargs console=ttyS0,115200n8
noinitrd rw ip=192.168.1.201:192.168.1.207:192.168.1.1:255.255.255.0:::off
root=/dev/nfs nfsroot=192.168.1.207:/home/zyang1/workdir/filesys,nolock
mem=116MDM355 EVM # bootLoading from NAND 1GiB 3,3V 8-bit, offset 0x400000
Image Name: Linux-2.6.10_mvl401 Image Type: ARM Linux Kernel Image
(uncompressed) Data Size: 1585240 Bytes = 1.5 MB Load Address: 80008000
Entry Point: 80008000DM355 EVM # bdinfoarch_number = 0x00000565env_t =
0x00000000boot_params = 0x80000100DRAM bank = 0x00000000-> start =
0x80000000-> size = 0x08000000ethaddr = 00:0E:99:02:C2:1Aip_addr =
0.0.0.0baudrate = 115200 bps
I
am not sure if it is because I made the wrong settings before and saved
them, so now the Uboot shows many bad blocks. Anyway to restore the normal
operation of the board? I am sorry for raising so many issues but it is really
frustrating.
Thank you.
Kind regards,
Michael
Subject: RE: problems on testing the shared file system
Date: Tue, 29 Apr 2008 08:54:10 +0100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [email protected]
Can you post the output of the console during the boot
- it is impossible to diagnose the issue with what you are showing. I need to
see all the diagnostic stuff not just the u-boot header
output.
I would not put 'line wraps' into boot arguments - how
do you know they are interpreted correctly (or at all)?
I am not convinced setting 'nfshost' and 'rootpath'
actually does anything - perhaps somebody else who is more into the inner
workings of u-boot can confirm this. At most it may affect the files that
u-boot
would load - I fail to see how the kernel ever knows the value of these
variables.
I need to see the kernel booting to confirm the boot
arguments it sees and at what point it is failing.
There is no point doing a 'mkdir /dev/nfs' - this is a
'fake' device (not a directory) that the kernel understands to perform a
'root filesystem over NFS' operation (it doesn't actually exist under /dev). In
fact given your target isn't booting where are you typing this in?
For your reference, I tried booting my DM355 with the
following options (lines are wrapped by minicom)...
DM355 EVM # setenv bootargs 'mem=116M
console=ttyS0,115200n8 noinitrd root=/dev/
nfs rw
nfsroot=172.18.0.13:/tftpboot/remote_fs/davinci_dm355
ip=172.18.1.222:172
.18.1.49:172.18.0.254:255.255.0.0:::off'
DM355 EVM #
bootd
The interesting parts of the kernel
booting....
Starting kernel ...
Uncompressing
Linux.............................................................
Linux
version 2.6.10_mvl401 ([EMAIL PROTECTED]) (gcc
version 3.4.3 (Mo
ntaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Tue Mar 11
13:20:15 GMT 2008
CPU: ARM926EJ-Sid(wb) [41069265] revision 5
(ARMv5TEJ)
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes,
associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes,
associativity 4, 32 byte lines, 64 sets
Machine: DaVinci DM355 EVM
Memory
policy: ECC disabled, Data cache writeback
DM0350
Built 1
zonelists
Kernel command line: mem=116M console=ttyS0,115200n8 noinitrd
root=/dev/nfs rw n
fsroot=172.18.0.13:/tftpboot/remote_fs/davinci_dm355
ip=172.18.1.222:172.18.1.49
:172.18.0.254:255.255.0.0:::off
This confirms that the kernel has 'seen' the boot
arguments I specified.
Then later....
eth0: link down
IP-Config:
Complete:
device=eth0, addr=172.18.1.222,
mask=255.255.0.0, gw=172.18.0.254,
host=172.18.1.222, domain=, nis-domain=(none),
bootserver=172.18.1.49, rootserver=172.18.0.13, rootpath=
Looking up port of
RPC 100003/2 on 172.18.0.13
Looking up port of RPC 100005/1 on
172.18.0.13
VFS: Mounted root (nfs filesystem).
Freeing init memory:
164K
eth0: link up, 100Mbps, half-duplex, lpa 0x40A1
This confirms that the
interface has taken the values specified in the boot line for its IP address,
netmask & gateway. The 'rootserver' value has been taken from the 'nfsroot'
parameter.
The message to look for is the VFS:
Mounted root(nfs filesystem). This shows that the NFS server has allowed the
remote filesystem to be mounted.... If it says anything else then it isn't
working.
You should then get the line
INIT: version 2.85 booting
This is the first program to
run and is loaded from the root filesystem - which proves it is working
otherwise it would not be able to output anything..
Regards
Phil Q
Phil Quiney, Senior Software
Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T:
+44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of YangZhijun
Sent: 28 April 2008 21:27
To:
[email protected]
Subject: RE: problems
on testing the shared file system
Thank you Phil and Chris,
I followed your
suggestions to do the test. First I changed INTERFACES="eth1" in
/etc/default/dhcp3-server
Then, I linked
the ethernet cable from my board to LAN 1 port on router box,
and RS232
cable with my laptop. Before power up the board I tested the
local NFS as
the first step
mkdir /mnt/nfsmount -t nfs 192.168.1.207:/home/zyang1/workdir/filesys /mnt/nfs
I can see the subdirs and files
in the originally empty /mnt/nfs subdir. It seems the
NFS is locally
working
I then power up the board and try the second
step
After break into the board command line EVM #, I
entered,
DM355 EVM # setenv nfshost
192.168.1.207 DM355 EVM # setenv rootpath
/home/zyang1/workdir/filesys DM355 EVM # setenv bootargs
console=ttyS0,115200n8
noinitrd rw ip=192.168.1.199:192.168.1\.207:192.168.1.1:255.255.255.0:::off
root=/dev/nfs
nfsroot=192.168.1.207:/home/zyang1/workdir\/filesys,nolock
mem=116M
Here I try to set a static IP address 192.168.1.199 to
the board. I use two line wraps at the end of two lines and the next character
starts at the beginning of the next line.
I then typed bdinfo to check,
and find,
DM355 EVM # bdinfo
arch_number = 0x00000565 env_t =
0x00000000 boot_params = 0x80000100 DRAM
bank = 0x00000000 -> start = 0x80000000
->
size = 0x08000000 ethaddr = 00:0E:99:02:C2:1A
ip_addr = 0.0.0.0 baudrate = 115200
bps
So the board does not get an IP address as expected. I
boot it with boot command, get,
DM355 EVM # boot Loading from NAND
1GiB 3,3V 8-bit, offset 0x400000 Image Name:
Linux-2.6.10_mvl401 Image Type: ARM Linux
Kernel Image (uncompressed) Data Size: 1585240
Bytes = 1.5 MB Load Address: 80008000 Entry
Point: 80008000
Same as before. Then I find that /dev
does not have a subdir of nfs, so I created one, and do
mount -t nfs 192.168.1.207:/home/zyang1/workdir/filesys /dev/nfs
Now the /dev/nfs has the shared subdir and files.
I repeated the whole process but still got the same result. Any more
suggestions?
Thanks.
Michael
Subject: RE: problems on testing the shared file system
Date: Mon, 28 Apr
2008 08:56:38 +0100
From: [EMAIL PROTECTED]
To:
[EMAIL PROTECTED]; [email protected]
Hi,
your INTERFACES=eth0 should be
INTERFACES=eth1
The laptop has associated with the router via
eth1, hence the IP address of eth1 is in the range you are trying to set up
DHCP for. Your eth0 interface has no IP address.
You will need to plug the DM355 into the router
and not eth0. If you want to use eth0 for the DM355 you will need a switch,
using cross over cables can cause problems with the link coming up at all.
Then you will have to set the address on eth0 manually.
(Mmm - just a thought - if you did plug the DM355
into the router, won't it get an IP address from there.)
I would try to fix this in 2
stages...
First: test your NFS server by mounting the
exported filesystem locally....
As root (changing IP address to suit yours) - note
your IP address is NOT 77.97.207.254 (I assume this is the public IP address
of your router - I am not sure why you thought we neded to know this). It
needs to be the IP address of one of the interfaces on your laptop,
preferably
the eth1 as this seems to be your LAN address.
mkdir /mnt/nfs
mount -t nfs 172.18.1.49:/share/path
/mnt/nfs
This must work before it will ever work to a
remote board. You should then be able to see files under /mnt/nfs, the usual
'bin boot dev etc home...'
Second: On the DM355 end, try setting the
ip address statically, instead of ip=dhcp in the 'bootargs' variable
something like...
ip=::::::
Example:
ip=172.18.1.222:172.18.1.49:172.18.0.254:255.255.0.0:::off
This will force the IP address so you won't need
DHCP at all. You need to turn off the 'autoconf' variable - hence the final
'off'. If you don't it will still try to DHCP. The hostname & device
sections are not required but must be specified (as NULL, hence the
':::').
Then try booting the board...post the console
output if it fails.
Regards
Phil Q
Phil Quiney, Senior Software
Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T:
+44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of YangZhijun
Sent: 27 April 2008 22:28
To:
[email protected]
Subject: problems on
testing the shared file system
Hi Folks,
I still have some problems on testing my shared
file system in my laptop with the DVEVM355 board. I think Spectrum's getting
started guide for DM355 DVEVM is insufficient for a newbie to get start,
especially in a different linux distribution like my case of Ubuntu. Now I
list all the procedure I used from the very start, and hope you can
help.
I first installed NSF in my laptop as follows,
sudo
apt-get install nfs-kernel-server nfs-common portmap
Then I followed
the getting started guide 4.3.4 to export a shared file system for target
access.
After installing NFS, and before I tried to set up DHCP server
in my laptop, I use
/sbin/ifconfig,
--------------------------------------------------------------------------------------
[EMAIL PROTECTED]:~$
/sbin/ifconfig
eth0 Link encap:Ethernet
HWaddr 00:1C:23:3C:75:E4
UP BROADCAST!
MULTICAST MTU:1500
Metric:1
RX
packets:0 errors:0 dropped:0 overruns:0
frame:0
TX packets:0
errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0
b) TX bytes:0 (0.0
b)
Interrupt:18
eth1 Link encap:Ethernet HWaddr
00:1F:3C:13:88:D6
inet
addr:192.168.1.207 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::21f:3cff:fe13:88d6/64
Scope:Link
UP
BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
&!
nbsp; RX packets:53423
errors:26 dropped:401 overruns:0
frame:0
TX
packets:39067 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:49489243
(47.1 MiB) TX bytes:5500038 (5.2
MiB)
Interrupt:17
Base address:0x8000 Memory:efdff000-efdfffff
eth0:avah Link
encap:Ethernet HWaddr 00:1C:23:3C:75:E4
inet
addr:169.254.7.95 Bcast:169.254.255.255
Mask:255.255.0.0
UP
BROADCAST MULTICAST MTU:1500
Metric:1
Interrupt:18
lo Link
encap:Local Loopback
!
; inet addr:127.0.0.1
Mask:255.0.0.0
inet6
addr: ::1/128
Scope:Host
UP
LOOPBACK RUNNING MTU:16436
Metric:1
RX
packets:93 errors:0 dropped:0 overruns:0
frame:0
TX
packets:93 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:7156 (6.9
KiB) TX bytes:7156 (6.9
KiB)
-----------------------------------------------------------------------------------------------
I
can see that eth0 is the interface for network card and eth1 my wireless. I
then use,
sudo apt-get install dhcp3-server
I get the following lines,
---------------------------!
--------------------------
[EMAIL PROTECTED]:~$ sudo apt-get install dhc
p3-server
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed
dhcp3-server
0 upgraded, 1 newly installed, 0 to remove and 196 not upgraded.
Need to get 302kB of archives.
After unpacking 856kB of additional disk space will be used.
Get: 1 http://gb.archive.ubuntu.com feisty/main dhcp3-server 3.0.4-12ubuntu4
[302kB]
Fetched 302kB in 8s (37.2kB/s) !
=== message truncated ===
---------------------------------
Meet people who discuss and share your passions. Join them now._______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
