LabVIEW Embedded

cancel
Showing results for 
Search instead for 
Did you mean: 

Adopt emb.LV to emb.Linux Target ARM9 Prozessor

Hi,

This error is most likely due to the fact that the location of the m68k-uclinux-gcc.exe is not part of your system's Path variable. Add that directory location to the Path variable, then restart LabVIEW. It's just like step 10 in this tutorial <http://zone.ni.com/devzone/cda/tut/p/id/5412>, except you need to add the location of m68k-uclinux-gcc.exe, not Cygwin.
--
Michael P
National Instruments
0 Kudos
Message 21 of 56
(6,859 Views)
hello,
    The problem  above is   ok now.Thank you very much!
    There are still a problem as follows:
    Firstly, the GCC compiler in the freescale coldfire uclinux target  is different with  the GCC in the cygwin,isn't?do we  need to change the complier if i  use the ARM7(S3C44B0)?   which complier should we choose?the GCC in the cygwin? can you give me some advices about how to change the target to use in the arm7(s3c44b0)?thank you very much!
 
 
 
lianzi
 
i like thinking ,i enjoy doing the work.baxia
0 Kudos
Message 22 of 56
(6,842 Views)


    Firstly, the GCC compiler in the freescale coldfire uclinux target  is different with  the GCC in the cygwin,isn't?do we  need to change the complier if i  use the ARM7(S3C44B0)?   which complier should we choose?the GCC in the cygwin? can you give me some advices about how to change the target to use in the arm7(s3c44b0)?thank you very much!

Yes, the cross-compiler for the ColdFire uCLinux target is not the same as Cygwin's gcc for Windows. The target implementation for the ColdFire target contains plug-in VIs that call the correct cross-compiler. You can view the plug-in VIs, and modify them to call other tool chains. That's part of the process of adding support for a new target.

labview\Targets\NI\Embedded\unix\m5329evb\unix_m5329evb_LEP_TargetPlugin\LEP_unix_m5329evb_ScriptCompiler.vi

Instructions on setting up the ColdFire target are located in chapter 2 of the Embedded Porting Guide (page 2-18).
--
Michael P
National Instruments
0 Kudos
Message 23 of 56
(6,833 Views)
hello,professor Michael
       i know that i should use the arm-elf-gcc complier in the target.in the plug-in VIs  i changed it.but when i build it,it occurs many errors as  follows:
E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\lvEmbeddedMain.c:16:20: stdlib.h: No such file or directory
In file included from D:\program files\labview 8.5\CCodeGen\include\blockdiagram/LVCGenIncludes.h:1,
                 from E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\lvEmbeddedMain.c:20:
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:6:20: unistd.h: No such file or directory
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:7:19: stdio.h: No such file or directory
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:10:20: assert.h: No such file or directory
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:12:18: time.h: No such file or directory
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:13:22: sys/time.h: No such file or directory
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:15:19: errno.h: No such file or directory
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:16:23: sys/types.h: No such file or directory
D:\program files\labview 8.5\CCodeGen\include\os\unix/LVSysIncludes.h:17:22: sys/stat.h: No such file or directory
In file included from D:\program files\labview 8.5\CCodeGen\include\blockdiagram/LVCGenIncludes.h:3,
                 from E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\lvEmbeddedMain.c:20:
D:\program files\labview 8.5\CCodeGen\include\blockdiagram/LVCCG.h:247: error: `NULL' undeclared here (not in a function)
In file included from E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\lvEmbeddedMain.c:25:
E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\/LVISRList.h:7: error: initializer element is not constant
E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\/LVISRList.h:7: error: (near initialization for `gISRInfoTable[0].viName')
E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\/LVISRList.h:7: error: initializer element is not constant
E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\/LVISRList.h:7: error: (near initialization for `gISRInfoTable[0].isrRun')
E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\/LVISRList.h:7: error: initializer element is not constant
E:\labview test\embedded\labview 8.5\test2\1\Freescale_M5329EVB__uClinux\My_Application\/LVISRList.h:7: error: (near initialization for `gISRInfoTable[0]')
 
when i make the makefile in the linux,there are also some errors(i have changed the m68k-uclinux-gcc with arm-elf-gcc):
CCGArrSupport2.c
In file included from ../CCodeGen/include/blockdiagram/MemCheck.h:12,
                 from ../CCodeGen/include/blockdiagram/LVCCG.h:26,
                 from ../CCodeGen/libsrc/blockdiagram/CCGArrSupport2.c:18:
../CCodeGen/include/blockdiagram/LVCritSect.h:18: Invalid token in expression
In file included from ../CCodeGen/include/comms/CCGCommsSupport.h:7,
                 from ../CCodeGen/libsrc/blockdiagram/CCGArrSupport2.c:21:
../CCodeGen/include/comms/CCGTcpUdpSupport.h:12: Invalid token in expression
../CCodeGen/include/comms/CCGTcpUdpSupport.h:24: Invalid token in expression
make[1]: *** [obj/dbg/CCGArrSupport2.o] Error 1
make: *** [debug] Error 2
 
maybe the porblem is the  files in the CCodeGen?could you give me some advices,thank you!
 
 
lianzi
 
i like thinking ,i enjoy doing the work.baxia
0 Kudos
Message 24 of 56
(6,808 Views)
Hi,

What tool chain are you using? Are you using any compiler flags that tell the compiler not to add in the standard includes? The issue appears to be that the standard includes are not being included by default.

Please copy/paste the command line command being used for compiling and linking -- Perhaps this will point us to the problem.
--
Michael P
National Instruments
0 Kudos
Message 25 of 56
(6,798 Views)

hello,

  I used the arm-elf-gcc complier ,which is used for arm7 +uclinux.The cflags used in the target plugins and the makefile are showed in the accessory.

 I am not sure about the cflags in the files.

 Thank you very much!

 

i like thinking ,i enjoy doing the work.baxia
0 Kudos
Message 26 of 56
(6,793 Views)
Sorry,I forgot to add the accessory just now!
thank you !
i like thinking ,i enjoy doing the work.baxia
0 Kudos
Message 27 of 56
(6,792 Views)
Hi,

I'm having some trouble un-archiving the file you attached. I tried "tar -zxvf problems.tar", and it returned "not in gzip format". I tried -xvf, and it returned "This does not look like a tar archive".
--
Michael P
National Instruments
0 Kudos
Message 28 of 56
(6,778 Views)
hello,soryry,i tried again!
i like thinking ,i enjoy doing the work.baxia
0 Kudos
Message 29 of 56
(6,763 Views)
hello,Mr Michael
       The error occured in the Makefile( D:\program files\labview 8.5\Targets\NI\Embedded\unix\m5329evb\build)  disappeared when i don't compile the mcfqspi.c which  loctated in the D:\program files\labview 8.5\Targets\NI\Embedded\unix\m5329evb\drivers.
      now ,i want to ask you a question about  the use of the driver such as the mcfqspi.c.
 
Thank you!
 
lianzi
i like thinking ,i enjoy doing the work.baxia
0 Kudos
Message 30 of 56
(6,747 Views)