MicroIOC is not MicroIOC. There are multiple versions with different hardware and components. In 2013 a new mainboard was introduced to the microioc line. List of all available microIOCs.

MicroIOC serial box

With lots of serial interfaces. There are two different versions of this one.

Pre-2013: Intel Celeron 400 Mhz, 256MB Ram, Two onboard pc104 cards (with eight ports each) handled by kernel (builtin) 8250. Requires kernel with parameters. CONFIG_SERIAL_8250_NR_UARTS must be at least 20 (two onboard, two reserved by pc104 bus, two times eight for the extra cards). Default is to low, we compile our Kernel with 256. The number of automaticly created devices is controled by CONFIG_SERIAL_8250_RUNTIME_UARTS. Default is four. Additional devices are created using kernel cmdline parameter 8250.nr_uarts=20 . The additional devices need to be initialized using setserial.

Starting 2013: PCI Id 13fe:3618 is advantech icom PCM-3618i pc-104 board. PCI Id 13fe:f618 is a slave id of the same board. The board provides 8 serial ports. They can be configured to rs232 or rs485 via onboard jumpers. .... With a advantech ? card. http://support.advantech.com.tw/support/DownloadSRDetail.aspx?SR_ID=1-1W8FZ5&Doc_Source=Download

starting kernel 3.16 the driver is in the kernel http://lxr.free-electrons.com/ident?v=3.16;i=PCI_DEVICE_ID_ADVANTECH_PCI3618 (and the adv950 won't compile any more). Higher baud rates might not work.

PCI Id 16da:0011 is an ines GPIB-PCI-104 pc-104 board. It provides a gpib interface. Driver support via http://linux-gpib.sourceforge.net

PCI Id 13a8:0154 is a exar XR17C154 chip used in connecttech cti_serial boards. Provides four port rs 485.

MicroIOC M-Box

Motion controler box. Has an internal Ethernet connection to a ip based motion controller box. Motion controlers IP is staticly configured to In addition the box holds a connecttech serial card with rs-485 interfaces, special kernel modul and utilities. ftp://ftp.connecttech.com/pub/support/cti_serial_113-2.6.38.tgz. The kernel module requires a sleep after loading.

2013-06: with an intel atom D525, realtek ethernet, 4GB Ram and an xport management modul. Mainboard is a NANO-PV-D525

Troubleshooting Serial Interfaces M-Box

Nearly any kernel has a builtin serial driver 8250. This driver also feals responsible for the serial interfaces of the connecttech serial add on card. The kernel must be limited to the first five serial interfaces using a kernel boot parameter "8250.nr_uarts=5". Kernel boot paramters can be checked in a running system by cat /proc/cmdline. Check that /dev only contains tttyS0 to ttyS4 and ttyCTI*.

The default configuration for Serial Interfaces M-Boxes should use microioc-mbox, for example:

asl730$ cd /common/tftp/csco/pxe/pxelinux.cfg
asl733$ ls -l | grep kueci01
lrwxrwxrwx 1 root     root    7 Mar  6  2015 8CB58030 -> kueci01
lrwxrwxrwx 1 hechler  bel    13 Feb 17 10:10 kueci01 -> microioc-mbox

This file contains the correct "8250.nr_uarts=5" configuration.

BIOS update

before using any nano-pc based microioc with 64bit they must get a bios update, otherwise system is very slow. Required Bios is AR15 and is attached. After a bios update all settings are reset to defaults.

As of 2016-03 there is a bios version AR17, but we will consitently run all microioc on AR15 until there is time to flash them all at once. Until then, new microioc will be downgraded to AR15 version.

BIOS settings

Load optimized defaults (f3)

Advanced -> Serial Port Console Redirections -> COM4 -> Console Redirection Enabeld

Boot -> Quiet Boot -> Disabled

Boot -> Launch PXE OpROM -> enabled

Save and exit

MicroIOC Gpib

Extra Card with gpib interfaces. http://sourceforge.net/projects/linux-gpib/files/linux-gpib%20for%202.6.x%20kernels/3.2.17/linux-gpib-3.2.17.tar.gz/download. The cosylab version has modifications

Xport Management (for remote reset)

MicroIOC after 2013 come with an Xport management modul. The default DNS for this port is HOSTNAMEi64. It allows remote access to the serial interface and provides remote reset. Factory default account admin/PASS.

console. telnet into device, select microIOC. (Note the itx board com4 (ttyS3) is connected to the xport)

reset. telnet into device. exit to CLI. enable. cpm. set RESET 1. (wait 30 seconds). set RESET 0. exit.

Initial Configuration (incomplete notes):
  • cli->configurationj: set login and enable password. disable ssh (for now we run no encryption)
  • cpm->CPs->CP2: configure as output.
  • cpm->Groups: add group RESET, add cp2 as bit 0.
  • ftp: disable
  • http: set username/passwort and delete admin account
  • line: set name, rs232, enable, tunnel, 115200, none, 8, 1 none
  • snmp (read community, write community, contact, systemname)
  • syslog (set destination logsv1 and enable)
  • system (name, longname)
  • tftp (disable)
  • terminal: type unknown, login menu and exit menu enabled. echo disabled.

(Note: com4, general purpose pin)


This Section describes how we want to integrate future MicroIOC into the FAIR Environment

Operating System

The Systems runs a custom embedded Linux version. Busybox, 64bit, x86 based system running from a Ramdisk. Libraries are compatible to the central development systems Number of libraries is limited. Current default set is crypt, resolve, nss, c, util, m, dl, pthread, rt, thread_db.

User Applications are added to the running system and are not part of the ramdisk.

Network Boot

This is the default operating mode. System Bios will execute PXE Stack of network interfaces. Kernel and initial Ramdisk are fetched via tftp.

Local Boot

There is a user request to run MicroIOCs without a connection to the ACC Network. Syslinux is loaded from local storage media (USB Pendrive) and which in turn fetches kernel and initial ramdisk from the local storage media.

See EmbeddedRamdiskUSB

Error handling

Pendrive must be disconnected once local boot is no longer required.

Input/Output device

MicroIOC have a normal VGA output and the possibility to connect an USB Keyboard.

In addition they have a Lantronics Xport Pro.

Local Storage

Current MicroIOC have a compact flash storage media. This slot must not be used.

Slits Application

The Slits Application code must cleanly compile on the GSI Reference System. Currently that means compiling 32bit applications on Redhat Enterprise Linux 5 64bit. The slits daemon accessing the hardware must have limited library dependencies (see above) and fit into the Ramdisk. The slits daemon must support calling an external application to fetch and store its configuration data. This will be used to mount an NFS share on demand during normal operation, or access a local storage media during local operation.
I Attachment Action Size Date Who Comment
DOC-microIOC-MBOX-PDC-TechnicalDocument.pdfpdf DOC-microIOC-MBOX-PDC-TechnicalDocument.pdf manage 1 MB 20 Mar 2014 - 08:21 ChristophHandel microioc mbox pdc technical documentation
NANO-PV-D5251-R10_AR15.zipzip NANO-PV-D5251-R10_AR15.zip manage 1 MB 23 Feb 2015 - 14:58 ChristophHandel bios update microioc 64bit
NANO-PV-D5251-R10_AR17.zipzip NANO-PV-D5251-R10_AR17.zip manage 1 MB 11 Mar 2016 - 08:10 ChristophHandel  
linux-gpib-3.2.17-csl.zipzip linux-gpib-3.2.17-csl.zip manage 4 MB 19 Aug 2013 - 07:17 ChristophHandel Modified GPIB from cosylab
microioc_boot.graphmlgraphml microioc_boot.graphml manage 19 K 18 Jul 2012 - 15:25 ChristophHandel  
microioc_boot.pngpng microioc_boot.png manage 26 K 18 Jul 2012 - 15:02 ChristophHandel  
Topic revision: r28 - 08 Oct 2020, SolveighMatthies
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback