diff options
| -rw-r--r-- | getting-started/footers/intel-footer.md | 10 | ||||
| -rw-r--r-- | getting-started/machines/R-Car-Starter-Kit-gen3.md | 36 | ||||
| -rw-r--r-- | getting-started/machines/porter.md | 2 | ||||
| -rw-r--r-- | getting-started/setup-sdk-environment.md | 12 | ||||
| -rw-r--r-- | getting-started/troubleshooting.md | 12 | ||||
| -rw-r--r-- | sec-blueprint/04-adversaries.md | 65 |
6 files changed, 92 insertions, 45 deletions
diff --git a/getting-started/footers/intel-footer.md b/getting-started/footers/intel-footer.md index e9d9832..191ff98 100644 --- a/getting-started/footers/intel-footer.md +++ b/getting-started/footers/intel-footer.md @@ -8,6 +8,16 @@ Multiple options are avaiable but dd and tar can very easily let you down due to The script [mkefi-agl.sh](https://github.com/dominig/mkefi-agl.sh) has been done to help you.<br> The option -h will print the help and the option -v will detailled the operation and ease any debug.<br> +## Selecting the SD or USB to boot. +When booting a Minnowboard or a Joule you can change the default boot device by hitting F2 during initial UEFI boot. +It's easier to acheive it in the right time with a USB keyboard than via serial link. +During boot USB hub are not supported, you need to connect the keyboard directly in the USB socket.<br> +It's also preferable to use F9 and to change the boot order once for all.<br> +Please note: You can only change the boot order, when a valid device is inserted in the corresponding port (USB or SD). + +The Minnow, Joule, many laptops and NUCs will not accept to boot with some USB3 stick. If you have some trouble to get your USB3 stick detected during boot, swap it for a USB2. In anycase working with SD card is faster to flash and to boot. SD should be prefered.<br> +The Joule seems to refuse to boot with my SD-HC-I type cards while I had no problem with the Minnow. If you work with a Joule, use regular SD-HC (mode 4 and 10 work fine) + ## Serial debug Port diff --git a/getting-started/machines/R-Car-Starter-Kit-gen3.md b/getting-started/machines/R-Car-Starter-Kit-gen3.md index a89134a..e18de67 100644 --- a/getting-started/machines/R-Car-Starter-Kit-gen3.md +++ b/getting-started/machines/R-Car-Starter-Kit-gen3.md @@ -1,4 +1,4 @@ -# AGL Kickstart on Renesas R-Car Starter Kit Gen3 (h3ulcb, m3ulcb) +# AGL Kickstart on Renesas R-Car Starter Kit Gen3 V2.16 (h3ulcb, m3ulcb) Here is a non exhaustive list of hardware parts that could be used to setup the R-Car Starter Kit Gen3 board development environment: @@ -23,9 +23,9 @@ The following documents may also be helpful: Before setting up the build environment, you need to download the proprietary drivers. -* Download Renesas graphics drivers with a "click through" license from Renesas website [Link][rcar demoboard] +* Download Renesas graphics drivers with a "click through" license from Renesas website [Link][rcar Linux] and [Link][rcar Linux Drivers] * Under the Target hardware: **R-Car H3/M3** section. - + #### Note: * You have to register with a free account on MyRenesas and accept the license conditions before downloading them the drivers. @@ -36,10 +36,10 @@ Here after is an example of the typical files downloaded at the time of writing: ``` chmod a+r $XDG_DOWNLOAD_DIR/*.zip -ls -l $XDG_DOWNLOAD_DIR +ls -1 $XDG_DOWNLOAD_DIR total 8220 --rw-r--r--. 1 1664 agl-sdk 4.5M Dec 8 15:23 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.zip --rw-r--r--. 1 1664 agl-sdk 2.5M Dec 8 15:24 R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20160906.zip +-rw-r--r--. 1 1664 agl-sdk 4.5M Dec 8 15:23 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170125.zip +-rw-r--r--. 1 1664 agl-sdk 2.5M Dec 8 15:24 R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170125.zip ``` ## Setting up the build environment: @@ -73,12 +73,14 @@ In case of missing graphics drivers, you could notice an error message as follow [snip] --- fragment /home/working/workspace_agl_master/meta-agl/templates/machine/h3ulcb/50_setup.sh /home/working/workspace_agl_master /home/working/workspace_agl_master/build_gen3 -The graphics and multimedia acceleration packages for the R-Car Gen3 board can be download from : - <http://www.renesas.com/secret/r_car_download/rcar_demoboard.jsp> - -These 2 files from there should be store in your'/home/ronan/Téléchargements' directory. - R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.zip - R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20160906.zip +The graphics and multimedia acceleration packages for +the R-Car Gen3 board can be downloaded from: + https://www.renesas.com/en-us/software/D6000821.html + https://www.renesas.com/en-us/software/D6000822.html + +These 2 files from there should be store in your'/home/devel/Téléchargements' directory. + R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170125.zip + R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170125.zip /home/working/workspace_agl_master/build_gen3 --- fragment /home/working/workspace_agl_master/meta-agl/templates/base/99_setup_EULAconf.sh --- end of setup script @@ -168,7 +170,8 @@ lsblk └─sdc2 8:34 1 788M 0 part ``` -**IMPORTANT NOTE**: This is a critical operation, each computer is different and removable devices can change from time to time: so you should repeat this operation each time you insert the microSD card to confirm the device name. +**IMPORTANT NOTE**: This is a critical operation, each computer is different and removable devices can change from time to time: +so you should repeat this operation each time you insert the microSD card to confirm the device name. In the example above, we see: * the first SATA drive as 'sda'. @@ -322,7 +325,9 @@ The lighter of the 3 is “picocom” (it has less dependencies). ## Plug a USB cable from your computer to the serial CP2102 USB port (micro USB-A). -With “dmesg” you can check the device created for the serial link. Usually, it's /dev/ttyUSB0 but the number may vary depending on other USB serial ports connected to the host. To get it, you must switch the board on. +With “dmesg” you can check the device created for the serial link. +Usually, it's /dev/ttyUSB0 but the number may vary depending on other USB serial ports connected to the host. +To get it, you must switch the board on. For example: ``` @@ -590,7 +595,8 @@ Generic guide on how to add a new service in the BSP. [R-car m3ulcb]: http://elinux.org/R-Car/Boards/M3SK [R-car h3ulcb]: http://elinux.org/R-Car/Boards/H3SK [R-car yocto]: http://elinux.org/R-Car/Boards/Yocto-Gen3 -[rcar demoboard]: https://www.renesas.com/en-eu/solutions/automotive/rcar-demoboard.html +[rcar Linux]: https://www.renesas.com/en-us/software/D6000821.html +[rcar Linux Drivers]: https://www.renesas.com/en-us/software/D6000822.html [Iot.bzh AGL-Kickstart-on-Renesas-Porter-Board]: http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Kickstart-on-Renesas-Porter-board.pdf [Iot.bzh AGL-Devkit-Image-and-SDK-for-Porter]: http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Devkit-Image-and-SDK-for-porter.pdf [Iot.bzh AGL-Devkit-Build-your-1st-AGL-Application]: http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Devkit-Build-your-1st-AGL-Application.pdf diff --git a/getting-started/machines/porter.md b/getting-started/machines/porter.md index fe585fc..f3f6d15 100644 --- a/getting-started/machines/porter.md +++ b/getting-started/machines/porter.md @@ -364,7 +364,7 @@ setenv ethaddr 2e:09:0a:00:75:b5 ``` setenv bootargs_console 'console=ttySC6,38400 ignore_loglevel' setenv bootargs_video 'vmalloc=384M video=HDMI-A-1:1920x1080-32@60' -setenv bootargs_root 'root=/dev/mmcblk0p1 rootdelay=3 rw rootfstype=ext3 rootwait' +setenv bootargs_root 'root=/dev/mmcblk0p1 rootdelay=3 rw rootfstype=ext4 rootwait' setenv bootmmc '1:1' setenv bootcmd_sd 'ext4load mmc ${bootmmc} 0x40007fc0 boot/uImage+dtb' setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} ${bootargs_root}; run bootcmd_sd; bootm 0x40007fc0' diff --git a/getting-started/setup-sdk-environment.md b/getting-started/setup-sdk-environment.md index 0e9e7cd..1435b50 100644 --- a/getting-started/setup-sdk-environment.md +++ b/getting-started/setup-sdk-environment.md @@ -35,12 +35,12 @@ chmod a+w ~/ssd ~/devel ### Get docker image #### Pre-built image -A pre-built image is available on [IoT.bzh](http://iot.bzh) public site and can be used directly. +A pre-built image is available on automotivelinux download public site and can be used directly. First, download and load the image in your local Docker instance: ```bash -wget -O - http://iot.bzh/download/public/2016/docker/docker_agl_worker-3.0.tar.xz | sudo docker load; +wget -O - https://download.automotivelinux.org/AGL/snapshots/sdk/docker/docker_agl_worker-3.0.tar.xz | sudo docker load; docker images; REPOSITORY TAG IMAGE ID CREATED SIZE docker.automotivelinux.org/agl/worker 3.0 42009148bc03 6 days ago 926.9 MB @@ -48,7 +48,7 @@ docker images; hello-world latest c54a2cc56cbb 5 months ago 1.848 kB ``` #### Rebuilt image -The Docker image for AGL Worker can be rebuilt using the scripts published here [agl-docker-worker](https://github.com/iotbzh/agl-docker-worker). +The Docker image for AGL Worker can be rebuilt using the scripts published here [docker-worker-generator](https://git.automotivelinux.org/AGL/docker-worker-generator/). ### Start image Then, use the 'create_container' script to start a new, fresh container based on the AGL Worker image: @@ -56,12 +56,12 @@ Then, use the 'create_container' script to start a new, fresh container based on * The password for the id 'devel' inside the docker image is 'devel'. ```bash -git clone https://github.com/iotbzh/agl-docker-worker; -cd agl-docker-worker; +git clone https://git.automotivelinux.org/AGL/docker-worker-generator; +cd docker-worker-generator; ./contrib/create_container 0; docker ps; CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES - 4fb7c550ad75 docker.automotivelinux.org/agl/worker:2.1 "/usr/bin/wait_for_ne" 33 hours ago Up 33 hours 0.0.0.0:2222->22/tcp, 0.0.0.0:69->69/udp, 0.0.0.0:8000->8000/tcp, 0.0.0.0:10809->10809/tcp agl-worker-odin-0-sdx + 4fb7c550ad75 docker.automotivelinux.org/agl/worker:3.0 "/usr/bin/wait_for_ne" 33 hours ago Up 33 hours 0.0.0.0:2222->22/tcp, 0.0.0.0:69->69/udp, 0.0.0.0:8000->8000/tcp, 0.0.0.0:10809->10809/tcp agl-worker-odin-0-sdx ``` diff --git a/getting-started/troubleshooting.md b/getting-started/troubleshooting.md index 0027738..183d0c9 100644 --- a/getting-started/troubleshooting.md +++ b/getting-started/troubleshooting.md @@ -40,6 +40,18 @@ CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0" BUILD_CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" TARGET_CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" ``` +## Screen orientation for Splash and in Weston +Depending of your scren mounting the default orientation of the UI an/or splash screen might be incorrect. +To change the orientation of the splash screen patch +``` +File: /etc/systemd/system/sysinit.target.wants/psplash-start.service +Line: ExecStart=/usr/bin/psplash -n -a 90 +``` +To change the orientation of the UI in Weston patch +``` +File: /etc/xdg/weston/weston.ini +Line: transform=90 +``` ## Disabling Homescreen in AGL 3.0.x CC release diff --git a/sec-blueprint/04-adversaries.md b/sec-blueprint/04-adversaries.md index acf3764..8740ae5 100644 --- a/sec-blueprint/04-adversaries.md +++ b/sec-blueprint/04-adversaries.md @@ -1,25 +1,44 @@ ---- - -title : Adversaries -date : 2016-06-30 -categories: architecture, automotive -tags: architecture, automotive, linux -layout: techdoc +This section lists some of the adversaries and attackers in Automotive. +## Enthusiast Attackers: + Enthusiast attackers have physical access to the Engine Control + Units (ECUs) at the circuit board level. They can solder ‘mod chips’ + onto the board and have access to probing tools. They also have + information on ECUs that have been hacked previously and have + access to softwares and instructions developed by other members + of car modification forums. The goal of the enthusiast hacker + could be, but is not limited to, adding extra horse power to the + car or hacking it just for fun. ---- - -**Table of Content** - -1. TOC -{:toc} - -## Authorised malicious project admin/developer - -## Malware developer - -## Organised crime - -## Authorised device/cloud user - -## Network mass attacker +## Corrupt Dealers: + These are attackers that have access to the same capabilities as + enthusiasts, but also have access to the car manufacturer's (OEM) + dealer network. They may also have access to standard debugging + tools provided by the car manufacturer. Their goal may be to support + local car theft gangs or organized criminals. + +## Organized Criminal: + Organized Criminals have access to all of the above tools but may + also have some level of control over the internal network at + many dealerships. They may have hacked and gained temporary + control of the Over-The-Air (OTA) servers or the In-Vehicle + Infotainment (IVI) systems. This is very much like the role of + organized criminals in other industries such as paid media today. + Their goal is to extort money from an OEMs and/or governments by + threatening to disable multiple vehicles. + +## Malware Developers: + Malware Developers have developed malicious software to attach + and compromise a large number of vehicle. The malicious software + would usually be designed spread from one vehicle to another. + The goal usually is to take control of multiple machines then sell + access to them for malicious purposes like denial-of-service (DoS) + attacks or stealing private information and data. + +## Security Researchers: + These attackers are ‘self-publicized’ security consultants trying + to make a name for themselves. They have access standard tools for + software security analysis. They also have physical access to the + vehicle and standard hardware debugging tools (Logic Analyzers, + Oscilloscopes, etc). Their goal is to publicize attacks for personal + gains. |