From 8100d4683ca7dac8f78af6964ec568232becc9de Mon Sep 17 00:00:00 2001 From: Stefan Wahren Date: Thu, 11 Dec 2025 17:04:54 +0100 Subject: [PATCH 1/4] Troubleshooting: Add more recent FAQs Signed-off-by: Stefan Wahren --- docs/source/troubleshooting.rst | 52 +++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/docs/source/troubleshooting.rst b/docs/source/troubleshooting.rst index 7182284..55349ae 100644 --- a/docs/source/troubleshooting.rst +++ b/docs/source/troubleshooting.rst @@ -41,6 +41,14 @@ and a `library `_ +(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 `_ . + + Where can I find the device tree sources of the Charge SOM? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ From 8224eb5e2b65d085609d062c219f4c9e15342e49 Mon Sep 17 00:00:00 2001 From: Stefan Wahren Date: Fri, 12 Dec 2025 13:54:48 +0100 Subject: [PATCH 2/4] Troubleshooting: Fix console blocks Signed-off-by: Stefan Wahren --- docs/source/troubleshooting.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/source/troubleshooting.rst b/docs/source/troubleshooting.rst index 55349ae..8c9ade8 100644 --- a/docs/source/troubleshooting.rst +++ b/docs/source/troubleshooting.rst @@ -65,7 +65,7 @@ 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:: +.. code-block:: console root@chargesom:/# cat /proc/tty/driver/fsl-lpuart serinfo:1.0 driver revision: @@ -81,12 +81,13 @@ 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:: +.. code-block:: console - cat /sys/kernel/debug/pinctrl/443c0000.pinctrl/pinconf-pins + 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): . . + pin 0 (IMX93_IOMUXC_DAP_TDI): 0x31e + ... Which LVDS displays have been tested with the Charge SOM EVB? From 286565e8fff77112d2dd2c71c083a39f03faf6a1 Mon Sep 17 00:00:00 2001 From: Stefan Wahren Date: Fri, 12 Dec 2025 13:44:22 +0100 Subject: [PATCH 3/4] Improve CAN documentation Signed-off-by: Stefan Wahren --- docs/source/hardware.rst | 38 +++++++++++++++++++++++++++------ docs/source/troubleshooting.rst | 10 +++++++++ 2 files changed, 42 insertions(+), 6 deletions(-) diff --git a/docs/source/hardware.rst b/docs/source/hardware.rst index 7a4e616..736f478 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,33 @@ 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 permanent, please adapt BitRate value and run the following commands: + +.. code-block:: console + + cat < /etc/systemd/network/can0.network + [Match] + Name=can0 + + [Link] + RequiredForOnline=no + + [CAN] + BitRate=125000 + TripleSampling=yes + EOF + + networkctl reload + networkctl reconfigure can0 + systemctl restart everest + ******************************************** Insulation Monitoring Device (IMD, X9 + X15) @@ -135,7 +160,7 @@ still depend on the pinmuxing of these 16 pins! +---------------+------------------+-----------------------------------+-------------------------------------------+ | SDIO | 1 | | | +---------------+------------------+-----------------------------------+-------------------------------------------+ -| CAN | 1 | | | +| CAN [#]_ | 1 | | | +---------------+------------------+-----------------------------------+-------------------------------------------+ | PWM | 6 | | | +---------------+------------------+-----------------------------------+-------------------------------------------+ @@ -143,6 +168,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 8c9ade8..b01d56d 100644 --- a/docs/source/troubleshooting.rst +++ b/docs/source/troubleshooting.rst @@ -58,6 +58,16 @@ 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? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ From 63b8e48d0238a45a1367a91e57d819806a838512 Mon Sep 17 00:00:00 2001 From: Stefan Wahren Date: Mon, 15 Dec 2025 10:28:11 +0100 Subject: [PATCH 4/4] Hardware: Address CAN comments Signed-off-by: Stefan Wahren --- docs/source/hardware.rst | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/docs/source/hardware.rst b/docs/source/hardware.rst index 736f478..5fe2463 100644 --- a/docs/source/hardware.rst +++ b/docs/source/hardware.rst @@ -1,7 +1,7 @@ .. _hardware.rst: ################### -Hardware interfaces +Hardware Interfaces ################### Since the Charge SOM itself is a module which cannot be used without a carrier board, @@ -90,29 +90,27 @@ The CAN-FD interface is connected to X16, which is a full implementation of the specification version 2.0B. It is available on Linux network interface ``can0``, which has a default bitrate of 1 Mbit/s. -CAN configuration +CAN Configuration ================= -In order to change the default CAN bitrate permanent, please adapt BitRate value and run the following commands: +In order to change the default CAN bitrate of can0 interface, please adapt ``BitRate`` value and +run the following commands: .. code-block:: console - cat < /etc/systemd/network/can0.network - [Match] - Name=can0 - - [Link] - RequiredForOnline=no - + mkdir /etc/systemd/network/can0.network.d + cat < /etc/systemd/network/can0.network.d/bitrate.conf [CAN] BitRate=125000 - TripleSampling=yes 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)