View Single Post
  #1   Spotlight this post!  
Unread 17-02-2010, 16:56
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: Robot code won't load

Quote:
Originally Posted by RevusHarkings View Post
We are unable to load code to the cRIO at all. In WindRiver, all the settings are properly set, but Deploying code stopped working after a while. For a while, we manually put the .out file into the /system/startup directory on the cRIO, and that worked for a while, but then that stopped working too. Instead of loading the new code, it used an older version of the code we were using. We tried re-imaging the cRIO (image v20), and while it deleted the old code, it didn't fix the issue with being unable to load in any new code. Does anyone have an idea what's going on?
You probably need to connect a terminal program (TeraTerm is great) to the cRio serial port and see what's happening as the unit boots.
It wouldn't hurt to check the flash file system...

-> chkdsk "/c"
Reliance File System Integrity Checker
Datalight Reliance v3.2.2 Buid 1376BV
VxWorks Editio for ppc603
Copyright (c) 2003-2008 Datalight, Inc. All Rights Reserved Worldwide.
Checking 19M Byte drive

Checkingcritical meta blocks...............................1OK
Checking indices........................................... .5OK
Checking all drectory contents and inode...................79OK
Cecking allocation map.....................................OK
Checkng for stranded blocks.........................6891OK
relFsChk complete.

Volume Information:
125,583,360 bytes in volue
22,847,488 bytes i 138 files
163,840 ytes in 20 directories
49,152 bytes system ovrhead
102,522,880 byts available for use

8,192 bytes per block
15,330 total block in volume
12,515 locks available
value =0 = 0x0

Edit: the output of the chkdsk command clearly lost some characters. :-(
__________________
Robots never, ever, ever, ever break -- The Robot Repairman (Backyardigans)

Last edited by gvarndell : 17-02-2010 at 16:58. Reason: note the dropped characters in pasted text
Reply With Quote