RE: EPICS nfs mount issues

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Ø  I set the jumpers on the MAXv correctly.. but it still doesn’t work.

 

Please send a photo of the jumpers.  It is easy to make a mistake with those.

 

I have attached a photo of a MAXv set to address 0x5000 in A16 address space. 

 

The jumpers are described starting on page 2-1 in this manual:

https://wiki.bnl.gov/nsls2controls/images/5/59/OMS_MAXv_manual_MAXvmana.pdf

 

On jumper block J12 the 3 jumpers on the left select the addressing mode.  The jumpers from left to right are A32, A24, or A16.  In the photo you will see that jumper A16 is installed on our board.

 

The 3 jumpers on the right of J12 select the IRQ in the range 0-7.  If a jumper is installed that bit is 0.  On our board the center jumper is installed, which means IRQ=5.

 

On jumper block J13 the six jumpers on the right select the Address Modifier.  These bits go from 0 to 5 from left to right.  On our board bits 1 and 4 have jumpers.  This selects Data Access, Supervisory Access, Short Access (A16).

 

The 8 jumpers on the left of J13 are labeled A24 through A31.  In A16 mode which we are both using only jumpers A28-A31 are used.  These select A16 addresses 0x0000 through 0xF000.  If a jumper is installed that bit is 0.  On our board jumps A29 and A31 are installed, so those bits are 0.  That means bits 0 and 2 are 1 which is address 0x5000.

 

This is the output when I run "dbior" at the vxWorks prompt, which shows that it is finding the card OK.

 

Driver: drvMAXv

    Oms MAXv motor card #0 @ 0xfbff5000, id: MAXv-8000 ver:1.49, s/n:000176, FPGA:B7:A7 BOOT:1.3 - Oregon Micro Systems

 

On our vxWorks system the A16 address space begins at CPU address 0xfbff0000.   So the board address is indeed A16 0x5000

 

Mark

 

 

 

 

From: whitetiger1123 <holyeongbaeg at gmail.com>
Sent: Thursday, November 24, 2022 10:52 PM
To: Mark Rivers <rivers at cars.uchicago.edu>
Subject: RE: EPICS nfs mount issues

 

Yes I edit the /etc/exports file on ubuntu

Like this -> /mnt/nfs_share 10.4.49.67(rw,sync)

10.4.49.67 is inet on ethernet. Do I have to change this ip to host inet?

 

 

 

I know you already answered my question, but it still doesn’t work and makes same error..

I set the jumpers on the MAXv correctly.. but it still doesn’t work.

But I’ll search about this again.

 

thanks

 

 

보낸 사람: Mark Rivers
보낸 날짜: 2022년 11월 25일 금요일 오후 1:41
받는 사람: whitetiger1123
참조: tech-talk at aps.anl.gov
제목: Re: EPICS nfs mount issues

 

Did you edit the /etc/exports file on Ubuntu to allow the vxWorks machine permission to do mount that file system?

 

I already answered you question about the MAXv errors. Are you sure you set the jumpers on the MAXv correctly?

 

Mark

 

 

Sent from my iPhone

 

On Nov 24, 2022, at 10:36 PM, whitetiger1123 via Tech-talk <tech-talk at aps.anl.gov> wrote:



 

 

We are mostly running VxWorks 6.9 now, and with that we have no problem NFS mounting file systems on Ubuntu.

 

I set nfs on ubuntu it works well on there.

But if I try to run EPICS IOC on vxWorks, my st.cmd file makes this error:

 

<../nfsCommands

hostAdd(“test”, “10.4.49.170”)

value=0=0x0

nfsMount(“test”, “/home/test/epics/synApps_6_1/motor-R7-1/modules/motorOms/iocs/omsIOC”)

value = -1 = 0xffffffff

 

I set hostAdd(“epics server(ubuntu) username”, “epics server(ubuntu) IP” and

nfsMount(“epics server(ubuntu) username”, “epics server(ubuntu) motorOMS folder”)

 

this is my nfsmount file script:

#Instructions for creating and using a real nfsCommands file

# in order to use nfs do the following:

# 1) Create hostAdd and nfsMount commands for each nfs server

# 2) In each st.cmd file add the following two commands BEFORE any load commands

#    ../nfs.cmd

#    cd "<iocname>

#

# The hostAdd command has the form:

# hostAdd("<host>","xxx.xxx.xxx.xxx")

#

# The vxWorks nfsMount command has the form:

# nfsMount("<host>")

#

# You can also mount subdirectories as follows:

# nfsMount("<host>", "/xxx/xxx/xxx", "/xxx")

#

# For example assume

#

# host is mercury with inet address 155.77.2.56

# You want to mount the directory (which is a file system of mercury)

# /home/mercury5/iocinfo

#    as

# /iocinfo

#

# The commands would be

#

# hostAdd("mercury","155.77.2.56")

# nfsMount("mercury","/home/mercury5/iocinfo","/iocinfo")

 

hostAdd("test","10.4.49.170")

nfsMount("test","/home/test/epics/synApps_6_1/motor-R7-1/modules/motorOms/iocs/omsIOC")

 

Is nfsMount(“test”,”/home/test/epics/…/omsIOC”) path wrong? I really don’t know how to set this path.. If you have any example, please tell me about this.

 

And I’d like to ask one more thing. The IOC appears to have started normally so it should work. But I have this problem:

iocInit

Starting iocInit

############################################################################

## EPICS R3.15.6

## EPICS Base built Oct  7 2022

############################################################################

WARNING: OS Clock time was read before being set.

Using 1990-01-02 00:00:00.000000 UTC

iocInit: Time provider has not yet synchronized.

Illegal field value PV: oms:m1 motor_init_record_com(): card does not exist!

Illegal field value PV: oms:m2 motor_init_record_com(): card does not exist!

Illegal field value PV: oms:m3 motor_init_record_com(): card does not exist!

Illegal field value PV: oms:m4 motor_init_record_com(): card does not exist!

Illegal field value PV: oms:m5 motor_init_record_com(): card does not exist!

Illegal field value PV: oms:m6 motor_init_record_com(): card does not exist!

Illegal field value PV: oms:m7 motor_init_record_com(): card does not exist!

Illegal field value PV: oms:m8 motor_init_record_com(): card does not exist!

What I want to ask is do I have to connect MAXv controller if I want to fix this error?

Currently, my connect HW layout is like this:

I guess this error is not connect MAXv controller(I don’t know well).. Is it right?

 

 

Thanks!

 

 

Attachment: MAXv_jumpers.jpg
Description: MAXv_jumpers.jpg