docs/arm/sabrelite: Mention FlexCAN support

Also added example command line usage of the Sabrelite board
with FlexCAN controllers.

Signed-off-by: Matyáš Bobek <matyas.bobek@gmail.com>
Signed-off-by: Pavel Pisa <pisa@fel.cvut.cz>
Tested-by: Pavel Pisa <pisa@fel.cvut.cz>
Reviewed-by: Bernhard Beschow <shentey@gmail.com>
Reviewed-by: Pavel Pisa <pisa@fel.cvut.cz>
Message-id: 19407fc30bdf6b264d1c093a82903609e9cfee48.1782140438.git.matyas.bobek@gmail.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
This commit is contained in:
Matyáš Bobek
2026-06-22 18:08:12 +02:00
committed by Peter Maydell
parent b3d4fc22f6
commit e2929b3bc9
2 changed files with 25 additions and 0 deletions

View File

@@ -24,6 +24,7 @@ The SABRE Lite machine supports the following devices:
* 4 SDHC storage controllers
* 4 USB 2.0 host controllers
* 5 ECSPI controllers
* 2 FlexCAN CAN controllers
* 1 SST 25VF016B flash
Please note above list is a complete superset the QEMU SABRE Lite machine can

View File

@@ -173,6 +173,30 @@ The test can also be run the other way around, generating messages in the
guest system and capturing them in the host system. Other combinations are
also possible.
Examples on how to use CAN emulation for FlexCAN on SabreLite board
-------------------------------------------------------------------
FlexCANs are connected to QEMU CAN buses by passing the bus IDs as machine
properties:
* property ``canbus0`` for connecting ``flexcan1``
* property ``canbus1`` for connecting ``flexcan2``
Note that upstream Linux SabreLite DTs have only a single FlexCAN (``flexcan1``)
enabled.
An example command to run QEMU emulating a Sabrelite development board
with both FlexCANs connected to a single QEMU CAN bus (called ``qcan0``),
bridged to host system ``can0`` interface::
qemu-system-arm -M sabrelite -smp 4 -m 1G \
-object can-bus,id=qcan0 \
-machine canbus0=qcan0 -machine canbus1=qcan0 \
-object can-host-socketcan,if=can0,canbus=qcan0,id=qcan0-socketcan \
-kernel ... -dtb ... -initrd ...
Note that in the Linux guest, bitrate for the FlexCAN device is ignored,
but needs to be set via the ``ip`` command.
Links to other resources
------------------------