Academic Hardware Products (myDAQ, myRIO)

cancel
Showing results for 
Search instead for 
Did you mean: 

Binary not found

I'm trying to deploy the AIO demo to the myrio, and everytime I press search project in the Run Configurations dialog, no binaries appear. Can someone please help me! This is apart of my TSA Engineering Design event entry, and it's due tomorrow. And yes... I did build the project first.

0 Kudos
Message 1 of 13
(9,227 Views)

Hey jeremiahb,

 

It sounds like you are trying to build and deploy a startup exe to run on the myRIO, is that correct?  If so here is some information on doing that.

 

Is the project you're trying to deploy a built in sample project or something you (or someone else) built?  Where is the Run Configuration window you referred to?

 

Thanks!

 

-Sam K

LabVIEW Hacker

Join / Follow the LabVIEW Hacker Group on google+

 

0 Kudos
Message 2 of 13
(9,225 Views)

I am attempting to deploy the AIO C# example onto the myRIO.

0 Kudos
Message 3 of 13
(9,221 Views)

Hey jeremiahb,

 

Did you go through the instructions here?  Let me know if if those don't help I'll set this up here to try and help out.

 

Thanks!

 

-Sam K

LabVIEW Hacker

Join / Follow the LabVIEW Hacker Group on google+

0 Kudos
Message 4 of 13
(9,218 Views)

Yes, I have followed all of these steps. I'm getting the following errors when building:

 

Description Resource Path Location Type
Symbol 'SYSAO_SCALERDY' could not be resolved main.c /myRIO Example - AIO line 77 Semantic Error
Symbol 'SYSAI_SCALERDY' could not be resolved main.c /myRIO Example - AIO line 76 Semantic Error
Program "gcc" not found in PATH Preferences, C++/Build/Settings/Discovery, [CDT GCC Builtin Compiler Settings] options C/C++ Scanner Discovery Problem
Symbol 'uint16_t' could not be resolved AIO.c /myRIO Example - AIO line 80 Semantic Error
Program "g++" not found in PATH Preferences, C++/Build/Settings/Discovery, [CDT GCC Builtin Compiler Settings] options C/C++ Scanner Discovery Problem
Type 'uint16_t' could not be resolved AIO.c /myRIO Example - AIO line 57 Semantic Error
Type 'uint16_t' could not be resolved AIO.c /myRIO Example - AIO line 87 Semantic Error
Symbol 'int16_t' could not be resolved AIO.c /myRIO Example - AIO line 80 Semantic Error
Type 'int16_t' could not be resolved AIO.c /myRIO Example - AIO line 159 Semantic Error
Type 'uint16_t' could not be resolved AIO.c /myRIO Example - AIO line 133 Semantic Error
Symbol 'AIA_3WGHT' could not be resolved main.c /myRIO Example - AIO line 65 Semantic Error
Symbol 'AIA_3VAL' could not be resolved main.c /myRIO Example - AIO line 64 Semantic Error
Symbol 'AOB_0VAL' could not be resolved main.c /myRIO Example - AIO line 69 Semantic Error
Symbol 'AIA_3OFST' could not be resolved main.c /myRIO Example - AIO line 66 Semantic Error
Symbol 'AOB_0OFST' could not be resolved main.c /myRIO Example - AIO line 71 Semantic Error
Program "gcc" not found in PATH myRIO Example - AIO [Discovery Options] page in project properties C/C++ Problem
Program "make" not found in PATH myRIO Example - AIO C/C++ Problem
Symbol 'AOB_0WGHT' could not be resolved main.c /myRIO Example - AIO line 70 Semantic Error
Symbol 'SYSAIRDY' could not be resolved main.c /myRIO Example - AIO line 75 Semantic Error
Symbol 'AOSYSGO' could not be resolved main.c /myRIO Example - AIO line 72 Semantic Error
Type 'uint32_t' could not be resolved AIO.h /myRIO Example - AIO line 44 Semantic Error
Type 'uint32_t' could not be resolved AIO.h /myRIO Example - AIO line 43 Semantic Error
Type 'uint32_t' could not be resolved AIO.h /myRIO Example - AIO line 42 Semantic Error
Type 'time_t' could not be resolved main.c /myRIO Example - AIO line 50 Semantic Error
Type 'uint32_t' could not be resolved AIO.h /myRIO Example - AIO line 29 Semantic Error
Symbol 'AIA_0WGHT' could not be resolved main.c /myRIO Example - AIO line 60 Semantic Error
Type 'uint32_t' could not be resolved AIO.h /myRIO Example - AIO line 30 Semantic Error
Symbol 'AIA_0OFST' could not be resolved main.c /myRIO Example - AIO line 61 Semantic Error
Type 'uint32_t' could not be resolved AIO.h /myRIO Example - AIO line 27 Semantic Error
Type 'time_t' could not be resolved main.c /myRIO Example - AIO line 51 Semantic Error
Type 'uint32_t' could not be resolved AIO.h /myRIO Example - AIO line 28 Semantic Error
Symbol 'AIA_0VAL' could not be resolved main.c /myRIO Example - AIO line 59 Semantic Error
Type 'uint32_t' could not be resolved AIO.c /myRIO Example - AIO line 186 Semantic Error
Type 'uint32_t' could not be resolved AIO.c /myRIO Example - AIO line 187 Semantic Error

0 Kudos
Message 5 of 13
(9,215 Views)

From that it sounds like your path variables are not setup correctly.  I'd run through the Setting up 'Software Environment' section of that document again to make sure all the paths are correct.

 

-Sam K

LabVIEW Hacker

Join / Follow the LabVIEW Hacker Group on google+

0 Kudos
Message 6 of 13
(9,210 Views)

I've been through that section multiple times. Even on my new laptop, and it still does not work. The project just won't build. I've done everything correctly.

 

 

Description	Resource	Path	Location	Type
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - PWM		[Discovery Options] page in project properties	C/C++ Problem
Type 'uint32_t' could not be resolved	DIO.h	/myRIO Example - DIO	line 24	Semantic Error
Type 'NiFpga_Bool' could not be resolved	DIO.h	/myRIO Example - DIO	line 34	Semantic Error
Type 'uint8_t' could not be resolved	DIO.h	/myRIO Example - DIO	line 27	Semantic Error
Type 'uint32_t' could not be resolved	DIO.h	/myRIO Example - DIO	line 26	Semantic Error
Type 'uint32_t' could not be resolved	DIO.h	/myRIO Example - DIO	line 25	Semantic Error
Type 'uint8_t' could not be resolved	DIO.c	/myRIO Example - DIO	line 58	Semantic Error
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - Encoder		[Discovery Options] page in project properties	C/C++ Problem
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - Accelerometer		[Discovery Options] page in project properties	C/C++ Problem
Type 'NiFpga_Status' could not be resolved	DIO.c	/myRIO Example - DIO	line 57	Semantic Error
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - AIO		[Discovery Options] page in project properties	C/C++ Problem
Type 'NiFpga_Bool' could not be resolved	DIO.c	/myRIO Example - DIO	line 55	Semantic Error
Type 'NiFpga_Session' could not be resolved	DIO.c	/myRIO Example - DIO	line 27	Semantic Error
Type 'NiFpga_Bool' could not be resolved	DIO.h	/myRIO Example - DIO	line 40	Semantic Error
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - DIO		[Discovery Options] page in project properties	C/C++ Problem
Type 'uint8_t' could not be resolved	DIO.c	/myRIO Example - DIO	line 161	Semantic Error
Symbol 'DIOA_70IN' could not be resolved	main.c	/myRIO Example - DIO	line 66	Semantic Error
Type 'uint8_t' could not be resolved	DIO.c	/myRIO Example - DIO	line 162	Semantic Error
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - SPI		[Discovery Options] page in project properties	C/C++ Problem
Symbol 'DIOB_70DIR' could not be resolved	main.c	/myRIO Example - DIO	line 69	Semantic Error
Symbol 'DIOB_70OUT' could not be resolved	main.c	/myRIO Example - DIO	line 70	Semantic Error
Symbol 'NiFpga_False' could not be resolved	DIO.c	/myRIO Example - DIO	line 178	Semantic Error
Symbol 'DIOB_70IN' could not be resolved	main.c	/myRIO Example - DIO	line 71	Semantic Error
Symbol 'NiFpga_False' could not be resolved	DIO.c	/myRIO Example - DIO	line 215	Semantic Error
Type 'uint8_t' could not be resolved	DIO.c	/myRIO Example - DIO	line 59	Semantic Error
Symbol 'DIOA_70OUT' could not be resolved	main.c	/myRIO Example - DIO	line 60	Semantic Error
Symbol 'DIOA_70IN' could not be resolved	main.c	/myRIO Example - DIO	line 61	Semantic Error
Type 'NiFpga_Bool' could not be resolved	DIO.c	/myRIO Example - DIO	line 157	Semantic Error
Type 'NiFpga_Status' could not be resolved	DIO.c	/myRIO Example - DIO	line 159	Semantic Error
Symbol 'DIOA_70DIR' could not be resolved	main.c	/myRIO Example - DIO	line 64	Semantic Error
Type 'uint8_t' could not be resolved	DIO.c	/myRIO Example - DIO	line 160	Semantic Error
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - I2C		[Discovery Options] page in project properties	C/C++ Problem
Symbol 'DIOA_70OUT' could not be resolved	main.c	/myRIO Example - DIO	line 65	Semantic Error
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Example - UART		[Discovery Options] page in project properties	C/C++ Problem
Symbol 'NiFpga_True' could not be resolved	DIO.c	/myRIO Example - DIO	line 226	Semantic Error
Symbol 'NiFpga_False' could not be resolved	DIO.c	/myRIO Example - DIO	line 226	Semantic Error
Type 'time_t' could not be resolved	main.c	/myRIO Example - DIO	line 50	Semantic Error
Symbol 'DIOA_70DIR' could not be resolved	main.c	/myRIO Example - DIO	line 59	Semantic Error
Type 'time_t' could not be resolved	main.c	/myRIO Example - DIO	line 51	Semantic Error
Program "arm-none-linux-gnueabi-gcc" not found in PATH	myRIO Template		[Discovery Options] page in project properties	C/C++ Problem

 

356+65.PNG

0 Kudos
Message 7 of 13
(9,039 Views)

Hi jeremiahb,

 

If you navigate to:

 

C:\Program Files (x86)\National Instruments\Eclipse\toolchain\
gcc-4.4-arm\i386\bin

 

Can you verify that the files are located there?  What does that directory look like?

 

Also, can you assert that you are using Windows 64 bit?

 

 

Let me know how this goes,

 

Nick

Applications Engineer
National Instruments
0 Kudos
Message 8 of 13
(9,018 Views)

6981651.PNG654654.PNG

0 Kudos
Message 9 of 13
(9,011 Views)

Hi jeremiahb,

 

I do see that all of these files are located at the directory that you have shown, but this is not the same directory that your "PATH" variable is set to.  In your earlier photo, it appears that PATH is set to C:\Program Files\National Instr... where the directory in your last image is C:\Program Files (x86)\National Instr...

 

Try changing your Environment Variable "PATH" to reference the x86 version of the Program Files.  This should allow the software to find the directories.

 

Let me know how this works!

 

Nick

Applications Engineer
National Instruments
0 Kudos
Message 10 of 13
(8,995 Views)