Chapter 7. Advanced troubleshooting

In the unlikely event of the user experiencing problems with the operation of the Minimus, a diagnostics tool is available via the GNSS connector, which also acts as a terminal communications device via a Serial connection.

The user should first plug in the serial adapter to the GNSS connector, which is then attached to a 9-pin COM port on your PC/laptop (if a 9-pin COM port is not available, a serial-to-USB converter should be used instead and connected to an available USB port. Güralp recommend converters based on the FTDI chip-set.)

A connection is then made using a terminal emulator, such as minicom under Linux or PuTTY under Windows. The appropriate COM port should be entered as the "Serial line", and the Speed should be set to 115,200.

Click the button and a terminal window should open, displaying the status logs of the Minimus.

In the event of any operational issues, the Güralp Support Team may request a copy of this terminal log in order to be able to diagnose any issues.

7.1 Reset all settings during boot phase

The Minimus can be reset to its factory settings during its boot-up stage. This is useful in cases where the user is not able to communicate with the Minimus via a network connection, where the unit is not responsive, or where it does not appear in the Discovery software’s scan results.

To carry out a full system reset, connect to the terminal port via a serial connection (as described in section 7). During the middle part of the boot phase, when the text @GURALP SYSTEMS and the firmware version number is displayed, key +. This causes all settings (except Username, Password and Bluetooth PIN) to revert to their factory default values, and the Minimus will re-boot. It may be necessary to enter this key combination several times.

A typical boot log is shown below, identifying the stages where + will cause the Minimus to reset and re-boot.

Do not press any buttons during the first phase of boot-up:

RomBooT

AT91Bootstrap 3.5.3 G1.01

SF: Got Manufacturer and Device ID:0x1f 0x47 0x1 0x0 0x0

SF: Copy 0x80000 bytes from 0x8400 to 0x26f00000

SF: Image loaded

U-Boot 2012.10 (Oct 01 2014 - 09:59:23)

CPU: SAMA5D36

Crystal frequency: 12 MHz

CPU clock : 528 MHz

Master clock : 132 MHz

DRAM: 256 MiB

WARNING: Caches not enabled

NAND: 256 MiB

MMC: mci: 0, mci: 1

SF: Detected AT25DF321 with page size 4 KiB, total 4 MiB

In: serial

Out: serial

Err: serial

Net: gmacb0

Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x200000, size 0x200000

2097152 bytes read: OK

## Starting application at 0x21000000 ...

Heap start 22464180

t_who_called: Frame outside stack 20fffd0c [210efcf4 eafffffe]

Mclk 135168000Hz

t_who_called: Frame outside stack 20fffeac [210efcf4 eafffffe]

t_who_called: Frame outside stack 20fffebc [210efcf4 eafffffe]

@GURALP SYSTEMS

Once the “@GURALP SYSTEMS” banner has been printed, keying + (at least once) will cause all settings (except Username, Password and Bluetooth PIN) to revert to their default values and cause the Minimus to reboot.

0.80-15331 by ysoon on 14:43:49 14-Sep-2016

Vecbase: 21000020 CPUid: 410fc051 Cache: c51878

PMT init

Unsafe to change DBGU clock while running

mux start SP 20ffff64

MMU start

Page table address 0x300000

Starting mmu for first time

Data cache invalidation done..

New system control 00c5187d

If you are seeing this mmu and caches are working fine..

FPU start

VFP Id=41023051

Calling-> init_dbgprint

Calling-> init_cmdutils

Calling-> init_pmt_dlg

Calling-> init_newtask

Calling-> show_tasks

00 Prio:40 Taskname: startup thread

01 Prio:00 Taskname: Baseloop

Run PMT changing stacks

Calling-> init_memdlg

Calling-> malloc_debug

Calling-> rtc_init

Calling-> start_timer_interrupts

Calling-> uart_start_ints

Calling-> init_arm_parse

Calling-> t_init_task_utils

Calling-> init_leds

Calling-> gpio_init

Calling-> init_devio

Calling-> init_usart

Calling-> init_devio_cmds

Calling-> rpc_init

Calling-> ram_init

If your key-strokes have been recognised, Ctrl+R will be printed in the boot log, as shown below – once for each time your keystrokes were logged: