[Marta Soncodi]

Thank you for the support!

Regards,
Marta Soncodi

[Marta Soncodi]

My mLinux Conduit is alive again.

I used tftpd64 from: http://www.softpedia.com/get/Internet/Servers/FTP-Servers/Tftpd32.shtml

A more recent version can be downloaded here:https://tftpd64.codeplex.com/
They even make available the source code: https://tftpd64.codeplex.com/SourceControl/latest#readme.txt

Of course, these downloads come with the risk of untrusted sources.

The more important piece of information for Windows users is that reading the minicom information alone does not give the full answer. TeraTerm and its Control > Macro functionality can be used to set the environment variables in U-boot, using the minicom script referred at http://www.multitech.net/developer/software/mlinux/using-mlinux/flashing-mlinux-firmware-for-conduit/
The actual re-flashing is done by TeraTerm with files being uploaded via tftpd64.

It would be nice if the TeraTerm and equivalent minicom macro information would be available on the main site.

I also verified reset and long reset work again.

• This reply was modified 7 years, 10 months ago by Marta Soncodi.
• This reply was modified 7 years, 10 months ago by Marta Soncodi.
• This reply was modified 7 years, 10 months ago by Marta Soncodi.

[Marta Soncodi]

At this point ping shows ‘host 192.168.2.2 is alive’.
Also, I enabled tftp client on my laptop and verified I can transfer both files via tftpd64.

run krb still does not work:

U-Boot> run krb
macb0: PHY present at 0
macb0: link up, 100Mbps full-duplex (lpa: 0xcde1)
Using macb0 device
TFTP from server 192.168.2.2; our IP address is 192.168.2.1
Filename 'oe_uImage.bin'.
Load address: 0x20000000
Loading: T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
macb0: PHY present at 0
macb0: link up, 100Mbps full-duplex (lpa: 0xcde1)
Using macb0 device
TFTP from server 192.168.2.2; our IP address is 192.168.2.1
Filename 'oe_uImage.bin'.
Load address: 0x20000000
Loading: T T T T

I turned on/off ‘Option negotiation’ in tftpd64 and it makes no difference.

[Marta Soncodi]

You are right:

U-Boot> ping 192.168.2.2
macb0: PHY present at 0
macb0: link up, 100Mbps full-duplex (lpa: 0xcde1)
Using macb0 device
ping failed; host 192.168.2.2 is not alive
U-Boot>

Problem is that in tftp server I only have access to 127.0.0.0.1 (loopback). 192.168.2.2 is dimmed and I cannot select it.

[Marta Soncodi]

Ooops… missed this http://git.multitech.net/cgi-bin/cgit.cgi/meta-multitech.git/plain/contrib/uboot-setenv-mtcdt.minicom

Need to figure-out how to input all those lines without minicom.

[Marta Soncodi]

Looked at NAND Flash Layout again and these need to happen:

0x00200000 oe_uImage.bin
0x01800000 oe_rootfs.jffs2

I guess nand could prepare for nboot but… cannot find manual or documentation for this.

[Marta Soncodi]

Attempting to re-flash in u-boot, not sure which command I should use to transfer the 2 files:

U-Boot> tftpboot oe_uImage.bin
macb0: PHY present at 0
macb0: link up, 100Mbps full-duplex (lpa: 0xcde1)
Using macb0 device
TFTP from server 192.168.2.99; our IP address is 192.168.2.1
Filename 'oe_uImage.bin'.
Load address: 0x22000000
Loading: T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
macb0: PHY present at 0
macb0: link up, 100Mbps full-duplex (lpa: 0xcde1)
Using macb0 device
TFTP from server 192.168.2.99; our IP address is 192.168.2.1
Filename 'oe_uImage.bin'.
Load address: 0x22000000
Loading: T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again

using tftp boot does not make sense since oe_rootfs.jffs2 needs to be transferred too…

Read this too, but did not clarify which command I should use: http://www.multitech.net/developer/forums/topic/connection-refused-after-auto-fash/

[Marta Soncodi]

Here is the init section:

INIT: Entering runlevel: 5
Configuring network interfaces... IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
done.
Starting system message bus: dbus.
macb f802c000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Starting OpenBSD Secure Shell server: sshd
done.
Starting syslogd/klogd: done
Loading [g_serial]
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
lighttpd: disabled in /etc/default
Starting Mosquitto...
lora-network-server: disabled in /etc/default
Starting crond: OK
Found MTAC-LORA-915 with MTAC-LORA-1.0 hardware
No internet connection, waiting...
No internet connection, waiting...

I appreciate the help as I do need to understand how to properly configure and recover the conduit.

[Marta Soncodi]

John, thank you for the re-flash info. mLinux version is 3.2.0 but I may as well use 3.3.6 when re-flashing. (Will use SCP and Tftp32 from softpedia.)

[Marta Soncodi]

Jeff, I have indeed installed TTN LoRa and mp-packet-forwarder is likely waiting for network access.

I had started the “Getting started with mLinux” procedure http://www.multitech.net/developer/software/mlinux/getting-started-with-conduit-mlinux/ and reconfigured for DHCP then conduit got stuck waiting for connection.

At this point changing ipaddress and serverip does not seem to help. Ex. router.us.thethings.network = 13.66.213.36.

Any suggestions on what I might use for ipaddress and serverip to avoid re-flashing the Conduit?

[Marta Soncodi]

Stopped autoboot and got a bit more info:

U-Boot> printenv 
baudrate=115200
bootargs=mem=256M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2
bootcmd=nboot.jffs2 ${loadaddr} 0 ${kernel_addr}; bootm ${loadaddr}
bootdelay=0
ethact=macb0
ethaddr=00:08:00:4a:17:9c
hostname=AT91SAM9G25
ipaddr=192.168.2.1
kernel_addr=0x200000
loadaddr=0x22000000
netmask=255.255.255.0
serverip=192.168.2.2
stderr=serial
stdin=serial
stdout=serial

[Marta Soncodi]

Jason, thank you, it works as described here:

DNS configuration on MLinux

[Marta Soncodi]

OK, found your previous post here: http://www.multitech.net/developer/forums/topic/dns-configuration-on-mlinux/

I have it set up similr to your recommendation:
# Wired interface
auto eth0
iface eth0 inet static
address 192.168.2.100
gateway 192.168.2.1
netmask 255.255.255.0

I have Internet access (ping IP) but not DNS (“us1.loriot.io” translation).

[Marta Soncodi]

Thank you, Jason.

I am connected LAN via Ethernet cable. I set static IP via /etc/network/interfaces – address, netmask, gateway, dns-nameservers (this one is a guess, does not work).

The link you sent does not display results. Please clarify.

[Author]

Posts