Bambino-200 Manual/Rebuild mbed Firmware - Revision history

Support at 20:12, 11 February 2015

Support — Wed, 11 Feb 2015 20:12:43 GMT

← Older revision		Revision as of 20:12, 11 February 2015
Line 18:		Line 18:
	ARM_INC = join(ARM_PATH, "ARMCC", "include")		ARM_INC = join(ARM_PATH, "ARMCC", "include")
	ARM_LIB = join(ARM_PATH, "ARMCC", "lib")		ARM_LIB = join(ARM_PATH, "ARMCC", "lib")
-	~~ARM_CPPLIB = join(ARM_LIB, "cpplib")~~

	# GCC ARM		# GCC ARM

Support at 19:59, 11 February 2015

Support — Wed, 11 Feb 2015 19:59:27 GMT

← Older revision		Revision as of 19:59, 11 February 2015
Line 12:		Line 12:
	from os.path import join		from os.path import join

		+	# ARM
	armcc = "keil"		armcc = "keil"
	ARM_PATH = "C:/Keil/ARM"		ARM_PATH = "C:/Keil/ARM"
	ARM_BIN = join(ARM_PATH, "ARMCC", "bin")		ARM_BIN = join(ARM_PATH, "ARMCC", "bin")
-	ARM_INC = join(ARM_PATH, "~~INC~~")	+	ARM_INC = join(ARM_PATH, "ARMCC", "include")
-	ARM_LIB = join(ARM_PATH, "~~RV31~~", "~~LIB~~")	+	ARM_LIB = join(ARM_PATH, "ARMCC", "lib")
		+	ARM_CPPLIB = join(ARM_LIB, "cpplib")
		+
		+	# GCC ARM
	GCC_ARM_PATH = "C:/Program Files (x86)/GNU Tools ARM Embedded/4.8 2014q2/bin"		GCC_ARM_PATH = "C:/Program Files (x86)/GNU Tools ARM Embedded/4.8 2014q2/bin"
		+
		+	# GCC CodeRed
	GCC_CR_PATH = "C:/nxp/LPCXpresso_7.5.0_254/lpcxpresso/tools/bin"		GCC_CR_PATH = "C:/nxp/LPCXpresso_7.5.0_254/lpcxpresso/tools/bin"
-	~~IAR_PATH = "C:/Program Files (x86)/IAR Systems/Embedded Workbench 6.5/arm"~~
	5. Compile the base mbed libraries. These are typical commands to change to the source directory, setup compiler environment and build the bootloader. Note that the Python directory in the PATH may be different in your development system.		5. Compile the base mbed libraries. These are typical commands to change to the source directory, setup compiler environment and build the bootloader. Note that the Python directory in the PATH may be different in your development system.
	cd mbed-master		cd mbed-master

Support at 20:32, 21 January 2015

Support — Wed, 21 Jan 2015 20:32:19 GMT

← Older revision		Revision as of 20:32, 21 January 2015
Line 3:		Line 3:
	The source code for the mbed library is open source and can be downloaded from the [http://github.com/mbedmicro/mbed mbed mainline repository] or the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:		The source code for the mbed library is open source and can be downloaded from the [http://github.com/mbedmicro/mbed mbed mainline repository] or the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:

-	1. Install a compatible ARM toolchain. The mbed port for LPC4330 targets currently supports the [http://www.keil.com/arm/~~selector~~.asp Keil MDK], [http://launchpad.net/gcc-arm-embedded GCC ARM] and [http://www.lpcware.com/lpcxpresso/download GCC LPCXpresso] toolchains. ~~Firmware at Micromint is mostly developed using~~ Keil MDK ~~4.73~~.	+	1. Install a compatible ARM toolchain. The mbed port for LPC4330 targets currently supports the [http://www.keil.com/arm/mdk.asp Keil MDK], [http://launchpad.net/gcc-arm-embedded GCC ARM] and [http://www.lpcware.com/lpcxpresso/download GCC LPCXpresso] toolchains. The Keil MDK is the main ARM toolchain at Micromint.

	2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.		2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.

Support: /* Command Line Build */

Support — Wed, 21 Jan 2015 15:46:37 GMT

Command Line Build

← Older revision		Revision as of 15:46, 21 January 2015
Line 25:		Line 25:
	python workspace_tools/build.py -v -r -m LPC4330_M4 -t ARM > build.log		python workspace_tools/build.py -v -r -m LPC4330_M4 -t ARM > build.log
	python workspace_tools/build.py -v -r -m LPC4330_M4 -t GCC_ARM >> build.log		python workspace_tools/build.py -v -r -m LPC4330_M4 -t GCC_ARM >> build.log
-	If your build is successful, the mbed libraries and headers for the LPC4330 will be available in the ..\build directory. If not, check the build.log file. For more documentation on these procedures please visit the [https://developer.mbed.org/handbook/mbed-tools mbed ~~build~~ tools] site.	+	If your build is successful, the mbed libraries and headers for the LPC4330 will be available in the ..\build directory. If not, check the build.log file. For more documentation on these procedures please visit the [https://developer.mbed.org/handbook/mbed-tools mbed tools] site.
		+
	==IDE Build==		==IDE Build==
	When implementing new or modified mbed functionality, a large percentage of the development time is spent debugging and troubleshooting code changes. To improve prodctivity, our implementation includes project files to build and debug the mbed library with the Keil MDK. These allow you to access a full featured ARM development environment and debugger. A [[Bambino-200_Manual/User_Interfaces,_Connectors,_and_Jumpers#Field_Installable_Options\|JTAG]] is required for debugging.		When implementing new or modified mbed functionality, a large percentage of the development time is spent debugging and troubleshooting code changes. To improve prodctivity, our implementation includes project files to build and debug the mbed library with the Keil MDK. These allow you to access a full featured ARM development environment and debugger. A [[Bambino-200_Manual/User_Interfaces,_Connectors,_and_Jumpers#Field_Installable_Options\|JTAG]] is required for debugging.

Support at 15:46, 21 January 2015

Support — Wed, 21 Jan 2015 15:46:02 GMT

← Older revision		Revision as of 15:46, 21 January 2015
Line 25:		Line 25:
	python workspace_tools/build.py -v -r -m LPC4330_M4 -t ARM > build.log		python workspace_tools/build.py -v -r -m LPC4330_M4 -t ARM > build.log
	python workspace_tools/build.py -v -r -m LPC4330_M4 -t GCC_ARM >> build.log		python workspace_tools/build.py -v -r -m LPC4330_M4 -t GCC_ARM >> build.log
-	If your build is successful, the mbed libraries and headers for the LPC4330 ~~M4 and M0 cores~~ will be available in the ..\build directory. If not, check the build.log file. For more documentation on these procedures please visit the [https://developer.mbed.org/handbook/mbed-tools mbed build tools] site.	+	If your build is successful, the mbed libraries and headers for the LPC4330 will be available in the ..\build directory. If not, check the build.log file. For more documentation on these procedures please visit the [https://developer.mbed.org/handbook/mbed-tools mbed build tools] site.
	==IDE Build==		==IDE Build==
	When implementing new or modified mbed functionality, a large percentage of the development time is spent debugging and troubleshooting code changes. To improve prodctivity, our implementation includes project files to build and debug the mbed library with the Keil MDK. These allow you to access a full featured ARM development environment and debugger. A [[Bambino-200_Manual/User_Interfaces,_Connectors,_and_Jumpers#Field_Installable_Options\|JTAG]] is required for debugging.		When implementing new or modified mbed functionality, a large percentage of the development time is spent debugging and troubleshooting code changes. To improve prodctivity, our implementation includes project files to build and debug the mbed library with the Keil MDK. These allow you to access a full featured ARM development environment and debugger. A [[Bambino-200_Manual/User_Interfaces,_Connectors,_and_Jumpers#Field_Installable_Options\|JTAG]] is required for debugging.

Support at 15:27, 21 January 2015

Support — Wed, 21 Jan 2015 15:27:32 GMT

← Older revision		Revision as of 15:27, 21 January 2015
Line 1:		Line 1:
	[[Category: Bambino-200_Manual\|06]]		[[Category: Bambino-200_Manual\|06]]
	==Command Line Build==		==Command Line Build==
-	~~All mbed firmware used in~~ the ~~Bambino 200~~ is open source and can be downloaded from the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:	+	The source code for the mbed library is open source and can be downloaded from the [http://github.com/mbedmicro/mbed mbed mainline repository] or the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:

-	1. Install a compatible ARM toolchain. ~~Currently~~ the [http://www.keil.com/arm/selector.asp Keil MDK] ~~and [http://www.iar.com/en/Products/IAR-Embedded-Workbench/ IAR EWARM] are supported. Firmware at Micromint is mostly developed using Keil MDK 4.73. Releases are also tested with~~ [http://launchpad.net/gcc-arm-embedded GCC ARM] and [http://~~code-red-tech~~.com/~~products.php~~ GCC ~~Code Red toolchain~~].	+	1. Install a compatible ARM toolchain. The mbed port for LPC4330 targets currently supports the [http://www.keil.com/arm/selector.asp Keil MDK], [http://launchpad.net/gcc-arm-embedded GCC ARM] and [http://www.lpcware.com/lpcxpresso/download GCC LPCXpresso] toolchains. Firmware at Micromint is mostly developed using Keil MDK 4.73.

	2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.		2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.

-	3. Install the [https://github.com/mbedmicro/mbed/archive/master.zip mbed Library Sources]. This includes full source code for multiple ~~mbed libraries. The Micromint port of mbed to the LPC43XX is included in the master distribution~~.	+	3. Install the [https://github.com/mbedmicro/mbed/archive/master.zip mbed Library Sources]. This includes full source code for all supported multiple microcontrollers and boards.

-	4. Compile the base mbed libraries. These are typical commands to change to the source directory, setup compiler environment and build the bootloader. Note that the Python directory in the PATH may be different in your development system.	+	4. Edit workspace_tools/private_settings.py to reflect your toolchain directories.
-	cd \mbed-master	+	from os.path import join
		+
		+	armcc = "keil"
		+	ARM_PATH = "C:/Keil/ARM"
		+	ARM_BIN = join(ARM_PATH, "ARMCC", "bin")
		+	ARM_INC = join(ARM_PATH, "INC")
		+	ARM_LIB = join(ARM_PATH, "RV31", "LIB")
		+	GCC_ARM_PATH = "C:/Program Files (x86)/GNU Tools ARM Embedded/4.8 2014q2/bin"
		+	GCC_CR_PATH = "C:/nxp/LPCXpresso_7.5.0_254/lpcxpresso/tools/bin"
		+	IAR_PATH = "C:/Program Files (x86)/IAR Systems/Embedded Workbench 6.5/arm"
		+	5. Compile the base mbed libraries. These are typical commands to change to the source directory, setup compiler environment and build the bootloader. Note that the Python directory in the PATH may be different in your development system.
		+	cd mbed-master
	SET PATH=C:\Windows\system32;C:\Windows;C:\Python27		SET PATH=C:\Windows\system32;C:\Windows;C:\Python27
-	python workspace_tools/build.py -v -m LPC4330_M4 -t ARM >build.log	+	python workspace_tools/build.py -v -r -m LPC4330_M4 -t ARM > build.log
-	python workspace_tools/build.py -v -m ~~LPC4330_M0~~ -t ~~ARM~~ >>build.log	+	python workspace_tools/build.py -v -r -m LPC4330_M4 -t GCC_ARM >> build.log
-	If your build is successful, the mbed libraries and headers for the LPC4330 M4 and M0 cores will be available in the ..\build directory. If not, check the build.log file.	+	If your build is successful, the mbed libraries and headers for the LPC4330 M4 and M0 cores will be available in the ..\build directory. If not, check the build.log file. For more documentation on these procedures please visit the [https://developer.mbed.org/handbook/mbed-tools mbed build tools] site.
-		+
	==IDE Build==		==IDE Build==
	When implementing new or modified mbed functionality, a large percentage of the development time is spent debugging and troubleshooting code changes. To improve prodctivity, our implementation includes project files to build and debug the mbed library with the Keil MDK. These allow you to access a full featured ARM development environment and debugger. A [[Bambino-200_Manual/User_Interfaces,_Connectors,_and_Jumpers#Field_Installable_Options\|JTAG]] is required for debugging.		When implementing new or modified mbed functionality, a large percentage of the development time is spent debugging and troubleshooting code changes. To improve prodctivity, our implementation includes project files to build and debug the mbed library with the Keil MDK. These allow you to access a full featured ARM development environment and debugger. A [[Bambino-200_Manual/User_Interfaces,_Connectors,_and_Jumpers#Field_Installable_Options\|JTAG]] is required for debugging.

Support at 14:38, 21 January 2015

Support — Wed, 21 Jan 2015 14:38:23 GMT

← Older revision		Revision as of 14:38, 21 January 2015
Line 3:		Line 3:
	All mbed firmware used in the Bambino 200 is open source and can be downloaded from the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:		All mbed firmware used in the Bambino 200 is open source and can be downloaded from the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:

-	1. Install a compatible ARM toolchain. Currently the [http://www.keil.com/arm/selector.asp Keil MDK] and [http://www.iar.com/en/Products/IAR-Embedded-Workbench/ IAR EWARM] are supported. Firmware at Micromint is mostly developed using Keil MDK 4.71. Releases are also tested with ~~IAR EWARM 6~~.~~5.0.6. The~~ [http://code-red-tech.com/products.php GCC Code Red toolchain] ~~will be supported by the end of August~~.	+	1. Install a compatible ARM toolchain. Currently the [http://www.keil.com/arm/selector.asp Keil MDK] and [http://www.iar.com/en/Products/IAR-Embedded-Workbench/ IAR EWARM] are supported. Firmware at Micromint is mostly developed using Keil MDK 4.73. Releases are also tested with [http://launchpad.net/gcc-arm-embedded GCC ARM] and [http://code-red-tech.com/products.php GCC Code Red toolchain].

	2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.		2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.

Support at 11:24, 11 July 2013

Support — Thu, 11 Jul 2013 11:24:03 GMT

← Older revision		Revision as of 11:24, 11 July 2013
Line 1:		Line 1:
-	[[Category: Bambino-200_Manual\|6]]	+	[[Category: Bambino-200_Manual\|06]]
	==Command Line Build==		==Command Line Build==
	All mbed firmware used in the Bambino 200 is open source and can be downloaded from the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:		All mbed firmware used in the Bambino 200 is open source and can be downloaded from the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:

Support at 13:29, 8 July 2013

Support — Mon, 08 Jul 2013 13:29:48 GMT

← Older revision		Revision as of 13:29, 8 July 2013
Line 23:		Line 23:
	[[Bambino-200_Manual/Hardware\|NEXT: Hardware]]		[[Bambino-200_Manual/Hardware\|NEXT: Hardware]]

-	[[Bambino-200_Manual/Rebuild ~~NetMF~~ Firmware\|PREVIOUS: Rebuild NetMF Firmware]]	+	[[Bambino-200_Manual/Rebuild Firmware\|PREVIOUS: Rebuild NetMF Firmware]]

Support at 13:24, 8 July 2013

Support — Mon, 08 Jul 2013 13:24:40 GMT

← Older revision		Revision as of 13:24, 8 July 2013
Line 3:		Line 3:
	All mbed firmware used in the Bambino 200 is open source and can be downloaded from the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:		All mbed firmware used in the Bambino 200 is open source and can be downloaded from the [http://github.com/micromint Micromint repository]. To recompile it please follow these steps:

-	1. Install a compatible ARM toolchain. Currently the [http://www.keil.com/arm/selector.asp Keil MDK] and [http://www.iar.com/en/Products/IAR-Embedded-Workbench/ IAR EWARM] are supported. Firmware ~~distributed by~~ Micromint is developed ~~with~~ Keil MDK 4.71 ~~and~~ also tested with IAR EWARM 6.5.0.6. The [http://code-red-tech.com/products.php GCC Code Red toolchain] will be supported by the end of August.	+	1. Install a compatible ARM toolchain. Currently the [http://www.keil.com/arm/selector.asp Keil MDK] and [http://www.iar.com/en/Products/IAR-Embedded-Workbench/ IAR EWARM] are supported. Firmware at Micromint is mostly developed using Keil MDK 4.71. Releases are also tested with IAR EWARM 6.5.0.6. The [http://code-red-tech.com/products.php GCC Code Red toolchain] will be supported by the end of August.

	2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.		2. Install [http://www.python.org/getit/ Python 2.7]. The mbed build scripts are written in Python.