[Jesse Gilles]

The serial accessory card (MTAC-MFSER) supports RS485 and your best option would be to write an application for mLinux using libmodbus.

Jesse

[Jesse Gilles]

As Brandon pointed out, /etc/resolv.conf is configured by default as a “volatile” file and this scheme works well when using DHCP or when using PPP (cellular). A simple workaround for static configuration is to put something like the following in your /etc/network/interfaces file for eth0.

post-up echo “nameserver 8.8.8.8” > /etc/resolv.conf

Jesse

• This reply was modified 9 years ago by Jesse Gilles.

[Jesse Gilles]

FYI – you can issue a remote reboot command which will reboot the entire device (and thus Node-RED).

[Jesse Gilles]

Mainly the following:

* More CPU cores
* Fast disk I/O (SSD)
* Set BB_NUMBER_THREADS and PARALLEL_MAKE in local.conf based on the number of cores you have. If you keep these low and have more cores available, the build will be much slower than necessary
* Have source code pre-fetched (corecdp tarballs have sources downloaded already so little/no downloading is needed)

Also keep in mind that the initial build of corecdp will take a while, but subsequent builds in the same directory will be incremental and only build what is needed.

[Jesse Gilles]

If you want to enable the hardware watchdog, you can edit the following bbappend file and uncomment the line that brings in the watchdog patch. Then build the new bootstrap and flash it in.

http://git.multitech.net/cgi-bin/cgit.cgi/corecdp.git/tree/multitech/recipes/at91bootstrap/at91bootstrap_2.13.bbappend

# uncomment to enable watchdog in bootstrap
#SRC_URI += ” file://at91bootstrap-2.13-enable-watchdog.patch”

[Jesse Gilles]

Guillermo,

Have you tested this after a cold boot and it still occurs? Or did this only happen after stopping the MultiTech software and then running the Loriot software with out a power cycle in between? It is possible the MTAC-LORA card needs to be reset when switching to the Loriot application and the Loriot software is not doing it.

If you haven’t already, my recommendation would be to try the following:
* Disable MultiTech packet forwarder and network server from starting on boot (see files in /etc/default)
* Power off
* Power on (network server disabled)
* Start Loriot app

If you do the above and still get errors then I would follow Brandon’s advice.

Thanks,
Jesse

[Jesse Gilles]

Fix is pushed to meta-mlinux layer. Thanks again for the patch.

Jesse

[Jesse Gilles]

Dear Mr. Godinez,

The issue got through since it builds fine if you have host ssl libs/headers installed (apt-get install libssl-dev) and was on the list of things to fix. Thanks for the fix, we will integrate it.

Jesse

[Jesse Gilles]

Justyn,

In general, it is safe to power off the device without fear of filesystem corruption. If you have an application that is writing to the flash before the power off, data can certainly be lost, but the filesystem itself should not be corrupted. Only the file being written to could be lost/damaged.

I’m not sure why you had issues with pppd not starting when performing a power off versus a halt. How did you have pppd configured to started on boot?

Jesse

[Jesse Gilles]

The layers are set up as git submodules, so to update things after updating the main repo:

git submodule sync (only needed if submodule URIs have changed)
git submodule update

If you run into file download/checksum issues, I recommend grabbing the release tarball which includes the pre-downloaded sources dir. You could also copy a sources dir from a previous build into a separate area and create a soft link to it. This gives you one source download dir to share between multiple build dirs.

[Jesse Gilles]

If you don’t want to re-clone, you can wipe out the build/tmp dir which is where bitbake puts literally everything it builds and uses.

At the top of your dir:
rm -rf build/tmp

Jesse

[Jesse Gilles]

It also now been posted to multitech.net:

http://www.multitech.net/developer/products/multiconnect-ocg/references/

[Jesse Gilles]

Hi Rafael,

I committed lighttpd 1.4.35 support to the CoreCDP git repository. I would recommend building it and then putting the following lines in your lighttpd.conf to disable SSLv2 and SSLv3.

ssl.use-sslv2 = "disable"                     
ssl.use-sslv3 = "disable"

Jesse

[Jesse Gilles]

Jeeva, please start a new topic for your problem and provide more details about your device and issue. The OCG already includes a basic FTDI USB-serial driver, but perhaps it doesn’t support your device.

Jesse

[Jesse Gilles]

You’ll need to use the CONFIG_SYS_TEXT_BASE value in the patch once you are ready to flash it into the nand since that is where at91bootstrap is putting u-boot.

[Jesse Gilles]

How did you test your u-boot build?

I tested it by flashing it into the nand and then rebooting. I didn’t try executing it directly using ‘go’.

Jesse

[Jesse Gilles]

Hi Tim,

I was able to get u-boot 2012.10 for MT100EOCG/MTCDP working with the following patch:

http://www.multitech.net/downloads/u-boot-2012.10-mtcdp.patch

It was likely hanging due to the difference in CONFIG_SYS_TEXT_BASE. The older at91bootstrap on the EOCG is loading u-boot at a different address than the default in u-boot.

The rest of the patch is for boot defaults and ethernet functionality.

Hope that helps, the same changes may also apply to later versions.

The only issue I’ve noticed is that when I press the Tab key at the u-boot prompt, it hangs — I’m not sure why, but it works otherwise.

Jesse

[Jesse Gilles]

Yes, you should be able to update it without flashing.

After building the updated bash, you’ll find the .ipk at:
build/tmp/deploy/eglibc/ipk/armv5te/bash_3.2-r14.10_armv5te.ipk

Once you get that onto a device by some means (SCP, SD card, etc), you can run ‘opkg install ‘ and it will install the updated package locally. After installing, ‘bash –version’ should show 3.2.54.

I don’t think you will have any issues running it on CoreCDP 2.2.2. If you do, please report back.

Jesse

[Jesse Gilles]

Ian,

A fix has been committed to the CoreCDP git repository that updates bash to 3.2.54 and resolves the recent vulnerabilities.

http://git.multitech.net/cgi-bin/cgit.cgi/corecdp.git/commit/?id=5a9a1b6e0cfabaa591a63e8e637c3b03b806bd59

Are you building a custom image for your project?

Jesse

[Jesse Gilles]

Not quite sure what the issue is. Can you post your apnconf_1.0.bb and your image recipe?

Thanks,
Jesse

[Jesse Gilles]

Klaus,

You can modify the files provided by the multitech “config” recipe. It is located in multitech/recipes/multitech. The network interface file is at multitech/recipes/multitech/config/network/interfaces. The config recipe is what creates the links from /etc to /var/config for the various files that it provides. I would recommend looking at the recipe contents and the startup script to get an idea of how it works.

You can either modify the interfaces file that is already there, or you can write a .bbappend file to the config recipe and provide your own copy of interfaces there.

Changing the files provide by the config recipe only changes the defaults, as BT was pointing out. If you update the rootfs with your new settings, you will need to delete the file(s) in /var/config and reboot (they get unpacked from defaults on boot if they don’t exist).

Hope that helps,
Jesse

[Jesse Gilles]

Lewis,

The error regarding /etc/device_table is really a warning and I don’t think it is related to your issue in any way.

The reason your file isn’t showing up in the image is because it isn’t in a standard path. Bitbake defines the FILES variable to include files located in standard linux locations by default (/etc, /usr/bin, /usr/lib).

You can override the FILES variable and set your custom location by putting the following in your recipe:
FILES_${PN} = "/newFolder"

Or you could add to it:
FILES_${PN} += "/newFolder"

Jesse

[Jesse Gilles]

Just tried a standard 32GB card today (max SDHC size) — it also worked.

Jesse

[Jesse Gilles]

The OCG-E does support SDHC cards. We have tested standard size SD cards up to 8GB and micro SD cards up to 4GB and they have worked.

Jesse

[Jesse Gilles]

Thanks for sharing!

Jesse

[Jesse Gilles]

/media/ram is not needed and you can disable it if you wish. You won’t get much RAM freed up though, tmpfs only uses RAM based on what is stored in the filesystem.

Jesse

[Jesse Gilles]

Sendmail can be invoked periodically if it is trying to email the output of a cron job. It won’t send any mail by default though since it isn’t configured with any SMTP server.

The most likely reason is the default cron job that runs ntpdate periodically to sync the time on the OCG. Feel free to disable it or change the interval.

You can run ‘crontab -l’ as root or look in /var/cron/tabs/root to see the jobs.

Jesse

[Jesse Gilles]

The most likely cause is not having full permissions to the directory where corecdp was extracted.

Recommendations:
Login as a regular user (admin/root is not required)
Extract corecdp somewhere in your home directory and build there

Hope that helps,
Jesse

[Jesse Gilles]

Greg,

There are multiple RAM-based filesystems on the unit by default. If you run ‘mount’ you can look for filesystems of type ‘tmpfs’.

You will find that /var/volatile is also a tmpfs and if you run ‘ls -l’ in /var, you will see that /var/log is a soft link to /var/volatile/log. So /var/log is actually in the tmpfs and therefore in RAM.

Jesse

[Jesse Gilles]

Is your bitbake layer for usage with OpenEmbedded-Core/Yocto? If so, CoreCDP is still using OE Classic for now, so BBFETCH2 may not be the only issue you run into regarding compatibility.

Is this a custom layer or a community-supported one?

Thanks,
Jesse

[Author]

Posts