Trying to get eps to work with Garmin Geko 201 on Zaurus 5500 rom 3.10, and not having much luck. Here is what I have tried. I installed the eps_arm.0.9.1c.ipk and javacommapi_1.0_arm.ipk packages in RAM, using the standard package installer. EPS runs but appears not to communciate with the GPS in Garmin interface mode. I also tried the Display NMEA Output in the GPS menu, and appeared to get nothing also. I know the NMEA works because I have used other applications with the same cables on this machine and they display the NMEA output correctly.
In the GPS menu of EPS, Comm Ports shows a little tick mark when the arrow is selected, and not something like /dev/stty0, which is what I would expect. Reading the java comm api documentation suggested it was because I might not have the javax.comm.properties file installed, in which case you would get no ports.
I verified I have javax.comm.properties in the /home/QtPalmtop/lib area, which was part of the initial installation. The line in that file says Driver=gnu.io.RXTXCommDriver.
Now I thought I might need to load rxtx. I tried loading rxtx for linux, and put RXTXcomm.jar, librxtxSerial.so, librxtxParallel.so in the /home/QtPalmtop/lib directory. Still no luck. Do you have suggestions on what I might try next?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I found that by running eps in the terminal I could see error messages from rxtx complaining about not having permissions to create a lock in /var/lock. Running chmod 777 from 775 on this directory allowed eps to run from the terminal and the /dev/tty0, /dev/tty1, and /dev/tty2, show up in the comm ports menu correctly.
Two problems remain: still does not run correctly when activated from Jeode tab - I don't know why, since runeps works from the terminal; also, waypoints load with garbage (binary) names from the Geko 201 GPS - I think this may be because Garmin has changed the waypoint protocol for this new GPS device, but I am not sure.
If in my explorations I find more, I will post here for others.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trying to get eps to work with Garmin Geko 201 on Zaurus 5500 rom 3.10, and not having much luck. Here is what I have tried. I installed the eps_arm.0.9.1c.ipk and javacommapi_1.0_arm.ipk packages in RAM, using the standard package installer. EPS runs but appears not to communciate with the GPS in Garmin interface mode. I also tried the Display NMEA Output in the GPS menu, and appeared to get nothing also. I know the NMEA works because I have used other applications with the same cables on this machine and they display the NMEA output correctly.
In the GPS menu of EPS, Comm Ports shows a little tick mark when the arrow is selected, and not something like /dev/stty0, which is what I would expect. Reading the java comm api documentation suggested it was because I might not have the javax.comm.properties file installed, in which case you would get no ports.
I verified I have javax.comm.properties in the /home/QtPalmtop/lib area, which was part of the initial installation. The line in that file says Driver=gnu.io.RXTXCommDriver.
Now I thought I might need to load rxtx. I tried loading rxtx for linux, and put RXTXcomm.jar, librxtxSerial.so, librxtxParallel.so in the /home/QtPalmtop/lib directory. Still no luck. Do you have suggestions on what I might try next?
Well, I found that by running eps in the terminal I could see error messages from rxtx complaining about not having permissions to create a lock in /var/lock. Running chmod 777 from 775 on this directory allowed eps to run from the terminal and the /dev/tty0, /dev/tty1, and /dev/tty2, show up in the comm ports menu correctly.
Two problems remain: still does not run correctly when activated from Jeode tab - I don't know why, since runeps works from the terminal; also, waypoints load with garbage (binary) names from the Geko 201 GPS - I think this may be because Garmin has changed the waypoint protocol for this new GPS device, but I am not sure.
If in my explorations I find more, I will post here for others.