Ticket #1371 (assigned defect)
corrupted data from u-blox
| Reported by: | mdt@… | Owned by: | openmoko-kernel |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | hardware | Version: | GTA02v6 |
| Severity: | normal | Keywords: | |
| Cc: | buglog@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description (last modified by roh) (diff)
i receive wrong nmea sentances with incorrect checksums. it seems that
null-bytes are inserted and/or characters are missing when the debugboard is
connected.
has someone else similar expiriences? did someone play around with gsp, nmea
with the debugboard connected?
Change History
comment:4 Changed 5 years ago by emdete
- Summary changed from receiving nmea has errors when debug board is connected to corrupted data from u-blox
i get corrupted data with debug-board attached and without debug board, with board attached there are just more occurences.
there is no difference which mode is used - nmea-sentences and u-blox-data get corrupted.
i do not get any corruption, if no other functionality is used: a testscript alone that just checks the /dev/ttySAC1 does not show any errors. only my whole app suite (pyneo.org) shows errors and fso's daemons with some other prozesses (i.e. installing packages over usb to nand) shows errors.
Someone should verify this with a debug board v3 and a pre-MP model.