Yes. It does somewhat work for me using Ubuntu Jaunty.
First you need to get the cdc-acm module patch, or a newer kernel, as mentioned here.
from dmesg:
[336437.465045] usb 4-1: acm_ctrl_irq – usb_submit_urb failed with result -19<6>usb 4-1: new full speed USB device using uhci_hcd and address 6
[336440.364917] usb 4-1: configuration #1 chosen from 1 choice
[336440.370003] cdc_acm 4-1:1.1: ttyACM0: USB ACM device
When you get a /dev/ttyACM0, you’re good to go.
mtkbabel reading status:
lkarsten@meta:~/osm$ mtkbabel -s 115200 -p /dev/ttyACM0
MTK Test OK
MTK Firmware: Version: 1, Release: AXN_1.0-B_1.3_C01, Model ID: 0002
Log format: (0002003F) UTC,VALID,LATITUDE,LONGITUDE,HEIGHT,SPEED,RCR
Size in bytes of each log record: 34 + (0 * sats_in_view)
Logging TIME interval: 0.00 s
Logging DISTANCE interval: 1.00 m
Logging SPEED limit: 0.00 km/h
Recording method on memory full: (2) STOP
Log status: (000100000100) AUTOLOG_OFF,STOP_WHEN_FULL,ENABLE_LOG
Next write address: 512 (0×00000200)
Number of records: 0
Memory health status (failed sectors mask): FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
lkarsten@meta:~/osm$
Save GPS data to disk:
lkarsten@meta:~/osm$ mtkbabel -s 115200 -l off -p /dev/ttyACM0 -f foo -t -w
Packet checksum error: expected 0×77, computed 0×2C
MTK Test OK
MTK Firmware: Version: 1, Release: AXN_1.0-B_1.3_C01, Model ID: 0002
>> Switch recording to OFF
Log format: (0002003F) UTC,VALID,LATITUDE,LONGITUDE,HEIGHT,SPEED,RCR
Size in bytes of each log record: 34 + (0 * sats_in_view)
Logging TIME interval: 0.00 s
Logging DISTANCE interval: 1.00 m
Logging SPEED limit: 0.00 km/h
Recording method on memory full: (2) STOP
Log status: (000100000100) AUTOLOG_OFF,STOP_WHEN_FULL,ENABLE_LOG
Next write address: 528 (0×00000210)
Number of records: 0
Memory health status (failed sectors mask): FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
>> Retrieving 65536 (0×00010000) bytes of log data from device…
Saved log data: 0.00%
Saved log data: 3.12%
[..]
Saved log data: 96.88%
Total record count: 0
lkarsten@meta:~/osm$
I was smart enough to “test” the erasing first, so the GPS was empty here. It does work, however :)
Erase GPS data:
lkarsten@meta:~/osm$ mtkbabel -s 115200 -p /dev/ttyACM0 -E
MTK Test OK
MTK Firmware: Version: 1, Release: AXN_1.0-B_1.3_C01, Model ID: 0002
>> Erasing log memory…
ERROR: Reading from device: Illegal seek at /usr/bin/mtkbabel line 610.
lkarsten@meta:~/osm$
Data is erased from the GPS, despite of ‘illegal seek’.
In other news; the battery on the unit is a bit unpredictable. It charges from USB. It seems like if you leave it connected (to the _powered_ USB bus) after it is fully charged, it starts to discharge. Leave it by your computer over night, and it’s empty the day after. Silly.