Group Actions
Engagement
  • Author Author: fvan
  • Date Created: Date Created
  • Views 4977 views
  • Likes 6 likes
  • Comments 6 comments
Related
Recommended

RIoTboard - Getting Started

fvan

I met Gregory from Freescale at Maker Faire Paris beginning of May after some emails going back and forth regarding another Freescale board. After having exchanged some ideas and feedback, he was kind enough to send me a RIoTboard and some accessories for evaluation purposes and has also given me access to a preview version of the new RIoTboard website due to be launched this summer.

 

This is my first post about the RIoTboard, more specifically on getting everything set up and ready for some projects.

 

 

What is it ?

 

The RIoTboard is an open source community platform, supported by element14 and powered by a Freescale i.MX6 ARM Cortex-A9 processor. The board is meant to help evaluate the various peripherals and includes:

 

imageimage

  • 10/100/Gb ethernet port
  • HDMI port
  • LVDS
  • analog audio in/out
  • microSD and SD card interfaces
  • JTAG
  • two camera ports
  • four USB ports
  • two mini USB ports
  • serial debug port
  • expansion port with PWM, SPI, I2C, UART, ...
  • reset button


The Freescale i.MX6 ARM Cortex-A9 processor runs at 1GHz, there is 1GB of DDR memory and 4GB eMMC. Powering the board is done through a 5V DC barrel jack connector.


The name appears to be a clever wordplay as the tag line is "Revolutionising the Internet of Things":  revolution, IoT, riot, RIoTboard. The logo of a raised fist holding the board fits nicely in the theme.


The board is currently listed at 73EUR (before tax) on the Farnell website, which compared to a Raspberry Pi or Beaglebone Black may seem on the high side, especially since the launch of the quad core Raspberry Pi model 2 at 38EUR.

 

What's in the box ?

image


In the box, you'll find the following items:

  • RIoTboard
  • mini-USB cable
  • quick start guide

 

Additionally, you will need following items:

  • HDMI monitor
  • USB keyboard and mouse for input, even if only for initial configuration
  • 5V/4A power supply

 

And you may need:

  • wifi dongle for wireless connectivity instead of using the ethernet port
  • (micro)SD card (4GB minimum) to use/test an alternative operating system
  • USB UART cable for troubleshooting

 


imageimage

 

First boot


By default, the RIoTboard boots from the onboard flash which has Android 4.3 pre-installed.

 

Different OS


There are two ways to use a different operating system with the RIoTboard:

  • overwrite the pre-installed OS on the onboard flash
  • boot from a (micro)SD card containing a different OS


I personally prefer the second option (SD card), especially when starting out, for the following reason:

  • more simple procedure that can be executed on any operating system
  • preserves the onboard flash in its current state
  • is not limited to 4GB


Because of these reasons, I will only be covering the SD card approach to use a different operating system.

 

Operating systems


There are currently four flavours of available operating systems:

  • Android 4.3 (Jelly Bean)
  • Android 4.4 (Kit Kat)
  • Linux 3.10.17 (Yocto)
  • Linux  3.0.35 (Ubuntu)


All four come in two variants: eMMC or SD Card. Depending on where you wish to flash the OS on, you will need to download the correct image.Which flavour you pick depends on your preference, what you are familiar with and what you intend to do with the RIoTboard. For this getting started guide, I'll be proceeding with the Yocto Linux image.


If you want to know more about Android, check out this link to training material for developers: https://developer.android.com/training/index.html

 

Flashing the SD card


Flashing an image to the SD card is done in the same way as with the Raspberry Pi. So if you are familiar with that, there should be no problems.First, extract the downloaded zip file containing the image, then using "dd" (Linux/OS X) or "Win32DiskImager" (Windows), flash the image on the SD card. The time to flash the SD card may vary depending on its speed, but I've experienced times around 10 minutes using the latest image. It is recommended to use an SD card of at least 4GB, preferably 8GB.



image

 

DIP switch settings


Once the SD card is ready, power off the RIoTboard and insert the SD card. Before powering on the board, it is required to tell it to boot from the card rather than the onboard flash. This is done using the DIP switch in the middle of the board.


These are the settings:

  • boot from onboard flash: 10110111
  • boot from SD card: 10100101

 

Booting


With the SD card inserted and the DIP switch settings adapted, all that remains is to power on the RIoTboard.

 

Wireless connectivity


As far as I'm aware, there are currently two officially supported wifi dongles:

  • Wi-Pi wifi dongle
  • element14 wifi dongle (purple)

 

Both can be obtained from element14 and are compatible with other boards such as the Raspberry Pi or Beaglebone Black.

 

image

 

Android

 

Wireless connectivity works out-of-the-box using the Android 4.4 image (not with 4.3!).

 

Linux

 

Using the Yocto image, I was having trouble getting the wifi to work. The wifi dongle was listed using the "lsusb" command, but no "wlan0" interface was available.

 

image

 

After seeking help on the element14 forums in the RIoTboard area, I was given a newer Yocto image (riotboard_yocto_gui_SVN3000) with which wifi worked immediately, just like with the Android 4.4 image. I've been told this newer image will be officially released soon and the issue was related to kernel gadget support not being configured in the previous build.

 

The new image I received is also more lightweight (1.4GB vs 3.9GB) and boots straight to a graphical environment.

 

imageimage

imageimage

 

Connecting remotely

 

SSH

 

SSH is enabled by default. One thing to pay attention to though, is that no password is configured for the "root" user, making the system open for anyone.

A password is easily configured using the "passwd" command.

 

Fredericks-Mac-mini:~ frederickvandenbosch$ ssh root@192.168.0.136
root@riotboard:~# passwd
Changing password for root
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
New password:
Re-enter new password:
passwd: password changed.

 

Next time you try to log in via SSH, you will be prompted for the password.

 

Fredericks-Mac-mini:~ frederickvandenbosch$ ssh root@192.168.0.136
root@192.168.0.136's password:
root@riotboard:~#

 

VNC

 

Using VNC, it is possible to access the desktop remotely.

First the VNC server needs to be started. This can be done via SSH with the following command:

 

root@riotboard:~# x11vnc -bg -rfbport 5900 -skip_lockkeys -o /tmp/x11vnc.log

 

Once this is executed, connect to the desktop using a VNC client and IP address of the RIoTboard and port 5900.

 

imageimage

 

Just like with SSH, there is no password configured by default. This can easily be changed.

 

root@riotboard:~# x11vnc -storepasswd
Enter VNC password:
Verify password:
Write password to /home/root/.vnc/passwd? [y]/n
Password written to: /home/root/.vnc/passwd

 

Running VNC with an additional "-usepw" flag will ensure the defined password is required when connecting.

 

root@riotboard:~# x11vnc -usepw -bg -rfbport 5900 -skip_lockkeys -o /tmp/x11vnc.log

 

image

 

Additional resources

 

This is a list of useful links to tutorials or additional information on the RIoTboard.

 

Conclusion

 

Aside from the issues with the wifi using the Linux image, setting up the RIoTboard is fairly easy. If you already have experience with other SBCs such as the Raspberry Pi or Beaglebone Black, there is not much new to know to get started.

 

In a next post, I'll be working on a first project using the RIoTboard, continuing with the Yocto Linux OS.

  • in reply to Former Member

    Strange, the images I worked with could boot properly and the only reason I switched to the SVN3000 image was to get the Wifi to work.

     

    Are you properly unmounting the SD card before doing the dd command ? Do you have the full output ?

     

    * sudo diskUtil list

    * sudo diskUtil unmountDisk /dev/sdX
    * sudo dd if=/path/to/image of=/dev/sdX

     

    Looking at your other thread (Problems flashing new Image (Yocto or Ubuntu)) it seems you have the problem with many more images.

     

    How are the DIP switches configured on the RIoTboard ?

  • Very interesting post, Frederik. Thanks for these detailled information

  • Hey Frederick,

     

    tried the same procedure by downloading the Yocto image (svn3000) and flashing it to an 8GB SDCard using dd on OS X... However trying to boot from this SDCard yields the following output:

    U-Boot 2013.04 (Nov 25 2014 - 15:03:06)
CPU:   Freescale i.MX6SOLO rev1.1 at 792 MHz
CPU:   Temperature 23 C, calibration data: 0x58750d5f
Reset cause: POR
Board: MX6SOLO RIoTboard
I2C:   ready
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment


No panel detected: default to HDMI
Display: HDMI (640x480)
In:    serial
Out:   serial
Err:   serial
mmc0 is current device
Net:   FEC [PRIME]
Warning: failed to set MAC address


Normal Boot
Hit any key to stop autoboot:  1 ... 0 
mmc0 is current device
reading boot.scr
** Unable to read file boot.scr **
reading uImage
5417664 bytes read in 291 ms (17.8 MiB/s)
Booting from mmc ...
reading imx6solo_RIoTboard.dtb
46315 bytes read in 20 ms (2.2 MiB/s)
## Booting kernel from Legacy Image at 12000000 ...
   Image Name:   Linux-3.10.17_1.0.0_RIoTboard+gb
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5417600 Bytes = 5.2 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Loading Kernel Image ... OK
OK
   Using Device Tree in place at 18000000, end 1800e4ea
Starting kernel ...

     

    And that's it... it doesn't get any further. Can anyone help?

  • in reply to fvan

    Yes I did but my feeble mind did not connect it with you. Sorry!image

  • in reply to clem57

    Are you saying you haven't seen my (famous ?) BBB Radio before ?? image  Beaglebone Black Radio Challenge - Part 5: Project Finalisation

    So yes, I've worked with the BBB before, nothing extremely advanced though image

     

    I'll be looking at expanding partitions in the next post to fully use the SD card and might throw in the memory test you mention as well image