factory reset not working

Home › Forums › Conduit: AEP Model › factory reset not working

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • June 15, 2017 at 12:21 pm #19560
    Pascal
    Participant

    Hi. I haven’t used the conduit AEP in a while and now i can’t communicate with it. i’m trying a factory reset per these instructions:
    http://www.multitech.net/developer/products/conduit/resetting-the-device/
    I understand that for this procedure needs to be performed with the gateway powered off because A) it doesn’t say to turn it on in step 1, B) the picture shows all LEDs off, C) the picture shows no cables connected.
    However I tried it both ways anyways and neither worked.
    I hold the button in for longer than 5 seconds as described in step 2). It appears that nothing is happening.
    Following the procedure I connect it to my laptop with the LAN cable and power it up. I configure my laptop with a static IP of 192.168.2.2 with a netmask of 255.255.255.0. I proceed by going to the browser, https://192.168.2.1 (I also tried it without https). Nothing comes up.
    I’m now thinking that the gateway broke on its own?
    Should I send it back or is there an error in the procedure on the MultiTech website?

    June 15, 2017 at 2:11 pm #19563
    Jeff Hatch
    Keymaster

    Pascal,

    I looked at the code that handles the reset button press. It is handled in the mts-io kernel module and by the reset-monitor process. The kernel module keeps track of a short press (~5s), a long press (> ~5s && < = ~30s), and an extra long press (> ~30s).

    On AEP, for a short press a SIGHUP is sent to the reset-monitor. For a long press a SIGUSR1 is sent to the rest-monitor. For an extra long press a SIGUSR2 is sent to the reset monitor. These are not the hard-coded defaults, but are set on boot by the AEP watchdog process. On the AEP Conduit the reset monitor process is the watchdog process. The following is what happens for each button press length:

    short press (< ~5s): the system just reboots long press (> ~5s && < ~30s): the device is reset to user defined defaults and rebooted. The factory settings are used if user defined defaults have not been set. extra long press (> ~30s): the device is reset to factory defaults.

    I believe that the status LED should go solid at the start of reboot until the kernel is back up and the mts-io module is reloaded, then the status LED should start blinking normally again, but don’t quote me on that as I have not dug into that functionality to verify that.

    I have not observed any behavior outside these parameters on my device, however it is only one device, and the hardware is almost a year old.

    I am interested what the load is on these devices that are exhibiting this bad behavior on reset. If you have time to gather some information and let me know here or file a support portal ticket at https://support.multitech.com, please let me know. If you can provide the following information:

    1) Output of a top command to see what the CPU and memory state of the system is.
    2) A ‘cat’ of /sys/devices/platform/mts-io/reset-monitor.
    3) A ‘cat’ of /sys/devices/platform/mts-io/reset-monitor-intervals

    That would be a start to figure some of these issues out. If #’s 1, 2, and 3 look OK, maybe it is an actual bad hardware problem.

    Jeff

    June 15, 2017 at 3:56 pm #19566
    Pascal
    Participant

    Hi, thank you for the reply and also appreciate the phone call with Steve!
    The reset button produces no effect, whether short, medium, or long. I tried many different ways. Also the console access behind the MultiTech front cover will display the boot-up process but afterwards there is no console login. It just echoes back anything I type. Also I used to be able to get access to the console through the USB connector on the back, this is also no longer working.
    I think the device may be defective. I will contact MultiTech tomorrow and I will send the gateway to you for further investigation.

    Many thanks!

    Below is the log from the boot process, that’s the best I can do right now:

    AT91Bootstrap 3.5.3-r2 (Thu Nov 17 17:15:52 CST 2016)

NAND: ONFI flash detected
NAND: Manufacturer ID: 0x2c Chip ID: 0x32
NAND: Disable On-Die ECC
NAND: Initialize PMECC params, cap: 0x4, sector: 0x200
NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000
NAND: Done to load image

U-Boot 2012.10-mtcdt-r6 (Nov 17 2016 - 17:15:52)

CPU: AT91SAM9G25
Crystal frequency:       12 MHz
CPU clock        :      400 MHz
Master clock     :  133.333 MHz
I2C:   ready
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  256 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
vendor-id:  Multi-Tech Systems
product-id: MTCDT-210A
device-id:  18919932
hw-version: MTCDT-0.0
mac-addr:   00:08:00:4a:11:fd
Net:   macb0
Hit any key to stop autoboot:  0

Loading from nand0, offset 0x200000
   Image Name:   mLinux/3.12.27/mtcdt
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2801115 Bytes = 2.7 MiB
   Load Address: 20008000
   Entry Point:  20008000
## Booting kernel from Legacy Image at 22000000 ...
   Image Name:   mLinux/3.12.27/mtcdt
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2801115 Bytes = 2.7 MiB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 3.12.27 (jenkins@frylock) (gcc version 4.8.2 (GCC) ) #1 Thu Nov 17 16:55:55 CST 2016
Machine: Atmel AT91SAM (Device Tree), model: Multi-Tech Systems MTCDT
AT91: Detected soc type: at91sam9x5
AT91: Detected soc subtype: at91sam9g25
AT91: sram at 0x300000 of 0x8000 mapped at 0xfef70000
Kernel command line: mem=256M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc04ef50c   (5022 kB)
      .init : 0xc04f0000 - 0xc0517cbc   ( 160 kB)
      .data : 0xc0518000 - 0xc05407a0   ( 162 kB)
       .bss : 0xc05407a0 - 0xc055f408   ( 124 kB)
NR_IRQS:16 nr_irqs:16 16
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Calibrating delay loop... 199.06 BogoMIPS (lpj=995328)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Initializing cgroup subsys blkio
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc03a9b70 - 0xc03a9bc8
devtmpfs: initialized
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
AT91: Power Management (with slow clock mode)
AT91: Starting after power-restored wakeup
gpio-at91 fffff400.gpio: at address fefff400
gpio-at91 fffff600.gpio: at address fefff600
gpio-at91 fffff800.gpio: at address fefff800
gpio-at91 fffffa00.gpio: at address fefffa00
pinctrl-at91 pinctrl.2: initialized AT91 pinctrl driver
bio: create slab <bio-0> at 0
at_hdmac ffffec00.dma-controller: Atmel AHB DMA Controller ( cpy slave ), 8 channels
at_hdmac ffffee00.dma-controller: Atmel AHB DMA Controller ( cpy slave ), 8 channels
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c-gpio i2c.3: using pins 30 (SDA) and 31 (SCL)
i2c-gpio i2c.4: using pins 64 (SDA) and 65 (SCL)
Switched to clocksource tcb_clksrc
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
msgmni has been set to 496
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered (default)
io scheduler deadline registered
io scheduler cfq registered
fffff200.serial: ttyS0 at MMIO 0xfffff200 (irq = 16, base_baud = 8333333) is a ATMEL_SERIAL
console [ttyS0] enabled
f8040000.serial: ttyS1 at MMIO 0xf8040000 (irq = 26, base_baud = 8333333) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
at24_get_setup: found a match for eeprom at 56
at24 0-0056: 512 byte 24c04 EEPROM, writable, 16 bytes/write
sam9x5: read 512 bytes from id eeprom
at24_get_setup: found a match for eeprom at 50
at24 1-0050: 512 byte 24c04 EEPROM, writable, 16 bytes/write
sam9x5: ap1 eeprom read failed: -110
at24_get_setup: found a match for eeprom at 52
at24 1-0052: 512 byte 24c04 EEPROM, writable, 16 bytes/write
sam9x5: read 512 bytes from ap2 eeprom
atmel_nand 40000000.nand: Using dma0chan0 for DMA transfers.
ONFI param page 0 valid
ONFI flash detected
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xaa (Micron MT29F2G08ABBEAHC), 256MiB, page size: 2048, OOB size: 64
atmel_nand 40000000.nand: ONFI params, minimum required ECC: 4 bits in 512 bytes
atmel_nand 40000000.nand: Initialize PMECC params, cap: 4, sector: 512
Scanning device for bad blocks
9 ofpart partitions found on MTD device atmel_nand
Creating 9 MTD partitions on "atmel_nand":
0x000000000000-0x000010000000 : "NANDFlash"
0x000000000000-0x000000040000 : "at91bootstrap"
0x000000040000-0x0000000c0000 : "u-Boot"
0x0000000c0000-0x000000160000 : "u-Boot Config"
0x000000160000-0x000000200000 : "u-Boot Redundant Config"
0x000000200000-0x000000800000 : "uImage"
0x000000800000-0x000001000000 : "Config"
0x000001000000-0x000001800000 : "OEM Config"
0x000001800000-0x000010000000 : "Rootfs"
libphy: MACB_mii_bus: probed
macb f802c000.ethernet eth0: Cadence MACB at 0xf802c000 irq 23 (00:08:00:4a:11:fd)
macb f802c000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=f802c000.etherne:00, irq=-1)
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-atmel: EHCI Atmel driver
atmel-ehci 700000.ehci: EHCI Host Controller
atmel-ehci 700000.ehci: new USB bus registered, assigned bus number 1
atmel-ehci 700000.ehci: irq 31, io mem 0x00700000
atmel-ehci 700000.ehci: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.12.27 ehci_hcd
usb usb1: SerialNumber: 700000.ehci
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci 600000.ohci: AT91 OHCI
at91_ohci 600000.ohci: new USB bus registered, assigned bus number 2
at91_ohci 600000.ohci: irq 31, io mem 0x00600000
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: AT91 OHCI
usb usb2: Manufacturer: Linux 3.12.27 ohci_hcd
usb usb2: SerialNumber: at91
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
rtc (null): invalid alarm value: 1900-1-1 0:0:0
at91_rtc fffffeb0.rtc: rtc core: registered fffffeb0.rtc as rtc0
at91_rtc fffffeb0.rtc: AT91 Real Time Clock driver.
i2c /dev entries driver
at91sam9_wdt: enabled (heartbeat=15 sec, nowayout=0)
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3973 buckets, 15892 max)
ipip: IPv4 over IPv4 tunneling driver
gre: GRE over IPv4 demultiplexor driver
ip_gre: GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: cubic registered
NET: Registered protocol family 17
l2tp_core: L2TP core driver, V2.0
Key type dns_resolver registered
at91_rtc fffffeb0.rtc: setting system clock to 2017-06-15 20:52:22 UTC (1497559942)
usb 1-2: new high-speed USB device number 2 using atmel-ehci
usb 1-2: New USB device found, idVendor=0424, idProduct=2534
usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
usb 2-3: new full-speed USB device number 2 using at91_ohci
usb 2-3: New USB device found, idVendor=04e2, idProduct=1412
usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-2.2: new high-speed USB device number 3 using atmel-ehci
usb 1-2.2: New USB device found, idVendor=0403, idProduct=6014
usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.2: Product: Single RS232-HS
usb 1-2.2: Manufacturer: FTDI
jffs2: Empty flash at 0x08541214 ends at 0x08541800
jffs2: Empty flash at 0x0e719da0 ends at 0x0e71a000
jffs2: notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
VFS: Mounted root (jffs2 filesystem) readonly on device 31:8.
devtmpfs: mounted
Freeing unused kernel memory: 156K (c04f0000 - c0517000)
INIT: version 2.88 booting
jffs2: Empty flash at 0x004e3930 ends at 0x004e4000
jffs2: notice: (73) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
jffs2: notice: (73) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Starting udev
udevd[84]: starting version 182
tmp102 0-0048: initialized
atmel_spi f0000000.spi: version: 0x212
atmel_spi f0000000.spi: Using dma0chan1 (tx) and dma0chan2 (rx) for DMA transfers
atmel_spi f0000000.spi: Atmel SPI Controller at 0xf0000000 (irq 28)
atmel_spi f0000000.spi: master is unqueued, this is deprecated
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
vizzini 2-3:1.0: This device cannot do calls on its own. It is not a modem.
vizzini 2-3:1.0: ttyXRUSB0: XR21v14x usb uart device
atmel_spi f0004000.spi: version: 0x212
atmel_spi f0004000.spi: Using dma1chan0 (tx) and dma1chan1 (rx) for DMA transfers
atmel_spi f0004000.spi: Atmel SPI Controller at 0xf0004000 (irq 29)
atmel_spi f0004000.spi: master is unqueued, this is deprecated
vizzini 2-3:1.2: This device cannot do calls on its own. It is not a modem.
vizzini 2-3:1.2: ttyXRUSB1: XR21v14x usb uart device
usbcore: registered new interface driver vizzini
vizzini: Exar USB UART Driver for XR21V141x
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
pps pps0: new PPS source pps.7.-1
pps pps0: Registered IRQ 32 as PPS source
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
atmel_mci f0008000.mmc: version: 0x504
atmel_mci f0008000.mmc: using dma0chan3 for DMA transfers
atmel_mci f0008000.mmc: Atmel MCI controller at 0xf0008000 irq 22, 1 slots
atmel_usba_udc 500000.gadget: MMIO registers at 0xf803c000 mapped at d09e4000
atmel_usba_udc 500000.gadget: FIFO at 0x00500000 mapped at e1100000
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
ftdi_sio 1-2.2:1.0: FTDI USB Serial Device converter detected
usb 1-2.2: Detected FT232H
usb 1-2.2: Number of endpoints 2
usb 1-2.2: Endpoint 1 MaxPacketSize 512
usb 1-2.2: Endpoint 2 MaxPacketSize 512
usb 1-2.2: Setting MaxPacketSize 512
usb 1-2.2: FTDI USB Serial Device converter now attached to ttyUSB0
Starting Bootlog daemon: bootlogd.
/var/config already mounted
/var/oem already mounted
Loading mts-io module
[INFO] mts-io:mts_io_init:829: init: v1.1.1
[INFO] mts-io:mts_id_eeprom_load:754: detected board MTCDT-0.0
[INFO] mts-io:mts_id_eeprom_load:757: sizeof: 512
[INFO] mts-io:mts_id_eeprom_load:758: vendor-id: Multi-Tech Systems
[INFO] mts-io:mts_id_eeprom_load:759: product-id: MTCDT-210A
[INFO] mts-io:mts_id_eeprom_load:760: device-id: 18919932
[INFO] mts-io:mts_id_eeprom_load:761: hw-version: MTCDT-0.0
[INFO] mts-io:mts_id_eeprom_load:768: mac-addr: 00:08:00:4A:11:FD
[INFO] mts-io:mts_id_eeprom_load:770: imei:
[INFO] mts-io:mts_id_eeprom_load:771: capa-gps: no
[INFO] mts-io:mts_id_eeprom_load:772: capa-din: no
[INFO] mts-io:mts_id_eeprom_load:773: capa-dout: no
[INFO] mts-io:mts_id_eeprom_load:774: capa-adc: no
[INFO] mts-io:mts_id_eeprom_load:775: capa-wifi: no
[INFO] mts-io:mts_id_eeprom_load:776: capa-bluetooth: no
[INFO] mts-io:mts_id_eeprom_load:800: uuid: A49E3E0805F2D92BAF5CFEAF116E21DC
[INFO] mts-io:load_port:653: no accessory card inserted in port 1
[INFO] mts-io:load_port:688: accessory card 2 vendor-id: Multi-Tech Systems
[INFO] mts-io:load_port:689: accessory card 2 product-id: MTAC-LORA-915
[INFO] mts-io:load_port:690: accessory card 2 device-id: 18869565
[INFO] mts-io:load_port:691: accessory card 2 hw-version: MTAC-LORA-1.0
[INFO] mts-io:load_port:712: accessory card 2 eui: 00:80:00:00:00:00:C5:E5
[INFO] mts-io:lora_setup:42: loading LORA accessory card in port 2
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
INIT: Entering runlevel: 5
Configuring network interfaces... done.
Starting system message bus: dbus.
Starting HOSTAP Daemon: Configuration file: /etc/hostapd.conf
cfg80211: Calling CRDA to update world regulatory domain
rfkill: Cannot open RFKILL control device
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
nl80211 driver initialization failed.
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
hostapd_free_hapd_data: Interface wlan0 wasn't started
macb f802c000.ethernet eth0: link up (100/Full)
Starting syslogd/klogd: done
[INFO] eeprom_main.c:main:536: loaded id eeprom from /sys/bus/i2c/devices/i2c-0/0-0056/eeprom successfully
[INFO] eeprom_main.c:mts_id_eeprom_inspect:276: sizeof: 512
[INFO] eeprom_main.c:mts_id_eeprom_inspect:277: vendor-id: Multi-Tech Systems
[INFO] eeprom_main.c:mts_id_eeprom_inspect:278: product-id: MTCDT-210A
[INFO] eeprom_main.c:mts_id_eeprom_inspect:279: device-id: 18919932
[INFO] eeprom_main.c:mts_id_eeprom_inspect:280: hw-version: MTCDT-0.0
[INFO] eeprom_main.c:mts_id_eeprom_inspect:287: mac-addr: 00:08:00:4A:11:FD
[INFO] eeprom_main.c:mts_id_eeprom_inspect:288: imei:
[INFO] eeprom_main.c:mts_id_eeprom_inspect:289: capa-gps: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:290: capa-din: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:291: capa-dout: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:292: capa-adc: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:293: capa-wifi: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:294: capa-bluetooth: no
[INFO] eeprom_main.c:mts_id_eeprom_inspect:302: mac-bluetooth: 00:00:00:00:00:00
[INFO] eeprom_main.c:mts_id_eeprom_inspect:309: mac-wifi: 00:00:00:00:00:00
[INFO] eeprom_main.c:mts_id_eeprom_inspect:315: uuid: A49E3E0805F2D92BAF5CFEAF116E21DC
Reading accessory cards data
jffs2: notice: (241) check_node_data: wrong data CRC in data node at 0x0e719670: read 0x32195587, calculated 0x2a29a303.
Adding accessory cards data
Generating /var/run/config/lighttpd_port.conf
starting local time setup...jffs2: warning: (522) jffs2_sum_write_data: Not enough space for summary, padsize = -955
Setting timezone to  EST
Generating Timezone List
Loading [g_serial]
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
Starting Lighttpd Web Server: lighttpd.
syslog configure and reload
stopped syslogd (pid 389)
Starting Mosquitto...
starting backoff-timers setup
backoff-timers init...
array element is null. path [result/backOffTimers/timers/4/carrierName]. failed on [4]
Using Default Backoff Timer Configurations
starting network interfaces setup
null path [result/ppp/enabled]. failed on [enabled]
RTNETLINK answers: No such process
post-upgrade.init: Checking if upgrade scripts need to be run
Firewall Initialization
sshd enabled
SSH Port=22
Starting OpenBSD Secure Shell server: sshd
done.
Starting ddns
Ddns is disabled
starting dns and dhcp services
null path [result/ppp/enabled]. failed on [enabled]
Cellular module is not found
starting time setup...done.
Starting smsd
Starting WAN manager
Starting crond: OK
Starting Carrier Detect and Signal Strength LEDs
Starting RM client
Starting Call-Home Service
customapp.init: Starting custom apps through app-manager...
setting /sys/class/leds/led-status/trigger to heartbeat
starting node-red
Call-Home Not Needed
{
   "code" : 400,
   "error" : "Failed to read annexcd pid file",
   "status" : "fail"
}
starting Node-RED stunnel services
Found lora card MTAC-LORA-915
No internet connection, waiting...
No internet connection, waiting...
No internet connection, waiting...
No internet connection, waiting...
    June 15, 2017 at 7:14 pm #19567
    Jason Reiss
    Keymaster

    Did you install any 3rd party software?
    TNN or Loriot packet forwarder?

    Can you connect device to internet?
    It should be able to complete boot.

    • This reply was modified 7 years, 10 months ago by Jason Reiss.
    June 15, 2017 at 7:28 pm #19569
    Jason Reiss
    Keymaster

    Factory reset will restore omly configuration.
    This must be done with unit powered on.
    However in default setting the unit will be in gateway mode and not in DHCP client mode if you expect to connect to a network through Dhcp.

    The only way to recover is through reflash via rd to from uboot on debug interface.
    This will restore the rootfs.

    June 16, 2017 at 10:26 am #19575
    Pascal
    Participant

    Ok, I was hoping a factory reset would restore the original image as if the device was brand new again. I’ve been installing TTN and experimenting with a lot of other LoRaWAN network servers. It’s possible that if mts-io is an external kernel module that somehow it may have been deleted because the reset button did absolutely nothing (with power on of course). I was using 1.3.3 at the time.

    In any case I was finally able to get back into the system but only because I guessed the correct IP address that it was set to last. This is really why I wanted to reset it so it would have been back at 192.168.2.1.

    The closest thing to a factory reset I can achieve is by upgrading the firmware, even if it’s already the same firmware. This process seems to overwrite a lot of old stuff. I’m now on version 1.4.3 and the reset button is definitely working.
    At this point all my problems have been solved and again I highly appreciate the help from you and Steve.

    June 16, 2017 at 10:33 am #19577
    Jeff Hatch
    Keymaster

    Pascal,

    There are some packages that had issues because they expected Internet connectivity in their boot scripts and would block until it was available. This would cause the boot to “hang” before the process was started that handles the reset button press. I believe that TTN and Loriot were a couple that may have had this issue. Some of those packages have been fixed since.

    Jeff

    June 16, 2017 at 12:24 pm #19578
    Ajay K
    Participant

    Hi Jeff,

    I seemed to have run into something similar. Is there a way to reset to factory settings from the putty command prompt? I pressed the reset button for over 20 seconds and everything is as is. I am logged in via the putty command prompt via the debug port and my updated admin password is still intact inspite of doing a reset as mentioned above and I am on 1.4.1 firmware version.

    Thanks,
    Ajay

    June 16, 2017 at 12:47 pm #19579
    Ajay K
    Participant

    So I seemed to have managed to reset it to defaults, however I get the following error below and can’t seem to connect to the 192.168.2.1 ip and i am guessing it is because of the error below.

    udhcpc (v1.22.1) started
    Setting IP address 0.0.0.0 on eth0
    Sending discover…
    Sending discover…
    Sending discover…
    Usage: /etc/udhcpc.d/lanup {bound|renew|deconfig}
    run-parts: /etc/udhcpc.d/lanup exited with code 1
    No lease, failing

    Thanks,
    Ajay

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.