diff --git a/docs/source/hardware.rst b/docs/source/hardware.rst
index 7a4e616..5fe2463 100644
--- a/docs/source/hardware.rst
+++ b/docs/source/hardware.rst
@@ -1,8 +1,8 @@
 .. _hardware.rst:
 
-########
-Hardware
-########
+###################
+Hardware Interfaces
+###################
 
 Since the Charge SOM itself is a module which cannot be used without a carrier board,
 the following sections refer to the Charge SOM Evaluation Board as an example.
@@ -86,8 +86,31 @@ the board supports up to two EIA-485 interfaces.
 CAN (X16)
 *********
 
-The CAN-FD interface is connected to X16, which is a full implementation of the CAN FD
-protocol specification version 2.0B. It is available on Linux network interface ``can0``.
+The CAN-FD interface is connected to X16, which is a full implementation of the CAN FD protocol
+specification version 2.0B. It is available on Linux network interface ``can0``, which has a
+default bitrate of 1 Mbit/s.
+
+CAN Configuration
+=================
+
+In order to change the default CAN bitrate of can0 interface, please adapt ``BitRate`` value and
+run the following commands:
+
+.. code-block:: console
+
+   mkdir /etc/systemd/network/can0.network.d
+   cat <<EOF > /etc/systemd/network/can0.network.d/bitrate.conf
+   [CAN]
+   BitRate=125000
+   EOF
+
+   networkctl reload
+   networkctl reconfigure can0
+   systemctl restart everest
+
+The change takes effect immediately, but also persists across reboots and
+firmware updates.
+
 
 ********************************************
 Insulation Monitoring Device (IMD, X9 + X15)
@@ -135,7 +158,7 @@ still depend on the pinmuxing of these 16 pins!
 +---------------+------------------+-----------------------------------+-------------------------------------------+
 | SDIO          | 1                |                                   |                                           |
 +---------------+------------------+-----------------------------------+-------------------------------------------+
-| CAN           | 1                |                                   |                                           |
+| CAN [#]_      | 1                |                                   |                                           |
 +---------------+------------------+-----------------------------------+-------------------------------------------+
 | PWM           | 6                |                                   |                                           |
 +---------------+------------------+-----------------------------------+-------------------------------------------+
@@ -143,6 +166,7 @@ still depend on the pinmuxing of these 16 pins!
 +---------------+------------------+-----------------------------------+-------------------------------------------+
 
 .. [#] The UART7 has RTS/CTS signals available.
+.. [#] Keep in mind that these signals must be connected to a CAN transceiver.
 
 The following table indicates all possible muxing options for these signals.
 By default, the factory shipped configuration for the Charge SOM EVB is that the signals GPIO3_26 and GPIO3_27
diff --git a/docs/source/troubleshooting.rst b/docs/source/troubleshooting.rst
index 7182284..b01d56d 100644
--- a/docs/source/troubleshooting.rst
+++ b/docs/source/troubleshooting.rst
@@ -41,6 +41,14 @@ and a `library <https://github.com/EVerest/everest-core/tree/main/lib/everest/ca
 which uses the CAN interface. This might help as a starting point.
 
 
+How can I access the GPIOs under Linux?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Since the GPIO sysfs interface /sys/class/gpio has been deprecated since Linux 4.8,
+we recommend the usage of chardev GPIO and libgpiod. The modification of the bias
+settings via libgpiod is not yet implemented, so it needs to be done via device tree.
+
+
 What is the difference between CHSTOP_IN and SAFETY_ESTOPx?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -50,6 +58,61 @@ for timing critical use cases. Currently there is no EVerest module, which is ab
 In order to realize realtime emergency stop behavior use the SAFETY_ESTOPx signals, which are connected to the safety processor.
 
 
+Is there a Linux command to check for connection related CAN issues?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Yes
+
+.. code-block:: console
+
+   root@chargesom:/# ip -details -statistic link show can0
+
+
+How can I list the available UARTs?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+All UARTs of the i.MX93 are handled by the fsl-lpuart driver, so the following
+command should list all available UARTs. Please keep in mind that Linux starts
+counting from zero (ttyLP0 = UART1, ...).
+
+.. code-block:: console
+
+   root@chargesom:/# cat /proc/tty/driver/fsl-lpuart
+   serinfo:1.0 driver revision:
+   0: uart:FSL_LPUART mmio:0x44380010 irq:17 tx:9932 rx:0 RTS|CTS|DTR|DSR|CD
+   2: uart:FSL_LPUART mmio:0x42570010 irq:18 tx:12966 rx:26572 RTS|CTS|DTR|DSR|CD
+   3: uart:FSL_LPUART mmio:0x42580010 irq:19 tx:936 rx:617 RTS|CTS|DTR|DSR|CD
+   4: uart:FSL_LPUART mmio:0x42590010 irq:20 tx:0 rx:0 CTS|DSR|CD
+
+
+How can I print the current pin/pad control settings (e.g. bias, drive strength)?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The current PAD control settings are available under Linux only via debugfs,
+but this requires an equivalent pinctrl setting within the device tree:
+
+.. code-block:: console
+
+   root@chargesom:/# cat /sys/kernel/debug/pinctrl/443c0000.pinctrl/pinconf-pins
+   Pin config settings per pin
+   Format: pin (name): configs
+   pin 0 (IMX93_IOMUXC_DAP_TDI): 0x31e
+   ...
+
+
+Which LVDS displays have been tested with the Charge SOM EVB?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The `Distec DD-0700-MC01 <https://www.fortec-integrated.de/en/products/tft-components/tft-displays/detail/fortec-integrated/dd-0700-mc01/>`_
+(7 inch, 800x480 resolution) has been tested with the Charge SOM EVB.
+
+
+I like to create my own DT overlay. Is there an example?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Yes, please have a look at this `commit <https://github.com/chargebyte/linux/commit/125a587a0cf7e8d9db1fdddf9383a67c2b46d107>`_ .
+
+
 Where can I find the device tree sources of the Charge SOM?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^