Technical Support Request

If you require technical assistance please email us at: support@ursaleo.com

Please describe your problem in detail. If possible, include whether the problem is with an UrsaLeo DevKit device, the Ursaleo Cloud Platform, or other. A member of our support staff will respond as soon as possible.

FAQs

General

Q. How do I configure Wifi?

A. Remove your microSD card from the DevKit and insert it into a PC with card reader. Using a text editior create a new text document in the “Boot” drive named wpa_supplicant.conf with the following contents, replacing ssid & psk for those of your WiFi Access Point:

NOTE Windows Notepad adds .txt extensions to file names. Switch on View Filename Extensions and remove any .txt extension. Each command must be on a separate line:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
scan_ssid=1
ssid="TP-Link"
psk="12345678"	
}

Now put the microSD card back in your DevKit and restart. The wifi configuration will be copied to /etc/wpa_supplicant.conf and the wifi will connect.

Q. How do I connect my DevKit using Ethernet?

A. Just plug in your Ethernet cable and providing your network is running a DHCP service, then the DevKit will obtain an IP address and connect. For this to work, the wifi must not be configured.

NOTE UrsaLeo DevKits are currently designed to connect to either WiFi or Ethernet only, not both.

Q. How do I get terminal access to my DevKit?

A. To gain terminal access to your UrsaLeo DevKit depends on which DevKit you purchased.

UrsaLeo RPi

  1. Attach an HDMI monitor to the HDMI port on the DevKit using an HDMI cable. Attach a USB keyboard to any of the USB ports on the DevKit.

  2. Power on the UrsaLeo RPi and wait for the boot prompt to appear.
     BEC Linux 2.5 raspberrypi3 ttyS0
    
     raspberrypi3 login:
    
  3. Login as “root” with no password.
     BEC Linux 2.5 raspberrypi3 ttyS0
    
     raspberrypi3 login: root
    
    
  4. The shell prompt appears ready to run commands
     root@raspberrypi3:~#
    

UrsaLeo UltraLite

  1. Attach a PC using a USB cable connected to the micro USB port (Serial UART connector) near the ON/OFF slide switch.

  2. Download and install Silicon Labs Windows VCP drivers on PC: www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers

  3. Download and install Putty serial comms software on PC:

  4. Start Putty and configure serial settings.
    • Baud rate: 115200
    • Data bits: 8
    • Stop bits: 1
    • Parity: None Putty serial settings Putty configuration
  5. Power on the DevKit and wait for the boot prompt to appear.
     BEC Linux 2.5 imx6ulevk ttyS0
        
     imx6ulevk login:
    
  6. Login as “root” with no password.
     BEC Linux 2.5 imx6ulevk ttymxc0
        
     imx6ulevk login: root
    
  7. The shell prompt appears ready to run commands
     root@imx6ulevk:~#
    

Q. How can I tell if my Thunderboard has connected?

A. The Thunderboard has a central green LED which flashes once per second while it advertises for a BLE connection. Press the reset button near the centre of the Thunderboard and count the flashes. If there are less than 30 then the Thunderboard has established a connection.

Q. How can I check if my DevKit is connecting to the internet?

A. Gain terminal access (see above) and issue a ping command to the Google Mqtt API - the response should be similar to below:

```
root@raspberrypi3:~# ping mqtt.googleapis.com

PING mqtt.googleapis.com (64.233.184.206): 56 data bytes

64 bytes from 64.233.184.206: seq=0 ttl=42 time=101.939 ms

64 bytes from 64.233.184.206: seq=1 ttl=42 time=29.349 ms

64 bytes from 64.233.184.206: seq=2 ttl=42 time=53.844 ms

64 bytes from 64.233.184.206: seq=3 ttl=42 time=28.871 ms

^C
--- mqtt.googleapis.com ping statistics ---

4 packets transmitted, 4 packets received, 0% packet loss

round-trip min/avg/max = 28.871/53.500/101.939 ms
```

Q. The power LED on my DevKit is on but it will not boot, what should I do?

A. Whilst power is off, please check that the microSD card is correctly seated in the connector slot, then reboot.

BACK