OSI-M Tools - Revision history

Leo: /* Editing Labs */

2009-11-24T17:04:33Z

‎Editing Labs

Girts: /* Editing Labs */

2009-11-22T15:05:16Z

‎Editing Labs

Girts at 15:04, 22 November 2009

2009-11-22T15:04:22Z

Girts: /* Compiler Toolchain */

2009-09-13T12:32:03Z

‎Compiler Toolchain

Girts: /* Compiler Toolchain */ flex required for binutils compilation

2009-09-13T12:07:16Z

‎Compiler Toolchain: flex required for binutils compilation

Girts: /* Compiler Toolchain */ some bugfix added

2009-09-13T12:04:51Z

‎Compiler Toolchain: some bugfix added

Girts: /* Bochs Emulator */

2009-09-13T08:39:26Z

‎Bochs Emulator

Girts: /* Bochs Emulator */

2009-09-12T19:37:42Z

‎Bochs Emulator

Girts: /* Bochs Emulator */

2009-09-12T09:04:00Z

‎Bochs Emulator

Leo at 12:16, 10 September 2009

2009-09-10T12:16:10Z

@@ Line 135: / Line 135: @@
   }
-== Editing Labs ==
+== Editing Labs - Eclipse CDT ==
 To edit code in labs, it is suggested to have a convenient [http://en.wikipedia.org/wiki/Integrated_development_environment IDE]. One example: [http://www.eclipse.org/cdt/ Eclipse CDT] - Eclipse with C/C++ plugin. Open your lab as [[C Projects in Eclipse | C-Makefile-project in Eclipse]].

← Older revision		Revision as of 15:05, 22 November 2009
Line 136:		Line 136:

	== Editing Labs ==		== Editing Labs ==
	To edit code in labs, it is suggested to have a convenient [http://en.wikipedia.org/wiki/Integrated_development_environment IDE]. One example: [http://www.eclipse.org/cdt/ Eclipse CDT] - Eclipse with C/C++ plugin.		To edit code in labs, it is suggested to have a convenient [http://en.wikipedia.org/wiki/Integrated_development_environment IDE]. One example: [http://www.eclipse.org/cdt/ Eclipse CDT] - Eclipse with C/C++ plugin. Open your lab as [[C Projects in Eclipse \| C-Makefile-project in Eclipse]].

@@ Line 134: / Line 134: @@
     bx_guard.guard_for = old_guard;
   }
+== Editing Labs ==
+To edit code in labs, it is suggested to have a convenient [http://en.wikipedia.org/wiki/Integrated_development_environment IDE]. One example: [http://www.eclipse.org/cdt/ Eclipse CDT] - Eclipse with C/C++ plugin.

@@ Line 27: / Line 27: @@
 If there are errors compiling gcc when it gets to libstdc++, don't worry about it.
+Possible issues and fixes:
-If you're getting <code>"gas/config/tc-i386.h:451: error: array type has incomplete element type"</code> while compiling binutils, check [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299671 Debian Bug report #299671] for a fix: a couple of lines have to be modified in binutils sources before compiling.
+# If you're getting <code>"gas/config/tc-i386.h:451: error: array type has incomplete element type"</code> while compiling binutils, check [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299671 Debian Bug report #299671] for a fix: a couple of lines have to be modified in binutils sources before compiling.
-You also require flex installed (<code>sudo apt-get install flex</code>), otherwise you will get <code>"checking lex output file root... ./configure: 1: lex: not found"</code>.
+# You also require flex installed (<code>sudo apt-get install flex</code>), otherwise you will get <code>"checking lex output file root... ./configure: 1: lex: not found"</code>.
+# If you are getting <code>"/usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second"</code>, you must modify one line in gcc sources (replace open(a, b) by open(a, b, 755)) read [https://bugzilla.redhat.com/show_bug.cgi?id=330971 RedHad Bugzilla].
 Then you'll have in /usr/local/bin a bunch of binaries with names like i386-jos-elf-gcc. It will also be necessary to change the GNUMakefile used in the labs to use i386-jos-elf-gcc instead of gcc. There are instructions for how to do this inside of GNUMakefile.

@@ Line 28: / Line 28: @@
 If you're getting <code>"gas/config/tc-i386.h:451: error: array type has incomplete element type"</code> while compiling binutils, check [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299671 Debian Bug report #299671] for a fix: a couple of lines have to be modified in binutils sources before compiling.
+You also require flex installed (<code>sudo apt-get install flex</code>), otherwise you will get <code>"checking lex output file root... ./configure: 1: lex: not found"</code>.
 Then you'll have in /usr/local/bin a bunch of binaries with names like i386-jos-elf-gcc. It will also be necessary to change the GNUMakefile used in the labs to use i386-jos-elf-gcc instead of gcc. There are instructions for how to do this inside of GNUMakefile.

@@ Line 68: / Line 68: @@
             --enable-global-pages \
             --enable-pae \
-            --enable-all-optimizations \
             --disable-reset-on-triple-fault \
             --with-all-libs \

@@ Line 47: / Line 47: @@
 Since the script asks our server what the most current version of the Bochs tarball is.
+Note: If you're getting error "ERROR: X windows gui was selected, but X windows libraries were not found.", try installing packages xorg-dev and xserver-xorg-dev:
+ sudo apt-get install xorg-dev xserver-xorg-dev
 To do things manually, fetch the 6.828-modified Bochs 2.2.6 source as follows:

@@ Line 57: / Line 57: @@
  cd bochs-2.2.6-6.828r1
  ./configure --enable-disasm \
             --enable-smp \
             --enable-debugger \

@@ Line 2: / Line 2: @@
 It should be possible to get this development environment running under windows with the help of Cygwin. Install cygwin, and be sure to install the flex and bison packages (they are under the development header).
-Compiler Toolchain
+== Compiler Toolchain ==
 Most modern Linuxes and BSDs have an ELF toolchain compatible with the 6.828 labs. That is, the system-standard gcc, as, ld and objdump should just work. If your machine is in this camp, disable the i386-jos-elf- tool prefix in your make setup by adding the following line to conf/env.mk:
@@ Line 27: / Line 28: @@
 Then you'll have in /usr/local/bin a bunch of binaries with names like i386-jos-elf-gcc. It will also be necessary to change the GNUMakefile used in the labs to use i386-jos-elf-gcc instead of gcc. There are instructions for how to do this inside of GNUMakefile.
+== Bochs Emulator ==
+You can download, compile, and install Bochs from the source archive. If you download a prebuilt version of bochs, it will not be compiled with the same options as we use for the class. Also, the Bochs version for the class contains a bug fix to make single-stepping work.
+We've prepared an automated, self-updating script to assist you in installing Bochs and potentially upgrading to new versions of Bochs. As root:
+ # cd /some/tmp/build/dir
+ # wget http://pdos.lcs.mit.edu/6.828/2006/src/bochs-install.sh
+ # sh bochs-install.sh
+If we issue future updates to our 6.828 Bochs tarball, it would only be necessary to run:
+ # cd /some/tmp/build/dir
+ # sh bochs-install.sh
+Since the script asks our server what the most current version of the Bochs tarball is.
+To do things manually, fetch the 6.828-modified Bochs 2.2.6 source as follows:
+ $ wget http://pdos.lcs.mit.edu/6.828/2006/src/bochs-2.2.6-6.828r1.tar.gz
+You may want to run ./configure --help and look at the available options, particularly --prefix= which determines where Bochs will be installed.
+ tar xzvf bochs-2.2.6-6.828r1.tar.gz
+ cd bochs-2.2.6-6.828r1
+ ./configure --enable-disasm \
+            --enable-smp \
+            --enable-debugger \
+            --enable-new-pit \
+            --enable-all-optimizations \
+            --enable-4meg-pages \
+            --enable-global-pages \
+            --enable-pae \
+            --enable-all-optimizations \
+            --disable-reset-on-triple-fault \
+            --with-all-libs \
+            --with-x \
+            --with-x11 \
+            --with-nogui
+ make
+ make install
+For Mac OS X Tiger
+ ./configure --disable-cdrom --enable-disasm \
+  --enable-debugger --enable-new-pit --enable-all-optimizations \
+  --enable-4meg-pages --enable-global-pages --enable-pae \
+  --enable-all-optimizations --disable-reset-on-triple-fault \
+  --enable-smp --with-nogui --with-x11 --with-x --with-carbon
+If you wish to use a different UI than the default one, modify your .bochsrc file accordingly. See the bochsrc documentation. It should also be possible to just run man bochsrc .
+If you are compiling on a non-x86 platform or on windows, it may be necessary to remove the --enable-all-optimizations flag. If the make install step fails, it is probably possible to install it manually by copying ./bochs to /usr/bin/bochs and setting the environment variable BXSHARE to the path to the bochs-2.2.6 directory.
+If you want to use a different version of bochs (not recommended!), the 6.828-specific changes are in the bx_dbg_stepN_command function, in bx_debug/dbg_main.cc. The new function body looks like:
+  void bx_dbg_stepN_command(bx_dbg_icount_t count)
+  {
+    if (count == 0) {
+      dbg_printf("Error: stepN: count=0\n");
+      return;
+    }
+    // use simulation mode while executing instructions.  When the prompt
+    // is printed, we will return to config mode.
+    SIM->set_display_mode(DISP_MODE_SIM);
+    // single CPU
+    int old_guard = bx_guard.guard_for;
+    bx_guard.guard_for |= BX_DBG_GUARD_ICOUNT; // looking for icount
+    bx_guard.guard_for |= BX_DBG_GUARD_CTRL_C; // or Ctrl-C
+    bx_guard.guard_for &= ~BX_DBG_GUARD_IADDR_ALL;
+    // for now, step each CPU one instruction at a time
+    for (unsigned cycle=0; cycle < count; cycle++) {
+      for (unsigned cpu=0; cpu < BX_SMP_PROCESSORS; cpu++) {
+     bx_guard.icount = 1;
+        bx_guard.interrupt_requested = 0;
+        int old_mode_break = BX_CPU(cpu)->mode_break;
+        BX_CPU(cpu)->guard_found.guard_found = 0;
+  BX_CPU(cpu)->guard_found.icount = 0;
+        BX_CPU(cpu)->cpu_loop(1);
+        BX_CPU(cpu)->mode_break = old_mode_break;
+      }
+  #if BX_SUPPORT_SMP == 0
+      // ticks are handled inside the cpu loop
+  #else
+       BX_TICK1();
+  #endif
+    }
+    BX_INSTR_DEBUG_PROMPT();
+    bx_dbg_print_guard_results();
+    bx_guard.guard_for = old_guard;
+  }