- Timestamp:
-
08/12/14 01:40:43 (10 years ago)
- Author:
-
PavelPisa
- Comment:
-
/* Introduction to CAN QEMU support */
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v86
|
v87
|
|
4 | 4 | |
5 | 5 | The intention to provide generic CAN subsystem for RTEMS was initial idea for Jin Yang GSoC 2013 project. But lack |
6 | | of common environment for code and RTEMS testing lead to goal change to provide environment which provides |
7 | | complete emulated environment for testing and RTEMS GSoC slot has been donated to work on CAN hardware |
8 | | emulation on QEMU. |
9 | | |
10 | | The PCI addon card hardware has been selected as the first CAN interface to implement because |
| 6 | of common environment for code and RTEMS testing lead to of GSoC goal change. The new goal focused |
| 7 | on preparation of complete emulated environment for CAN drivers testing and RTEMS GSoC slot has been |
| 8 | in fact donated to work on CAN hardware emulation implementation for QEMU project. |
| 9 | |
| 10 | The PCI addon card hardware has been selected as the first CAN interface to be implement because |
11 | 11 | such device can be easily connected to systems with different CPU architectures (x86, PowerPC, ARM, etc.). |
12 | | We decided to focus on SJA1000 chip, because it is spread standalone controller variant. As for the |
13 | | concrete card we have selected Kvaser PCI which we (mentors from [http://www.cvut.cz/ Czech Technical University] [http://dce.fel.cvut.cz/en/department/organizational-structure/industrial-informatics-group IIG group]) because we have more these cards in |
| 12 | We decided to focus on SJA1000 chip, because it is widespread standalone controller variant. As for the |
| 13 | concrete card, we have selected Kvaser PCI because we (mentors from [http://www.cvut.cz/ Czech Technical University] [http://dce.fel.cvut.cz/en/department/organizational-structure/industrial-informatics-group IIG group]) use more these cards in |
14 | 14 | our project and can compare emulated HW behavior with real hardware. We selected interfacing |
15 | | to SocketCAN (Linux kernel standard CAN API/drivers) on QEMU host side to connect emulated controler |
16 | | CAN bus to virtual CAN network, monitoring tools or to real CAN hardware bus. |
| 15 | to SocketCAN (Linux kernel standard CAN API/drivers) on QEMU host side to connect emulated controller |
| 16 | CAN bus to virtual CAN network, monitoring tools or to real CAN bus wired network. |
17 | 17 | = CAN QEMU Sources and Testing = |
18 | 18 | |