Changes between Version 4 and Version 5 of Arch/Soclib
- Timestamp:
- Jun 21, 2010, 11:32:44 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Arch/Soclib
v4 v5 1 1 = SoCLib Architecture support = 2 2 3 SoCLib is an open platform for virtual prototyping of multi-processors system on chip (MP-SoC). From a software engineer point of view, SoCLib can be seen as an library of hardware component models which can be used to build various multi -processor machine emulators. MutekH can run on SoCLib based simulator.3 SoCLib is an open platform for virtual prototyping of multi-processors system on chip (MP-SoC). From a software engineer point of view, SoCLib can be seen as an library of hardware component models which can be used to build various multiprocessor machine emulators. 4 4 5 MutekH supports the SoCLib architecture specificities: 6 * drivers for SoCLib hardware components 7 * support for instrumentation-specific CPU registers 8 * heterogeneous platforms (platforms with ONE MutekH instance, but with different CPU architectures running at the same time, sharing OS global data) 9 * integrated build system and workflow 5 MutekH can run on SoCLib based simulator using Mips32, Arm and !PowerPc processor models. 10 6 11 You may be interested in reading the [wiki:Arch/Soclib/Tutorial Tutorial for SoCLib users] 7 It supports the SoCLib architecture specificities: 8 * drivers for SoCLib hardware components. 9 * heterogeneous multiprocessor platforms: platforms running a single MutekH instance on multiple processors of different architectures, sharing all variables and allocated data like in legacy shared memory SMP platforms. 10 * integrated build system and workflow. 12 11 13 You may want to visit the [https://www.soclib.fr/trac/dev/wiki SoCLib] project home page to learn more. 12 = Debugging features = 14 13 15 = SoCLib platform specificities = 14 SoCLib offer some interestring debbuging features for the kernel and embedded application developer: 15 * It provides a Gdb server to debug embedded software. 16 * It provides the [soclib:Tools/MemoryChecker MemoryChecker] tool which is able to watch various suspicious memory and spinlock operations. This tools is similar to [http://www.valgrind.org valgrind] but is designed to check kernel code behavior. 17 18 When combined, these tools are extremely powerful to track down bugs and race conditions and are extensively used to test MutekH during development. 19 20 = See also = 21 22 You may be interested in reading the [WikiStart#Gettingstarted various tutorial] to have MutekH running on SoCLib. 23 24 You may want to visit the [soclib:wiki: SoCLib] project home page to learn more. 25 26 = SoCLib specific topics = 16 27 17 28 * [wiki:Arch/Soclib/Xicu Xicu in Flattened device trees]