Changes between Version 27 and Version 28 of Hardware/jCM/dCM3/cSoftware


Ignore:
Timestamp:
Jan 11, 2013, 1:47:32 AM (12 years ago)
Author:
Ilya Chigirev
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Hardware/jCM/dCM3/cSoftware

    v27 v28  
    11[[TOC(Hardware/cCM/cCM3/*, depth=3)]]
    22
    3 === Software Description ===
     3==== Software Description ====
    44As mentioned previously software for the CM3 is developed in the Paradigm C++ Pro programming environment, and uses the Lantronix XPort AR SDK. At the time of this documents writing the SDK being used was release v5.2.0.0 R21. The CM3 works completely independently from the host node, and as soon as power is applied the native Lantronix XPort AR functions, such as network connectivity, start and then the custom
    55written CM software loads.
    66 
    7 ==== Files ====
     7===== Files =====
    88The following is a list of the basic files that are in the SVN repository, and what functionality they contain:
    99 * {{{CM3}}} - Initialization of the CM3, XML configuration, and the main program which runs the two primary threads
    … …  
    1414 * {{{CM3_IDENTITY}}} Contains functions that query the identifying features of the CM and node, like location, IP address, MAC address, etc.
    1515
    16 ==== Initialization ====
     16===== Initialization =====
    1717Upon start-up the CM3 will fist contact broadcast over the network to discover the IP address that should belong to it. Assuming that the MAC address is already in DHCP, an IP address will be assigned to it, and from there the custom CM3 software takes over. Much of the configuration of the device is done through the XML configuration method. [[BR]]
    1818
    … …  
    2424After XML configuration is completed the CM3 will populate the network information back into variables set up in software. This is because a lot of the network information is only available through the XML configuration file and so to recollect it each time you need it takes a long time. The CM3 then sets up the HTTP commands, which allow some basic functions of the CM3 to be executed over XML, and the custom command line interface for the CM3, as described in the Usage section.
    2525
    26 ==== Flashing Firmware ====
     26===== Flashing Firmware =====
    2727There are two primary methods to reflash a CM3, over the network and also through the serial port. This section will describe how to load new firmware onto the device using both methods. The latest 'known good image' can always be found on the [http://www.orbit-lab.org/browser/CM3/trunk/images SVN Repository]
    2828
    29 ===== Flashing firmware over network =====
     29====== Flashing firmware over network ======
    3030 1. open FTP session directly to the CM Lantronix device in terminal client
    3131{{{
    … …  
    4343 * The image '''must be''' sent to the Xpor AR named xport_ar.rom.gz, otherwise the device will not recognize it as new firmware and will not re-flash. Re-flashing the device will take a few minutes, it will reset itself and should come back online with no issues.
    4444
    45 ===== Flashing firmware over serial =====
     45====== Flashing firmware over serial ======
    4646Re-flashing as CM over the serial port should be done when the node is not accessible aver the network, it is a generally slower method than via FTP. Before you can recover the firmware over serial you will need to install Device Installer on your PC. Device Installer is free to download off the lantronix website, and can be found [http://ltxfaq.custhelp.com/app/answers/detail/a_id/644 here]. For this process to work correctly a straight (non-crossover) serial cable must be used.
    4747