LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO LVRT Duplicate Symbol

Solved!
Go to solution

I have created a cRIO system that I have duplicated and tried to run on a second cRIO system.  It seems there are issues during the start-up of LVRT on the cRIO.

 

The Console Out Bootlog is PARTIALLY attached here....

 

What would be the cause of all these "Duplicate Symbol: " errors?

 

I will be reinstalling the software on the controller and will let you know if it fixes the problem - I was curious about these errors.

 

 

Bootlog copied and pasted below - this is only a small fraction of the Duplicate Symbol errors that were returned.

 

 

cRIO-907x Boot


Copyright 2007 National Instruments Corp.

 

 

Bootrom version: 2.4.7
Creation date: Jul  9 2007, 00:45:07

 


Press any key to stop auto-boot...
 1
 0

auto-booting...


boot device          : tffs=0,0
unit number          : 0
processor number     : 0
host name            : host
file name            : /c/ni-rt/system/vxWorks
flags (f)            : 0x8

Mounting tffs...
Attaching to TFFS... Datalight Reliance v3.00.1218T
VxWorks Edition for ppc603
Copyright (c) 2003-2007 Datalight, Inc.
done.
3554816
Starting at 0x100000...

ATA device not detected.

Adding 8332 symbols for standalone.
Mounting onboard storage...
Datalight Reliance v3.00.1218T
VxWorks Edition for ppc603
Copyright (c) 2003-2007 Datalight, Inc.

-> lvusEngine: PPC603 CPU detected...
CPU tick frequency: 32.999923 MHz [Using: 1000 MHz]
MAX system identification name: NI-cRIO9074-0140DD3B
Initializing network... Static IP address assigned.
 Device 1 - MAC address: 00:80:2F:11:9A:7D - 134.194.105.181 (primary)
Device 2 - MAC address: 00:80:2F:11:9A:7E - 0.0.0.0 (secondary)

Loading LVRT...
Duplicate symbol:"LedInput" loading module  ni_emb.out
Duplicate symbol:"IPResetEnabled" loading module  ni_emb.out
Duplicate symbol:"GetFileSystemType" loading module  ni_emb.out
Duplicate symbol:"GetHighResTimestamp" loading module  ni_emb.out
Duplicate symbol:"GetPrimaryIPAddress" loading module  ni_emb.out
Duplicate symbol:"getOSVersionString" loading module  ni_emb.out
Duplicate symbol:"LoadStartupLibraries" loading module  ni_emb.out
Duplicate symbol:"LabVIEWRTDoneBooting" loading module  ni_emb.out
Duplicate symbol:"StatusLedInput" loading module  ni_emb.out
Duplicate symbol:"SerialRedirectEnabled" loading module  ni_emb.out
Duplicate symbol:"RebootSystem" loading module  ni_emb.out
Duplicate symbol:"CheckReliance" loading module  ni_emb.out
Duplicate symbol:"SafeModeEnabled" loading module  ni_emb.out
Duplicate symbol:"LoadEarlyStartupLibraries" loading module  ni_emb.out
Duplicate symbol:"ThreadTimeCounterUnInit" loading module  ni_emb.out
Duplicate symbol:"InitRDTSC" loading module  ni_emb.out
Duplicate symbol:"UserSwitchInput" loading module  ni_emb.out
Duplicate symbol:"CPULoadMonitorInit" loading module  ni_emb.out
Duplicate symbol:"PrintStringToConsole" loading module  ni_emb.out
Duplicate symbol:"NoAppEnabled" loading module  ni_emb.out
Duplicate symbol:"SystemSwitchInput" loading module  ni_emb.out
Duplicate symbol:"GetTargetID" loading module  ni_emb.out
Duplicate symbol:"GetNumCPUs" loading module  ni_emb.out
Duplicate symbol:"GetHighResTimestampFreq" loading module  ni_emb.out
Duplicate symbol:"LedOutput" loading module  ni_emb.out
Duplicate symbol:"GetCPULoad" loading module  ni_emb.out

Ryan Vallieu CLA, CLED
Senior Systems Analyst II
NASA Ames Research Center
0 Kudos
Message 1 of 3
(2,922 Views)
Solution
Accepted by topic author RVallieu

VxWorks does load-time linking which means all global functions and variables are placed in a symbol table when the library is loaded.  If a symbol name already exists in the symbol table then the "Duplicate Symbol" warning will be generated.  For more information see http://www-cdfonline.fnal.gov/daq/computing/vxworks/symbol_table.htm.  

 

My guess is that somehow a binary is being loaded for a second time, formatting the controller and re-installing software should fix this but let me know if it doesn't.

 

Sebastian

Message 2 of 3
(2,918 Views)

Formatting the controller was the key.

 

At first the installed NI software was uninstalled/installed - did not clear the error.

Ryan Vallieu CLA, CLED
Senior Systems Analyst II
NASA Ames Research Center
0 Kudos
Message 3 of 3
(2,881 Views)