The CIP open workshop will take place on Sunday 22th (the day before the ELCE starts) in the (room to be confirmed) on the ELCE venue from 14:00 to 18:00.

Please send your content proposals or topics you are interested on to the cip-dev mailing list. They will be discussed and the agenda will be defined as soon as possible.

This is the schedule for the CIP workshop on Sunday 22nd October 2017 which will take place at room Athens

• Goal: learn the basics of B@D in order to test the CIP kernel and CIP system.
• Description: B@D is a testing environment based on LAVA + KernelCI that allows you to test a kernel or a simple system in a board set up locally, like for example, connected to your own laptop. The workshop will guide you on the installation and configuration of the environment. Using the CIP kernel and system, those participating in the training session will learn how to execute tests on the board, get the results and interpret them.
• Number of participants: 10
• Pre-requisites:
  • Participants:
    • A laptop with enough space to install B@D which is a VM-VirtualBox (around 13 Gb).
    • The supported OS are Linux and W10 only. More info about the base system to come.
    • BBB and cables to connect it to the laptop: serial and network (RJ45) cables. There will be 5 boards available (Renesas). If you are not coming with your own BeagleBone Black (BBB) and need a board, please state so in the registration table below.
• Duration: 90 min

Please notify your interest in participating in this open activity by sending a mail to the cip-dev mailing list with the following data:

• Name
• Company
• Position/role
• Why you are interested on this workshop.
• Are you coming with your own board or do you need one?

Once confirmed, your name will be added to the below table. We have a limit of 10 participants.

Confirmed participants:

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.
  • Check the slides
• How B@D works
  • Main links are on the slides:

• 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 (are we 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?)
    • 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
  • 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

• 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)

Please notify your interest in participating in this open activity by sending a mail to the cip-dev mailing list with the following data:

• Name
• Company
• Position/role
• Why you are interested on.

Once confirmed, your name will be added to the below table. We have a limit of 10 participants.

Confirmed participants:

CIP has organised an open meeting where all developers interested in CIP current and future activities can gather and ask questions or propose their ideas and use cases to those who are currently involved in the project.

• When: Tuesday October 24th from 13:00 to 14:00 hours
• Where: Liben Room, Mezzanine Level al ELCE venue in Prague CZ.
• Agenda:
  • Short description of the technical activities that CIP is currently doing and some planned actions.
  • Q&A

Feel free to propose new topics in the cip-dev mailing list

Back to the parent page