Notification

Icon
Error

Build Fail...
Johanan
#1 Posted : Saturday, May 12, 2012 3:04:36 PM(UTC)
Rank: Newbie

Joined: 5/12/2012(UTC)
Posts: 0

My first time trying to build a port, according to begginres guid, i installed everything and looks ok, but have one error on build of iMXS, whithout changing any code.


The error is :


usart.cpp:(.text._ZN12USART_Driver5FlushEi+0x520): undefined reference to `MC9328MXL_AITC::c_IRQ_INDEX_UART2_MINT_TX'


Why do I get this undefined refernce? did I do somthing wrong?


Thnaks

Zach Libby
#2 Posted : Monday, May 14, 2012 11:37:46 AM(UTC)
Zach Libby

Rank: Tinkerer

Joined: 2/5/2010(UTC)
Posts: 243

Was thanked: 8 time(s) in 8 post(s)
Hello Johanan,

Which version of .Net MF are you using? It seems that you may have an older version. If so, please try installing v4.2 from our CodePlex site (http://netmf.codeplex.com/releases/).

Thanks,
Zach
Johanan
#3 Posted : Tuesday, May 15, 2012 12:33:25 AM(UTC)
Rank: Newbie

Joined: 5/12/2012(UTC)
Posts: 0

I amusing the 4.2 release, with GCC tool chain. used setenv_gcc c:\gcc\. and run MSBUILD from TyniCLR directory.


Is there another tool chain I need to use?


I tried to build the STM32 image but got handreds of errors, so I assume I am doing something wrong.


Thanks


Johanan

Zach Libby
#4 Posted : Tuesday, May 15, 2012 11:45:52 AM(UTC)
Zach Libby

Rank: Tinkerer

Joined: 2/5/2010(UTC)
Posts: 243

Was thanked: 8 time(s) in 8 post(s)
Are you building a debug flavor? We found a bug with the GCC compiler in handling the x ? y : z construct for debug builds only. Perhaps with your version of GCC this problem exists in other flavors as well. Try opening the MC9328's processor_selector.h (DeviceCode\Targets\native\mc9328\processor_selector.h) and change the following code to use the hardcoded pin numbers for all build flavors (remove the '&& defined(DEBUG)').

#if defined(__GNUC__) && defined(DEBUG)
// GCC with -O0 (debug) does not like "(Condition) ? (XXXXX::YYYYY) : (XXXXX:ZZZZZ)"
// Using hard-coded values instead.
#define USART_TX_IRQ_INDEX(x) ((x) ? 23 : 29 )
#else
#define USART_TX_IRQ_INDEX(x) ((x) ? MC9328MXL_AITC::c_IRQ_INDEX_UART2_MINT_TX : MC9328MXL_AITC::c_IRQ_INDEX_UART1_MINT_TX )
#endif

thanks,
zach
Johanan
#5 Posted : Wednesday, May 16, 2012 1:05:21 AM(UTC)
Rank: Newbie

Joined: 5/12/2012(UTC)
Posts: 0

I used release flavor, not debug.


What is the recomanded version of GCC? I can download whatever version is needed as I don't use GCC for anything else.


Thnaks


Johanan

Zach Libby
#6 Posted : Wednesday, May 16, 2012 11:42:04 AM(UTC)
Zach Libby

Rank: Tinkerer

Joined: 2/5/2010(UTC)
Posts: 243

Was thanked: 8 time(s) in 8 post(s)
For testing purposes, we use GCC v4.2.1 from CodeSourcery, but as long as you have an equivalent version it shouldn't matter. Did you try to make the change I recommended? That should get you past the iMXS build error.

Thanks,
Zach
Johanan
#7 Posted : Wednesday, May 16, 2012 2:38:49 PM(UTC)
Rank: Newbie

Joined: 5/12/2012(UTC)
Posts: 0

I made the change you recomanded, and it passed. Now I know my system is OK.


Also made a build for LPC 2478 - No errors.


Tried the STM32 (which is the one I am interested, as it has the largest rom - 1024K) but got too many errors.


I don't see how to attach a file to a post, but I'll be happy to email you the output from the build. Here are some errors which might give you a direction,


However, in the codeplex for STM32 it says that GCC is probably not suported, so I assume thats why.


I would like to purcahse a board for learnig the NETMF, but would like to have an LCD color interface with touch panel, and Ethernet + as much flash memory as possible in one chip. Can you recommand a board? (LPC 2478 is a good one but 512K, and would like to have 1024...)


Also I would like to establish that after learning to do some staff with it, I will be able to make my own bord and upload the whole image file to it, just as we do on any embedded chip using C.


Thanks.


//----------------


 "C:\GCC\\bin\arm-none-eabi-gcc.exe" -xc++ -Wno-invalid-offsetof -fcheck-new  -fno-default-inline  -mabi=aapcs -ffunction-sections 
-fomit-frame-pointer -mlong-calls -fdollars-in-identifiers -fshort-wchar -fno-exceptions -funsigned-char -mstructure-size-boundary=8
-DTINYCLR_ENABLE_SOURCELEVELDEBUGGING -DCOMPILE_THUMB2 -DVERSION_MAJOR=4 -DVERSION_MINOR=2 -DVERSION_BUILD=0 -DVERSION_REVISION=0
-DOEMSYSTEMINFOSTRING="\"Microsoft Copyright (C) Microsoft Corporation. All rights reserved.\"" -DPLATFORM_ARM_STM32
-DPLATFORM_ARM_STM32Stamp -DTARGETLOCATION_FLASH -DLITTLE_ENDIAN -DGCC_V4_2 -DPLATFORM_EMULATED_FLOATINGPOINT=1 -DPLATFORM_NO_CLR_TRACE=1
-DTINYCLR_NO_APPDOMAINS=1 -DTINYCLR_NO_IL_INLINE=1 -mcpu= -mlittle-endian -g1 -Os -DNDEBUG
-IC:\MicroFrameworkPK_v4_2\CLR\Core\HeapPersistence -IC:\MicroFrameworkPK_v4_2\DeviceCode\include
-IC:\MicroFrameworkPK_v4_2\DeviceCode\Cores\arm -IC:\MicroFrameworkPK_v4_2\Support\Include
-IC:\MicroFrameworkPK_v4_2\crypto\inc -IC:\MicroFrameworkPK_v4_2\CLR\Include
-IC:\MicroFrameworkPK_v4_2\CLR\Libraries\CorLib
-IC:\MicroFrameworkPK_v4_2\CLR\Libraries\SPOT
-IC:\MicroFrameworkPK_v4_2\CLR\Libraries\SPOT_Hardware
-IC:\MicroFrameworkPK_v4_2\CLR\Libraries\SPOT_Graphics
-IC:\MicroFrameworkPK_v4_2\CLR\Libraries\SPOT_Net
-IC:\GCC\\lib\gcc\arm-none-eabi\\include
-IC:\MicroFrameworkPK_v4_2\Solutions\STM32Stamp
-IC:\MicroFrameworkPK_v4_2\devicecode\Targets\Native\STM32
-IC:\MicroFrameworkPK_v4_2\DeviceCode\Cores\arm
-IC:\MicroFrameworkPK_v4_2\DeviceCode\Cores\arm\Include
-IC:\MicroFrameworkPK_v4_2\DeviceCode -IC:\MicroFrameworkPK_v4_2\DeviceCode\Include
-IC:\MicroFrameworkPK_v4_2\CLR\Include -IC:\MicroFrameworkPK_v4_2\DeviceCode\Targets\Native\STM32\STM32Stamp
-IC:\MicroFrameworkPK_v4_2\Support\Include
-IC:\MicroFrameworkPK_v4_2\DeviceCode\include
-IC:\MicroFrameworkPK_v4_2\CLR\include
-IC:\MicroFrameworkPK_v4_2\Crypto\inc
-IC:\MicroFrameworkPK_v4_2\CLR\core
-IC:\MicroFrameworkPK_v4_2\CLR\libraries\corlib
-IC:\MicroFrameworkPK_v4_2\CLR\libraries\SPOT
-IC:\MicroFrameworkPK_v4_2\CLR\libraries\SPOT_Hardware -Wabi -o
C:\MicroFrameworkPK_v4_2\BuildOutput\THUMB2\GCC4.2\le\ANY_MEDIA\release\obj\CLR\Core\HeapPersistence\Heap_Persistence_stub.obj -c
C:\MicroFrameworkPK_v4_2\CLR\Core\HeapPersistence\Heap_Persistence_stub.cpp
cc1plus.exe : error : missing argument to "-mcpu=" [C:\MicroFrameworkPK_v4_2\CLR\Core\HeapPersistence\dotNetMF_Stub.proj]
C:\MicroFrameworkPK_v4_2\tools\targets\Microsoft.SPOT.System.GCC.targets(276,5): error MSB3073: The command "
"C:\GCC\\bin\arm-none-eabi-gcc.exe" ...... -c C:\MicroFrameworkPK_v4_2\CLR\Core\HeapPersistence\Heap_Persistence_stub.cpp
" exited with code 1. [C:\MicroFrameworkPK_v4_2\CLR\Core\HeapPersistence\dotNetMF_Stub.proj]
Done Building Project "C:\MicroFrameworkPK_v4_2\CLR\Core\HeapPersistence\dotNetMF_Stub.proj" (Build target(s)) -- FAILED.


//---------------

 


Thanks for your help.


Johanan

Hema
#8 Posted : Tuesday, July 10, 2012 4:04:40 AM(UTC)
Rank: Newbie

Joined: 7/10/2012(UTC)
Posts: 0

Hi,


I am a Dot net MF newbie... trying to learn build MF for first time. I installed Dot Net MF v 4.1 and the respective tools according to the user guide.


I am trying to build the TincyCLR for iMXS sample Solution. I am getting an error like this: 


C:\MicroframeworkPK_v_4_1\tools\targets\Microsoft.SPOT.System.Targets(179, 5):
error MSB4062: The "Microsoft.Build.Tasks.CallTarget" task could not be loaded
from the assembly Microsoft.Build.Tasks.v4.0, version=4.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a. Could not load file or assembly 'Microsoft.Bu
ild.Tasks.v4.0, version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a
3a' or one of its dependencies. the system cannot find the file specified. Conf
irm that the <UsingTask> declartion is correct, and that the assembly and all
its dependencies are available.

I dont know, where to check those <UsingTask>.

Please help me to solve this problem.


Thanks,

hema

 

LL
#9 Posted : Monday, August 13, 2012 1:14:00 AM(UTC)
Rank: Newbie

Joined: 8/13/2012(UTC)
Posts: 0

I'm not realy sure how Windows does this but it is basically refering to the wrong registry entry when you build it on a x64 machine.

I had the same error when i build it on our TFS Build server, it was solved by copying everything:
from : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETMicroFramework
to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETMicroFramework

But now I get the following error:
C:\Program Files (x86)\MSBuild\Microsoft\.NET Micro Framework\v4.2\Device.targets (104): Unable to create directory "C:\Builds\1\[path]\[projectname]\Sources\Development\[solutionname]\[projectname]\C:\Builds\1\[path]\[projectname]\Binaries\le". The given path's format is not supported.

Would anybody know the soltion for this problem?


Rss Feed  Atom Feed
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.097 seconds.