FreedomEV repository. Unlocking the full potential of Linux on your EV!
Full launch presentation:
Do not upgrade to 2019.40.1.1; the latest supported version is 2019.36.2.1
*Upgrading to 2019.4 or higher needs additional work to get cron working *
Or look at the FAQ below.
FreedomEV repository. Unlocking the full potential of Linux on your Electric Vehicle!
Getting ready to support Model S and X with ARM based MCU (aka MCU1).
Newer Model S and X and Model 3 have an Intel based MCU, porting should be doable; other location for persistent launch and storage might be needed as well as other adjustments. If you have root on such a car and would like to explore, contact us. Similar for other Electric Vehicles with Linux running on them.
Official FOSDEM 2019 link: https://fosdem.org/2019/schedule/event/tesla_hacking/
This is not made by Tesla Inc., nor officially endorsed (just yet?). We take no responsibility whatsoever for damage, costs, injury or even death caused by this to you or third parties. In certain territories, it might violate local regulations, we don't know about that, and we don't care. We hope FreedomEV will enjoy your car even more. I am tell my Tesla Service Center about what we are doing here. When the car is serviced, I disable all strange stuff so they might not become too confused (unless they ask for it). Tesla car service people have instructions to remove all visible USB attached stuff to not interfere with possible updates, which is a good thing. Also, I don't claim warranty on stuff I broke myself, Tesla has been very reasonable with respect to that. We build this so all changes, apps and additions are on a USB stick. So, when you remove that and reboot the systems, everything is back like it was before. The '/var/freedomevstart' script is the only persistent addition and it stops immediately if the USB stick is not detected.
We hope Tesla will provide - in a not too distant future - a legitimate way for owners to get root on your own car. For example by allowing owners to request a secret ssh token through their web account or car app. Nothing is certain until Elon Musk tweets about it ;) We also hope other electric car manufacturers will be inspired, and allow the community to grow beyond what we currently imagine.
You need root access on the Central Instrument Display of your Tesla Model S or Model X with an ARM based MCU. Currently only tested on my Model X. I suppose it will also work on the Model S as the architecture is very similar. The latest generation of Model S/X and the Model 3 might be more problematic for now as they use an Intel based board instead of the ARM based Linux system. If someone has root to such a Tesla, we might get FreedomEV working. Aside from root access, we need some kind of 'persistence across reboot'. On the MCU 1.0 and 2.0 cars this is easily accomplished using the crontab as it reads from a read/writeable /var filesystem. Model 3 cars are even better closed down and harder to root. Tesla gives high bug bounties for those people finding root exploits and/or persistence across reboots; thus ensuring everybody their cars are safer. These tools and FreedomEV can help security researchers to better analyse and find potential problems. With root access, FreedomEV can be installed with one command: ``` curl https://raw.githubusercontent.com/jnuyens/freedomev/master/install > install && bash install
To fully remove FreedomEV - this will remove the /var/freedomevstart and crontab entry run:
curl https://raw.githubusercontent.com/jnuyens/freedomev/master/remove | bash ```
Additionally a USB stick with the 'Ubuntu for NVIDIA Tegra' based image is necessary:
You need a USB stick to insert into the car - best 16 or 32GB, formatted as ext4. Download and extract the latest image tarball on it as the root user (so the permissions and special files are correct). Download here: https://www.freedomev.com/FreedomEV-1.0-usbstickimage-extract-to-an-ext4-filesystem.tgz If you mounted the stick to /mnt/stick:
cd /mnt/stick tar xvf ~/Downloads/FreedomEV-1.0-usbstickimage-extract-to-an-ext4-filesystem.tgz mv freedomev-1.0-rootfs/* . mv freedomev-1.0-rootfs/.git . sync cd umount /mnt/stickIt depends on the speed of your USB stick if this will take a while. Insert the USB stick into the car, it will hopefully be mounted on a subdirectory of /disk/ Go into the chrooted environment:
bash /disk/usb.*/freedomevstart chroot /disk/usb.*/Update to the latest version of FreedomEV (execute in chroot on the stick / directory): ``` git pull
cd /var/www/html/raspap-webgui git pull ```
And test it out! (see below)
We start out from the NVIDIA Ubuntu image Extract it on a USB stick, use the mounting/chroot script and install extra packages (we don't use them all yet). Ensure you are connected to WiFi to not pull too much extra data over the Tesla network.
apt-get install flex bison liblzo2-dev texinfo zlib1g-dev zlib1g ncurses-dev g++ texinfo subversion m4 gettext texi2html liblzo2-2 libacl1 libacl1-dev libglib2.0-dev autoconf automake libtool git libexif-dev notify-osd ruby-notify zenity x11-apps kde-runtime oneko xpenguins xphoon xjokes kaffeine marble libreadline-dev libc-dev libncurses5-dev libreadline-dev libsqlite3-dev libgtk2.0-dev libagg-dev libfribidi-dev nmap wireshark tcpdump firefox i3 fbi imagemagick mplayer hostapd dnsmasq bridge-utils dstat screen tmux chromium-browser mpg123 feh vim qv4l2 qv4l2 kde-style-breeze-qt4 locate links wget festival festvox-kallpc16k festvox-kdlpc16k festvox-us-slt-hts festvox-don festvox-en1 festvox-rablpc16k festvox-us1 festvox-us2 festvox-us3 xterm konsole xdotool x11-utils xauth xserver-xephyr
On your usb stick you can go to the / filesystem directory and
git clone http://www.github.com/jnuyens/freedomev .For easy access to the applications, adjust your path:
echo "export PATH=$PATH:/freedomev/tools" >> ~/.bash_profile source ~/.bash_profile
cid-message "FreedomEV Upgrade Initiated, prepare to be Pan Galactic Gargleblasted!"
This should show this message on your central display
This should make the colors on you Instrument Cluster (behind the steering wheel) fade slowly
Have a look at the various directories in /freedomev/apps-available they all have a similar structure. These are the apps which are currently available in FreedomEV. Each app is using its own directory. If an app is enabled, a symbolic link is created in the /freedomev/apps directory to the /freedomev/apps-available directory. Adding an app or feature is simple. The most complete way to start out, is by looking at the 0template app in the /freedomev/apps-inprogress/ directory. In this directory apps are located which are not ready 'for prime time' yet, you can see if there's something you can contribute to. These are the files and directories in the 0template directory, most of them are optional: * optional file activation This file is run every time FreedomEV is activated. The USB stick looses power whenever the system goes to a certain sleep state. This file starts the required services as soon as FreedomEV becomes active again. * optional file deactivation This file is run when FreedomEV detects that the USB stick containing the root filesystem is no longer there. At activation this script is copied to the not-chrooted /tmp/freedomev/deactivation-applicationname so it will still be available. Here we can kill processes which can't run properly anyway as their root filesystem is gone. * description.json This file contains the full name of the application as how it will be displayed into the configuration screen. As well as a description, as well as the possibility to hide this application in the web interface. The 00core of FreedomEV provides the core functionality such as the configuration screen, this is uses the 'hidden' option, so it cannot be disabled by accident. Other apps might make use of it. * optional directories: everyminute, everyfiveminutes, everyhour, everyday and everymonth can contain executable scripts. They will be run at those time intervals. Suitable for most periodic tasks.
Is this like rooting a phone? Not really, when rooting a phone, all software components are replaced with an alternative Linux kernel, device drivers and root filesystem. In this case, all software remains the same, including the kernel and root filesystem. An Ubuntu NVIDIA ARM root filesystem is added, not used as a replacement. From it, additional software is started to run on the original Tesla Linux kernel. These processes add additional functionality and the configuration web interface - do not take up too much CPU or RAM. In this way we ensure they don't interfere with proper working of the original software components.
How to get root? We hope that Tesla will give car owners official root access to their cars if they register as 'security researchers'. As you are part of the OpenSource community, and use and extend this software, you might discover a bug or design mistake in one of the Tesla provided software components. Such a bug can have a security implication, and when this is reported to Tesla, they can pay you a 'bug bounty'. Tesla has fixed issues like this in the past immediately ensuring everybody their cars become safer. Until this happens, people with access to the 'Tesla Toolbox' might be able to give root command line access. Desoldering the eMMC also is a possibility, but I imagine this voids the warranty of that component.
Is this for the general public? While the functions in FreedomEV might appeal to everybody, we still consider FreedomEV in its current form, something for thinkerers and 'Linux geeks' or 'Linux Hackers', people who know the operating systems on which the car is running very well. Maybe in the future there will be releases geared at the general public if there's a solution to enable this on all cars, maybe it remains a testbed to try out new things quickly and see what works nice and what's fun.
Will this void my car warranty? We don't believe it will. In any case, we are only making a very small change to the central display to be able to work with the software on the USB stick. During this process, we opened up the car multiple times. Tesla was very helpful and understanding in this process. When I broke off a plastic part, I didn't claim warranty on it and for the extra work I proposed to pay for it. Tesla didn't even charge me for the extra work. Warranty on the other components of the car should not be affected at all.
What about insurance? When you are making modifications to the drive train, or modify your car so its value increases, you should report it to your insurance provider. These requirements change from country to country. But car modification, modding or tuning is a practice that is as old as the car itself. Advice for your specific region/state/country is certainly available online. It is typically focused on things which do matter with respect to safety: changing the suspension, making the car more powerful and things like that. An insurance company can't claim that the cause of an accident is because of an unrelated issue. Also, these cars are built to ensure that even a reboot will not interfere with its safe operation. That being said, insurance companies are not know for being reasonable everywhere. And this FreedomEV project is made specifically so it can be easily enabled and disabled. So you could - for example - insert the USB stick when parked at a Supercharger to enable Hotspot Mode. Of watch movies (when that feature gets added). Watching movies in a car is illegal in most countries unless the car is parked. Whether or not the car is parked can not easily be checked by the software, so if you add this functionality, add the required checks. Cars were never before in scope for us as OpenSource enthousiasts. Glad this is finally changing!
How to contact you? Email me for questions/additions. Pull requests welcome: jasper at linux.com
Interesting related projects: http://github.com/lunars/tesla