LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Nonfatal insanity in FPGA vi - what does this mean?

Solved!
Go to solution

I have some FPGA code that 'seems' to work - but when I close the project down i ALWAYS get a error that comes up.  The beginning of the log looks like this:

 

Any thoughts what hte problem is - or how to fix it?

 

 

####
#Date: 22 Mar 2013 12:26:55
#OSName: Windows 7 Home Premium Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 12.0.1F1 32-bit
#AppKind: FDS
#AppModDate: 02/15/2013 16:27 GMT
#LabVIEW Base Address: 0x00400000





<DEBUG_OUTPUT>
22/03/2013 12:32:53.014
DWarn 0xD1EED773: Nonfatal insanity (0x00000080) detected in'FPGACode_Personality_Main_(U16x8Counters).vi: NI.LV.OnlyLoadTypedefRef'
e:\builds\penguin\labview\branches\2012\dev\source\panel\fpsane.cpp(1053) : DWarn 0xD1EED773: Nonfatal insanity (0x00000080) detected in'FPGACode_Personality_Main_(U16x8Counters).vi: NI.LV.OnlyLoadTypedefRef'
minidump id: 5f67b12d-ed75-4375-a613-b327c073136d
$Id: //labview/branches/2012/dev/source/panel/fpsane.cpp#10 $

</DEBUG_OUTPUT>
0x0069FC03 - LabVIEW <unknown> + 0
0x10016460 - mgcore_SH_12_0 <unknown> + 0
0x00E60661 - LabVIEW <unknown> + 0
0x00F7E32B - LabVIEW <unknown> + 0
0x00DDDF7D - LabVIEW <unknown> + 0
0x00D2180B - LabVIEW <unknown> + 0
0x00CD3917 - LabVIEW <unknown> + 0
0x00E60581 - LabVIEW <unknown> + 0
0x009B1DCD - LabVIEW <unknown> + 0
0x00E6B8FF - LabVIEW <unknown> + 0
0x00DC7B8A - LabVIEW <unknown> + 0
0x00C96654 - LabVIEW <unknown> + 0
0x00DA2F3B - LabVIEW <unknown> + 0
0x00DC18C2 - LabVIEW <unknown> + 0
0x00C967A0 - LabVIEW <unknown> + 0
0x00D767DA - LabVIEW <unknown> + 0
0x00F7DE32 - LabVIEW <unknown> + 0
0x00F7EA62 - LabVIEW <unknown> + 0
0x005C0B07 - LabVIEW <unknown> + 0
0x005C23E0 - LabVIEW <unknown> + 0
0x005C003C - LabVIEW <unknown> + 0
0x005C180B - LabVIEW <unknown> + 0
0x005C1E5E - LabVIEW <unknown> + 0
0x0064A2FC - LabVIEW <unknown> + 0
0x00ECE493 - LabVIEW <unknown> + 0
0x00ECECC3 - LabVIEW <unknown> + 0
0x0153D67C - LabVIEW <unknown> + 0
0x0153F46A - LabVIEW <unknown> + 0
0x0155A670 - LabVIEW <unknown> + 0
0x015D278A - LabVIEW <unknown> + 0
0x015C2D9F - LabVIEW <unknown> + 0
0x015E1A69 - LabVIEW <unknown> + 0
0x015CBC39 - LabVIEW <unknown> + 0
0x015AEA37 - LabVIEW <unknown> + 0
0x015D1157 - LabVIEW <unknown> + 0
0x009B0957 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
#** sanity checking heap: "C:\confocal\DevVersion\SpiderConfocal_v2_00\FPGACode\Personality\FPGACode_Personality_Main_(U16x8Counters).vi"
#** sanity checking: "C:\confocal\DevVersion\SpiderConfocal_v2_00\FPGACode\Personality\FPGACode_Personality_Main_(U16x8Counters).vi"
#** compile: "C:\confocal\DevVersion\SpiderConfocal_v2_00\FPGACode\Personality\FPGACode_Personality_Main_(U16x8Counters).vi"
#** prop types: "C:\confocal\DevVersion\SpiderConfocal_v2_00\Libraries\FPGA\Main\FPGA_Main_OpenRef_Backend.vi"
GoDoit: VI "FPGA_Main_OpenRef_Backend.vi" (C:\confocal\DevVersion\SpiderConfocal_v2_00\Libraries\FPGA\Main\FPGA_Main_OpenRef_Backend.vi), HeapClass "FPHP", Act 50,
GoDoit: VI "FPGA_Main_OpenRef_Backend.vi" (C:\confocal\DevVersion\SpiderConfocal_v2_00\Libraries\FPGA\Main\FPGA_Main_OpenRef_Backend.vi), HeapClass "FPHP", Act 50,
#** prop types: "C:\confocal\DevVersion\SpiderConfocal_v2_00\Libraries\FPGA\Main\FPGA_Main_OpenRef_Backend.vi"
*** End Dump ***

Spoiler
 

 

0 Kudos
Message 1 of 5
(3,684 Views)
Solution
Accepted by topic author wideofthemark

Looks like you might have a corruption (non-fatal) in your project, possibly in the FPGA_Main_OpenRef_Backend.vi.

 

I would recommend first a mass compile of your LabVIEW project. This may take care of the problem, if not we need to try and narrow down which VI / project item is the culprit.

 

One way to check to see if the corrupt VI is the FPGA_Main_OpenRef_Backend.vi is to move it alone to another LV project and see if the error shows when you close the project.

 

Let's start with the mass compile and see if that bumps out the problem, if not post back and I'll try to recommend what steps to take next.

Nick C | Software Project Manager - LabVIEW Real-Time | National Instruments
Message 2 of 5
(3,634 Views)

Sounds like something in the VI's jacked up. 

This method worked for me for identifying/fixing the object:

http://forums.ni.com/t5/LabVIEW/Insane-object-at-BDHP-256D8-in-vi-graphics-0X80-wire-segment/m-p/204...

Message 3 of 5
(3,621 Views)

Many thanks for the suggestions.  Heappeak was exactly what i was looking for - i had tried selectively deleting vis, and components/subvis to see where the problem was without any luck before.

 

The problem seems (?) to have been resolved - although I'm not 100% certain this is completely finished - since i have got really inconsistent results from mass compiling, and I haven't had a chance to test on a live FPGA computer.

 

Basically I did a mass compile - and it came up with loads of 'insanities' - even in vis unrelated to the FPGA one that seemed to have a problem.  I tried to find the insanities using the heappeak thing.... and couldn't find the right codes.  After a bit of fruitless searching, I did another mass compile - and all the insanities had disapeared - but it forced me to recompile the FPGA code - so all the vis related were 'Bad'.

 

After recompiling the FPGA, the error on shutdown still was there - so I figured I would try mass compile again - and there were more insanities - but not in the same files......   Still couldn't find them.  Had to recompile the FPGA again (a real bummer - since it takes 40mins). 

 

After this the errors picked up on close seem to have gone - at least on my dev computer.... but I don't have the FPGA here to test if it actually runs - or causes other issues. 

 

So yeah - the problem might be gone - but I'm not exactly sure what i've done to fix it!

0 Kudos
Message 4 of 5
(3,598 Views)

Sounds to me that at some point several pieces of your project had been corrupted and/or had depdency problems. Working through a few mass compiles seems to have resolved those problems.

 

As for the being concerned the FPGA should function properly. The compilation won't start if the FPGA VI is in a broken state, so no worries there. As long as the compilation completed successfully and you have a bitfile, the FPGA will function exactly as you've defined in the VI.

Nick C | Software Project Manager - LabVIEW Real-Time | National Instruments
0 Kudos
Message 5 of 5
(3,587 Views)