Documentation change only: fix link.

u-blox · Mar 1, 2024 · 93e5257 · 93e5257
1 parent dd3b148
commit 93e5257
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/port/platform/zephyr/README.md b/port/platform/zephyr/README.md
@@ -134,7 +134,7 @@ In that case you must add a device tree `.overlay` file to your build that defin
 ```
 
 # I2C Troubles
-The I2C interface of Zephyr allows the underlying driver quite a lot of flexibility: if you experience problems using GNSS over I2C you should probably start by attaching a monitoring device (e.g. a [Saleae](https://www.saleae.com/ probe) to the I2C lines to see what is going on. For instance, the STM32 I2C drivers have a length limitation somewhere, which means that you will not be able to successfully receive the larger messages (e.g. large configuration messages, RRLP messages) that the GNSS device sends unless you set `maxSegmentSize` in the `uDeviceCfgI2c_t` structure (see [u_device.h](/common/device/api/u_device.h)), or set `i2c-max-segment-size` in the GNSS device entry in your `.overlay` file (see below for how to do that), to something like 255.
+The I2C interface of Zephyr allows the underlying driver quite a lot of flexibility: if you experience problems using GNSS over I2C you should probably start by attaching a monitoring device (e.g. a [Saleae](https://www.saleae.com/) probe to the I2C lines to see what is going on. For instance, the STM32 I2C drivers have a length limitation somewhere, which means that you will not be able to successfully receive the larger messages (e.g. large configuration messages, RRLP messages) that the GNSS device sends unless you set `maxSegmentSize` in the `uDeviceCfgI2c_t` structure (see [u_device.h](/common/device/api/u_device.h)), or set `i2c-max-segment-size` in the GNSS device entry in your `.overlay` file (see below for how to do that), to something like 255.
 
 # Specifying Device And Network Configuration Through The Device Tree
 For those familiar with the Zephyr device tree, it is possible to ignore the device and network configuration structures in the C code and instead set their entire contents through the device tree, binding files for which can be found in [dts/bindings](dts/bindings).