Benjamin Dagbert

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: Rollback AEP firmware version to 1.4.1 #23134
    Benjamin Dagbert
    Participant

    thank you for your help, I managed to flash the conduit through the procedure.

    in reply to: Rollback AEP firmware version to 1.4.1 #23130
    Benjamin Dagbert
    Participant

    Hi Jeff,
    The support answered me with the procedure for the Uboot environment, now my conduit boot but i’m still in 1.4.16 and the flash-upgrade and do_flash_upgrade directory doesn’t work. I created both directory, put my .bin and .jffs2 into and touch the do_flash_upgrade directory but nothings happened when I reboot. I still can’t acces to the ip address of the conduit on the net but I can now acces to the serial port.

    I follow this procedure :

    “1. I am using TeraTerm version 4.87.

    https://en.osdn.jp/projects/ttssh2/releases/

    2. Connect Ethernet cable from your Windows PC directly into the Conduit’s Ethernet port in the back and set your

    PC ipaddress to the same subnet as the Conduit. For example,

    Conduit: 192.168.2.1

    PC: 192.168.2.2

    3. You also need to setup a TFTP server on Windows OS PC.

    http://download.cnet.com/Tftpd32/3000-2085_4-10114225.html

    Here is an example of how to configure your TFTP server:

    http://www.tricksguide.com/how-to-setup-a-tftp-server-tftpd32-windows.html

    Notes: Attached is the firmware files for the AEP.

    oe_rootfs.jffs2

    oe_uImage.bin

    Put these two files onto your base directory of your TFTP server

    4. Then using TeraTerm to load the uboot-setenv file to Conduit via Uboot using the Serial Console.

    http://www.multitech.net/developer/products/conduit/connecting-to-the-debug-interface/

    I have also included the uboot-setenv file that will work with TeraTerm and some screen shots of how to

    download it to the Conduit using TeraTerm.

    Notes: Power cycle the unit and immediately kept hitting the space bar on your keyboard to get into Uboot prompt.

    If you miss it, then do it again.

    5. Once, you are able to load it into the Uboot of the Conduit. Type:

    printenv <–List out the current env

    setenv ipaddr xxx.xxx.xxx.xxx <–Set the Ip address of the Conduit.

    setenv serverip xxx.xxx.xxx.xxx <–Set the IP address of your TFTP server.

    saveenv <–Save it

    printenv <–Again to check to make sure it set.

    run krb <–This will automatically upgrade your Conduit.”

    What can I do next ?

    in reply to: Rollback AEP firmware version to 1.4.1 #23116
    Benjamin Dagbert
    Participant

    I’m opening a portal case, thanks for your help.
    I’ll keep you posted when they answer me.

    in reply to: Rollback AEP firmware version to 1.4.1 #23114
    Benjamin Dagbert
    Participant

    Thank you for your help, but now, my conduit don’t want to boot. I connected the DEBUG input and i have to boot it with uboot. When I power my conduit the debug input print :
    “Wrong Image Format for bootm command
    ERROR : can’t get kernel image”
    I downloaded tftpd32, my uImage.bin and rootfs.jffs2 and i created a TFTP server but when i run tftpboot, i see : “WARNING : no boot file name; using ‘COA80201.img’
    TFTP from 127.0.0.1; our IP address is 192.168.2.1; sending through gateway 127.0.0.1”
    It load then start again.

Viewing 4 posts - 1 through 4 (of 4 total)