AMC 68VZ328 software manual Home directory/dimmpci/source

Page 40

/(home directory)/dimmpci/source

(rw)

Of course you will need to add the home directory. This will allow anyone read and write access to that portion of the file system. This is acceptable if on a private network, but highly undesir- able if the computer is on the internet. See the man pages for the exports file if the NFS share needs to be secure.

After adding that line to the exports file a restart is necessary for the NFS server process, if it was running in the first place, to load the changes made to the file.

For the next step, the IP address of the computer must be known. If it’s not known, in a console window type ifconfig and a screen similar to this will appear:

eth0 Link encap:Ethernet HWaddr 00:50:BA:48:3E:D6 inet addr:192.168.10.34 Bcast:192.168.10.255 Mask:255.255.255.0

UP BROADCAST RUNNING MTU:1500 Metric:1

RX packets:11509 errors:0 dropped:0 overruns:0 frame:0 TX packets:2342 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100

Interrupt:12 Base address:0x9400

In this case the IP address would be 192.168.10.34. Next mount the NFS share on the dimmPCI file system. Depending on whether the dimmPCI CPU module is using DHCP or a statically assigned IP address the following command will be placed in one of two configuration files. If a static IP is being used, edit the ‘/opt/fs/romdisk/etc/rc’ file. Conversely if DHCP is being used, this command will have to be placed in the ‘/opt/fs/romdisk/etc/dhcpcd.sh’ file. For a static IP add the following toward the end of the file, right before the ‘exit 0’ line. For a DHCP system add this line to the end of the dhcp command file.

/bin/mount -t nfs 192.168.10.34:/path/to/share /mnt

Of course the IP address will be different than the one in this example. Following the IP address put the same path as is in the ‘/opt/fs/romdisk/etc/exports’ file. Once finished a new image file may be created and programmed onto the dimmPCITM CPU module.

After rebooting the CPU module, there will be access to the files on the PC from the dimmPCI development board in the ‘/mnt’ directory. Now code can be recompiled on the PC and the binaries will be instantly available on the development board.

40

www.amctechcorp.com

Image 40
Contents DimmPCITM 68VZ328 Hardware / Software Manual Contact Information Copyright noticeDimmPCITM Software Development Kit NETdimm Developers Kit Quick Start Guide Etc/issue Page This page left intentionally blank Introduction Launching Linux at the embeddedPage What’s on the CD? System RequirementsThis page left intentionally blank Features UC68VZ328 Embedded MicrocontrollerCPU Module BackplaneGeneral Description CPU Module DescriptionBackplane Description Architecture CPU ArchitectureSystem Memory MCU CoreMemory Map Memory Memory MapLayout of the Flash and Flash Schematic Layout of the Flash Sdram Ethernet Controller Viewing the Ethernet MAC IDNETdimm Ethernet Schematic Digital I/O IOdimmDigital Output Schematic Analog Output Schematic Analog Input Schematic Digital to Analog Converter Schematic Watchdog RS-232Highlights Usage LCD Schematic LCD InterfaceDimmPCITM Signal Descriptions DimmPCITM signals for System SlotPCI Electrical Characteristics Maximum RatingsThis page left intentionally blank Installing the dimmPCI TM System InstallationBuilder Kit Before beginningConfiguring and compiling the µClinux kernel Creating a ROM image Customizing the filesystemAccessing your dimmPCI development board via the serial port Static IP Accessing the NetworkDynamic IP Accessing your dimmPCI development board via telnet Compiling your own source codeUsing NFS to streamline the development cycle Home directory/dimmpci/source Updating Applications on your dimmPCI module MethodThis page left intentionally blank Programming the uC68VZ328 LoaderOops Cd /opt/boottools/oops Oops -p /dev/ttyS0 -k kernel.bin Page Page This page left intentionally blank Appendix Sample CodeClose the file afterwards fclose filehandle Page Longwatchdogid #include unistd.h #include stdio.h int main void This page left intentionally blank Journalling Flash File System Umount /usr Sbin/mkjffs /dev/flash0 Page This page left intentionally blank Development Tool Chains Normal Usage of the PIC-COFFTool Chain Page This page left intentionally blank D1 Application Note IntroductionKernel and Filesystem Configuration Kernel and Filesystem Configuration Flow Chart YESAvailable Digital I/O Pins List of all available digital I/O pins Programming Structure Dimmio structure descriptionDigital I/O Functions Page Sample Programs In0 In1 In2 In3 In4 In5 In6 In7 Out0 Even ParityMknod io1 c 123 Page This page left intentionally blank D2 Application Note AbstractKernel Configuration RequirementsAgain, from the main menu under Network device support Kernel Configuration Flow Chart AtCommandPrompt Filesystem Configuration Cd /opt/filesystem name make clean Make Filesystem Configuration Flow Chart Modifications to ‘rc’ fileHost machine Configuration TestingPage This page left intentionally blank Using Multiple NETdimm Modules Application NoteSimple Server & Client Inetd based Server & ClientPage This page left intentionally blank Using Analog and Digital I/O with IOdimmCd /opt Cp -Rpdx newfs iodimmmfs ADC MAX1203 Available I/O Pins Category Channel Backplane System Backplane Header Slot PinFunctions Digital Inputs and Outputs+ Κ Iodimm/dio Samples/cardspecific/iodimm/dio Page This page left intentionally blank Using Oops Purpose & basic format of files for oopsUpload & Flash Upload & Run DownloadCommon oops program arguments Appendix This page left intentionally blank 104 DimmPCITM Software Development Kit Distribution Licensing, Copyrights & LiabilityPreamble 106 107 108 109 No Warranty Appendix How to Apply These Terms to Your New Programs111 112 113 This page left intentionally blank 114 References/ Suggested Reading