These are the steps I use to download, install, and use the AMD SimNow simulator. You may not want to do exactly what I did, but it should get you started. There is PDF documentation that you can download on the same page as the simulator.
Build a ROM image for SimNow (Skip this step if you have your own Bios you want to use)
- make sure iasl tool is available
- Choose Payload Configuration
- Desired Payload is FILO
- Download the latest version of FILO from Subversion with
- svn co svn://coreboot.org/filo/trunk/filo
- cd libpayload
- make defconfig
- make DESTDIR=../build install
- make menuconfig Note: use default configuration.
- make CC="gcc -m32" LD="ld -b elf32-i386" HOSTCC="gcc" AS="as --32"
- filo.elf is generated.
- Choose Platform Configuration
- coreboot.rom is generated.
- Download SimNow from AMD's website
- Create an account
- Accept the license agreement
- Log in.
- Untar the .tar.gz file you download in a convenient place (You'll now have a directory called simnow-linux64-4.5.xpub - new release by April 2009 that eliminate SimNow patch source on coreboot)
- Follow the instructions from the help section "Setting up Linux" for the Simulator
- To get enough "mmap"able virtual address space, make sure you have a /etc/sysctl.conf file and that it contains the following line:
vm.max_map_count = 1048576
- Run ./simnow from the simnow-linux64-4.4.1pub directory
- Inside the SimNow Main Window do File->Open BSD, browse to the simnow-linux64-4.4.1pub/bsds directory and load either cheetah_1p.bsd or cheetah_1pjh.bsd (jh is dual-core)
Now you have a single Opteron socket motherboard with: AMD-8132 PCI-X controller, AMD-8111 I/O hub, and Winbond W83627HF SuperIO.
- Copy your coreboot ROM image to simnow-linux64-4.4.1pub/Images for convenience.
- Open the SimNow Device Window (View->Show Devices)
- Double click on Memory Device #5 (Your BIOS chip)
- Click on the Memory Configuration Tab, and change the Base Address, Size, and File (I use Base Address = fff00000 and Size = 32 because I use a 1 MB image)
- Click OK to save your changes
- Go to the main simulator window and hit Run Simulation (Play button)
Serial Port Configuration
In order to see the console output, go to the terminal you are running ./simnow in. Hit enter. You'll see a simnow> prompt.
- Type serial.SetCommPort pipe and hit enter.
- Type serial.GetCommPort and hit enter.
On my machine this returns path (/home/myles/.simnow/com1), mode (PIPE)
Open a new terminal and type cat /home/myles/.simnow/com1/simnow_out If you need to send input to the serial port, echo to /home/myles/.simnow/com1/simnow_in
Using the snserial tool
Alternatively, you can use a tool called 'snserial' to interact with the serial ports. snserial will combine the input and output, and provide access to the combined stream through either a psuedo tty, or a telenet port.
- Download the snserial tool from http://khepri.openbios.org/~jcrouse/snserial-1.0.tar.gz.
- Extract it: tar -zxvf snserial-1.0.tar.gz
- Build it: cd snserial/; make
Before running the tool, make sure that you have enabled the serial pipes as detailed above.
To enable serial through a pseudo TTY, start your simulation and type ./snserial comX in another Linux terminal window (where X is 1 or 2). The program will respond with:
SimNow Serial pipe Muxer Connection established. Type 'target remote /dev/pts/2' in GDB to connect. (Press CTRL-C to exit)
You can now connect your serial application (minicom, or GDB for debugging) to the specified pseudo-tty.
To enable serial interaction through telnet, start the simulation and type ./snserial -t comX. The program will respond with:
SimNow Serial pipe Muxer COM 1: Listening on port 9000 (Press CTRL-C to exit)
You can now connect to the serial stream by typing 'telnet localhost 9000' in a Linux terminal window.
Note: It is a quirk of SimNow that the pipes are not created until the simulation for the BSD is started for the first time. Make sure you start the simulation before running snserial, otherwise you will see this: Couldn't stat /home/<user>/.simnow/com1/simnow_out: No such file or directory. The best course of action is to start the simulation quickly, attach the snserial program, and then restart the simulation to see the early serial output.
- Hit the Stop Simulation button if the simulation is running
- File->Set IDE Primary Master Image
- Browse to your hard drive (.HDD) image
- File->Set IDE Secondary Master Image
- Browse to a CD (.ISO) image
- File->Set IDE Primary Master Image
- Hit Run Simulation again
You should get output from the serial port scrolling in one terminal, and be able to watch the VGA output in the main window.
If you used buildrom to get a BIOS image with coreboot + LAB, you'll end up at a linux prompt where you can mount the disks, etc.
|| This file is licensed under the Creative Commons Attribution ShareAlike 3.0 License.|
In short: you are free to share and make derivative works of the file under the conditions that you appropriately attribute it, and that you distribute it only under a license identical to this one.