View Single Post
  #4   Spotlight this post!  
Unread 31-03-2009, 09:50
gvarndell's Avatar
gvarndell gvarndell is offline
Software Engineer
AKA: Addi's and Georgie's Dad
FRC #1629 (GaCo)
Team Role: Parent
 
Join Date: Jan 2009
Rookie Year: 2008
Location: Grantsville, Maryland
Posts: 350
gvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond reputegvarndell has a reputation beyond repute
Re: No robot diagnostics

Quote:
Originally Posted by unobtainium-42 View Post
I got serial to work with a COM pot ton my pc. When I run a debug launch the processor says this:
program
Exception current instruction address: 0x012d4744
Machine Status Register: 0x0008b032
Condition Register: 0x20000008
Task: 0x12ef170 "FRC_RobotTask"
0x12ef170 (FRC_RobotTask): task 0x12ef170 has had a failure and has been stopped
.
0x12ef170 (FRC_RobotTask): fatal kernel task-level exception!

Earlier in the year I was using debug to monitor the robot, but that no longer works. Debug launches stop in the member declaration and promptly terminate, sometimes with errors, and never touch any of my breakpoints. Run launches just terminate immediately (sometimes with error). Fortunately, I can still program the robot with the FRC downloader.

Can anyone help me solve this problem?
Have you tried deleting all your old launches and recreating them?
Not sure that will work, but seems worth a try.
Reply With Quote