Microblaze Linux/Qemu/U-Boot wiki - ecos

Add custom board to mONeCos

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	====== Add custom board to mONeCos ======
	+	* A custom board can be added by ''mon_new_platform''
	+	* the script description is [[ecos:script\|here]]
	+
	+	* Move to your design folder
	+	* for reference designs to ''hw/design'' folder
	+	* for custom designs to ''hw/user-design'' folder
	+
	+	* Run ''mon_new_platfrom'' script there
	+	* script is in your path
	+
	+
	+	* The following log shows correct output of ''mon_new_platform'' script
	+
	+	[monstr@monstr Xilinx-Spartan3E1600-RevA-edk92-opb]$ mon_new_platform
	+	Distribution is set corectly
	+	Success
	+	Thank you for using this simple script
	+
	+	* Continue the manual with
	+	* compiling [[ecos:redboot\|RedBoot]]
	+	* compiling [[ecos:ecos:ecos\|eCos kernel]]
	+
	+	===== Problems =====
	+	==== Script not found? ====
	+	* go to mONeCos root folder and source ''ecosenv.sh'' script
	+
	+	[monstr@monstr ~]$ cd /home/projects/ecos/
	+	[monstr@monstr ecos]$ . ecosenv.sh
	+	Your ECOS root is set to '/home/projects/ecos'
	+
	+	==== Script failed ====
	+	Script failure may indicate two problems
	+	* first -- you forgot to set your software BSP
	+	* open MSS file
	+	* find latest ecos BSP record
	+	* second -- you forgot to build library
	+	* in EDK: Software -> Generate Libraries and BSPs
	+	* in shell: ''make -f system.make libs''
	+	* [[ecos:script\|more infomation]] about script
	+
	+

eCos BSP

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	====== eCos BSP ======
	+	New ecos BSP was developed for improving configuration. The BSP is located in ''hw/edk_repository''. The BSP helps you generate eCos configuration for your design. Together with ''mon_new_platfrom'' script, it brings up a powerful tool for adding new platforms to mONeCos distribution. If you experience any problems with the ecos BSP, please, report them to Michal Simek.
	+
	+	===== How to work with =====
	+
	+
	+	* run EDK
	+	* Windows: Start -> Programs -> Xilinx EDK -> Xilinx Platform Studio
	+	* Linux: ''source'' your Xilinx tools (ISE and EDK) and run ''xps''
	+
	+	[monstr@monstr ~]$ cd /opt/xilinx/ise92i/
	+	[monstr@monstr ise92i]$ . settings.sh
	+	[monstr@monstr ise92i]$ cd ../edk92i/
	+	[monstr@monstr edk92i]$ . settings.sh
	+	[monstr@monstr edk92i]$ xps
	+
	+
	+	* open your design and configure software setting Software -> Software Platform Settings
	+	* choose OS & Library setting to latest ecos BSP
	+	* set the correct value of CORE_CLOCK_FREQ_HZ
	+	* this value is used for eCos timing setting
	+	* the following figure shows setting the BSP
	+
	+	{{:ecos:xps.png\|Software platform settings}}
	+
	+	* choose a proper name for your design -- this name will be used in mONeCos
	+	* avoid using "/" character!
	+
	+
	+	{{:ecos:xps1.png\|Software platform settings OS & Lib}}
	+
	+
	+	* here is a corresponding block that was added in ''system.mss'' file
	+
	+	PARAMETER VERSION = 2.2.0
	+
	+	BEGIN OS
	+	PARAMETER OS_NAME = ecos
	+	PARAMETER OS_VER = 1.00.a
	+	PARAMETER PROC_INSTANCE = microblaze_0
	+	PARAMETER name = Spartan 3E1600
	+	END
	+
	+
	+	* build your library
	+	* Software -> Generate Libraries and BSPs
	+	* or alternatively from a shell you can call
	+
	+	make -f system.make libs
	+
	+	* here is the interesting part of log, you can see calling eCos BSP
	+
	+	[monstr@monstr Xilinx-Spartan3E1600-RevA-edk92-opb-gpio]$ make -f system.make libs
	+	*********************************************
	+	Creating software libraries...
	+	*********************************************
	+	...
	+	Running generate for OS'es, Drivers and Libraries ...
	+	#--------------------------------------
	+	# eCos BSP generate...
	+	#--------------------------------------
	+	Microblaze CPU
	+	#--------------------------------------
	+	# Standalone BSP generate...
	+	#--------------------------------------
	+	Calling standalone::generate
	+	Copying Library Files ...
	+	...
	+	Running execs_generate for OS'es, Drivers and Libraries ...
	+
	+	LibGen Done.
	+
	+	* if the configuration ends without any error you can continue to [[ecos:board\|next step]]
	+	* please report any problems to Michal Simek
	+
	+	===== TIPS =====
	+	To save your time, you can also use [[bsp:bsp\|top BSP]], which generates all BSPs for your eCos, Linux, U-Boot, [[http://developer.petalogix.com/PetaLinux]] and standalone applications. Reference design Xilinx-Spartan3E1600-RevA-xps-edk92 shows this feature. (PetaLinux BSP is not distributed with mONeCos)
	+
	+	BEGIN OS
	+	PARAMETER OS_NAME = top
	+	PARAMETER OS_VER = 1.00.b
	+	PARAMETER PROC_INSTANCE = microblaze_0
	+	PARAMETER name = Xilinx Spartan3e1600 xps edk92
	+	PARAMETER timer = xps_timer_1
	+	PARAMETER ethernet = Ethernet_MAC
	+	PARAMETER gpio = LEDs_6Bit
	+	PARAMETER lmb_memory = dlmb_cntlr
	+	PARAMETER flash_memory = FLASH
	+	PARAMETER main_memory = DDR_SDRAM
	+	PARAMETER stdin = RS232_DTE
	+	PARAMETER stdout = RS232_DTE
	+	END
	+
	+	===== License =====
	+	The ecos BSP is written under restricted license. You are not allowed to change and distribute the BSP without permission from Michal Simek. You can use these files without any restriction.
	+
	+	===== Future work =====
	+	* in empty name called this platform with the name of folder where project is
	+

Configtool

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	===== Configtool ======
	+	eCos configuration tool is a graphical tool to help a user configure and build a custom version of the eCos operating system. In mONeCos distribution, there is a precompiled version of this tool.
	+
	+	===== Configtool preparing =====
	+	* test precompiled configtool version included in distribution
	+	* you have to compile configtool yourself
	+	* use compilation script (mONeCos/tools/src/tool) from distribution which follows manual at [[http://www.ecoscentric.com/devzone/configtool.shtml\|ConfigTool]]
	+	* after compilation, use ''ecosenv.sh'' script to add compiled configtool to your path
	+	* running configtool is described below
	+
	+	[monstr@monstr ~]$ configtool
	+
	+	* if you see welcome page with i386 architecture your configtool works well
	+
	+	{{:ecos:i386.png\|Welcome page}}
	+
	+	* continue with building your [[ecos:designs\|hardware design]]
	+
	+
	+	===== Problems =====
	+	==== Segmentation fault ====
	+	You don't have permission to work with default folders
	+
	+	[monstr@monstr monecos]$ configtool
	+	[b7ef86d0 M 08:49:25] Failed to change to /home/monstr/.eCosPlatforms from /home/projects/monecos
	+	[b7ef86d0 M 08:49:25] Failed to initialize any targets
	+	Segmentation fault
	+
	+	* Solution 1: Look at to your home folder on .eCosConfigTool file and change paths
	+
	+
	+
	+	===== CentOS 5.1 =====
	+	* you have to install some packages before you start use and compile config tools
	+	* here is the list of packages
	+	* yum install tcl-devel.i386
	+	* yum install tk-devel.i386
	+	* yum install libXi-devel.i386
	+	* yum install glib-devel.i386
	+	* yum install gtk+-devel.i386

Reference designs

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	====== Reference designs ======
	+	In mONeCos distribution you can find some reference designs. These designs are placed in hw/design folder. In pre-built folder, there are placed bitstream, RedBoot and eCos with a test application.
	+
	+	===== List of reference designs =====
	+
	+	^Board^Design^Reference design name^eCos template name^RedBoot^eCos^
	+	\|S3E1600E\|opb\|Xilinx-Spartan3E1600-RevA-opb-edk92\|Xilinx Spartan3e1600 opb edk92 \|yes\|yes\|
	+	\|S3E1600E\|plb\|Xilinx-Spartan3E1600-RevA-xps-edk92\|Xilinx Spartan3e1600 xps edk92 \|yes\|yes\|
	+	\|ml505\|plb\|Xilinx-ml505-xps-edk92\|Xilinx ml505 xps edk92\|yes\|in progress\|
	+
	+
	+	* for eCos configuration use [[ecos:bsp\|ecos BSP]] or [[bsp:bsp\|top BSP]].
	+	* read design rules below
	+	* continue with the manual [[ecos:bsp\|here]]
	+
	+
	+	===== Design rules =====
	+	* use only [[designs#supported peripherals\|supported peripherals]] for working with mONeCos
	+	* for different IPs is necessary to change BSP - for this please contact me
	+	* run [[ecos:bsp\|ecos BSP]] before you start building bitstream
	+	* Microblaze limitation
	+	* use MSR instruction
	+	* use Barrel shifter
	+	* locate BRAM memory from zero address
	+	* check correctness of CORE_CLOCK_FREQ_HZ
	+	* current eCos BSP checks if your system contains minimally one uart16550 because only this driver is fully supported in eCos kernel
	+	* if you don't have uart16550 and you have one uartlite BSP shows warning about and you may have some problems with compilation
	+	* look at reference design - you can see that every system contains uart16550 and uartlite
	+	* if uartlite is in your system and it is enabled in configtool, RedBoot sends output to both serial interface but you can only work with uartlite
	+
	+
	+	===== Supported peripherals =====
	+	^Category^IP name^Version^State^
	+	\|CPU\|Microblaze\|4.00.a\|Works\|
	+	\| \|Microblaze\|7.00.b\|Works\|
	+	\|Serial\|opb_uart16550\|1.00.d\|Full support\|
	+	\| \|xps_uart16550\|1.00.a\|Full support\|
	+	\| \|opb_uartlite\|1.00.b\|BSP support\|
	+	\| \|xps_uartlite\|1.00.a\|BSP support\|
	+	\|Diagnostic output\|opb_uart16550\|1.00.b\|Xdriver support\|
	+	\| \|xps_uart16550\|1.00.a\|Xdriver support\|
	+	\| \|opb_uartlite\|1.00.b\|Xdriver support\|
	+	\| \|xps_uartlite\|1.00.a\|Xdriver support\|
	+	\|Ethernet\|opb_ethernetlite\|1.01.b\|Xdriver support\|
	+	\| \|xps_emaclite\|1.00.a\|Xdriver support\|
	+	\|GPIO\|xps_gpio\|1.00.a\|Simple support\|
	+	\| \|opb_gpio\|3.01.b\|Simple support\|
	+	\|Storage\|sysace\| \|PowerPC support\|
	+	\|Memory\|mpmc\|3.00.b\|Works\|
	+	\| \|mch_opb_ddr\|1.00.a\|Works\|
	+	\|Timer\|opb_timer\|1.00.b\|Full support\|
	+	\| \|xps_timer\|1.00.a\|Full support\|
	+	\|Interrupt controller\|opb_intc\|1.00.c\|Full support\|
	+	\| \|xps_intc\|1.00.a\|Full support\|
	+
	+	<!-- \| \|mch_opb_ddr2\|1.02.a\|Works\| -->
	+
	+
	+
	+	* Simple support -- Support in BSP and simple eCos driver
	+	* Full support -- Support in BSP and native eCos driver
	+	* Xdriver support -- Support in BSP and eCos driver based on Xilinx drivers
	+	* BSP support -- Support only in BSP
	+	* PowerPC support -- The driver exists for PowerPC405
	+	* Works -- Working with current eCos version - partial support

mONeCos - eCos distribution for Microblaze CPU

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	{{ :ecos:ecos.gif\|Logo }}
	+	====== mONeCos - eCos distribution for Microblaze CPU ======

	+	Hi developers,
	+
	+	It is pleasure for me to introduce first working eCos distribution called mONeCos for Microblaze CPU.
	+	I would like to say big thanks to Tomas Brabec, Michal Pfeifer and [[http://www.cvut.cz\|Czech Technical University]], [[http://www.fel.cvut.cz\|Faculty of Electrical Engineering]], [[http://cs.felk.cvut.cz\|Department of Computer Science and Engineering]] for help with doing first distribution based on eCos.
	+
	+
	+
	+	Michal Simek acknowledges [[http://www.petalogix.com\|PetaLogix]] for lending the reference board and [[http://www.xilinx.com\|Xilinx]] for providing design tool and the reference board.
	+
	+
	+
	+	I wish you many good experiences with mONeCos.
	+
	+
	+
	+	Best regards,
	+
	+	Michal Simek
	+	===== History =====
	+
	+	The eCos kernel for Microblaze CPU was developed at [[http://cs.felk.cvut.cz\|CTU]] by Michal Pfeifer((The diploma thesis is available in czech [[https://dip.felk.cvut.cz/browse/pdfcache/pfeifm1_2008dipl.pdf\|here]].)) (Tomas Brabec (supervisor) and me (Michal Simek) as opponent for this diploma work). This kernel is based on PowerPC405.
	+
	+	=== State before my changes ===
	+
	+	* the kernel was ported to one board that brought many problems to work with
	+	* the kernel was developed on Windows machine under cygwin
	+	* the kernel contained lot of commented and unused code
	+	* final application needed full software setting and drivers from Xilinx EDK
	+
	+	=== What my changes are ===
	+
	+	* I prepared new ecos config BSP tool for boards
	+	* I ported the kernel to Linux
	+	* I completely redesigned board handling which was taken from PowerPC405
	+	* I optimized this kernel for using with BSP tool and with many boards
	+	* I wrote some helping scripts
	+	* I tested the kernel
	+	* and many other things which are only small step for use but big step for work with
	+
	+	These facts helped with creating new eCos distribution which is optimized for Xilinx Microblaze CPU called mONeCos distribution.
	+
	+	== mONeCos distribution is maintained by Michal Simek and hosted only at http://www.monstr.eu. Please send feedback on using this distribution back to me. ==
	+
	+
	+	===== License =====
	+	This distribution contains files, which are written under restricted license, owned by Michal Simek. Private license is placed on the top of these files. You are not allowed to change and distribute these files without permission from Michal Simek. You can use these files without any restriction.
	+	===== Disclaimer =====
	+	This distribution is only a release for testing purposes and should not be used for life support, aerospace or other life- or mission-critical applications. Michal Simek does not respond for any claims caused by using mONeCos distribution.
	+	===== Overview =====
	+	mONeCos distribution is divided into three categories. First is focused on hardware (hw folder), second on software (sw folder) and third on tools.
	+
	+	=== Hardware ===
	+
	+	''Hardware'' folder contains three sub-folders. ''Design'' folder contains [[ecos#reference design\|reference designs]] used in eCos templates. Inside the ''pre-build'' folder, there is a bitstream, redboot and eCos elf file with testing application for reference designs. The folder ''user-design'' is prepared for custom designs. The folder ''edk_user_repository'' stores a BSP, which helps you setting the eCos kernel. Usage of BSP is described in [[ecos#BSP\|special paragraf]].
	+
	+	=== Software ===
	+	''Software'' folder contains three folders. Namely ''ecos-2.0'' containg eCos kernel, ''project'' containing projects for prepared reference boards, and ''user-projects'' prepared for your custom applications.
	+
	+
	+	=== Tools ===
	+	This folder contains a toolchain for Microblaze CPU, some helping scripts, and a packed source code for [[ecos#configtool\|configtool]].
	+
	+
	+	===== Documentation =====
	+	The following documentation covers work with mONeCos distribution
	+
	+	* [[ecos:prepare\|Work preparation]]
	+	* [[ecos:configtool\|Configtool]]
	+	* [[ecos:designs\|Reference designs]]
	+	* [[ecos:bsp\|Setup ecos BSP]]
	+	* [[ecos:board\|Add custom board to mONeCos]]
	+	* [[ecos:redboot\|RedBoot]]
	+	* [[ecos:redboot:usage\|RedBoot usage manual]]
	+	* [[ecos:ecos:ecos\|eCos]]
	+	* [[ecos:ecos:own\|Create own application]]
	+	* [[ecos:ecos:app\|Useful application]]
	+	* [[ecos:ecos:tests\|Kernel Tests]]
	+	* [[ecos:script\|Script description]]
	+
	+
	+	===== Download =====
	+
	+	^Version^Size^MD5SUM^SHA1SUM^Description^
	+	\|[[http://www.monstr.eu/monecos-pre-1.tar.gz\|monecos-pre-1.tar.gz]]\|80MB\|91d5ac374f57b1f34d50d9e76c0b90f5\|7b6b08a0924487f1c729891a23bae31158dc78c4\|Full distribution\|
	+	\|[[http://www.monstr.eu/ecos_v2_00_a.tar.gz\|ecos_v2_00_a.tar.gz]]\|6k\|afa50ff9656cc59b315aef9ee876ba2a\|09df604f4e747b419ff564bfcbfe66c2f93f917b\|Updated BSP for [[https://github.com/flyskywhy/ecos/blob/microblaze/README.md\|ecos port by Li Zheng]]\|
	+
	+	===== External documentation =====
	+	* {{:ecos:ecos-dev-guide.pdf\|Embedded Software Development with eCos}} by Anthony J. Massa
	+	* {{:ecos:ecos-user-guide-a4.pdf\|eCos User's Guide}} - A guide for installing eCos and using the host tools.
	+	* {{:ecos:ecos-ref-a4.pdf\|eCos Reference Manual}} - Reference documentation for all eCos packages.
	+	* {{:ecos:ecos-2.0-cdl-guide-a4.pdf\|eCos Component Writer's Guide}} - A guide for authors of new eCos packages.
	+	* [[http://ecos.sourceware.org/docs-latest/redboot/redboot-guide.html\|RedBoot user guide]] - A guide for installing and using the RedBoot debug and bootstrap monitor.
	+
	+	===== External links =====
	+	* http://ecos.sourceware.org/ecos/
	+	* http://www.ecoscentric.com/devzone/configtool.shtml
	+	* http://en.wikipedia.org/wiki/ECos
	+
	+	<!--
	+	* http://ecos.sourceware.org/ecos/anoncvs.html
	+	* http://sources.redhat.com/ecos/build-toolchain.html
	+	* http://sources.redhat.com/ecos/mirror.html
	+	* http://mind.be/?page=virtex-ecos - xilinx ppc405 support
	+	* http://ecos.sourceware.org/ml/ecos-patches/2004-10/msg00055.html
	+	* http://typo3.cs.uni-paderborn.de/fileadmin/Informatik/AG-Platzner/Research/ReconOS/eCos-ML403/ecos-ML403-miniHOWTO.txt
	+	-->

Work preparation

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	====== Work preparation ======
	+	This manual gives you introduction how to work with mONeCos distribution on Microblaze CPU.

	+	mONeCos distribution is tested under:
	+	* CentOS 5.1
	+	* CentOS 4.5 (recompilation of configtool required)
	+	Operation under Cygwin hasn't been tested yet but it will be possible in near feature.
	+
	+	\\
	+
	+	System setup:
	+	* Download mONeCos distribution from [[ecos:ecos\|mainpage]]
	+	* Unpack eCos distribution tarball to your location
	+	* my location is in /home/projects folder
	+
	+	mkdir /home/projects/
	+	cd /home/projects/
	+	gunzip -9c monecos-distr_pre_v1.tar.gz \| tar xvf -
	+
	+	* Move to mONeCos distribution and ''source'' ecosenv.sh script
	+	* ''ecosenv.sh'' script sets up shell variables, without this you can't work with mONeCos
	+
	+	[monstr@monstr ~]$ cd /home/projects/monecos/
	+	[monstr@monstr monecos]$ . ecosenv.sh
	+	Your ECOS root is set to '/home/projects/monecos'
	+
	+	* continue with testing configtool [[ecos:configtool\|here]]

RedBoot

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	====== RedBoot ======
	+	RedBoot is bootloader based on eCos Hardware Abstraction Layer. For more information look at http://sourceware.org/redboot/.
	+	===== How to compile RedBoot =====

	+	* choose Build->Templates
	+	* choose your board -- the name for reference board corresponds with table at [[ecos:designs\|reference design page]]
	+	* choose redboot package -- look at figure below
	+
	+	{{:ecos:temp-redboot.png\|Redboot template}}
	+
	+	* on the following figure you can see a list of choices and peripherals corresponidng to your design
	+
	+	{{:ecos:red1.png\|Redboot}}
	+
	+	* save your generated RedBoot project
	+	* ''sw/user-projects'' folder is used for this purpose
	+
	+	{{:ecos:red2.png\|Folder choosing}}
	+
	+	* build your redboot, Build->Library (F7)
	+	* check your RedBoot was built correctly
	+
	+	{{:ecos:red3.png\|Building succesfully}}
	+
	+	* move to folder where your RedBoot is
	+
	+	[monstr@monstr ~]$ cd /home/projects/ecos/sw/user-projects/s3e1600-redboot/
	+
	+	* there are some generated folders
	+	* ''redboot_build''
	+	* ''redboot_install''
	+	* ''bin'' folder contains ''redboot.elf''
	+	* ''redboot_mlt'' -- memory layout
	+	* ''redboot.ecc'' -- project settings
	+	* TIP add ''xmd.ini'' file to this folder
	+	* ''xmd.ini'' helps you with loading redboot to your board
	+	* ''xmd.ini'' is not automaticky created by the configtool, you have to add it yourself or load RedBoot with XMD command
	+
	+	[monstr@monstr s3e1600-redboot]$ cat xmd.ini
	+	connect mb mdm
	+	dow redboot_install/bin/redboot.elf
	+	run
	+	exit
	+
	+	* before running xmd, setup your serial terminal first
	+	* kermit serial terminal is recommended
	+	* default baudrate for uart16550 is 9600 without flow control
	+	* baudrate for uartlite is defined in MHS file
	+
	+	* load redboot into the board
	+	* run ''xmd'' in project folder
	+	* ''xmd.ini'' is automatictly loaded, if it exists
	+
	+	[monstr@monstr s3e1600-redboot]$ xmd
	+	Xilinx Microprocessor Debug (XMD) Engine
	+	Xilinx EDK 9.2.02 Build EDK_Jm_SP2.3
	+	Copyright (c) 1995-2007 Xilinx, Inc. All rights reserved.
	+
	+	XMD%
	+	Info:AutoDetecting cable. Please wait.
	+	...
	+	Info:Reusing A0060001 key.
	+	Info:Reusing 24060001 key.
	+	Info:Connecting to cable (Usb Port - USB21).
	+	Info:Checking cable driver.
	+	Info:File version of /opt/xilinx/ise92i/bin/lin/xusbdfwu.hex = 1030.
	+	Info:File version of /etc/hotplug/usb/xusbdfwu.fw/xusbdfwu.hex = 1030.
	+	Info: WinDriver v9.00 Jungo (c) 1997 - 2007 Build Date: Mar 27 2007 X86 32bit 22:31:22.
	+	PORT_INDEX = 0.
	+	CB_CABLE_COUNTER = 0.
	+	DeviceAttach: Cable found for usb21.
	+	Calling setinterface num=0, alternate=0.
	+	DeviceAttach: received and accepted attach for:
	+	vendor id 0x3fd, product id 0x8, device handle 0x9fcbda8
	+	Info: Cable PID = 0008.
	+	Info: Max current requested during enumeration is 74 mA.
	+	Info:Type = 0x0004.
	+	Info: Cable Type = 3, Revision = 0.
	+	Info: Setting cable speed to 6 MHz.
	+	Info:Cable connection established.
	+	Info:Firmware version = 1301.
	+	Info:File version of /opt/xilinx/ise92i/data/xusb_xlp.hex = 1301.
	+	Info:Firmware hex file version = 1301.
	+	Info:ESN Family Code: 00
	+	Info:ESN: 000000000000
	+	Info:CPLD file version = 0012h.
	+	Info:CPLD version = 0012h.
	+
	+	JTAG chain configuration
	+	--------------------------------------------------
	+	Device ID Code IR Length Part Name
	+	1 21c3a093 6 XC3S1600E
	+	2 f5046093 8 XCF04S
	+	3 f5046093 8 XCF04S
	+	4 06e5e093 8 XC2C64A_VQ44_1532
	+
	+	MicroBlaze Processor Configuration :
	+	-------------------------------------
	+	Version............................4.00.a
	+	MMU Type...........................No_MMU
	+	No of PC Breakpoints...............2
	+	No of Read Addr/Data Watchpoints...0
	+	No of Write Addr/Data Watchpoints..0
	+	Instruction Cache Support..........on
	+	Instruction Cache Base Address.....0x22000000
	+	Instruction Cache High Address.....0x23ffffff
	+	Data Cache Support.................on
	+	Data Cache Base Address............0x22000000
	+	Data Cache High Address............0x23ffffff
	+	Exceptions Support................off
	+	FPU Support.......................off
	+	Hard Divider Support...............on
	+	Hard Multiplier Support............on - (Mul32)
	+	Barrel Shifter Support.............on
	+	MSR clr/set Instruction Support....on
	+	Compare Instruction Support........on
	+	Number of FSL ports................1
	+
	+	Connected to MDM UART Target
	+	Connected to "mb" target. id = 0
	+	Starting GDB server for "mb" target (id = 0) at TCP port no 1234
	+	System Reset .... DONE
	+	Downloading Program -- redboot_install/bin/redboot.elf
	+	section, .vectors: 0x00000000-0x0000016f
	+	section, .text: 0x2203e800-0x22054677
	+	section, .rodata: 0x22054678-0x2205721f
	+	section, .data: 0x22057220-0x2205781f
	+	section, .bss: 0x22057820-0x220618c7
	+	Setting PC with Program Start Address 0x00000000
	+
	+	Info:Processor started. Type "stop" to stop processor
	+
	+	* on your serial terminal you can see RedBoot output with prompt
	+
	+	+Emaclite_ETH - Warning! Using default ESA for 'emaclite'
	+	Ethernet eth0: MAC address 08:00:3e:28:7a:ba
	+	Can't get BOOTP info for device!
	+
	+	RedBoot(tm) bootstrap and debug environment [RAM]
	+	Non-certified release, version v2_0 - built 21:30:37, Jun 11 2008
	+
	+	Platform: Spartan 3E1600 (Microblaze 4.0a) by ecos_v1.00.a
	+	Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
	+	Copyright (C) 2008 Michal Simek <monstr@monstr.eu>
	+
	+	RAM: 0x22000000-0x24000000, 0x220618c8-0x23ffffff available
	+	RedBoot>
	+
	+	* if you have uart16550 and uartlite in your design, you can see output on the both serial lines but for writing character you can use only uartlite, if you want to use uart16550, disable uartlite in configtool
	+
	+
	+	* RedBoot usage manual is [[ecos:redboot:usage\|here]]
	+	* eCos building manual is [[ecos:ecos:ecos\|here]]
	+
	+	===== Notes =====
	+	* by default, IP address is obtained via BOOTP protocol
	+	* if you don't have a DHCP server, you can set IP adress in the configtool manually
	+
	+	===== Know limitation =====
	+	* you can't use bin image because elf file is assembled of two memory parts (BRAM and Main memory)
	+	* bin file is thus huge((Because it spans an address range from 0x0 -- where BRAM is -- to the address of your main memory, which dependson your HW configuration.)) and unusable -- this choice is turned off
	+	* if you have not enought space on your devel PC don't generate bin file
	+	* proposed solution is to have filled ''.vectors'' section (in BRAMs) by RedBoot code
	+
	+	===== Future work =====
	+	* add flash support

Script description

anonymous@undisclosed.example.com (Anonymous) — Tue, 01 Sep 2020 08:59:14 +0000

2026/04/17 20:49	current
Line 1:	Line 1:
	+	====== Script description ======
	+	===== mon_new_platform =====
	+	* the script adds a package and a target record to ''ecos.db'' (''sw/ecos-2.0/package'')
	+	* the script creates a folder in (''sw/ecos-2.0/package/hal/microblaze/'') with the name which you filled in for board name
	+	* spaces in the name are replaced by underscores
	+	* run the script in your design folder
	+	* the script takes no parameters
	+	* an example of usage is given [[ecos:board\|here]]

	+	<!-- ==== Error values ==== -->
	+
	+
	+	==== Know limitation ===
	+	* the script failed on paralel system when you use eCos BSP on Microblaze CPU which is not zero labeled
	+
	+
	+	===== mon_new_shell =====
	+	* this script is only for developing purposes
	+	* the script unpacks the prepared shell to your project
	+	* run the script in your project
	+	* the script creates a shell folder and starts to compile eCos shell application
	+
	+	==== Know limitation ===
	+	* shell uses ''printf'' messages which break application and kernel
	+
	+
	+	<!--
	+	===== mon_new_app =====
	+	* the script create simple testing application for your ecos test
	+	FIXME
	+	-->
	+
	+
	+	===== tool =====
	+	* the script is located at ''tools/src/''
	+	* the script is not in your path
	+	* the script compiles the configtool
	+

2026/04/17 20:49	current
Line 1:	Line 1:
	+	====== Reference designs ======
	+	In mONeCos distribution you can find some reference designs. These designs are placed in hw/design folder. In pre-built folder, there are placed bitstream, RedBoot and eCos with a test application.
	+
	+	===== List of reference designs =====
	+
	+	^Board^Design^Reference design name^eCos template name^RedBoot^eCos^
	+	\|S3E1600E\|opb\|Xilinx-Spartan3E1600-RevA-opb-edk92\|Xilinx Spartan3e1600 opb edk92 \|yes\|yes\|
	+	\|S3E1600E\|plb\|Xilinx-Spartan3E1600-RevA-xps-edk92\|Xilinx Spartan3e1600 xps edk92 \|yes\|yes\|
	+	\|ml505\|plb\|Xilinx-ml505-xps-edk92\|Xilinx ml505 xps edk92\|yes\|in progress\|
	+
	+
	+	* for eCos configuration use [[ecos:bsp\|ecos BSP]] or [[bsp:bsp\|top BSP]].
	+	* read design rules below
	+	* continue with the manual [[ecos:bsp\|here]]
	+
	+
	+	===== Design rules =====
	+	* use only [[designs#supported peripherals\|supported peripherals]] for working with mONeCos
	+	* for different IPs is necessary to change BSP - for this please contact me
	+	* run [[ecos:bsp\|ecos BSP]] before you start building bitstream
	+	* Microblaze limitation
	+	* use MSR instruction
	+	* use Barrel shifter
	+	* locate BRAM memory from zero address
	+	* check correctness of CORE_CLOCK_FREQ_HZ
	+	* current eCos BSP checks if your system contains minimally one uart16550 because only this driver is fully supported in eCos kernel
	+	* if you don't have uart16550 and you have one uartlite BSP shows warning about and you may have some problems with compilation
	+	* look at reference design - you can see that every system contains uart16550 and uartlite
	+	* if uartlite is in your system and it is enabled in configtool, RedBoot sends output to both serial interface but you can only work with uartlite
	+
	+
	+	===== Supported peripherals =====
	+	^Category^IP name^Version^State^
	+	\|CPU\|Microblaze\|4.00.a\|Works\|
	+	\| \|Microblaze\|7.00.b\|Works\|
	+	\|Serial\|opb_uart16550\|1.00.d\|Full support\|
	+	\| \|xps_uart16550\|1.00.a\|Full support\|
	+	\| \|opb_uartlite\|1.00.b\|BSP support\|
	+	\| \|xps_uartlite\|1.00.a\|BSP support\|
	+	\|Diagnostic output\|opb_uart16550\|1.00.b\|Xdriver support\|
	+	\| \|xps_uart16550\|1.00.a\|Xdriver support\|
	+	\| \|opb_uartlite\|1.00.b\|Xdriver support\|
	+	\| \|xps_uartlite\|1.00.a\|Xdriver support\|
	+	\|Ethernet\|opb_ethernetlite\|1.01.b\|Xdriver support\|
	+	\| \|xps_emaclite\|1.00.a\|Xdriver support\|
	+	\|GPIO\|xps_gpio\|1.00.a\|Simple support\|
	+	\| \|opb_gpio\|3.01.b\|Simple support\|
	+	\|Storage\|sysace\| \|PowerPC support\|
	+	\|Memory\|mpmc\|3.00.b\|Works\|
	+	\| \|mch_opb_ddr\|1.00.a\|Works\|
	+	\|Timer\|opb_timer\|1.00.b\|Full support\|
	+	\| \|xps_timer\|1.00.a\|Full support\|
	+	\|Interrupt controller\|opb_intc\|1.00.c\|Full support\|
	+	\| \|xps_intc\|1.00.a\|Full support\|
	+
	+	<!-- \| \|mch_opb_ddr2\|1.02.a\|Works\| -->
	+
	+
	+
	+	* Simple support -- Support in BSP and simple eCos driver
	+	* Full support -- Support in BSP and native eCos driver
	+	* Xdriver support -- Support in BSP and eCos driver based on Xilinx drivers
	+	* BSP support -- Support only in BSP
	+	* PowerPC support -- The driver exists for PowerPC405
	+	* Works -- Working with current eCos version - partial support