RPi

2023-06-23T10:49:11Z

ElectronicZeta1:

<languages />
<translate>

'''Warning: RPi support should be considered as experimental. The USB controller has been unstable since the first version. Be prepared to face issues if you try GIMX on the RPi.'''

GIMX can run on many Linux targets, and the [http://www.raspberrypi.org/ the Raspberry Pi] is one of them!

== Setup using pre-made image == 


The simplest way to set up GIMX on a Raspberry Pi is by flashing a pre-made image. See forum user steel_3d's instructions on getting up and running: [http://www.steve-marton.com/gimx/?p=462 Build your own Plug n Play GIMX emulator using Raspberry Pi]

== Hardware considerations == 


Use a USB HUB only if there are no ports available on the RPi.<br />
It is highly recommended to use a HUB with an external power supply.

== USB adapter using the on-board UART interface == 

=== Hardware requirements === 


The on-board UART runs at 0V/3.3V levels, and the AVR USB board has to run at 5V to operate at 16MHz (running at 3.3V would only allow to operate at 8MHz).<br />
Connecting the RPi and the AVR USB board directly may damage the hardware!<br />
One cheap solution is to use a voltage divider:<br />
* Connect both GNDs
* It's safe to connect the TXD pin of the RPi to the Rx pin of the AVR USB board (the GIMX firmwares configure the Rx pin as an input)
* To connect the Tx pin of the AVR USB board to the RXD pin of the RPi, you'll need to convert the voltage level from 0..5V to 0..3.3V.<br />
This can be done with a simple [https://www.allaboutcircuits.com/textbook/direct-current/chpt-6/voltage-divider-circuits/ voltage divider]:
<div class="image200px">[https://gimx.fr/img/wiki/Resistive_divider.png https://gimx.fr/img/wiki/Resistive_divider.png]</div>
Vin is the Tx pin of the AVR USB board, Vout is the RXD pin of the RPi, R1=2.2kΩ , R2=3.3kΩ
* Do not connect any other pin!

=== Sotware adjustments === 


By default, the RPi UART is configured as a serial console.<br />
Disable this serial console using raspi-config:
<pre>
sudo raspi-config
</pre>
Then select:
<pre>
"Advanced Options", "Serial", "No", "Finish"
</pre>
The default configuration does not allow high baudrates.<br />
Enable high baudrates editing /boot/config.txt:
<pre>
sudo nano /boot/config.txt
</pre>
Add the following line at the end of the file:
<pre>
init_uart_clock=8000000
</pre>
Reboot to apply the changes:
<pre>
sudo reboot
</pre>

== GIMX installation == 
<pre>wget https://gimx.fr/download/gimx-raspbian -O gimx.deb
sudo dpkg -i gimx.deb
sudo apt-get update && sudo apt-get -f install</pre>


If you get a "Dependency is not satisfiable: ..." error message, upgrade Raspbian:
<pre>sudo apt-get update && sudo apt-get upgrade
sudo apt-get -f install</pre>

== Stop/disable triggerhappy service == 
[https://github.com/wertarbyte/triggerhappy/blob/master/README Triggerhappy] is a daemon that opens every input device for reading, and that consumes a few percent of the CPU time.


It seems a good idea to stop it while running GIMX.


To stop triggerhappy:
sudo service triggerhappy stop
To disable triggerhappy:
sudo update-rc.d triggerhappy disable

== Run GIMX == 
Read the [[Quick_Start|Quick start page]] to learn how to run GIMX through the GUI.<br />

A good idea is to run GIMX directly from a terminal, without starting a graphical session, which can be done over the network, using a ssh client, or you can [[#Autostart GIMX at boot without GUI]]<br />

Ideally, GIMX should be launched without using the Ethernet port (because it is connected on the USB bus). However, this doesn't seem to cause any issues generally.<br />

More details on command line options on [[Command_line|this page]].<br />

The GUI will help you download the config xmls. If you never run the GUI, you MUST grab the Linux config xmls from here: https://github.com/matlo/GIMX-configurations/tree/master/Linux The Windows xmls are NOT compatible!<br />

== Autostart GIMX at boot without GUI == 
Simply create a file /etc/systemd/system/gimx.service (as root):

<pre>
sudo nano /etc/systemd/system/gimx.service
</pre>

With the following contents:


<pre>
[Unit]
Description=GIMX
After=syslog.target network.target


[Service]
User=pi
Type=simple
# Replace /dev/ttyUSB0 with /dev/ttyAMA0 when using the on-board UART interface
ExecStart=/usr/bin/gimx -p /dev/ttyUSB0 -c LogitechDrivingForceGT_G29.xml --nograb
Restart=always
RestartSec=5


[Install]
WantedBy=multi-user.target
</pre>


Replace ttyUSB0 with your device (/dev/ttyAMA0 when using the on-board UART interface) and LogitechDrivingForceGT_G29.xml with your mapping file (which should be available in the pi home directory as /home/pi/.gimx/config/LogitechDrivingForceGT_G29.xml)


Run <pre>sudo systemctl daemon-reload</pre> to notify systemd about the new file and <pre>sudo systemctl enable gimx && sudo systemctl start gimx</pre> to enable the gimx service start at boot and start it in the same line.

== Notify when GIMX is running using a led == 
In order to have a proper confirmation about if the gimx service is up and running, you can add a simple python script that turns a led on if the gimx service is running.


The file will be located at /home/pi/blink.py:

<pre>sudo nano blink.py</pre>

With the following contents:


<pre>
#!/usr/bin/python
import os
import time
import RPi.GPIO as GPIO


led = 23
button = 18
GPIO.setmode(GPIO.BCM)
GPIO.setup(led, GPIO.OUT)
GPIO.setup(button, GPIO.IN, pull_up_down = GPIO.PUD_UP)


def Shutdown(channel):
GPIO.output(led, True)
time.sleep(0.2)
GPIO.output(led, False)
time.sleep(0.2)
GPIO.output(led, True)
time.sleep(0.2)
GPIO.output(led, False)
os.system("sudo shutdown -h now")


GPIO.add_event_detect(18, GPIO.FALLING, callback = Shutdown, bouncetime = 2000)


while True:
found = False
time.sleep(5)
pids = [pid for pid in os.listdir('/proc') if pid.isdigit()]
for pid in pids:
try:
cmd = open(os.path.join('/proc', pid, 'cmdline'), 'rb').read()
if "gimx" in cmd:
found = True
except IOError: # proc has already terminated
continue
if found == True:
GPIO.output(led, True)
else:
GPIO.output(led, False)
</pre>


As a bonus, you can add a button so when it is pressed, there is a little blink effect, and the pi is shutted down.


<div class="image200px">[https://gimx.fr/img/wiki/PiButtonLed.png https://gimx.fr/img/wiki/PiButtonLed.png]</div>


To start at boot, simply add it to the pi user crontab (crontab -e) as <pre>@reboot python /home/pi/blink.py &</pre>

== Powering on AVR and RPi simultaneously using the on-board UART interface == 
In case you want to power up AVR (Tested on Pro Micro ATmega32u4) and RPi at once (i.e. using PS4 USB port and a USB Y Splitter) using the on-board UART interface, you will need the adjust shown below in order to reset the AVR board from RPi once started.


It is planned to solve this issue on GIMX 8 version [https://github.com/matlo/GIMX/issues/426]


More details on support forum thread [https://gimx.fr/forum/viewtopic.php?f=5&t=1672]


'''Physically'''
* RPi's PIN40 / GPIO21 connected to ATmega32u4 RST pin directly. (Any RPi GPIO pin should works)


'''Logically'''
* New bash script created /home/pi/resetArduino.sh with content shown below:
<pre>
#!/bin/bash

echo 21 > /sys/class/gpio/export
sleep 1
echo out > /sys/class/gpio/gpio21/direction
sleep 1
echo 1 > /sys/class/gpio/gpio21/value
sleep 1
echo 0 > /sys/class/gpio/gpio21/value
sleep 1
echo 1 > /sys/class/gpio/gpio21/value

exit 0
</pre>
* Grant execution permissions
<pre>chmod +x /home/pi/resetArduino.sh</pre>
* Add the new script to boot sequence (like we do with blink.py program)
<pre>
pi@raspberrypi:~ $ crontab -l
@reboot /home/pi/resetArduino.sh && python /home/pi/blink.py &
</pre>

Using this configuration, GIMX is able to start correctly on its first attempt when RPi and ATmega32u4 are powered on from PS4 simultaneously using GPIO instead of CP2102 USB UART.

</translate>

GIMX - User contributions [en]

RPi