Changes between Version 8 and Version 9 of Developer/Simulators/QEMU/CANEmulation


Ignore:
Timestamp:
Jun 3, 2013, 12:57:51 AM (6 years ago)
Author:
C Rempel
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Simulators/QEMU/CANEmulation

    v8 v9  
    22
    33=  Device Requirements  =
     4
     5# sends CAN packets from a guest OS.
     6=  Use Cases / Testing  =
     7the best option is to implement that as simple
     8device
     9  -device can-kvasser-pcican-q
     10or
     11  -device pcican,model=kvasser-pcican-q
     12and use Linux mainlined SocketCAN API to connect virtual device
     13to real CAN hardware (SocketCAN allows multiple applications access)
     14or to SocketCAN Virtual CAN (vcan - TCP/IP lo equivalent).
     15This is straightforward and would result in minimal overhead and latency.
     16
     17The OS will be Linux and the current CAN driver to test will be Socket CAN (as it's maintlined into Linux)=  Excerpts from the email chain  =
    418
    519'''Stefan Weil''': PCI (and USB if they were supported with LinCAN) CAN controller boards
     
    5771'''Paulo B''':
    5872Ok, learnt a bit more...  You could probably implement this in two ways:
    59 1) "-netdev socket" would probably work as a CAN->UDP gateway; 2)
     731) "-netdev socket" would probably work as a CAN->UDP gateway;
     74
     752)
    6076connecting to a virtual CAN interface in the host, created using
    6177SocketCAN (similar to "-netdev tap", e.g. "-netdev cantap").
     
    7793several CAN buses.
    7894
    79 Each CAN controllerwas a TCP client connected to the CAN bus emulation.
     95Each CAN controller was a TCP client connected to the CAN bus emulation.
    8096
    8197The TCP clients sent CAN data packets (length, packet type and data)