Jesse Gilles
Forum Replies Created
-
AuthorPosts
-
Jesse Gilles
BlockedEdit /etc/default/dropbear and add the following line:
DROPBEAR_PORT=x
Where x is your port number.
September 10, 2012 at 6:26 pm in reply to: Mispelling in /etc/ppp/options result in device hanging #4255Blocked> I can go into U-boot but without network, the device can’t tftp the new rootfs.
You should still able to flash the rootfs over Ethernet via U-boot, as BT posted.
BlockedHi Lucas,
I’ve actually just made changes to address this type of issue. It can be fixed by adding udev rules that gives the modem a consistent name, even if the ttyUSB port name changes.
See commit:
This will be included in the next release of CoreCDP, which is currently in testing, but you are free to try the changes now.
If you use the rules from that commit, you can then set your ppp options file to use /dev/modem_at0 and that name will always point to the correct modem port.
Jesse
BlockedThe only way to recover a unit that doesn’t boot up properly is by using the debug serial port.
If it is only ethernet access that is not working, then you can also use the USB device port to log in as BT mentioned.
If you are developing for the OCG, it’s generally a good idea to have access to the debug port, especially if you are making any boot or kernel changes. Once you have working firmware that is reliable, then the debug port shouldn’t be as necessary.
BlockedYou can try applying the patch to the meta-java subdir inside your corecdp directory.
Something like:
cd corecdp-2.1.0/meta-java
patch -p1 < the_patch
BlockedHi Matt,
Yes, OpenJDK is very large compared to Classpath and will increase the size of the root filesystem dramatically — adding JamVM+OpenJDK is about 38MB.
If this is an issue for you, then you can certainly stick with Classpath if it is suitable for your java application. We added OpenJDK because it supports a much, much larger portion of the standard Java library and seems to have fewer bugs. But if your application doesn’t need the extra libraries and is running well with Classpath, you should be fine staying with it.
Jesse
BlockedHi Ken,
CoreCDP 2.1.0 has been tagged, but not officially released yet. Our current process is that we tag builds that are release candidates, they go to our internal test group and then when testing is good, I post release notes and announce the release. This eliminates the need to re-do a build/release simply to change the version number (such as from 2.1.0rc1 to 2.1.0).
However, the changes between 2.0.2 and 2.1.0 mainly affect java support, so if you aren’t using java, then the two builds are almost identical.
The only non-java-related change that would be noticeable would be the addition of SFTP and rsync to the standard base-image.
Jesse
BlockedNo, we haven’t really pursued this as of yet. We are using OpenEmbedded for building the toolchain and it is meant (and most tested) for using on Linux systems.
BlockedNo, You can’t power the OCG off the USB device port.
If you are connecting a USB device to the OCG, it should be connected to the USB Host port, not the device port.
The device port makes the OCG function as a USB device so that you can connect it to a PC or other USB host — the firmware that ships by default has it setup as a USB-serial device that provides a login prompt.
BlockedThe output pins are open collector outputs to make them more flexible for driving different types of circuitry (relays, etc) — this means the pin is floating for a logical 1, and driven to ground for logical 0. If you want to use the output as a standard digital out, you need an external pullup resistor to create a high voltage level.
Here is more information:
Also, I’ve left the pin names on the website as External Input/Output and updated the doc on the mts-io driver to match instead.
BlockedI updated the connector page to rename the pins as “Digital Input/Outputs” to better match with the driver names.
BlockedYou are correct, din6 (Digital Input 6) is the same as External Input 6 — just inconsistent naming. Sorry for the confusion.
Jesse
BlockedYes, you can do that by writing udev rules. There are some examples on this forum and plenty of others online. A quick search should yield lots of info. You can associate named ports (/dev/ttyUSB5) to vendor/product ids for instance.
Jesse
BlockedHi Dave,
The part is an Atmel AT91SAM9G20 processor.
Jesse
BlockedThere are likely patches and workarounds available for some of the incompatibilities in the upstream OpenEmbedded project. You are free to search their mailing lists and git repos and apply fixes you find.
Currently, building CoreCDP 2.0.2 will NOT work with any Ubuntu 11.10 version, that is correct. It’s possible that an update will be made to improve compatibility, but we ran into multiple issues with several software packages at release time, so it was decided not to support it. If you don’t want to bother with trying to fix the build issues, then we recommend using one the tested distributions documented in the release notes.
BlockedShort answers:
> Is the sms-utils C code really just slinging AT commands and putting a nice command line interface on that?
Yes.
> If I connected to the modem’s serial port from Java and piped in the right AT commands, could I do the same thing that sms-utils is doing?
Yes.
🙂
For details on the AT commands per modem, look at the guide for the radio you have. They are on the References page for OCG:
http://www.multitech.net/developer/products/multiconnect-ocg/references/
BlockedYou need to tell gcc to link against the pthread library when it builds.
Add ‘-lpthread’ to your compile command.
BlockedPthreads should work just fine, so something must be not quite right either with your includes or your compile command.
Please post a small code snippet and the command you are using to compile.
February 16, 2012 at 3:06 pm in reply to: Re: creating .ipk packages for “Hello World” in arago #3693BlockedHi,
Multi-Tech doesn’t provide the Arago distribution — it is maintained by TI. We provide CoreCDP, which is only supported on Multi-Tech Open Communications Gateways: models MTCDP and MT100EOCG.
See http://www.multitech.net/developer/products/multiconnect-ocg for more info.
Thanks,
Jesse
BlockedUnfortunately this isn’t possible with the existing hardware design.
This is something that could possibly be available in future hardware revisions.
BlockedAlso, if you are just starting out, you may want to try CoreCDP 2 which has more up-to-date software versions.
BlockedThe environment script should be right inside the main directory extracted from the CoreCDP tarball (corecdp-1.1.1.tar.gz). Extract the tarball, then it should be in the directory named ‘corecdp-1.1.1’.
BlockedAh, sorry, I meant 10.04 LTS, but 11.04 is supported as well. Either 64 or 32-bit is fine.
BlockedYes, Ubuntu 11.10 came out not very long before CoreCDP 2.0.2 and there are build problems with it — so it’s unsupported for now. The release notes specify distributions that are known to work. I recommend installing Ubuntu 11.04 LTS.
February 2, 2012 at 7:51 pm in reply to: Re: Assigining symlinks using UDEV rules for Modem ports #3671BlockedYes, the ports should always enumerate in the same order.
I don’t believe there is any attribute for udev to use that identifies the type of port.
Also, in case it’s useful, another persistent naming scheme is automatically available in /dev/serial/by-id.
February 1, 2012 at 11:02 pm in reply to: Re: Driver modifications, step by step inclusion into the CoreCDP kernel #3659BlockedI don’t know of any HOWTOs off hand regarding power management — you’ll have to look at Atmel documentation for the processor and at the driver, which is located at <linux src>/arch/arm/mach-at91/pm.c in the kernel source.
The easiest way to incorporate your changes into the CoreCDP kernel build is to generate a patch and add it into the kernel recipe. The location of the linux recipes varies depending on which CoreCDP version you are using. The 1.1.1 linux recipe is openembedded/recipes/linux/linux_2.6.32.bb. The 2.0.2 linux recipe is multitech/recipes/linux/linux_2.6.35.bb.
To generate the patch, I recommend looking at the ‘quilt’ tool. Or you can just use diff directly.
BlockedHm, it looks like you did the right thing with the udev rule. Perhaps try changing the priority of your rule so it runs earlier?
Another option is to use the persistent serial dev names instead of /dev/ttyUSBX. Have a look in /dev/serial/by-id.
BlockedUnfortunately, the ntp recipe puts that cron entry in the wrong file.
Per-user crontabs should actually be in /var/cron/tabs. So copy that file to /var/cron/tabs/root and see that should fix it.
You can also run ‘crontab -l’ to see a list of currents jobs for the user you are logged in as. ‘crontab -e’ will let you edit the entries directly using vi.
BlockedIf you keep track of the faxes scheduled from your web service, you can poll the status of them and use that as a status display for outbound faxes. Other things on the status page (status of the modems, inbound faxes, etc) aren’t supported by the API.
BlockedGRE is built into the kernel already, you don’t need to load a module for it.
-
AuthorPosts