John Klug

Forum Replies Created

Viewing 30 posts - 1 through 30 (of 53 total)
  • Author
    Posts
  • in reply to: Flashing MLinux #26680
    John Klug
    Moderator

    To flash the image during reboot for mlinux, you will do:

    mlinux-firmware-upgrade upgrade-file.bin

    You will always need a file.

    in reply to: Login incorrect #26641
    John Klug
    Moderator

    mLinux factory default settings does not include passwords, unless you write your own code.

    root/root are the default settings for mLinux, but if you build your own image, the password is found in password.txt in the build directory.

    If you cannot log in, you could re-flash your Conduit using U-Boot and tftp.

    See Using U-boot & TFTP:

    Flashing mLinux Firmware

    • This reply was modified 6 years, 6 months ago by John Klug.
    • This reply was modified 6 years, 6 months ago by John Klug.
    in reply to: Ethernet controller model name #26509
    John Klug
    Moderator

    If you mean the built-in ethernet (not an accessory card) it is the Atmel macb Linux driver using the KSZ8091.

    in reply to: custom image – libmpsse #26176
    John Klug
    Moderator

    It should automatically take it from the mirror when the primary source fails. However, our system was a little overtaxed the last couple of days.

    in reply to: custom image – libmpsse #26150
    John Klug
    Moderator

    This seems strange, as we mirror libmpsse on multitech.net:

    http://www.multitech.net/mlinux/sources/libmpsse-1.3.tar.gz

    You should be able to retrieve the file from multitech.net and place it in your downloads directory for the build as well.

    But if you are using our Yocto source, it should be able to retrieve from multitech.net as a mirror.

    in reply to: Debug interface ob conduit AP #25909
    John Klug
    Moderator

    To reset to defaults:

    Reset for mLinux (Factory Defaults or Reboot)

    The debug port is the micro-USB connector on the opposite side of the board as the Ethernet port.

    in reply to: AEP vs mLinux: Does it really matters? #25904
    John Klug
    Moderator

    AEP provides a variety of options for restarting PPP.

    Carriers will not hold PPP up forever, and if AEP is not used, you will need to write your own PPP monitor, or find one. As Jeff said, this is not provided in mLinux.

    An mLinux system may use AEP software, if you contact customer support.

    in reply to: MTCAP mlinux 4.0.1 default password #25820
    John Klug
    Moderator

    File password.txt will contain the password. It is in the same directory with setup.sh.

    in reply to: Best way to shutdown AEP #25818
    John Klug
    Moderator

    From the command line, you can type “/sbin/poweroff”.

    It is easier on the flash memory (less likely to create a bad block). Also, it is better for the battery backed up real time clock (if you have a battery).

    in reply to: Web sever access #25679
    John Klug
    Moderator
    in reply to: Yocto Version #25637
    John Klug
    Moderator

    mLinux 4 is almost through test. If nothing comes up it should be out this month.

    in reply to: BLE 18dBm transmit power? #25599
    John Klug
    Moderator

    The default is the maximum power.

    Did you connect an antenna to the wifi/bt port?

    BLE power is set in the rs9113 driver in /etc/default/rs9113:

    # Power selection
    # 0x00 – For Both TX and RX High Power
    # 0x11 – For Both TX and RX Medium Power
    # 0x22 – For Both TX and RX LOW Power
    # 0x10 – For High Power TX and Medium RX Power
    # 0x20 – For High Power TX and LOW RX Power
    # 0x01 – For Medium TX and RX High Power
    # 0x21 – For Medium Power TX and LOW RX Power
    # 0x02 – For Low Power TX and RX High Power
    # 0x12 – For LOW Power TX and Medium RX Power
    WLAN_RF_PWR_MODE=0x00
    BT_RF_PWR_MODE=0x00

    #Power_mode type
    # 0 – HIGH POWER MODE
    # 1 – MEDIUM POWER MODE
    # 2 – LOW POWER MODE
    BT_RF_TX_POWER_MODE=0
    BT_RF_RX_POWER_MODE=0

    It is set to the highest power by default.

    These same variables apply simultaneously to BLE and standard Bluetooth.

    If these values are changed, it is necessary to reload the driver:

    /etc/init.d/rs9113 stop
    /etc/init.d/rs9113 start

    If you are using bluetoothd, it will need to be restarted as well.

    /etc/init.d/bluetooth stop
    /etc/init.d/bluetooth start

    Likewise if you are using wpa_supplicant, or hostapd, in one of the modes that also supports wifi, these will need to be restarted.

    in reply to: Can not update opkg #23992
    John Klug
    Moderator

    Looking back, this issue was fixed in 3.3.13.

    in reply to: Can not update opkg #23991
    John Klug
    Moderator

    In some levels of mLinux, the file /etc/opkg/mlinux-feed.conf there is a bug, and the URL’s in the file are bad.

    To determine the correct URL, cat /etc/mlinux-version to determine which level of mLinux is installed. (maybe 3.3.6?).

    Then look at available URL’s. They are found by going from:

    Downloads

    This has a link called pre-built packages.

    This goes to a directory called:
    http://www.multitech.net/mlinux/feeds/

    Then you pick the level you desire. If you just want to install additional packages, I would recommend the directory that matches the version of mLinux you already have.

    Then you must edit /etc/opkg/mlinux-feed.conf file, and modify the ‘3.3’ to the exact micro-level of 3.3 you have, such as 3.3.6. There will be several lines in the file with the incorrect path in the URL.

    in reply to: Can not update opkg #23985
    John Klug
    Moderator

    You must successfully do “opkg update” before you can install more packages.

    in reply to: Python 3 Support #23311
    John Klug
    Moderator

    Python 3 will be installable from feeds in mLinux 4.

    Default will be 2.7.12.

    Release date is currently end of June, but that has been a moving target.

    in reply to: Insert data into MySQL #23303
    John Klug
    Moderator

    You would not want to install -dev packages on a Conduit, since usually these are for building objects, and development tools will not fit. You must cross compile if you are to compile objects.

    The list of pre-built packages is referenced on this page:

    Downloads

    Look for pre-built packages. If you follow the links, you will find both MTCAP and MTCDT hardware at various levels.

    Installation instructions are here:

    OPKG Package Manager

    If none of the packages are what you want, you will need to investigate open-embedded, and build what you want using our tools:

    The title of this is building images, but you can build individual packages as well with the bitbake command:

    Building Images

    You could then copy the files in build/tmp/deploy/ipk onto an HTML server of your own, and reconfigure /etc/opkg/mlinux-feed.conf to point at your packages.

    • This reply was modified 7 years ago by John Klug.
    in reply to: RealTimeClock accuracy #23299
    John Klug
    Moderator

    The battery (if present) powers the SAM9G25 Real Time Clock.

    See page 124, section 14:

    http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-11032-32-bit-ARM926EJ-S-Microcontroller-SAM9G25_Datasheet.pdf

    • This reply was modified 7 years ago by John Klug.
    in reply to: Yocto Version #22933
    John Klug
    Moderator

    The still unreleased mLinux 4 is based on Morty currently.

    in reply to: Configure WiFi as WAN in mlinux #22931
    John Klug
    Moderator

    For WiFi access point, see this:

    Wi-Fi Access Point

    For station, see this:

    Wi-Fi Station

    For access point you will probably want dnsmasq, which is available from the feeds using the opkg command.

    in reply to: USB to serial device #22930
    John Klug
    Moderator

    It is not reliable to use two LoRa cards with MTCDT, since the power supply would be marginal, and it would be unreliable. A Serial port uses less power. It should be possible to use serial to USB converter. I have not tried this.

    in reply to: RealTimeClock accuracy #22579
    John Klug
    Moderator

    If ntpd is running, it will periodically update the real time clock (hardware clock). Also, shutdown (/etc/init.d/hwclock.sh stop) will update the real time clock with the system clock.

    There is also the script /etc/network/if-up.d/ntpdate-sync script that can be configured through /etc/default/ntpdate to update the hardware clock, if it can reach an ntpserver, when a network is brought up.

    hwclock –systohc will set the hardware clock to UTC, based on the system clock.

    in reply to: mlinux problem #22392
    John Klug
    Moderator

    You must get AEP images from customer support. They are not publicly available. Only mLinux images are available, which have no GUI. mLinux requires editing files to configure Lora-Network-Server, etc.

    in reply to: mlinux problem #22350
    John Klug
    Moderator

    You can use u-boot to re-flash the firmware:

    Flashing mLinux Firmware

    in reply to: DNS Settings (mlunix) #22097
    John Klug
    Moderator

    I should add that /etc/network/interfaces is ignored in AEP, I believe.

    in reply to: DNS Settings (mlunix) #22096
    John Klug
    Moderator

    Your netmask is questionable:

    netmask 255.255.255.252

    10.x.y.z is usually class A.

    Your netmask would then be 255.0.0.0

    I have never had problems with the gateway line in /etc/network/interfaces.

    in reply to: DNS Settings (mlunix) #22091
    John Klug
    Moderator

    Did you try:

    ping 8.8.8.8

    How about:

    ping [gateway address]?

    in reply to: Conduit not communicating on subnet #22031
    John Klug
    Moderator

    255.255.255.0 would correspond to 192.168.2.6/24

    Not sure if it will fix the issue, but it might

    in reply to: Error when using AT&T SIM Card #22026
    John Klug
    Moderator

    I thought some SIM/modems did not work in context 1. Here is an example chat script with context 3.

    OK ‘AT+CGDCONT=3,”IP”,”YourAPN”‘

    OK ‘ATD*99***3#’

    in reply to: GPS error #22000
    John Klug
    Moderator

    Conduits use U-Blox, not Venus.

    The uBlox documentation is here:

    https://www.u-blox.com/sites/default/files/products/documents/u-blox8-M8_ReceiverDescrProtSpec_%28UBX-13003221%29.pdf

    GPSFIXOK is documented on page 307 and is a single bit.

    If you are seeing an even value, this means you have a bad signal strength, and the GPS was not able to get a “FIX”.

    You can observe the gps output with the gpsmon command run over ssh.

    The conduit documentation for gpsd is here:

    GPSD

Viewing 30 posts - 1 through 30 (of 53 total)