OK6410 starts automatically mounting the nfs file system

Publisher:温暖微风Latest update time:2018-10-11 Source: eefocusKeywords:OK6410 Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

①Start and stop the nfs service of the ubuntu server through commands:

Run from the command line:

      /etc/init.d/nfs restart

Use this command to stop the nfs service:

      /etc/init.d/nfs stop

Check whether the nfs server is enabled:  

      service nfs status

Restart the corresponding 2 services:      

      service portmap restart 

      service nfs restart

Check the firewall to see if the nfs port is blocked

      service iptables stop

      service iptables status

②Set permissions for the Ubuntu directory to be mounted:

sudo vi /etc/exports

Add to:

/home/book/workspace/ok6410_project/fs_ok6410_yaffs2 *(insecure,rw,async,no_root_squash)

sudo chown book:book fs_ok6410_yaffs2/ -R

chmod 755 /home/book/workspace/ok6410_project/fs_ok6410_yaffs2

Try mounting yourself:

mount -t nfs -o nolock,vers=2 192.168.48.104:/home/book/workspace/ok6410_project/fs_ok6410_yaffs2 /mnt

mount -t nfs -o nolock 192.168.48.104:/home/book/workspace/ok6410_project/fs_ok6410_yaffs2 /mnt

③Set the development board IP parameters:

  vi /etc/init.d/rcS Make the following changes at the end of the file to allow the kernel to automatically configure network parameters and open the network card connection after startup:

  ifconfig eth0 192.168.16.16

  ifconfig eth0 up

④Modify u-boot startup parameters:

default value:

bootargs=root=/dev/mtdblock2 rootfstype=yaffs2 init=/linuxrc console=ttySAC0,115200

set bootargs root=/dev/mtdblock2 rootfstype=yaffs2 init=/linuxrc console=ttySAC0,115200

After changing to NFS startup:

seten bootargs noinitrd root=/dev/nfs nfsroot=192.168.48.104:/home/book/workspace/ok6410_project/fs_ok6410_yaffs2 ip=192.168.48.100:192.168.48.104:192.168.48.255:255.255.255.0::eth0:off init=/linuxrc console=ttySAC0,115200

save

⑤Restart the development board:

reset

reboot


Keywords:OK6410 Reference address:OK6410 starts automatically mounting the nfs file system

Previous article:OK6410 nand flash block device driver
Next article:Writing your own bootloader for OK6410

Recommended ReadingLatest update time:2024-11-16 04:40

OK6410 burns bare metal program into nandflash
When I first started learning embedded systems, I started with bare metal programs. When I first started learning, I didn't know how to run bare metal programs on the development board. There are actually many ways on the Internet, but the ones I have tested are all based on UBOOT, using DNW or jlink and other tools to
[Microcontroller]
OK6410 burns bare metal program into nandflash
A brief analysis of Wei Dongshan's driver video based on ok6410--USB driver
Note: The mouse driver described in this article can only realize the button-like functions of the left and right mouse buttons and the scroll wheel. Pressing the left button will type "l", the right button will type "s", and the scroll wheel will type "enter". If you want to realize a normal mouse driver, refer to
[Microcontroller]
OK6410 USB device driver
usb.c source code: // Reference: drivers/hid/usbhid/usbmouse.c #include "linux/kernel.h" #include "linux/slab.h" #include "linux/module.h" #include "linux/init.h" #include "linux/usb/input.h" #include "linux/hid.h" #include "linux/input.h"  static struct input_dev *mk_dev; static int len; static char *buf; static dma_
[Microcontroller]
Develop ARM programs using only serial ports and network bare metal (OK6410 development board)
Recently, I want to learn about ARM development board. I want to develop bare metal programs according to the routine of single chip microcomputer. I searched on Baidu and found that most bare metal programs are developed with RVDS or ADS, and burned into Sdram with JLink or JTag for execution. Since I am used to us
[Microcontroller]
3.3.Use of Uboot
Unzip the uboot package to get the uboot project file uboot, enter uboot, open the Makefile file, and search for the type of your development board. Mine is OK6410 256. Then execute the configuration file: Then execute the following command to compile: Compiled screenshot:
[Microcontroller]
3.3.Use of Uboot
Feiling OK6410 timer accurately controls LED
Note on reference and copyright: The code provided by Feiling has some problems, and some key codes are not explained. After collecting various materials, I combined the corrections from netizens and my own understanding, and annotated some of the parts that I think are important. Of course, if the masters think it is
[Microcontroller]
Feiling OK6410 timer accurately controls LED
LCD operation based on OK6410
In S3C6410, the LCD display has been made very convenient to operate. From the floor schematic, we can see that all the LCD pins are connected to GPI and GPJ, so these two groups of GPIO are configured to the corresponding functions of LCD display. Several different domains are HSYNC (Horizontal Sync. Signal), VSYNC (
[Microcontroller]
LCD operation based on OK6410
Feiling OK6410 development board transplanted u-boot official latest version u-boot-2012.10.tar.bz2
Part 0 Preparatory knowledge 0.1 Key Parameters 0.1.1 Development Board Description OK6410 is a development board released by Feiling. There are currently two versions, OK6410-A and OK6410-B. I am currently using the former. The former has also been upgraded, so there are 128M ram and newer 256 memory versions. The na
[Microcontroller]
Latest Microcontroller Articles
  • Download from the Internet--ARM Getting Started Notes
    A brief introduction: From today on, the ARM notebook of the rookie is open, and it can be regarded as a place to store these notes. Why publish it? Maybe you are interested in it. In fact, the reason for these notes is ...
  • Learn ARM development(22)
    Turning off and on interrupts Interrupts are an efficient dialogue mechanism, but sometimes you don't want to interrupt the program while it is running. For example, when you are printing something, the program suddenly interrupts and another ...
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
  • Learn ARM development(15)
  • Learn ARM development(16)
  • Learn ARM development(17)
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号