4.2

Tutorial to setup “Porting Kit” and “ARM RVDS compiler”.

1st step.

Make sure that “msbuiild” is properly set. Open command prompt and type “msbuild”. If you got the message, “'msbuild' is not recognized as an internal…”, you need to add or change Path for MSBuild in “Environment Variables” of your system. In my case I added the path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319;”

2nd step.

Download and install Porting Kit 4.2 (RTM QFE2): http://netmf.codeplex.com/downloads/get/470706

Make sure that you don’t have installed other versions of Porting Kits. I would suggest installing Porting Kit into default location as C:\MicroFrameworkPK_v4_2

Just in case if something will go wrong, create backup copies of 2 folders: C:\MicroFrameworkPK_v4_2\DeviceCode and C:\MicroFrameworkPK_v4_2\Solutions

Download source code of Cerberus firmware from: http://ghiopensource.codeplex.com/ From downloaded zip file copy the folders “Solutions ” to C:\MicroFrameworkPK_v4_2\Solutions and “DeviceCode” to C:\MicroFrameworkPK_v4_2\DeviceCode . If some files already existing, just overwrite them.

3rd step

RVDS is pretty expensive software. But you can use for one month full functional trial version.

Go to the http://www.arm.com/ and create an account.

After account verification and site authorization, go to the downloads section: https://silver.arm.com/browse → Development Tools → RVDS and download the file “RealView Development Suite (RVDS) 4.1 Professional”

During installation process, there would be popup message, asking you to select Ethernet interface. Copy somewhere the number of your network interface.

Go to the https://silver.arm.com/browse website again, Licensing→Eval Products→Evaluation Products→Development Studio 5 (DS-5)

Provide all information required and select: “View license” and save license file or text to “license.lic” file. I don't know why, but I had the problems when license file with default “.dat” extension.

4th step.

Just in case, create a copy of setenv_base.cmd file Go to the http://netmf.codeplex.com/workitem/777, and from attachment download the file RVDS_v4_1.zip Extract files to C:\MicroFrameworkPK_v4_2\

I know this is not right solution, but that way resolving many problems with PATH variables and files locations.

Create the folders structure:

C:\MicroFrameworkPK_v4_2\tools\ads_v4_1 C:\MicroFrameworkPK_v4_2\tools\ads_v4_1\BIN C:\MicroFrameworkPK_v4_2\tools\ads_v4_1\licenses

Copy into C:\MicroFrameworkPK_v4_2\tools\ads_v4_1\license your license.lic file Copy to C:\MicroFrameworkPK_v4_2\tools\ads_v4_1\BIN all files from C:\Program Files\ARM\RVCT\Programs\4.1\713\win_32-pentium for 32 bits compiler or C:\Program Files\ARM\RVCT\Programs\4.1\713\win_32-x86_64 for 64 bits compiler.

Open in text editor setenv_base.cmd file, and find the line: set ARMLMD_LICENSE_FILE On my file it’s looks: “set ARMLMD_LICENSE_FILE=%ARMROOT%\licenses\license.lic”

5th step

Open command prompt, change location to “C:\MicroFrameworkPK_v4_2 “and type: setenv_base.cmd RVDS4.1

Type in command prompt: “armcc.exe”.

If everything is set right, you should see the message “ARM C/C++ compiler…. Your license …. will expire…”

Now you are ready to compile firmware.

Type in command prompt: msbuild C:\MicroFrameworkPK_v4_2\Solutions\FEZCerberus\ dotnetmf.proj /p:flavor=release

Make a cup of coffee and wait.

If after compilation you will see warning messages, just ignore them. If you will see errors, redirect msbuild messages to some text file to found out the problems.

In “C:\MicroFrameworkPK_v4_2\BuildOutput\THUMB2\RVDS4.1\le\FLASH\release\FEZCerberus\bin\tinyclr.hex” folder you will find compiled firmware.

Still I didn’t find the way, how to compile the Cerberus firmware with Ethernet support. I hope somebody from the community or GHI will help with that problem.

In “C:\MicroFrameworkPK_v4_2\tools\bin\SolutionWizard” you can find SolutionWizard.exe application. Not the best software, but you can use it to clone or edit existing solutions. At least to see what is going on inside the project.

Also you can download NETMF source code from http://netmf.codeplex.com and in the folder client_v4_2_comm\tools\bin\PKStudio you will find PKStudio software to manage firmware solutions. Only the problem, I couldn’t make to compile under PKStudio. But still worth to look.

Helpful links:

http://www.ghielectronics.com/downloads/FEZ/Beginners%20Guide%20to%20Porting%20NETMF.pdf http://www.netmf.com/working-with-the-net-mf-porting-kit-v41.aspx http://netmf.codeplex.com/wikipage?title=The%20.NET%20MF%20Codeplex%20Distribution%20HowTo%20Manual http://netmf.codeplex.com/documentation http://www.mountaineer.org/app/download/6083569375/NETMF+for+STM32+-+Tour+d%27Horizon.pdf?t=1339779332

Great tutorials about debugging NETMF boards on native code level.

http://www.tinyclr.it/journey-under-the-hood-of-net-micro-framework.aspx http://www.tinyclr.it/a-new-journey-under-the-hood-of-net-micro-framework-let%E2%80%99s-dig-deep-into-interrupts-management.aspx

Hope my information helps and good luck with compiling Smiley

Zdroje

netmf/porting-kit-4.2.txt · Poslední úprava: 17.08.2013 21:21 autor: vm

Nástroje pro stránku