[Jesse Gilles]

Message received. I am reorganizing the new release into a bitbake layer rather than a custom branch, so it will be in a new repository completely. I am planning to move the current internal git repo onto git.multitech.net soon. We are still doing testing internally so it’s not release ready quite yet.

You can be assured the development platform is definitely not going stale 🙂

Jesse

[Jesse Gilles]

Try the libmodbus recipes in the master branch of the OpenEmbedded git repository.

You can view them here:

http://git.openembedded.org/cgit.cgi/openembedded/tree/recipes/libmodbus

[Jesse Gilles]

See my post on your other thread. If you built and installed the library in /usr/local, I’m guessing it didn’t get cross-compiled to run on the CDP, but instead was compiled to run on your Linux workstation, which isn’t an ARM platform.

Jesse

[Jesse Gilles]

< I have come across this modbus library, ‘libmodbus’. I have compiled and installed it on my system.

It looks like there are bitbake recipes to build libmodbus in the OpenEmbedded git repository. I would suggest copying those into your tree and building libmodbus with bitbake.

Jesse

[Jesse Gilles]

This should not be an issue and would not reduce the life of the flash. The flash life is only affected by erase/write cycles and powering the device up and down should not affect it.

Jesse

[Jesse Gilles]

The device could be powered from a vehicle, but currently it can’t be put into suspend mode, it would simply be powered off if the vehicle is off. Also, the mts_io driver doesn’t support interrupt driven GPIO at this point — it exposes a sysfs interface which allows reading and writing of pins from userspace.

Jesse

[Jesse Gilles]

Ken,

Yes, there are plans and work is currently in progress to release a new CoreCDP version based off a new OE snapshot (currently will be based off the 2011.03 branch).

Also, source code is mirrored on multitech.net:

http://www.multitech.net/corecdp/sources/

The build process is supposed to fall back on this as a source when other locations fail, but if you get a new file with a different MD5 sum, it obviously doesn’t help.

Jesse

[Jesse Gilles]

Whoops, yeah, I meant to have the –in-file option in there, sorry.

[Jesse Gilles]

My suspicion would be that the php executable is getting created with debug info and isn’t getting stripped for some reason, though I can’t say why off hand.

[Jesse Gilles]

Brandon,

mts-id-eeprom is the application you want, but you have to give it the path to the eeprom (which you already also found).

mts-id-eeprom --help will give command-line options.

Running:

mts-id-eeprom /sys/devices/platform/i2c-gpio/i2c-0/0-0056/eeprom

will produce yaml output that you can parse.

Jesse

[Jesse Gilles]

You can either add it to a custom image and reflash the device:

http://www.multitech.net/developer/products/cellular-development-platform/development/creating-a-custom-image/

Or, you can build just the venus-gps package using bitbake and install it on the device:

http://www.multitech.net/developer/products/cellular-development-platform/development/working-with-a-single-recipe/

[Jesse Gilles]

You can fix the port name by writing udev rules that match the device and create a symlink with a specific name.

A google search yielded this as an example:

http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/

[Jesse Gilles]

The external RS232 port is setup to be a DCE port, so the RX and TX lines are swapped compared to your PC serial port (DTE). You’ll need to use a null modem adapter when you’re connecting the serial device to the CDP since the CDP is DCE and your external device is also DCE.

[Jesse Gilles]

The /dev/ttyGS0 is the port for the gadget serial driver, which is operating on the USB device port. The ftdi driver will give you a new tty device to use. Run ‘dmesg’ after you attach the device to see the tty assigned to it.

[Jesse Gilles]

JM,

You don’t need to use minicom to talk to the modem. Linux treats the serial port for the modem (/dev/ttyUSB0) as a file, so you can do reads and writes as if it were a regular file in your C application. There are also C calls you can make to configure the serial port (baud rate, etc).

Here is a page that has some examples, take a look at the section labeled “termios”.

http://en.wikibooks.org/wiki/Serial_Programming/Serial_Linux

You are also free to look at and use the source code for the sms-utils application, which is written in C.

http://git.multitech.net/

Jesse

[Jesse Gilles]

Sorry I didn’t realize this earlier — the sms-utils packages doesn’t currently support the EV2 radio. You can still send/receive SMS with it, but at the moment you’d have to write a utility to do it using the AT commands documented in the manual for the radio. We are hoping to update the sms-utils to support the EV2 in the future.

http://www.multitech.net/developer/products/cellular-development-platform/references/

[Jesse Gilles]

Noah,

The sms utility needs to know which device port to talk to since the various CDP models have different cellular radios in them and therefore can have different device ports.

Just for future reference, an overview of the ports per model is here:

http://www.multitech.net/developer/products/cellular-development-platform/hardware/accessing-hardware-interfaces/

As Bryan mentioned, the H4 model has /dev/ttyUSB3 that you can send AT commands to, it also has /dev/ttyUSB4 as well. This allows you to have a ppp link up on /dev/ttyUSB4 and still issues AT commands (sms, etc) on /dev/ttyUSB3.

Thanks,

Jesse

[Jesse Gilles]

If you are running as root on the CDP, then the .smsconfig should be in /home/root/.smsconfig, so you can just copy the file over using scp and then try it or edit on the box with vi or nano. If that is still giving issues, try passing the –device option on the command line when you run the app. If you run ‘sms’ with no options, it should print out a usage.

[Jesse Gilles]

Good, glad you got it working.

Did you edit your $HOME/.smsconfig file to use the correct port for your modem? You need to edit the “device:” line to use the right port depending on which model of CDP you have. Otherwise, you can set the device using the command line options.

http://www.multitech.net/developer/products/cellular-development-platform/applications/sms-utils/

[Jesse Gilles]

You don’t need to specify the port and IRQ, you should just need to use /dev/ttyS2 (it is already configured with the correct hardware info). I would recommend running microcom on the port with the correct baud rate and confirm that you can send data back and forth?

[Jesse Gilles]

Yeah, using shell variables inside minicom won’t work, so you do have to give the full path to the file you want to run. I would make sure you use the full path and try again. Also, if the path is too long, run minicom from the same directory as where the script is and then just give the filename with no path.

[Jesse Gilles]

Unfortunately, this is likely not a trivial task. Most of the support for building OpenJDK (from Jalimo) was merged into the OE repo after CoreCDP 1.1.1 was branched off it. Building OpenJDK has a lot of dependencies (many recipes) so I don’t think it would be a simple matter of bringing over one directory of recipes and building it.

[Jesse Gilles]

JamVM is the only Java VM that Multi-Tech has tried and tested. It might be possible to use the Cacao VM.

More information is here (some of it old):

http://wiki.openembedded.net/index.php/Java

[Jesse Gilles]

As the error indicates, you also need to install libesmtp and libyaml since sms-utils depends on them.

If you’re building sms-utils into your image and then re-flashing the unit, then this is taken care of automatically.

If you are manually installing the package by copying the ipk file to the unit and running opkg, then you need to also provide all need dependencies.

The third option is to set up a package feed on your development machine so that you can run ‘opkg install sms-utils’ on the CDP and have it download and install everything that is needed.

See the documentation on multitech.net for more information.

Thanks,

Jesse

[Jesse Gilles]

There is a short overview page here:

http://www.multitech.net/developer/products/cellular-development-platform/applications/sms-utils/

And the full source is available here:

http://git.multitech.net/cgi-bin/cgit.cgi/sms-utils.git/

[Jesse Gilles]

You should be using the CoreCDP local.conf file located at corecdp-1.1.1/openembedded/contrib/multitech/local.conf and you shouldn’t need to change any of the variables.

Please see the Getting started page for more info:

http://www.multitech.net/developer/products/cellular-development-platform/getting-started/

You should verify that you can build corecdp-base-image before you try building any other packages that you might want.

Also, in the future, please start a new topic for new questions.

Thanks,

Jesse

[Jesse Gilles]

Just to be sure, are you only using a particular tty port for one thing at a time? In other words, if you have a PPP link up on /dev/ttyUSB3, you can’t use /dev/ttyUSB3 for anything else while that is active.

[Jesse Gilles]

The usage for mts-io-sysfs doesn’t make it very clear, but you have to quote the arguments to reset-monitor (it only takes one string as an argument).

So try this:

mts-io-sysfs store reset-monitor '1948 1 2'

Jesse

[Jesse Gilles]

Yes, upgrading the default python (/usr/bin/python) in CentOS/RHEL is bad and will cause problems I believe. But installing python 2.6 from EPEL doesn’t touch the default python and installs it separately as python26 so it doesn’t break anything with existing python scripts.

Glad you were able to build the base image. jamvm is the Java VM that runs on the CDP, if you don’t need it, then you don’t need to run Java, then I wouldn’t bother building it, it will only make your image larger and take longer to build.

If you do need it, it looks like you are missing the libffi library on your CentOS system, which is needed to build the native (runs on your workstation) version of jamvm. Hopefully you can find a package with yum that provides libffi and try again.

[Jesse Gilles]

I was able to build the corecdp-base-image using CentOS 5.6 and the EPEL repository with python 2.6.

See http://www.multitech.net/developer/forums/topic.php?id=87#post-269 for more information.

[Author]

Posts