civilinfrastructureplatform:cipconferences:cipwselce2017
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
civilinfrastructureplatform:cipconferences:cipwselce2017 [2017/10/20 14:09] Agustin Benito Bethencourt training session |
civilinfrastructureplatform:cipconferences:cipwselce2017 [2017/10/20 17:10] (current) Agustin Benito Bethencourt cancelled |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| | 14:00 to 15:00 | AGL Testing & B@D Collaboration Discussion | BoF | Nori Fukuyasu (LF) | | | 14:00 to 15:00 | AGL Testing & B@D Collaboration Discussion | BoF | Nori Fukuyasu (LF) | | ||
| | 15:00 to 16:00 | CIP kernel maintenance meeting | Meeting (CIP Members only) | Ben Hutchings (Codethink) | | | 15:00 to 16:00 | CIP kernel maintenance meeting | Meeting (CIP Members only) | Ben Hutchings (Codethink) | | ||
| - | | 16:00 to 17:30 | [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting#action-1board-at-desk-single-developer-b-d|B@D]] 101: how to test the CIP kernel using B@D | Training (open under registration) | Robert Marshall (Codethink) | | + | | 16:00 to 17:30 | <WRAP center round alert 60%> |
| + | |||
| + | Cancelled | ||
| + | |||
| + | </WRAP> [[https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting#action-1board-at-desk-single-developer-b-d|B@D]] 101: how to test the CIP kernel using B@D | Training (open under registration) | Robert Marshall (Codethink) | | ||
| | 17:30 to 18:30 | CIP Kernel maintenance Q&A session | BoF (open) | Ben Hutchings | | | 17:30 to 18:30 | CIP Kernel maintenance Q&A session | BoF (open) | Ben Hutchings | | ||
| Line 42: | Line 46: | ||
| ^ Number ^ Name ^ Company ^ Role ^ Need Board? ^ | ^ Number ^ Name ^ Company ^ Role ^ Need Board? ^ | ||
| - | | 1 | Chris Paterson | Renesas | Developer | No | | + | | 1 | -- | -- | -- | -- | |
| - | | 2 | Findlay Shearer | Intel | Sr. Product Marketing | -- | | + | | 2 | -- | -- | -- | -- | |
| - | | 3 | Jan Simon Moller | AGL | Release Manager | No | | + | | 3 | -- | -- | -- | -- | |
| - | | 4 | Jan Kiszka | Siemens | Architect/Consultant | No | | + | | 4 | -- | -- | -- | -- | |
| - | | 5 | Binh Nguyen | Renesas Design Vietnam | Developer | Yes | | + | | 5 | -- | -- | -- | -- | |
| - | | 6 | Takuo Koguchi | Hitachi | Chief Researcher | Yes | | + | | 6 | -- | -- | -- | -- | |
| | 7 | -- | -- | -- | -- | | | 7 | -- | -- | -- | -- | | ||
| | 8 | -- | -- | -- | -- | | | 8 | -- | -- | -- | -- | | ||
| Line 54: | Line 58: | ||
| ==== Training session script ==== | ==== Training session script ==== | ||
| - | |||
| - | Training session ToC | ||
| - | * Introductions: trainers and participants | ||
| - | * Check slides. | ||
| - | * CIP Testing project intro | ||
| - | * Check the slides | ||
| - | * B@D v1.0 description | ||
| - | * Check the slides | ||
| - | * Pre-requisites and considerations before the training session starts. | ||
| - | * download B@D. This is for me! Participants will use the sticks | ||
| - | * Check the slides | ||
| - | * Boards | ||
| - | * Check the slides | ||
| - | * Modifications introduced for this training session | ||
| - | * Check the slides | ||
| - | * Networking modifications | ||
| - | * Check the slides | ||
| - | * Check connections to board - ftdi & ssh | ||
| - | * Check that the serial to the board & ssh over the network connection works before starting the box. | ||
| - | * Serial in console / putty or similar on windows. | ||
| - | * How B@D works | ||
| - | * Main links are on the slides | ||
| - | |||
| - | === How B@D works === | ||
| - | |||
| - | * Copy the box | ||
| - | * going to talk through and assist with use of the already provisioned box | ||
| - | * check attendees on requirements | ||
| - | * copy box to their machines (we are going to provide a copy of the git repos too) | ||
| - | * importbox.sh - outline use | ||
| - | * vagrant ssh | ||
| - | * Up the box | ||
| - | * me and them check progress | ||
| - | * user catchup | ||
| - | * kernelci | ||
| - | * outline kernelci | ||
| - | * repos already there - show git state | ||
| - | * set up env variables (different to what's on the box!) and run it (with them) | ||
| - | * Enumerate them here with build command (handout?) | ||
| - | * export TREE_NAME=cip-example | ||
| - | * export ARCH=arm | ||
| - | * export CROSS_COMPILE=arm-linux-gnueabihf- | ||
| - | * user catchup | ||
| - | * What about initramfs?? | ||
| - | * while the above happens | ||
| - | * going to need 2 ssh sessions on the vm! | ||
| - | * check ip address of host and update jinja | ||
| - | * sed 's/10.24.3.106/<host_ip>/g' mybbb.dat > bbb.mine | ||
| - | * show how to add to data dictionary | ||
| - | * sudo cp bbb.mine /etc/lava-server/dispatcher-config/devices/bbb01.jinja2 | ||
| - | * user catchup | ||
| - | * U-boot version. LAVA fix | ||
| - | * 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) is ok - but observe the prompt! | ||
| - | * Certain versions of U-Boot on the Beaglebone black have => as a prompt rather than U-Boot=> in the ‘=>’ case you need to make the following change on the VM - | ||
| - | * sudo vi /etc/lava-server/dispatcher-config/device-types/beaglebone-black.jinja2 | ||
| - | * Add the line: {% set bootloader_prompt = bootloader_prompt|default('=>') %} | ||
| - | * (line 2) | ||
| - | * The built kernel. Web interface | ||
| - | * kernelci | ||
| - | * start webserver /vagrant/scripts/start_webserver.sh | ||
| - | * show results - a variety | ||
| - | * Integration of LAVA and kernelci | ||
| - | * And this box also has ... | ||
| - | * LAVAv2 | ||
| - | * visit http://localhost:8080 | ||
| - | * login | ||
| - | * show health checks (link?) - qemu, BBB and renesas | ||
| - | * Health Check | ||
| - | * When? | ||
| - | * show health check results - table and an individual result | ||
| - | * Run healthcheck | ||
| - | * ...and hopefully the tutees! | ||
| - | * Allow users to catchup - if that’s possible - though it would be good to run even if it’s going to fail! | ||
| - | * Notify | ||
| - | * have a pre-prepared yaml file with notify (at least irc, will email work? - best not privacy concerns!?) | ||
| - | * run lava-tool | ||
| - | * user catchup | ||
| - | === Demo using the Renesas board === | ||
| - | |||
| - | * 3 files should be in the $directory (uimage, ramfs, dtb) | ||
| - | * As before place these in the kernelci locations as defined in the test case file | ||
| - | * Modify jinja file if needed, replace telnet ip with specific etc | ||
| - | * Ensure a local telnet/ssh can happen before health check | ||
| - | * Copy paste health check into test, run etc | ||
| - | * The board does serial over micro usb, baud rate 115200 (check which dev/ on linux & on windows use device manager to get correct port for putty etc) | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
civilinfrastructureplatform/cipconferences/cipwselce2017.1508508576.txt.gz · Last modified: 2017/10/20 14:09 by Agustin Benito Bethencourt
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
