My understanding of ArcNet protocol

What is ArcNet?

Attached Resource Computer Network is a communication protocol widely used in build automation. This protocol is very efficient in Local Area Network, wherein multiple devices want to share information at faster phase. Core functionality of this protocol relies on token passing between nodes. Better analogy could be, consider network as a shared object and token as the key to the object.

What are other features?

Data speeds up to 10Mpbs, Variable packet lengths, Supports Bus or star topology, Uni-cast and broadcast messages.

Let’s dive into each message types in the protocol.

RECON – Reconfiguration

This is another important message or feature to keep track of the network changes. This message can be triggered in following cases:

  1. When a node joins the network
  2. When a node leaves the network
  3. For high performance, it can be triggered every 20 – 30ms


ITT: Invitation to Transmit

Token is the identifier for the node or the device in the network. When node enters the network it sends a RECON message. This message will inform the network about change in configuration of the network and re-start the token passing.

Let’s take a simple example of a network.

Now node 1 starts the token passing, it will send out ITT message to destination nodes starting from next address of its current address. In our case it would be 0x0B. It keeps on sending ITT until it receives the response from any node in the network.


Now as you can see, 0x02 node has responded to the request from 0x0a. Now the token is with 0x02 node, so it starts it token parsing to find out another node in the network.

When ITT message reached the destination as 0x05, node three responds takes on the task of token parsing. Then it identifies the another node that is i.e 0x0a. So token passing happens until all nodes in the network are identified. For our setup the intial token passing is completed we have a network 0x0A <-> 0x02 <-> 0x05 <-> 0x0a.

After accomplishing the network and identifying the nodes in the network. The token passing keeps on continuing as shown below for efficient data transfer.


How? say for example 0x0a wants to send some data to 0x05. It can send the data only when it has the token. As I said earlier, token is kind of key to the network infrastructure and resources.

FBE – Free Buffer Enquiry

Before a nodes a sends packet to another node, it needs to know if the receiver can accept incoming packets.

When the node has the token, it would send a FBE request to receiving node. The receiver can chose to send ACK or NAK.

FBE with NAK/ACK is shown below


PAC: Packet

This is the message protocol to send data frames to the receiving node. The data could be anything.

The frame contains Source address node, destination node, length and the actual data. The receiver can ACK or NAK the transmission.

PAC sequence is shown below:


ACK: Acknowledgement

Sent by receiving node to the sender about accepting the information sent

NAK: Negative Acknowledgement

Sent by receiving node to the sender about rejecting the information sent


Auto login in TI-SDK, Am335x

I have been working with TI-SDK for past two years and every time i come across some interesting trivia posed by the systems engineers 🙂 . One of such request was to enable automatic login in tisdk. The idea is to lead the user directly to command prompt after kernel boot up. I tried several approaches over weeks, and zeroed in on the following simpler approach.

I am going to run through serious of steps followed to enable auto login in tisdk or embedded linux.

The setup which I used:

Version : TISDK 7.0

Hw: AM335x

Rootfs: Hosted on Network file system on ubuntu [ which is a guest OS on Vmware]

Firstly I need a configuration file for setting username and password. I can just hard code in the tool but want to give user the control.

The configuration file looks like:

#cat /etc/autologin.profile


Then I wrote a small tool to read the username and password from configuration file and use /bin/login for login to the shell..

// Autologin.c

// GPL, Author: Johnnie J. Alan

#include <unistd.h>
#include <stdio.h>

int main()
int nrv = 0;
FILE* fptr = 0;
char user[64];

char pass[64];

// clear buffer

// open autologin profile file
fptr = fopen(“/etc/autologin.profile\0″,”r\0″);

// make sure the file exists and was opened
if (fptr != 0)
// the return value from fscanf will be 1 if the autologin profile name is read correctly
nrv = fscanf(fptr,”%s,%s\0”,user,pass);

// only autologin if the profile name was read successfully,
// otherwise show the regular login prompt
if (nrv > 0)
nrv = execlp(“login”,”login”,”-f”,user,0);
nrv = execlp(“login”,”login”,”\0″,pass,0);

return 0;

Note: you can change this according to your needs

I cross compiled the tool for ARM and placed the compiled tool in /sbin

arm-linux-gnueabihf-gcc -o autologin autologin.c

Then I changed the init scripts to reflect the changes, basically setting up getty. My setup uses Uart0 port for console.

The configuration for the console is present in /etc/inittab. The changes which I made is highlighted below.

#Johnnie S:2345:respawn:/sbin/getty 115200 ttyO0

The file myloginShell is just used for my configurations, the idea is to isolate my changes from the defaults.

The contents of the myloginShell is


# I have removed some of other configuration which is not relevant for this post.

if [ $showLogin -eq 1 ]; then
while true; do
# This is line which is important. ttyO0 indicates by Uart0 console port

# I am asking getty to use my tool instead of /bin/login which is default.
/sbin/getty -n -l /sbin/autologin 115200 ttyO0
if [ “$exitCode” = “129” ]; then
stty -echo

Viola, You have the setup ready to automatic login.

You can also do the same in inittab itself.

#Johnnie S:2345:respawn:/sbin/getty 115200 ttyO0
S:2345:respawn:/sbin/getty -n -l /sbin/autologin 115200 ttyO0

Thanks for reading this post and Happy logging.