[meta-xilinx] How to develop?

[Philip Balister]

On 04/27/2014 09:51 PM, Nathan Rossi wrote:
>> -----Original Message-----
>> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
>> bounces at yoctoproject.org] On Behalf Of Rich Wilson
>> Sent: Monday, April 28, 2014 7:23 AM
>> To: aland at softorchestra.com
>> Cc: meta-xilinx at yoctoproject.org
>> Subject: Re: [meta-xilinx] How to develop?
>>
>> 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.
>>
>>
> 
> There are many methods, just to list a few (including NFS).
> 
> * NFS
> * SCP (you will need openssh/dropbear) or SFTP
> * FTP
> * TCF (requires tcf-agent package) - this is the flow Xilinx SDK uses now, it is part of the Eclipse tools. It is quite powerful, have a look if you are interested (it even does the debugging without the need for gdb)

sshfs also works well.

Philip

> 
>>
>> 	> 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?
> 
> You are going to want to add nfs-utils to your image. Core-image-minimal leaves it out by default, just add something similar to below to your local.conf to get it in your rootfs:
> 
> CORE_IMAGE_EXTRA_INSTALL += "nfs-utils"
> 
> You will then have mount.nfs and the associated userspace daemon stuff for NFS. And nfs should then just work.
> 
> Regards,
> Nathan
> 
> 
>