Send Davinci-linux-open-source mailing list submissions to
davinci-linux-open-source@linux.davincidsp.com
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. RE: Davinci-linux-open-source Digest, Vol 25, Issue 57
(Jinu Joy Thomas)
2. Re: Problem booting via NFS (Robert W. Kuhn)
3. Re: TI is releasing Gstreamer for DaVinci DM6446 to open
source (Dirk Behme)
4. booting linux AND accessing DSP (Robert W. Kuhn)
5. Re: Problem booting via NFS (Caglar Akyuz)
6. Re: Problem booting via NFS (Caglar Akyuz)
7. Re: Problem booting via NFS (Robert W. Kuhn)
----------------------------------------------------------------------
Message: 1
Date: Fri, 25 Jan 2008 15:02:56 +0530
From: "Jinu Joy Thomas" <[EMAIL PROTECTED]>
Subject: RE: Davinci-linux-open-source Digest, Vol 25, Issue 57
To: <davinci-linux-open-source@linux.davincidsp.com>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hi Robert,
The observation is that the kernel is not stopping but the UART
is not able to send the prints (because it stopped) it is mainly because
of an error in the tty settings of your bootargs as Niko has mentioned.
Regards,
JINU JOY THOMAS
Partner,
Ittiam Systems Pvt Ltd
(M) 9886112290
Message: 3
Date: Fri, 25 Jan 2008 09:19:00 +0100
From: "Robert W. Kuhn" <[EMAIL PROTECTED]>
Subject: Problem booting via NFS
To: davinci-linux-open-source@linux.davincidsp.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hello,
I try to boot my davinci-board via nfs (I followed the instructions from
c:\mvcyg4.0\opt\montavista\pro\documentation\docs\quickstart\cross-devel
opment\html\index.html)
But the kernel doies not boot:
TFTP from server 172.16.0.1; our IP address is 172.16.0.2
Filename 'uImage-ti-davinci_evm'.
Load address: 0x80700000
Loading:
#################################################################
#################################################################
#################################################################
#################################################################
#
done
Bytes transferred = 1334744 (145dd8 hex)
DaVinci EVM # bootm
## Booting image at 80700000 ...
Image Name: Linux-2.6.10_mvl401-davinci_evm
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1334680 Bytes = 1.3 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing
Linu..............................................................
.......................... done, booting the
And now nothing happens. The evm stops.
What is the problem. The S3-switches are 1011 (from S0 to S3).
Thank you for your help!
Robert
------------------------------
Message: 4
Date: Fri, 25 Jan 2008 09:27:12 +0100
From: "Schoenemann, Nikolaus" <[EMAIL PROTECTED]>
Subject: RE: Problem booting via NFS
To: "Robert W. Kuhn" <[EMAIL PROTECTED]>,
<davinci-linux-open-source@linux.davincidsp.com>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Robert,
The switches are ok. Could you please post the exact bootargs you're
using. When the boot sequence stops, it's mostly a typing error in the
bootargs.
Cheers,
Niko
******************
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]
**********************************************************************
------------------------------
Message: 2
Date: Fri, 25 Jan 2008 11:10:08 +0100
From: "Robert W. Kuhn" <[EMAIL PROTECTED]>
Subject: Re: Problem booting via NFS
To: davinci-linux-open-source@linux.davincidsp.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Am Fri, 25 Jan 2008 10:28:10 +0100 schrieb Robert W. Kuhn:
And wehre could be the problem?
Okay, I had tho change my dhcpd.conf. Now it looks like that:
# dhcpd.conf
#
deny unknown-clients;
ddns-update-style none;
allow bootp;
lease-file-name "/var/spool/dhcp/dhcpd.leases";
subnet 172.16.0.0 netmask 255.255.0.0 {
default-lease-time 1209600; # two weeks
max-lease-time 31557600; # one year
# option routers i.j.k.l;
group {
host dvevm.local {
hardware ethernet 00:0e:99:02:5c:3e;
fixed-address 172.16.0.2;
# filename "<kernel-image>"; # Relative to TFTP root
# MVL installation image root
option root-path
"/opt/montavista/pro/devkit/arm/v5t_le/target";
}
}
}
Now I'm getting it is booting:
IP-Config: Got DHCP answer from 172.16.0.1, my address is 172.16.0.2
IP-Config: Complete:
device=eth0, addr=172.16.0.2, mask=255.255.0.0, gw=255.255.255.255,
host=172.16.0.2, domain=, nis-domain=(none),
bootserver=172.16.0.1, rootserver=172.16.0.1, rootpath=/opt/montavista/pro/
devkit/arm/v5t_le/target
Looking up port of RPC 100003/2 on 172.16.0.1
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 172.16.0.1
Root-NFS: Unable to get mountd port number from server, using default
mount: server 172.16.0.1 not responding, timed out
Root-NFS: Server returned error -5 while mounting /opt/montavista/pro/devkit/arm
/v5t_le/target
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Here it stops
My Env:
DaVinci EVM # printenv
bootdelay=3
baudrate=115200
ipaddr=172.16.0.2
netmask=255.255.0.0
bootcmd=dhcp;bootm
serverip=172.16.0.1
bootfile=/tftpboot/uImage-ti-davinci_evm
nfshost=172.16.0.1
bootargs=console=ttyS0,115200n8 noinitrd ip=dhcp root=/dev/nfs nfsroot=172.16.0.
1:/opt/montavista/pro/devkit/arm/v5t_le/target mem=120m
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0e:99:02:5c:3e
videostd=pal
Environment size: 381/131068 bytes
Thanks for any help!
Robert
------------------------------
Message: 3
Date: Fri, 25 Jan 2008 11:40:37 +0100
From: Dirk Behme <[EMAIL PROTECTED]>
Subject: Re: TI is releasing Gstreamer for DaVinci DM6446 to open
source
To: davinci-linux-open-source@linux.davincidsp.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Jeff, Brian wrote:
The package was built for the latest Montavista kernel on the DM6446
DVEVM. Some additional work may be needed to port this to the latest
community open source Linux kernel for DaVinci.
While trying to build with non-MV toolchain and open source Linux
kernel, I progressed until gstreamer.
There, linking of libgstreamer-0.10.so.0.10.0 fails cause it trys to
link with stuff from /opt/gnome/lib:
arm-linux-gcc -shared .... -L/opt/gnome/lib -lpthread
/opt/gnome/lib/libgobject-2.0.so /opt/gnome/lib/libgthread-2.0.so
/opt/gnome/lib/libgmodule-2.0.so -ldl /opt/gnome/lib/libglib-2.0.so
... -o .libs/libgstreamer-0.10.so.0.10.0
/opt/gnome/lib/libgobject-2.0.so: could not read symbols: File in
wrong format
which is of course the x86 stuff. LD_LIBRARY_PATH links to filesys, so
this can't be the problem. Does MV toolchain come with ARM version of
libgobject-2.0.so and friends? If not, any idea whats wrong then?
Regards
Dirk
Btw: configure of gstreamer failed with
checking for XML... yes
configure: error: Could not link libxml2 test program. Check if you
have the necessary dependencies.
I worked around by disabling the exit in configure. Any better way to
come around this?
------------------------------
Message: 4
Date: Fri, 25 Jan 2008 11:50:00 +0100
From: "Robert W. Kuhn" <[EMAIL PROTECTED]>
Subject: booting linux AND accessing DSP
To: davinci-linux-open-source@linux.davincidsp.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hello,
I have read
http://c6000.spectrumdigital.com/davincievm/revd/files/DaVinciEVM_FAQ.html#JTAG_Emulation_Setup
but it is possible to boot linux on the arm side and to connect to the
DSP with CCS and JTAG?
Or do I have to write my dsp-program and flash the dsp always before
booting into linux again?
Bye - Robert
------------------------------
Message: 5
Date: Fri, 25 Jan 2008 12:56:27 +0200
From: Caglar Akyuz <[EMAIL PROTECTED]>
Subject: Re: Problem booting via NFS
To: "Robert W. Kuhn" <[EMAIL PROTECTED]>
Cc: davinci-linux-open-source@linux.davincidsp.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
Robert W. Kuhn wrote:
Am Fri, 25 Jan 2008 09:27:12 +0100 schrieb Schoenemann, Nikolaus:
The switches are ok. Could you please post the exact bootargs you're
using. When the boot sequence stops, it's mostly a typing error in the
bootargs.
It works with this settings:
[...]
Looking up port of RPC 100003/2 on 172.16.0.1
Looking up port of RPC 100005/1 on 172.16.0.1
VFS: Mounted root (nfs filesystem).
Please note that you're mounting your nfs successfully here. On your
next post, after changing dhcp settings, you'll see that it no longer
mounts root file system. So, you should revert back to these settings.
Freeing init memory: 140K
Warning: unable to open an initial console.
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
(with a long delay after "Warning: unable to open an initial console.")
The last line in /var/log/nfsd.log are:
nfsd[252] 01/25/108 10:24 auth_clnt.c 340 : Unable to seteuid(0):
Invalid argument
but I believe this is a cygwin-problem. When I boot from hda1
I am able to mount /opt/montavista/pro/devkit/arm/v5t_le/target
The problem here is that you are not changing the owner ship of the nfs
file system correctly. I mean you are not performing all the
instructions/steps on the dvevm manual for nfs mount. For example you
are not cloning montavista filesystem. You may damage your only copy in
this case. Moreover you should change the owner of this
"/opt/montavista/pro/devkit/arm/v5t_le/target" folder in case you
haven't already. Finally did you enter "no_root_squash" in your
/etc/exports file?
I think you are very close to running your NFS server successfully, just
the folder owner is not correct.
Regards,
Caglar
------------------------------
Message: 6
Date: Fri, 25 Jan 2008 12:57:09 +0200
From: Caglar Akyuz <[EMAIL PROTECTED]>
Subject: Re: Problem booting via NFS
To: "Robert W. Kuhn" <[EMAIL PROTECTED]>
Cc: davinci-linux-open-source@linux.davincidsp.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
Robert W. Kuhn wrote:
Am Fri, 25 Jan 2008 10:28:10 +0100 schrieb Robert W. Kuhn:
And wehre could be the problem?
[...]
I think things are worse now.
Looking up port of RPC 100003/2 on 172.16.0.1
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 172.16.0.1
Root-NFS: Unable to get mountd port number from server, using default
mount: server 172.16.0.1 not responding, timed out
Root-NFS: Server returned error -5 while mounting
/opt/montavista/pro/devkit/arm
/v5t_le/target
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Your board is now unable to mount NFS server, however, it was mounting
it in your previous post. Moreover your portmap settings are not letting
your board to use NFS on your host machine.
I think you should revert your recent changes. Please look into my
previous post for my reasoning.
Regards,
Caglar
------------------------------
Message: 7
Date: Fri, 25 Jan 2008 12:22:44 +0100
From: "Robert W. Kuhn" <[EMAIL PROTECTED]>
Subject: Re: Problem booting via NFS
To: davinci-linux-open-source@linux.davincidsp.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Am Fri, 25 Jan 2008 12:56:27 +0200 schrieb Caglar Akyuz:
Looking up port of RPC 100003/2 on 172.16.0.1
Looking up port of RPC 100005/1 on 172.16.0.1
VFS: Mounted root (nfs filesystem).
Please note that you're mounting your nfs successfully here. On your
next post, after changing dhcp settings, you'll see that it no longer
mounts root file system. So, you should revert back to these settings.
I reverted my changes. Thanks for the hint! Not it looks again like this
IP-Config: Complete:
device=eth0, addr=172.16.0.2, mask=255.255.0.0, gw=255.255.255.255,
host=172.16.0.2, domain=, nis-domain=(none),
bootserver=172.16.0.1, rootserver=172.16.0.1,
rootpath=/opt/montavista/pro/
devkit/arm/v5t_le/target
Looking up port of RPC 100003/2 on 172.16.0.1
Looking up port of RPC 100005/1 on 172.16.0.1
VFS: Mounted root (nfs filesystem).
Freeing init memory: 140K
Warning: unable to open an initial console.
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
The last line in /var/log/nfsd.log are:
nfsd[252] 01/25/108 10:24 auth_clnt.c 340 : Unable to seteuid(0):
Invalid argument
but I believe this is a cygwin-problem. When I boot from hda1
I am able to mount /opt/montavista/pro/devkit/arm/v5t_le/target
The problem here is that you are not changing the owner ship of the nfs
file system correctly. I mean you are not performing all the
instructions/steps on the dvevm manual for nfs mount.
Do you mean the DVEVM Getting Started Guide (SPRUE66C)?
For example you
are not cloning montavista filesystem. You may damage your only copy in
this case. Moreover you should change the owner of this
"/opt/montavista/pro/devkit/arm/v5t_le/target" folder in case you
haven't already. Finally did you enter "no_root_squash" in your
/etc/exports file?
the ownership:
[EMAIL PROTECTED] /opt/montavista/pro/devkit/arm/v5t_le
$ ls -ld target
drwxr-xr-x+ 20 akuhn Kein 0 Jan 25 10:04 target
the /etc/exports:
/opt/montavista/pro/devkit/arm/v5t_le/images/myimage.img
(rw,no_root_squash,no_a
/opt/montavista/pro/devkit/arm/v5t_le/target (rw,no_root_squash,no_all_squash)
Thanks and bye!
Robert
------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
End of Davinci-linux-open-source Digest, Vol 25, Issue 58
*********************************************************
