BSP Developer Training Internal
From DDCIDeos
Jump to navigationJump to search
Wiki is center of universe
- Watch pages
- Private:
- Shared IP
- HowTos
- Configuration Management How-to
- Problem Reporting
- Software Change
- Software Release
- viewSCM
- HowTos
Background
- Have you read DO-178C?
- Component Descriptions
- kernel
- boot
- PAL
- Additional Considerations
- ABC
- Deactivated and dead code.
Customer View
https://ddci.zapto.org/scm/Deos/products/bsp/dev-kit/branches/mainline/BSP-customer-interview.txt
- boot interface
- hypstart is like Linux initrd
- the kernel bundled in such a way that it can be trivially started (bootstrapped) into a running environment
- KFS (two types LFS, MFS) read only, RAM based, Deos proprietary, file system images
Topics for Deos BSP Maintainer Training:
- Types of BSPs - Reference/BareMetal/VerifiedP1/Verified
- Work Flow for Reference BSP, BareMetal, VerifiedP1, and Verification
- BSP Training for Customers
- Boot Design
- PAL Design (timers required for scheduling, interrupts, extension library, etc)
- Dev-kit (boot/pal)
- BSP Integration
- Memory map (scripts to generate it, errors, overlaps, etc)
- Integration files (pi, cd, fp, basecon.hyp etc)
- openarbor.options (inside OpenArbor becomes .options)
- Common build infrastructure (see Common-Makefile-HowTo.htm)
- Lauterbach: Some notes from Deos developers can be found at: Lauterbach_Emulators More intensive training may be available directly from the Lauterbach.
- uboot (1/2 day or less - every experience is different, so you have to figure it out as you go)
- Requirements levied by the kernel:
- $DESKHOME/help/deos-pal-software-requirements.htm
- $DESKHOME/help/deos-boot-software-requirements.htm
- Deos Trace tags 1/2 day
- Adhoc testing is documented in The BSPAdhocTesting.txt
- Testing Boots
- Throughput test
- Testing Pals
- Testing Network Drivers
- Testing Boots
- ABC (Structural Coverage Tool)
- PRLs
- Processor architecture differences, and how these differences impact BSP development
- EL levels vs hypervisor/supervisor/user modes
- Interrupt structure
- Boot loaders
- Assembly language
- Common reference manuals, BSP specific manuals are usually in the BSP itself.
- Open Arbor (limited usefulness for BSPs, but good for other components)
- Being a Deos Maintainer: Creating/using PCRs, Subversion, Wikis, etc (Optional if team desires but this is generally self-directed training)
- Location of reference materials