mlinux update

Home Forums Conduit: mLinux Model mlinux update

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #31059
    Florian
    Participant

    hi,

    im trying to update a mtcap from 5.1.8 to 5.2.7

    im trying the update right after i flashed the 5.1.8

    mtcap:/var/volatile# wget http://www.multitech.net/mlinux/upgrades/mtcap/5.1/update-mtcap-5.1.8-5.2.7.bin

    mtcap:/var/volatile# mlinux-firmware-upgrade update-mtcap-5.1.8-5.2.7.bin
    firmware_upgrade: Wrong firmware for this hardware
    firmware_upgrade: hw version: MTCAP-0.0
    firmware_upgrade: firmware model: mtcdt|mtcdtip|mtcdtiphp

    mtcap:/var/volatile# cat /etc/version
    20191018234905

    mtcap:/var/volatile# mts-io-sysfs show lora/hw-version
    MTCAP-LORA-1.5

    mtcap:/var/volatile# cat /etc/opkg/mlinux-feed.conf
    src/gz mlinux-all http://multitech.net/mlinux/feeds/5.1.8/all
    src/gz mlinux-arm926ejste http://multitech.net/mlinux/feeds/5.1.8/arm926ejste
    src/gz mlinux-mtcap http://multitech.net/mlinux/feeds/5.1.8/mtcap

    #31062
    Jason Reiss
    Keymaster

    The full 5.2.7 image is available here.

    http://www.multitech.net/mlinux/images/

    #31063
    Jason Reiss
    Keymaster

    It appears that the mtcap update file is not the correct file.

    #31065
    Florian
    Participant

    when will u fix the mtcap update file?

    #31067
    Florian
    Participant

    thx for the update,

    how can i confirm that the update was successfully?

    the /etc/opkg/mlinux-feed.conf still points to 5.1.8, do i have to edit it manually?

    mtcap:/var/volatile# mlinux-firmware-upgrade update-mtcap-5.1.8-5.2.7.bin
    firmware_upgrade: Checking MD5 for uboot.bin…
    -: OK
    firmware_upgrade: Checking MD5 for install.sh…
    -: OK
    firmware_upgrade: Rebooting

    Broadcast message from root@mtcap (pts/2) (Wed Aug 12 02:21:12 2020):

    The system is going down for reboot NOW!

    mtcap:~$ cat /etc/opkg/mlinux-feed.conf
    src/gz mlinux-all http://multitech.net/mlinux/feeds/5.1.8/all
    src/gz mlinux-arm926ejste http://multitech.net/mlinux/feeds/5.1.8/arm926ejste
    src/gz mlinux-mtcap http://multitech.net/mlinux/feeds/5.1.8/mtcap

    mtcap:~$ cat /etc/version
    20191018234905

    mtcap:~$ cat /etc/mlinux-version
    mLinux 5.1.8
    Built from branch: HEAD
    Revision: 74e26af726444b2928c739b9daa4da5b2327bcc6

    • This reply was modified 3 years, 7 months ago by Florian.
    #32092
    mattdm
    Participant

    The last post on this was a year ago but it doesn’t look like there is a solution. I am experiencing the same issue with a Multitech (mtcdt) conduit when updating from 5.0.0 to 5.1.8. I downloaded the files just fine and ran the mlinux-firmware-upgrade command and the system rebooted, but when I check the version using cat /etc/mlinux-version, it still shows as version 5.0.0

    Question: After the .bin file has been downloaded, is the command that Florian posted above the correct command for updating mlinux?:
    mlinux-firmware-upgrade update-mtcdt-5.1.8-5.2.7.bin

    If so, how can I verify that the mlinux OS has updated successfully?

    #32093
    Steve Kovarik
    Moderator

    Hi Matt

    I have had success flashing mLinux firmware using the ‘Auto-Flash during Reboot – detailed steps’ method described at the link below.

    http://www.multitech.net/developer/software/mlinux/using-mlinux/flashing-mlinux-firmware-for-conduit/

    The mLinux files for this method can be found at the link below.

    http://www.multitech.net/mlinux/images/mtcdt/

    -Best Regards

    #32094
    mattdm
    Participant

    Hi Steve,
    Thanks, I just tried that again using the method in the link you provided on a gateway that I have which has mlinux version 5.0.0 and I tried to update to version 5.1.8. After rebooting, it still shows it as version 5.0.0

    login as: root

    Last login: Tue Sep 7 11:37:40 2021 from 192.xxx.x.xx
    root@matt-49ef:~# mkdir /var/volatile/flash-upgrade
    root@matt-49ef:~# cd /var/volatile/flash-upgrade/
    root@matt-49ef:/var/volatile/flash-upgrade# cat /etc/mlinux-version
    mLinux 5.0.0
    Built from branch: HEAD
    Revision: 479b47ce169dd801a98e17dfe030ad73f40c426d
    root@matt-49ef:/var/volatile/flash-upgrade# wget http://www.multitech.net/mlinux/upgrades/mtcdt/5.0/update-mtcdt-5.0.0-5.1.8. bin
    –2021-09-07 16:50:11– http://www.multitech.net/mlinux/upgrades/mtcdt/5.0/update-mtcdt-5.0.0-5.1.8.bin
    Resolving http://www.multitech.net… 65.126.90.22
    Connecting to http://www.multitech.net|65.126.90.22|:80… connected.
    HTTP request sent, awaiting response… 200 OK
    Length: 11270536 (11M) [application/octet-stream]
    Saving to: ‘update-mtcdt-5.0.0-5.1.8.bin’

    update-mtcdt-5.0.0-5.1.8.bin 100%[==================================================================>] 10.75M 310KB/s in 28s

    2021-09-07 16:50:40 (390 KB/s) – ‘update-mtcdt-5.0.0-5.1.8.bin’ saved [11270536/11270536]

    root@matt-49ef:/var/volatile/flash-upgrade# touch /var/volatile/do_flash_upgrade
    root@matt-49ef:/var/volatile/flash-upgrade# reboot

    Broadcast message from root@matt-49ef (pts/0) (Tue Sep 7 16:51:37 2021):

    The system is going down for reboot NOW!
    root@matt-49ef:/var/volatile/flash-upgrade#

    after reboot:
    login as: root
    root@matt-49ef:~# cat /etc/mlinux-version mLinux 5.0.0
    Built from branch: HEAD
    Revision: 479b47ce169dd801a98e17dfe030ad73f40c426d
    root@matt-49ef:~# date
    Tue Sep 7 16:55:15 PDT 2021
    root@matt-49ef:~#

    #32096
    Steve Kovarik
    Moderator

    Hi Matt

    I was asking that you perform the specific instructions below.
    Are you willing to try that.

    Detailed Steps
    Obtain the required update files from the downloads page. (You can also find these files in your current build of mLinux in the built/tmp/deploy/images directory.) Refer to the Conduit: mLinux Mode, Other Downloads, and click on Pre-Built Images. Select your hardware (currently MTCAP or MTCDT).
    Select the version you want to use.
    Then download the jffs2 file desired (base or factory image) and uImage file. For example:
    mlinux-factory-image-mtcdt-20150527081222.rootfs.jffs2
    uImage–3.12.27-r11.2-mtcdt-20150527052826.bin
    On your PC, rename the new firmware files like this:
    mlinux-factory-image-mtcdt-20150527081222.rootfs.jffs2 → rootfs.jffs2
    uImage–3.12.27-r11.2-mtcdt-20150527052826.bin → uImage.bin
    Connect the Conduit to your PC via an ethernet cable and ssh into it.
    On the Conduit, first create the destination directory:
    mkdir /var/volatile/flash-upgrade
    Copy the files to the device. If using Windows, you’ll need a tool like WinSCP or SCP in Cygwin.
    Using SCP on your PC:
    scp uImage.bin root@192.168.2.1:/var/volatile/flash-upgrade/uImage.bin
    scp rootfs.jffs2 root@192.168.2.1:/var/volatile/flash-upgrade/rootfs.jffs2
    After transferring the files, on the Conduit run:
    For mLinux 3.x:
    Run touch /var/volatile/do_flash_upgrade
    Run reboot
    For mLinux 4 or higher:
    Run sudo touch /var/volatile/do_flash_upgrade
    Run sudo reboot

    -Best Regards

    #32148
    mattdm
    Participant

    Hi Steve,
    So I finally followed those procedures to flash the latest mlinux OS. Unfortunately now it doesn’t connect to WiFi anymore. It kept my SSID/pw in /etc/wpa_supplicant.conf file, but I think the flash overwrote the Redpine software/driver that it was previously using to connect to Wifi.

    -Matt

    • This reply was modified 2 years, 6 months ago by mattdm. Reason: typo
    #32150
    mattdm
    Participant

    Following up on my last response, I was able to do another upgrade to version 5.3.5 using pre-built image that included the redpine software and the WiFi is working now.

    It still isn’t clear how to just use the mlinux updates instead of reflashing the os with a new image.

    • This reply was modified 2 years, 6 months ago by mattdm.
Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.