unobtainium-42
24-01-2009, 16:50
We've got a drivable base, updated the hardware and PC software, and I connected to the cRIO over wireless with my laptop. I suspect that I could download new software onto the cRIO. But, when I run a build even with the SimpleRobot example it never seems to finish building. I've given it as long as an hour and nothing new happened :( No errors, no crashes. The thermometer bar just keeps cycling. Can anyone help me fix this? How long should this take?
This is the Build Output:
Build Started in Project 'SimpleTemplate': 2009-01-22 19:40:37
Generation of makefiles started.
Generation of makefiles finished (Elapsed Time: 00:01).
Platform: Wind River VxWorks 6.3
Command: make --no-print-directory BUILD_SPEC=PPC603gnu DEBUG_MODE=1 TRACE=1
Working Directory: G:/FRC/2009/Workspace/SimpleTemplate/PPC603gnu
if [ ! -d "`dirname "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"`" ]; then mkdir -p "`dirname "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"`"; fi;echo "building SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"; ccppc -g -mcpu=603 -mstrict-align -mno-implicit-fp -mlongcall -ansi -Wall -MD -MP -mlongcall -IC:/WindRiver/vxworks-6.3/target/h -IC:/WindRiver/vxworks-6.3/target/h/WPILib -IC:/WindRiver/vxworks-6.3/target/h/wrn/coreip -DCPU=PPC603 -DTOOL_FAMILY=gnu -DTOOL=gnu -D_WRS_KERNEL -o "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o" -c "G:/FRC/2009/Workspace/SimpleTemplate/MyRobot.cpp"
building SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o
You might notice that the files are on G:\. I did it again on a C:\ project and the problem persisted.
While the build is running, a process called get_feature.exe consumes an entire processor (from a dual core). What is it doing :confused:
This is the Build Output:
Build Started in Project 'SimpleTemplate': 2009-01-22 19:40:37
Generation of makefiles started.
Generation of makefiles finished (Elapsed Time: 00:01).
Platform: Wind River VxWorks 6.3
Command: make --no-print-directory BUILD_SPEC=PPC603gnu DEBUG_MODE=1 TRACE=1
Working Directory: G:/FRC/2009/Workspace/SimpleTemplate/PPC603gnu
if [ ! -d "`dirname "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"`" ]; then mkdir -p "`dirname "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"`"; fi;echo "building SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o"; ccppc -g -mcpu=603 -mstrict-align -mno-implicit-fp -mlongcall -ansi -Wall -MD -MP -mlongcall -IC:/WindRiver/vxworks-6.3/target/h -IC:/WindRiver/vxworks-6.3/target/h/WPILib -IC:/WindRiver/vxworks-6.3/target/h/wrn/coreip -DCPU=PPC603 -DTOOL_FAMILY=gnu -DTOOL=gnu -D_WRS_KERNEL -o "SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o" -c "G:/FRC/2009/Workspace/SimpleTemplate/MyRobot.cpp"
building SimpleTemplate_partialImage/Debug/Objects/SimpleTemplate/MyRobot.o
You might notice that the files are on G:\. I did it again on a C:\ project and the problem persisted.
While the build is running, a process called get_feature.exe consumes an entire processor (from a dual core). What is it doing :confused: