Hi
We seem to be getting corruption of received data from a ublox GPS unit
To me it looks like a fifo overrun of some sort??
background:
I'm attempting to use 6.3.3 as a new base for one of our systems.
Previously it was using 5.1.7 as a base.
The uart in question is one of the two in the Cyclone V SOC HPS.
And to muddy the waters the linux console TTYS0 is the other Uart from
the same HPS core
Yet the console appears to be working ok.
Note all other libs and apps are at the same revision and build, it is
only the kernel that is different.
Both versions of the kernel are also built using the same bitbake bsdk..
Seeing the following with 6.3.3:
00000000: 45 58 54 20 43 4F 52 45 20 33 2E 30 31 20 28 31 | EXT CORE
3.01 (1
00000010: 31 31 31 34 31 29 00 00 00 00 00 00 00 00 30 30 |
11141)........00
00000020: 30 38 30 30 30 30 00 00 52 4F 4D 20 42 41 53 45 |
080000..ROM BASE
00000030: 20 32 2E 30 31 20 28 37 35 33 33 31 53 00 00 00 | 2.01
(75331S...
00000040: 00 00 00 00 00 00 00 00 00 00 00 00 53 42 41 53 |
............SBAS
00000050: 3B 49 4D 45 53 3B 51 5A 53 53 00 00 00 00 00 00 |
;IMES;QZSS......
00000060: 00 00 00 00 00 00 00 00 00 00 01 3D 29 00 00 00 |
...........=)...
00000070: 00 00 00 00 00 00 46 57 56 45 52 3D 54 49 4D 20 |
......FWVER=TIM
00000080: 31 2E 31 30 00 00 00 00 00 00 00 00 00 00 00 00 |
1.10............
00000090: 00 00 00 00 50 52 4F 54 56 45 52 3D 32 32 2E 30 |
....PROTVER=22.0
000000a0: 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
0...............
000000b0: 00 00 4D 4F 44 3D 4C 45 41 2D 4D 38 54 2D 30 00 |
..MOD=LEA-M8T-0.
000000c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
................
000000d0: 46 49 53 3D 30 78 45 46 34 30 31 35 20 28 31 30 |
FIS=0xEF4015 (10
000000e0: 30 31 31 31 29 00 00 00 00 00 00 00 00 00 47 50 |
0111).........GP
000000f0: 53 3B 47 4C 4F 3B 47 41 4C 3B 42 44 00 00 00 00 |
S;GLO;GAL;BD....
00000100: 00 00 | ..
But should be seeing this as shown on 5.1.7:
Excuse the offset (due to this frame also showing the packet id's and
lengths)
But the body of the frame is what we should be seeing.
00000000: B5 62 0A 04 FA 00 45 58 54 20 43 4F 52 45 20 33 | µb..ú.EXT
CORE 3
00000010: 2E 30 31 20 28 31 31 31 31 34 31 29 00 00 00 00 | .01
(111141)....
00000020: 00 00 00 00 30 30 30 38 30 30 30 30 00 00 52 4F |
....00080000..RO
00000030: 4D 20 42 41 53 45 20 32 2E 30 31 20 28 37 35 33 | M BASE
2.01 (753
00000040: 33 31 29 00 00 00 00 00 00 00 00 00 46 57 56 45 |
31).........FWVE
00000050: 52 3D 54 49 4D 20 31 2E 31 30 00 00 00 00 00 00 | R=TIM
1.10......
00000060: 00 00 00 00 00 00 00 00 00 00 50 52 4F 54 56 45 |
..........PROTVE
00000070: 52 3D 32 32 2E 30 30 00 00 00 00 00 00 00 00 00 |
R=22.00.........
00000080: 00 00 00 00 00 00 00 00 4D 4F 44 3D 4C 45 41 2D |
........MOD=LEA-
00000090: 4D 38 54 2D 30 00 00 00 00 00 00 00 00 00 00 00 |
M8T-0...........
000000A0: 00 00 00 00 00 00 46 49 53 3D 30 78 45 46 34 30 |
......FIS=0xEF40
000000B0: 31 35 20 28 31 30 30 31 31 31 29 00 00 00 00 00 | 15
(100111).....
000000C0: 00 00 00 00 47 50 53 3B 47 4C 4F 3B 47 41 4C 3B |
....GPS;GLO;GAL;
000000D0: 42 44 53 00 00 00 00 00 00 00 00 00 00 00 00 00 |
BDS.............
000000E0: 00 00 53 42 41 53 3B 49 4D 45 53 3B 51 5A 53 53 |
..SBAS;IMES;QZSS
000000F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
................
00000100: 01 3D | .=.
As you can see it looks like the frame thats received on the 6.3.3
kernel is mangled?
This same message is just being requested over and over again from the
GPS unit.
The offset where the tears occur looks to be pretty similar between each
poll request.
Usually the 1 at the end of the (75331 is where the first tear occurs.
I'd appreciate some quidance in how to track this down as there appears
to have been a reasonable amount of work done to this driver and the
serial core between these two versions.
Cheers
Richard Tresidder
