- Mon May 03, 2021 2:38 pm
#225584
Hi,
Again I have a strange issue, this time with the I2C bus.
The uBlox GPS ZOE-M8Q is connected to the Artemis Openlog via the Qwiic Connector. I'm using the ubx binary protocol which works fine.
In rare cases I get an checksum error. I have tracked the issue down and found that the received bytes by the Ambiq Apollo 3 differ from what I'm seeing on the oscilloscope.
The oscilloscope decodes the data to
Needless to say, the issue is present without the oscilloscope, so it needs to be fixed. I'm quite puzzled at the moment. What can be the source of the problem?
Again I have a strange issue, this time with the I2C bus.
The uBlox GPS ZOE-M8Q is connected to the Artemis Openlog via the Qwiic Connector. I'm using the ubx binary protocol which works fine.
In rare cases I get an checksum error. I have tracked the issue down and found that the received bytes by the Ambiq Apollo 3 differ from what I'm seeing on the oscilloscope.
The oscilloscope decodes the data to
Code: Select all
Whereas the Ambiq Apollo 3 receives
0x00 17 DA 00 00 00 11 39 00 00 00 11 00 26 10 01 00 00 11 39 00 00 00 13 00 20 2C 01 00 00 11 39 00 00 00 15 00 24 94 00 00 00 11 39 00 00 00 16 00 3B 4F 00 00 00 11 39 00 00 00 1F 00 1D 46 00~A
Code: Select all
So the first bit of the first byte differs. I have probed the data with the x10 multiplier of the oscilloscope, because even more strange is the fact, when I measure with x1 the issue disappears.80 17 da 00 00 00 11 39 00 00 00 11 00 26 10 01 00 00 11 39 00 00 00 13 00 20 2c 01 00 00 11 39 00 00 00 15 00 24 94 00 00 00 11 39 00 00 00 16 00 3b 4f 00 00 00 11 39 00 00 00 1f 00 1d 46 00
Needless to say, the issue is present without the oscilloscope, so it needs to be fixed. I'm quite puzzled at the moment. What can be the source of the problem?
You do not have the required permissions to view the files attached to this post.