[Tom Ooten]

Hi,

I used the TFTP server proposed on the “Flashing mLinux Firmware” page of Multitech Developer Resources, called tftpd32.

About the configuration of it, I followed the following tutorial : http://www.tricksguide.com/how-to-setup-a-tftp-server-tftpd32-windows.html

With this configuration, the error described in post #10754 occured : firmware files can not be copy from the tftp server because they are too heavy.
To fix this, I unchecked the checkbox called “Option negociation”

Regards,

Tom.

• This reply was modified 9 years, 2 months ago by Tom Ooten.

[Tom Ooten]

Alright,

Problem fixed, topic close !
My MultiConnect is re-flashed and works just as when I started with it.

I was unable to copy the files because I checked the checkbox “Option negociation” on TFTP server settings.

Thank you for all your support.

Best Regards,

Tom.

[Tom Ooten]

Hi Jeff,

Okay, I have another problem now, I can not get the files oe_uImage.bin and oe_rootfs.jffs2 from my PC because they are to heavy.
I obtain the following log => TFTP error: ‘Undefined error code’ (0)

I tried with a lighter file (.txt) and it works, I can copy the .txt file from my PC, but not the firmware files.

I think I am very close

Edit : And now after trying this, I can not boot it anymore even with “env defaut -a” and then “save env”, returning this error :

Loading from nand0, offset 0x200000
** Unknown image type
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Tom.

• This reply was modified 9 years, 3 months ago by Tom Ooten.

[Tom Ooten]

Jeff,

Thanks for the tips.

However, I can’t set up the U-boot environment with the minicom, with this command line :

minicom --script=uboot-setenv

The script is running from “setting U-Boot variables…” to “printenv”, then I quit the minicom

So I reboot, interrupt U-Boot, and printenv, but it is still the same environment (with no krb, tftp_kernel and tftp_rootfs)

I tried to setenv manually but errors occurs (syntax error, unknown command ‘nand erase.part bootstarp’)

I think understand that I have to run the uboot-setenv script from U-Boot> but I don’t know how, minicom is not working there.

[Tom Ooten]

Hi again,

I tried the debug mode (micro USB connection in the front of the conduit) and this line appears after boot :

jffs2: notice: (186) check_node_data: wrong data CRC in data node at 0x0883dec8: read 0x103ae9f2, calculated 0xb69d3c7e.

So it seems the flash went wrong

Also, I will try to do the U-Boot TFTP to flash the firmware, but I am not sure about the TFTP. All I have to do is put the oe_uImage.bin and oe_rootfs.jffs2 files in the tftpboot dir (c:\tftpboot ?) and configure the ip adresses ?

[Tom Ooten]

Hi Jeff,

Your point is interesting, I checked both files I have download with the md5sums.text file ans it match, so I suppose the files were not corrupted.
Then I tried to re-flash the conduit with the exact same process than I did last time, but when I reboot the conduit nothing happen (the LEDs do not blink in a progression pattern), even with a SD card

Tom

[Tom Ooten]

Hi again,

The logs on the messages i posted are output from the multitech mlinux model after auto-flashing it with the followed instructions : http://www.multitech.net/developer/software/mlinux/using-mlinux/flashing-mlinux-firmware-for-conduit/ (section “Using Auto-Flash During Reboot”)

To do this I took the following files from the library http://www.multitech.net/mlinux/images/3.1.0/mtcdt/ :

– mlinux-factory-image-mtcdt-20150527081222.rootfs.jffs2
– uImage–3.12.27-r11.2-mtcdt-20150527052826.bin

Should I try using other files for the auto-flash or are those two files okay ?

Tom.

[Tom Ooten]

It seems “/etc/init.d/sshd restart” is doing nothing, no logs on “/var/log/messages” either

sshd is not working

I am off for today, restarting tomorrow on the issue

Thanks a lot to both of you

Tom.

• This reply was modified 9 years, 3 months ago by Tom Ooten.

[Tom Ooten]

Jeff,

Nothing particular on the log messages, exept from errors about jffs2 :

Dec 14 17:38:45 mtcdt user.warn kernel: jffs2: Empty flash at 0x03c6b8d0 ends at 0x03c6c000
Dec 14 17:38:45 mtcdt user.notice kernel: 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.
Dec 14 17:38:45 mtcdt user.info kernel: VFS: Mounted root (jffs2 filesystem) readonly on device 31:8.
Dec 14 17:38:45 mtcdt user.info kernel: devtmpfs: mounted
Dec 14 17:38:45 mtcdt user.info kernel: Freeing unused kernel memory: 156K (c04ef000 - c0516000)
Dec 14 17:38:45 mtcdt user.notice kernel: jffs2: notice: (64) check_node_data: wrong data CRC in data node at 0x03c6b750: read 0xb4fd09ac, calculated 0x53b26c49.
Dec 14 17:38:45 mtcdt user.notice kernel: jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x004417cc: Read 0xffffffff, calculated 0xd09df165
Dec 14 17:38:45 mtcdt user.warn kernel: jffs2: Empty flash at 0x004418c4 ends at 0x00442000
Dec 14 17:38:45 mtcdt user.notice kernel: 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.
Dec 14 17:38:45 mtcdt user.notice kernel: 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.
Dec 14 17:38:45 mtcdt user.err kernel: cdc_acm 1-2.3:1.0: This device cannot do calls on its own. It is not a modem.

And here is my ifconfig, I am pretty sure I have got the right interface up :

root@mtcdt:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:08:00:4A:02:0E
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:34 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3543 (3.4 KiB)  TX bytes:0 (0.0 B)
          Interrupt:23 Base address:0xc000

gre0      Link encap:UNSPEC  HWaddr 00-00-00-00-FF-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1476  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

gretap0   Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1462  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

tunl0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Plus I have this log :

Dec 14 17:41:14 mtcdt user.info kernel: macb f802c000.ethernet eth0: link up (100/Half)

Also, when I ping google, the output is : Network is unreachable

Tom.

• This reply was modified 9 years, 3 months ago by Tom Ooten.
• This reply was modified 9 years, 3 months ago by Tom Ooten.
• This reply was modified 9 years, 3 months ago by Tom Ooten.

[Tom Ooten]

Hi Jeff,

Thanks for the reply.

The output I showed on post #10429 was from “netstat -na”, there is nothing more that is displayed

I wonder if I did well while flashing the Multiconnect, it seems that the mLinux distribution is not the same as before

• This reply was modified 9 years, 3 months ago by Tom Ooten.

[Tom Ooten]

Indeed, it seems that the TCP is not configurated or something like that

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node Path
unix  2      [ ACC ]     STREAM     LISTENING       1157 /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     SEQPACKET  LISTENING        401 /var/run/udev/control
unix  4      [ ]         DGRAM                      1195 /dev/log
unix  3      [ ]         DGRAM                       407
unix  3      [ ]         STREAM     CONNECTED       1161
unix  3      [ ]         DGRAM                       408
unix  2      [ ]         DGRAM                      1198
unix  3      [ ]         STREAM     CONNECTED       1160
unix  2      [ ]         DGRAM                      1285

I know about the gateway definition for connecting on my network subnet, already did it thank you 🙂

[Tom Ooten]

Thank you for the support jason, I can now access the gateway via USB.

But I am still not able to connect via ssh, and here is my /etc/network/interfaces file :

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# Wired interface
auto eth0

iface eth0 inet static
address 192.168.2.1
netmask 255.255.255.0

# Bridge interface with eth0 (comment out eth0 lines above to use with bridge)
# iface eth0 inet manual
#
# auto br0
# iface br0 inet static
# bridge_ports eth0
# address 192.168.2.1
# netmask 255.255.255.0

# Wifi client
# NOTE: udev rules will bring up wlan0 automatically if a wifi device is detected
# and the wlan0 interface is defined, therefore an "auto wlan0" line is not needed.
# If "auto wlan0" is also specified, startup conflicts may result.
#iface wlan0 inet dhcp
#wpa-conf /var/config/wpa_supplicant.conf
#wpa-driver nl80211

I still have a “ssh: connect to host 192.168.2.1 port 22: Connection refused” when I connect with my PC via ethernet

• This reply was modified 9 years, 3 months ago by Tom Ooten.

[Author]

Posts