[meta-xilinx] How to develop?

[Rich Wilson]

On Sun, Apr 27, 2014 at 11:54 AM, Alan DuBoff <aland at softorchestra.com>wrote:

> On Sat, April 26, 2014 8:00 pm, Rich Wilson wrote:
> > How do I get my application to the SD card without a bunch of SD card
> > gymnastics (remove, mount, cp, umount,
> > reboot...) ?
>
> Create a bitbake recipe that will build it properly and populate the
> sysroot.
>

I'm sorry, I wasn't specific enough. When I edit the source code of my
application
on my development system, how do I get the resulting binary to the target
system?
On other projects I have used nfs, hence the next question.


>
> > How about nfs?
> > # mount 192.168.1.40:/ /mnt
> > mount: wrong fs type, ... you might need a /sbin/mount.<type> helper
> > program)
>
> You need to pass the proper arguments to mount. -t nfs will do that if you
> have the nfs support in your image. You also need the proper share on the
> host
> you're trying to mount.
>
>
-t nfs isn't needed. But the below shows the result of adding it:

root at zedboard-zynq7:~# mount -t nfs 192.168.1.40:/ /mnt
mount: wrong fs type, bad option, bad superblock on 192.168.1.40:/,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
root at zedboard-zynq7:~#

Nothing interesting in dmesg.

I think the kernel is set up:

root at zedboard-zynq7:/var/volatile/log# cat /proc/filesystems | grep nfs
nodev   nfs
root at zedboard-zynq7:/var/volatile/log#

Wireshark shows that there is no network activity caused by the
above attempt to do the nfs mount.

What is missing in my image? How do I get it there?

Rich


> --
> Cheers,
> Alan
>
>


-- 
Rich Wilson
richaw at gmail.com
425-337-7129 (land line)
425-374-4760 (Google)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20140427/3c825e26/attachment.html>