News

Attend a five-day Embedded Real-Time Linux Training from 13th Sep to 17th Sep 20

Embedded Real-Time Linux Training from 13th Sep to 17th Sep 2004 in Maribor/Slovenia

24 August 2004 - Norik Systems is organizing a five-day Embedded Real-Time Linux Training from 13th to 17th September 2004, in Maribor, Slovenia. Training will be organized at the local Faculty of Electrical Engineering and Computer Science by Norik Systems in cooperation with OpenTech EDV-Research GmbH. The trainer will be Mr. Nicholas McGuire, an ex-FSMLabs Engineer, founder of an "open source company" OpenTech GmbH and the official maintainer of GPL version of RTLinux.
Mr. Mcguire has more than 8 years experience in using Linux in embedded systems and has given talks, seminars and workshops for Real-Time Linux and Embedded Linux in Austria, Germany, France, Italy, Sweden, Spain, UK, Slovenia, Singapore and the USA since 2000. He co-founded and organized The Real Time Linux Workshops in Vienna 1999, Orlando 2000, Milan 2001, Boston 2002 and Valencia 2003.

The language in the training is english, but since the trainer and his asistants are multilingual, help in german and slowene will be provided as well.

If you are interested in attending the training, and if you want to make some suggestions regarding the programme, please, do not hesitate to contact us by sending e-mail to info@norik.com. You can also download our brochure about the Training:


Detailed programme:

Duration: 5 days
Method: hands-on and homework
Language: German/English
Material: printed document collection and complete software on CDs

Intro basic concepts of embedded Dev-Env

  • General introduction of embedded Linux
    - resources
    - scanning available technologies
    - note on open source
    - note on homework
    - general themes for this session
  • Setting up a Linux desktop system from scratch
    - file-system type selection
    - notes on partitioning
    - Project Management: security issues
    - system monitoring with default tools
    - Project Management: documentation requirements
  • CVS
    - initialization
    - common usage
    - CVS structure
    - branching
    - tags
    - Project Manegement: CVS policy, package management
  • Building a kernel for RTLinux/GPL
    - resolving the configuration
    - unpacking packages - notes on sanity checking
    - patching kernel sources, diff and patch, context and resolving problems
    - build and rebuild procedures
    - building kernel documentation
    - Project Management: what needs a backup and documentation ?
    - toolchain dependencies
    - introduction to kernel debug tools
  • Symmetric development environment
    - host system chroot environment
    - host system ramdisk boot env
    - setting up services for the target (NFS,BOOTP,tftp)
    - target system
    - Project Management: Open Source integration issues
  • Backup issues
    - simple backup strategies
    - some backup related tools: using diff, crypt and md5
    - validating backups especially on removable media
    - Project Management: what to document ?
  • Linux kernel introduction
    - Overview of Linux kernel
    - Linux for embedded systems
    - Linux for real-time
    - 2.6 kernel: some essential features
    - general intro scheduling
    - O(1) sched
    - kernel preemption
    - interactive preference
    - Project Management: use resources before inventing resources
    - kernel space processing
    - interrupt management in Linux
    - some optimizations relevant for embedded systems
    - O_STREAM and caching behavior
    - variable HZ patch
    - lazy FPU
    - limitations of optimizations for RT systems
    - Project Management: documenting kernel requirements
    - Project Management: investigation phase in Open Source
    - Project Management: Open Source risk management issues
  • Introduction to RTLinux/GPL internals
    - core concepts
    - soft-hard-non real-time
    - design dilemma
    - dual kernel concept
    - ride on POSIX
    - Project Management: coding style
    - pure POSIX - the natural concept ?
    - POSIX timers and signals
    - the scheduler in RTLinux/GPL
    - periodic and aperiodic tasks
    - interrupt management
    - the emulation code
    - DSR issues
    - non-POSIX extensions
    - lazy FPU
    - CPU affinity
    - running RTLinux with Linux shutdown
  • Embedded Toolchain (development kit)
    - introduction development kit
    - build script set introduction
    - script design and documentation requirements
    - Project Management: how to build a development kit and document it ?
    - introduction to make
  • Introduction to minimum filesystem part I
    - the naive file system
    - first steps in change root
    - libs, config files and executables
    - UNIX file-system concepts
  • Dependency and error analysis
    - glibc - a library system
    - ldd
    - strace
    - ltrace
    - oprofile
    - LD_PRELOAD
  • Introduction to minimum file-system part II
    - selecting the lib set
    - multicall binaries
    - filesystem layer optimization
    - creation parameters
    - symbolic links and files
    - static vs. dynamic
    - target filesystem: first cleanup
    - busybox
    - tinylogin
    - minimum set of libs
    - building a ramdisk
    - introduction to kernel processing
    - kthreads
    - proc filesystem
    - booting the ramdisk system
    - resolving errors
  • Introduction to debugging
    - compile time issues
    - preprocessor errors
    - bgcc
    - memory leaks
    - mtrace
    - top
    - core files
    - segfaults
    - system calls
    - library calls
    - debuging in RTLinux
    - GDB in RTLinux how does it work
    - managing symbols and some limitations
    - temporal debuging
    - using the rtl_trace and symbol issues
  • System monitoring
    - syslogd
    - proc filesystem, proc_utils
    - sysctl
    - using RTLinux/GPL as software watchdog
    - LD_PRELOAD monitors
  • Target system first steps (if target systems available)
    - serial console and kernel command line
    - booting the kernel
    - adding the filesystem as ramdisk
    - filesystem via NFS
    - remote syslogd access
  • Written and Practical exam
  • Session cleanup
< Back