Rookies need expert in flashing Crio

[RonnyV]

Hello CD community,

We're having big problems with flashing our Crio. We did it once, successfully. We were able in uploading a program, after that we try to delete the code from the crio since then we're struggling with everything.

We can't get it working anymore. We cannot flash the Crio properly anymore, windriver gives constant errors.. we've been working on it for a week now with no results.

We would like to have a skype call with someone that knows stuff about windriver and can help us with step by step flashing.

What we ultimate want is:

Crio Flash
Demo program compile
Upload

Help us
Thanks in advance..


My skype = ronvisserhcm

[bob.wolff68]

Hey Ron,
Your description of the problem tells me that possibly there is some confusion about the flashing of the crio versus uploading/deploying programs. Before going to a conversation about this, I figure I should say:
- cRio Imaging tool is usually done once at the beginning of the season to "catch up" with the latest flash version. This year, v47 is the version that should be on your cRio. You can verify this with the imaging tool. Just run it with the ethernet cable directly attached between the computer and the crio. The imaging tool is pretty good at discovering the crio and telling you on the UI what version is currently on the device. If it's v47, there's no need to re-flash again until FIRST says they have an update - which may or may not happen again this season.
- The cRio imaging tool has nothing to do with Windriver Workbench. Windriver workbench is the development environment for writing programs, compiling them, and 'uploading' or 'deploying' them to the crio. This is not the same as flashing the device. The deployment is simply ftp'ing a compiled program to the cRio so that it will be run the next time the cRio is rebooted.

With that couple of clarifications... let us know if you're on v47 or not and then let's talk about compilation, deploy, and reboot / diagnostic of whether things are healthy from there.

We'll get ya runnin'. I'm confident!

bob

[RonnyV]

We're having some time difference, it will make it a bit hard! I'm not into electronics/programming that much. I'm just the messenger.

What I do know is that they tried the whole day (today) to flash the crio. With a ethernet cable and the flashing tool. (We used crossover cable and normal cable) It was stuck at: Crio rebooting.

We decided on reflashing the CRIO because of the fact that windriver wasn't working anymore. We couldn't upload a code or anything, so we re-installed windriver and labview couple of times. (no succes)

[bob.wolff68]

Thanks for the additional details - a few more questions...

Is it true that the imaging tool sees the crio and then the team has told it to 'format'? And after telling it to format, it gets stuck at 'crio rebooting' ?

If the team is able to turn off the crio, turn it back on, wait 2 minutes, then run the imaging tool, I would be interested to see a screen shot of the imaging tool at this stage to see what the device looks like from the imaging tool standpoint.

Also, have you ever had success in booting this crio or deploying code to it? If so, what changed to make it no longer able to deploy code to it?

I'll send you a friend request on skype and see what I can do.

**OTHERS** I'd appreciate other mentor/experience here as I'm starting to think that there may be a safe-mode-reformat required here and I'm not certain how to do that if this is a 4-port crio without a 'safe' dip-switch.

Thanks,
Bob Wolff

[Greg McKaskle]

If you are in the shop in the afternoon you can use phone support to NI technical support. You need to disable wireless and firewalls before imaging, and an earlier tool would have the side-effect of leaving a second IP setting on your wired network interface card, and that would confuse things as well. You find this in the Advanced button of the IPv4 properties.

If you need to put a 4 slot into safe mode, I believe you hold the reset button for a little over 10 seconds during power up.

Greg McKaskle