Xtensa on QEMU - Revision history

Jcmvbkbc: update core import script location

2018-03-09T17:55:32Z

update core import script location

← Older revision		Revision as of 17:55, 9 March 2018
Line 196:		Line 196:
	== Extending QEMU ==		== Extending QEMU ==

	Starting with QEMU-2.2 there's a script [https://github.com/OSLL/qemu-xtensa/blob/master/target-xtensa/import_core.sh qemu/target-xtensa/import_core.sh] that adds new core to QEMU from the xtensa configuration overlay.		Starting with QEMU-2.2 there's a script [https://github.com/OSLL/qemu-xtensa/blob/master/target/xtensa/import_core.sh qemu/target-xtensa/import_core.sh] that adds new core to QEMU from the xtensa configuration overlay.

Jcmvbkbc: fix u-boot page link and 'extending qemu' section

2018-03-02T23:07:20Z

fix u-boot page link and 'extending qemu' section

← Older revision		Revision as of 23:07, 2 March 2018
Line 94:		Line 94:
	'''-net nic,vlan=0 -net user,vlan=0,tftp=.,hostname=dc232b-lx200 -pflash lx200.flash \'''		'''-net nic,vlan=0 -net user,vlan=0,tftp=.,hostname=dc232b-lx200 -pflash lx200.flash \'''
	'''-kernel u-boot-xtensa.git/u-boot.dc232b_xtav200'''		'''-kernel u-boot-xtensa.git/u-boot.dc232b_xtav200'''
	In this scenario binary u-boot image may be downloaded from TFTP and copied to the FLASH as described [[~~Setting_up_U~~-Boot\|here]].		In this scenario binary u-boot image may be downloaded from TFTP and copied to the FLASH as described [[U-Boot\|here]].

	Alternatively FLASH image containing u-boot may be preformatted and QEMU may be booted from it:		Alternatively FLASH image containing u-boot may be preformatted and QEMU may be booted from it:
Line 197:		Line 197:

	Starting with QEMU-2.2 there's a script [https://github.com/OSLL/qemu-xtensa/blob/master/target-xtensa/import_core.sh qemu/target-xtensa/import_core.sh] that adds new core to QEMU from the xtensa configuration overlay.		Starting with QEMU-2.2 there's a script [https://github.com/OSLL/qemu-xtensa/blob/master/target-xtensa/import_core.sh qemu/target-xtensa/import_core.sh] that adds new core to QEMU from the xtensa configuration overlay.

	To manually extend QEMU with new xtensa core an appropriate XtensaConfig structure must be registered. This structure may be mostly automatically filled in from the overlay data, see mainline commits [http://jcmvbkbc.spb.ru/git/?p=dumb/qemu-xtensa.git;a=commitdiff;h=53add759be1a39063cfc52ca2a6d0fcdd1091697 53add759be1a39063cfc52ca2a6d0fcdd1091697] (target-xtensa: add dc232b core) and [http://jcmvbkbc.spb.ru/git/?p=dumb/qemu-xtensa.git;a=commitdiff;h=935f7a2b428f71a40e985f09955bccaaf09518fa 935f7a2b428f71a40e985f09955bccaaf09518fa] (target-xtensa: add fsf core) for example:
	* target-xtensa/core-<core name>/core-isa.h is a copy of config/core.h from xtensa-config-overlay.tar.gz;
	* target-xtensa/core-<core name>/gdb-config.c is made from gdb/xtensa-config.c from xtensa-config-overlay.tar.gz, only rmap entries for PC, A, AR, SR, UR are retained;
	* XtensaConfig::gdb_regmap::num_regs is the total number of rmap entries in the gdb-config.c;
	* XtensaConfig::gdb_regmap::num_core_regs is the number of contiguous non-privileged ((flags & 1) == 0) rmap entries in the gdb-config.c.

Jcmvbkbc: specify better stty options for sim

2015-11-26T13:10:30Z

specify better stty options for sim

← Older revision		Revision as of 13:10, 26 November 2015
Line 74:		Line 74:
	'''-kernel sim-2.6.29-smp/arch/xtensa/boot/Image.elf'''		'''-kernel sim-2.6.29-smp/arch/xtensa/boot/Image.elf'''

	Since the QEMU doesn't manage terminal settings in semihosting mode, ^C and other terminal control codes interrupt QEMU instead of its guest. stty ~~raw~~ may be used to set up terminal not to terminate QEMU.		Since the QEMU doesn't manage terminal settings in semihosting mode, ^C and other terminal control codes interrupt QEMU instead of its guest. '''stty -echo -icanon -isig''' may be used to set up terminal to not echo input characters and not terminate QEMU.

	== XTFPGA (LX60/LX200/ML605/KC705/...) platforms ==		== XTFPGA (LX60/LX200/ML605/KC705/...) platforms ==

Jcmvbkbc: add ML605/KC705 to the list of platforms

2015-07-20T21:39:33Z

add ML605/KC705 to the list of platforms

← Older revision		Revision as of 21:39, 20 July 2015
Line 4:		Line 4:

	Starting with version 1.0 QEMU offers [http://wiki.qemu.org/Features/Xtensa Xtensa architecture emulation].		Starting with version 1.0 QEMU offers [http://wiki.qemu.org/Features/Xtensa Xtensa architecture emulation].
	DC232B, DC233C (LE) and fsf (BE) cores are supported on sim and LX60/LX200 platforms.		DC232B, DC233C (LE) and fsf (BE) cores are supported on sim and LX60/LX200/ML605/KC705 platforms.

	== Getting and building QEMU ==		== Getting and building QEMU ==
Line 53:		Line 53:
	\|-		\|-
	\| -pflash <flash-image>		\| -pflash <flash-image>
	\| (Not for sim) Mount flash-image as a system FLASH. Note that image size must match platform FLASH size (4MB for LX60, 16MB for LX200~~, 32MB for~~ ML605, 128MB for KC705).		\| (Not for sim) Mount flash-image as a system FLASH. Note that image size must match platform FLASH size (4MB for LX60, 16MB for LX200 and ML605, 128MB for KC705).
	\| -pflash u-boot.dc232b_xtav200.flash		\| -pflash u-boot.dc232b_xtav200.flash
	\|-		\|-

Jcmvbkbc: fix 'extending QEMU' paragraph

2015-07-20T21:24:51Z

fix 'extending QEMU' paragraph

← Older revision		Revision as of 21:24, 20 July 2015
Line 196:		Line 196:
	== Extending QEMU ==		== Extending QEMU ==

	To extend QEMU with new xtensa core an appropriate XtensaConfig structure must be registered. This structure may be mostly automatically filled in from the overlay data, see mainline commits [http://jcmvbkbc.spb.ru/git/?p=dumb/qemu-xtensa.git;a=commitdiff;h=53add759be1a39063cfc52ca2a6d0fcdd1091697 53add759be1a39063cfc52ca2a6d0fcdd1091697] (target-xtensa: add dc232b core) and [http://jcmvbkbc.spb.ru/git/?p=dumb/qemu-xtensa.git;a=commitdiff;h=935f7a2b428f71a40e985f09955bccaaf09518fa 935f7a2b428f71a40e985f09955bccaaf09518fa] (target-xtensa: add fsf core) for example:		Starting with QEMU-2.2 there's a script [https://github.com/OSLL/qemu-xtensa/blob/master/target-xtensa/import_core.sh qemu/target-xtensa/import_core.sh] that adds new core to QEMU from the xtensa configuration overlay.

			To manually extend QEMU with new xtensa core an appropriate XtensaConfig structure must be registered. This structure may be mostly automatically filled in from the overlay data, see mainline commits [http://jcmvbkbc.spb.ru/git/?p=dumb/qemu-xtensa.git;a=commitdiff;h=53add759be1a39063cfc52ca2a6d0fcdd1091697 53add759be1a39063cfc52ca2a6d0fcdd1091697] (target-xtensa: add dc232b core) and [http://jcmvbkbc.spb.ru/git/?p=dumb/qemu-xtensa.git;a=commitdiff;h=935f7a2b428f71a40e985f09955bccaaf09518fa 935f7a2b428f71a40e985f09955bccaaf09518fa] (target-xtensa: add fsf core) for example:
	* target-xtensa/core-<core name>/core-isa.h is a copy of config/core.h from xtensa-config-overlay.tar.gz;		* target-xtensa/core-<core name>/core-isa.h is a copy of config/core.h from xtensa-config-overlay.tar.gz;
	* target-xtensa/core-<core name>/gdb-config.c is made from gdb/xtensa-config.c from xtensa-config-overlay.tar.gz, only rmap entries for PC, A, AR, SR, UR are retained;		* target-xtensa/core-<core name>/gdb-config.c is made from gdb/xtensa-config.c from xtensa-config-overlay.tar.gz, only rmap entries for PC, A, AR, SR, UR are retained;
	* XtensaConfig::gdb_regmap::num_regs is the total number of rmap entries in the gdb-config.c;		* XtensaConfig::gdb_regmap::num_regs is the total number of rmap entries in the gdb-config.c;
	* XtensaConfig::gdb_regmap::num_core_regs is the number of contiguous non-privileged ((flags & 1) == 0) rmap entries in the gdb-config.c.		* XtensaConfig::gdb_regmap::num_core_regs is the number of contiguous non-privileged ((flags & 1) == 0) rmap entries in the gdb-config.c.

	~~There's also a (draft) script that adds new core to QEMU from the xtensa configuration overlay [https://github.com/OSLL/qemu-xtensa/blob/xtensa-cores/target-xtensa/import_core.sh here].~~

Jcmvbkbc: Fix broken formatting in -kernel

2014-09-11T16:46:01Z

Fix broken formatting in -kernel

← Older revision		Revision as of 16:46, 11 September 2014
Line 36:		Line 36:
	\| -semihosting		\| -semihosting
	\|-		\|-
	\| -kernel <elf-image\|uImage>		\| -kernel <elf-image/uImage>
	\| Load elf-image or uImage and start emulation from its entry point. Note that image is loaded to virtual addresses it is linked for. For XTFPGA this option also chooses 'boot from SRAM' mode, mapping SRAM to the System ROM region at physical address 0xFE000000.		\| Load elf-image or uImage and start emulation from its entry point. Note that image is loaded to virtual addresses it is linked for. For XTFPGA this option also chooses 'boot from SRAM' mode, mapping SRAM to the System ROM region at physical address 0xFE000000.
	\| -kernel xtensa-2.6.29-smp/arch/xtensa/boot/Image.elf		\| -kernel xtensa-2.6.29-smp/arch/xtensa/boot/Image.elf

Jcmvbkbc: More updates: initrd, dtb, FLASH sizes, monitor to telnet, gdb to arbitrary port

2014-09-11T16:44:31Z

More updates: initrd, dtb, FLASH sizes, monitor to telnet, gdb to arbitrary port

← Older revision		Revision as of 16:44, 11 September 2014
Line 28:		Line 28:
	\| -cpu dc232b		\| -cpu dc232b
	\|-		\|-
	\| -m ~~megs~~		\| -m <memory size>
	\| Set emulated RAM size ~~to megs MB~~		\| Set emulated RAM size. M and G suffixes for mega- and gigabytes.
	\| -m ~~128~~		\| -m 128M
	\|-		\|-
	\| -semihosting		\| -semihosting
Line 36:		Line 36:
	\| -semihosting		\| -semihosting
	\|-		\|-
	\| -kernel <elf-image>		\| -kernel <elf-image\|uImage>
	\| Load elf-image and start emulation from its entry point. Note that image is loaded to virtual addresses it is linked for. For ~~LX60/LX200~~ this option also chooses 'boot from SRAM' mode, mapping SRAM to the System ROM region at physical address 0xFE000000.		\| Load elf-image or uImage and start emulation from its entry point. Note that image is loaded to virtual addresses it is linked for. For XTFPGA this option also chooses 'boot from SRAM' mode, mapping SRAM to the System ROM region at physical address 0xFE000000.
	\| -kernel xtensa-2.6.29-smp/arch/xtensa/boot/Image.elf		\| -kernel xtensa-2.6.29-smp/arch/xtensa/boot/Image.elf
	\|-		\|-
Line 43:		Line 43:
	\| (Not for sim) Wrap kernel arguments into the bootparameters block and pass pointer to it to the elf-image in a2.		\| (Not for sim) Wrap kernel arguments into the bootparameters block and pass pointer to it to the elf-image in a2.
	\| -append 'console=ttyS0 ip=dhcp root=/dev/nfs rw'		\| -append 'console=ttyS0 ip=dhcp root=/dev/nfs rw'
			\|-
			\| -initrd <initrd-image>
			\| (Not for sim) Load initial RAM disk image and pass its location to kernel in the bootparameters block.
			\| -initrd buildroot-build/images/rootfs.cpio
			\|-
			\| -dtb <Device-Tree-Blob>
			\| (Not for sim) Load DTB image and pass its location to kernel in the bootparameters block.
			\| -dtb xtensa-build/arch/xtensa/boot/dts/kc705.dtb
	\|-		\|-
	\| -pflash <flash-image>		\| -pflash <flash-image>
	\| (Not for sim) Mount flash-image as a system FLASH. Note that image size must match platform FLASH size (4MB for LX60, 16MB for LX200).		\| (Not for sim) Mount flash-image as a system FLASH. Note that image size must match platform FLASH size (4MB for LX60, 16MB for LX200, 32MB for ML605, 128MB for KC705).
	\| -pflash u-boot.dc232b_xtav200.flash		\| -pflash u-boot.dc232b_xtav200.flash
	\|-		\|-
Line 61:		Line 69:

	The sim platform is modelled after Tensilica ISS. It may run ELF images built for ISS, see e.g. [[Buildroot_Build_Instructions#Build_and_Run_a_Linux_Kernel_on_the_Instruction_Set_Simulator_(ISS)\|Build and Run a Linux Kernel on the Instruction Set Simulator (ISS)]].		The sim platform is modelled after Tensilica ISS. It may run ELF images built for ISS, see e.g. [[Buildroot_Build_Instructions#Build_and_Run_a_Linux_Kernel_on_the_Instruction_Set_Simulator_(ISS)\|Build and Run a Linux Kernel on the Instruction Set Simulator (ISS)]].
	There's only SIMCALL external interface available for the sim machine. To avoid console interference with QEMU monitor, monitor should be disabled with -monitor null or moved to network interface.		There's only SIMCALL external interface available for the sim machine. To avoid console interference with QEMU monitor, monitor should be disabled with -monitor null or moved to network interface with e.g. -monitor tcp::1236,telnet,server,nowait.

	$ '''qemu-system-xtensa -cpu dc232b -M sim -m 128M -semihosting -nographic -monitor null \'''		$ '''qemu-system-xtensa -cpu dc232b -M sim -m 128M -semihosting -nographic -monitor null \'''
	'''-kernel sim-2.6.29-smp/arch/xtensa/boot/Image.elf'''		'''-kernel sim-2.6.29-smp/arch/xtensa/boot/Image.elf'''
Line 96:		Line 105:
	== Debugging with QEMU ==		== Debugging with QEMU ==
	=== GDB ===		=== GDB ===
	There's builtin GDB server in the QEMU. -s command line switch activates it on the address 0.0.0.0:1234, -S switch stops QEMU at the first guest instruction waiting for 'continue' command from gdb.		There's builtin GDB server in the QEMU. -s command line switch activates it on the address 0.0.0.0:1234 (-gdb tcp:<ip>:<port> may be used instead of -s to change address and port to listen), -S switch stops QEMU at the first guest instruction waiting for 'continue' command from gdb.

	$ '''qemu-system-xtensa -M lx200 -nographic -pflash lx200.flash \'''		$ '''qemu-system-xtensa -M lx200 -nographic -pflash lx200.flash \'''

Jcmvbkbc: Update information on boards, gdb fixup script and core importing script

2014-09-11T15:48:00Z

Update information on boards, gdb fixup script and core importing script

← Older revision		Revision as of 15:48, 11 September 2014
Line 65:		Line 65:
	'''-kernel sim-2.6.29-smp/arch/xtensa/boot/Image.elf'''		'''-kernel sim-2.6.29-smp/arch/xtensa/boot/Image.elf'''

	~~== LX60/LX200 platform ==~~		Since the QEMU doesn't manage terminal settings in semihosting mode, ^C and other terminal control codes interrupt QEMU instead of its guest. stty raw may be used to set up terminal not to terminate QEMU.

	LX60/LX200 platform emulates system RAM, board-specific FPGA, UART, OpenCores 10/100 Mbit Ethernet MAC, National Semiconductors DP83848C 10/100 PHY and parallel FLASH.		== XTFPGA (LX60/LX200/ML605/KC705/...) platforms ==

			XTFPGA platform emulates system RAM, board-specific FPGA, UART, OpenCores 10/100 Mbit Ethernet MAC, National Semiconductors DP83848C 10/100 PHY and parallel FLASH.
	The platform may boot from either SRAM (when -kernel option is specified, SRAM is mapped to the System ROM region and ELF image is loaded) or from FLASH.		The platform may boot from either SRAM (when -kernel option is specified, SRAM is mapped to the System ROM region and ELF image is loaded) or from FLASH.

	NFS root export record for user network (there's no way to specify root-path option for the QEMU builtin DHCP server. Unless kernel parameter '~~rootpath~~' is given, you'll have to put the rootfs to /tftpboot/<hostname>):		NFS root export record for user network (there's no way to specify root-path option for the QEMU builtin DHCP server. Unless kernel parameter 'nfsroot' is given, you'll have to put the rootfs to /tftpboot/<hostname>):
	/tftpboot/ 127.0.0.1(rw,no_root_squash,insecure)		/tftpboot/ 127.0.0.1(rw,no_root_squash,insecure)

Line 89:		Line 91:
	$ '''qemu-system-xtensa -cpu dc232b -M lx200 -m 96M -nographic \'''		$ '''qemu-system-xtensa -cpu dc232b -M lx200 -m 96M -nographic \'''
	'''-net nic,vlan=0 -net user,vlan=0,tftp=.,hostname=dc232b-lx200 -pflash lx200.flash'''		'''-net nic,vlan=0 -net user,vlan=0,tftp=.,hostname=dc232b-lx200 -pflash lx200.flash'''

			(Note that KC705 expects bootloader to be at the offset 0x06000000 in the FLASH, unlike the older boards that boot at offset 0).

	== Debugging with QEMU ==		== Debugging with QEMU ==
Line 98:		Line 102:
	'''-kernel u-boot-xtensa.git/u-boot.dc232b_xtav200 -s -S'''		'''-kernel u-boot-xtensa.git/u-boot.dc232b_xtav200 -s -S'''

	By default xtensa gdb may only access unprivileged core registers. To allow access to all available registers ./gdb/xtensa-config.c needs to be modified, marking privileged registers as non-privileged.		By default xtensa gdb may only access unprivileged core registers. To allow access to all available registers ./gdb/xtensa-config.c needs to be modified, marking privileged registers as non-privileged. If [https://github.com/jcmvbkbc/xtensa-toolchain-build these scripts] are used to build the toolchain, the fixup-gdb.sh step does that.

	GDB breakpoints, watchpoints, single-stepping and other debugging features work as usual.		GDB breakpoints, watchpoints, single-stepping and other debugging features work as usual.
Line 188:		Line 192:
	* XtensaConfig::gdb_regmap::num_regs is the total number of rmap entries in the gdb-config.c;		* XtensaConfig::gdb_regmap::num_regs is the total number of rmap entries in the gdb-config.c;
	* XtensaConfig::gdb_regmap::num_core_regs is the number of contiguous non-privileged ((flags & 1) == 0) rmap entries in the gdb-config.c.		* XtensaConfig::gdb_regmap::num_core_regs is the number of contiguous non-privileged ((flags & 1) == 0) rmap entries in the gdb-config.c.

			There's also a (draft) script that adds new core to QEMU from the xtensa configuration overlay [https://github.com/OSLL/qemu-xtensa/blob/xtensa-cores/target-xtensa/import_core.sh here].

Jcmvbkbc: dc233c is now supported

2012-08-07T21:30:43Z

dc233c is now supported

← Older revision		Revision as of 21:30, 7 August 2012
Line 4:		Line 4:

	Starting with version 1.0 QEMU offers [http://wiki.qemu.org/Features/Xtensa Xtensa architecture emulation].		Starting with version 1.0 QEMU offers [http://wiki.qemu.org/Features/Xtensa Xtensa architecture emulation].
	DC232B (LE) and fsf (BE) cores are supported on sim and LX60/LX200 platforms.		DC232B, DC233C (LE) and fsf (BE) cores are supported on sim and LX60/LX200 platforms.

	== Getting and building QEMU ==		== Getting and building QEMU ==

Jcmvbkbc: Add debug logging subsection

2011-11-20T03:15:38Z

Add debug logging subsection

@@ Line 91: / Line 91: @@
 == Debugging with QEMU ==
+=== GDB ===
 There's builtin GDB server in the QEMU. -s command line switch activates it on the address 0.0.0.0:1234, -S switch stops QEMU at the first guest instruction waiting for 'continue' command from gdb.
@@ Line 146: / Line 146: @@
      f8000000-f83fffff (prio 0): lx60.io.flash
      fe000000-fe01ffff (prio 0): lx60.sram
 == Extending QEMU ==