Changes between Version 4 and Version 5 of Arch/Soclib

Timestamp:

Jun 21, 2010, 11:32:44 PM (14 years ago)

Author:

becoulet

Comment:

--

Arch/Soclib

@@ -1 +1 @@
 = SoCLib Architecture support =
 
-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.
+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.
 
-MutekH supports the SoCLib architecture specificities:
- * drivers for SoCLib hardware components
- * support for instrumentation-specific CPU registers
- * heterogeneous platforms (platforms with ONE MutekH instance, but with different CPU architectures running at the same time, sharing OS global data)
- * integrated build system and workflow
+MutekH can run on SoCLib based simulator using Mips32, Arm and !PowerPc processor models.
 
-You may be interested in reading the [wiki:Arch/Soclib/Tutorial Tutorial for SoCLib users]
+It supports the SoCLib architecture specificities:
+ * drivers for SoCLib hardware components.
+ * 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.
+ * integrated build system and workflow.
 
-You may want to visit the [https://www.soclib.fr/trac/dev/wiki SoCLib] project home page to learn more.
+= Debugging features =
 
-= SoCLib platform specificities =
+SoCLib offer some interestring debbuging features for the kernel and embedded application developer:
+ * It provides a Gdb server to debug embedded software.
+ * 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.
+
+When combined, these tools are extremely powerful to track down bugs and race conditions and are extensively used to test MutekH during development.
+
+= See also =
+
+You may be interested in reading the [WikiStart#Gettingstarted various tutorial] to have MutekH running on SoCLib.
+
+You may want to visit the [soclib:wiki: SoCLib] project home page to learn more.
+
+= SoCLib specific topics =
 
  * [wiki:Arch/Soclib/Xicu Xicu in Flattened device trees]