Cannot reset to factory default

[JC Petit]

Good morning,

I added some configuration in /etc/network/interfaces and when I rebooted, I get this line:

Initialising LoRa…
LoRa initialised, SymLink created.
Starting mini_snmpd … [ OK ]
Would start /usr/sbin/ntpd -u ntp:ntp -p /var/run/ntp.pid -g -c /etc/ntp.conf , and add -20 to the priority.
jffs2: notice: (252) check_node_data: wrong data CRC in data node at 0x0a978f20: read 0xf279f361, calculated 0x88d3fa2b.

Now I cannot reset to factory default. I am pretty new at this… anyone can help?

Thanks,
JC

• This topic was modified 7 years, 6 months ago by JC Petit.

[Jeff Hatch]

JC,

Are you saying that the boot just stops at that point? Are you running an AEP or mLinux Conduit? The jffs2 output is just a notice so I don’t think that is related to any problems.

Jeff

[JC Petit]

Thanks for the reply Jeff,

Yes it just stops at that point. I cannot run any commands afterward. Unfortunately, I cannot SSH to the LoRa and holding down the reset button does not work either to put it back to default IP. Not 100% sure but I think we are running mLinux Conduit.

The steps I took to get the error message is: unplug the poe, plug in the front USB, launch a putty session which is empty until I plug back the POE.

JC

[Jason Reiss]

You can also attach a USB cable to the device port on the back to get a terminal.

Use minicom, teraterm or putty to connect with the serial interface.
http://www.multitech.net/developer/products/multiconnect-conduit-platform/conduit/connecting-to-the-debug-interface/
There is also a port behind the Multitech logo on the front, remove the screw slide the plate off.

[JC Petit]

Hi Jason,

This is where I am plugged in when I get the error.

[John Klug]

If you are using mLinux, there is no factory default code, unless you wrote it yourself. Factory default reset is a feature of AEP.

If ethernet is configured, and ssh is running, it may be possible to log in with ethernet, even if boot does not complete.

Can you ping the ethernet port? Do you know its address? I believe the Conduit will print the ethernet port address on the debug port during boot, if it is a static IP. If you are using DHCP, you may have to get the address from your DHCP server. If you have created settings in /etc/network/interfaces that cause boot to hang, and you are using mLinux you will need to reflash your unit. Remember that if you have a WiFi/BT version of Conduit, you will need to get the images from the support portal as documented on this page:

Downloads:

Downloads

How to flash your unit (look at the U-Boot information):

Flashing mLinux Firmware

[JC Petit]

Hi John,

Yes I know its address but still cannot ssh to it or ping it. Looks like I will need to reflash but since I cannot ssh nor go past the error while connected to serial, I have no clue what to do. And as for the instruction on how to flash, I cannot do any commands on the unit.

[John Klug]

You need to access U-Boot. I assume you can see things happening on the debug port? Repeatedly hit a key on your PC connected through the debug port after you power up the device. You need to be quick.

You should see:
Hit any key to stop autoboot: 0
U-Boot>

You will need the images and a tftp server.

Flashing mLinux Firmware

See:
Using U-boot & TFTP on the flashing firmware page.

[henrik.thuren@netadminsystems.com]

I’m in a similar situation. Neither root/root nor mtadm/root works when I’m trying to login through the usb debug console. I can access U-Boot by interrupting the boot sequence but there’s a password configured which I don’t have.

Is there any way to reset U-Boot password or work around it?

[Jason Reiss]

Is this a lorawan gateway for a lorawan network provider?

[henrik.thuren@netadminsystems.com]

It’s specifically a MultiConnect® ConduitTM IP67 Base Station sold by the Swedish company Blink Services (http://blink.services/). They do provide their own LoRaWAN network operations services.

[Jason Reiss]

It may have been locked by the seller. I would contact them for instructions.

[Author]

Posts