'Frequenty Asked Questions'

Q. Where do you hold office hours?

TAs hold office hours in ECEE 2B37

Q. Where is the ECEE 2B37 and how do I get access to it?

Coming from the 436 parking lot towards the engineering center, the EE wing is on the right hand side. The lab is in the basement and was previously called the Capstone Lab. [Campus Map] To get access to this lab, please take your BuffOne card to the EE Office located on the same floor.

Q. I have access to the lab but I can't log into the computer, what should I do?

ECES Lab System Accounts gives all the information needed.

Q. I have questions regarding the lab, can you meet me at xyz date and time?

First line of defence, send us an email. [ john.pratt@colorado.edu, jay.khandhar@colorado.edu, neel.desai@colorado.edu, swetha.natham@colorado.edu ] It is in your interest to copy us all on the email, so who ever has time they can answer you back. I usually reply within 24 hours. If emails do not resolve the issue, come to office hours. That's what they are for. If all else fails, we will try to accomodate you and set up a time with you but please realize that the TAs have classes as well.

Q. What is the IP of the targets in the lab? for rtesp1 for rtesp2 for rtesp3

you get the idea!

If you want to know what ip is the target using, reboot the target, during initialization when it is counting down to start downloading the kernel, press ENTER. It will come to a prompt. Type "p" (without quotes) to print the settings. It has the ip address of the target and the ip address of the host (should be where it is downloading the kernel from. Type "@" (without quotes) to let it continue. If you need to change these settings, type "c".

Q. What is the replacement for Windview in the new Wind River Tools?

It is called the System Viewer, it can be found under Analyze menu, second one from the top.

Q. I can't seem to connect to the target EEK!! What should I do?

First ping it to see if it responds. (open a command prompt in windows and use the command 'ping <ip address>'. Then walk over to it and see if its turned off. Even if it is running, make sure no one else is using it (by asking everyone in the lab loudly), then reboot it! 99% of the time this will clear the probem. If the target still doesn't boot up, please email the TAs.

Q. Does the vxworks shell remember my command history?

Yes. But are you familiar with vi editing? If you are, press ESC inside the vxworks shell then type j or k to go up and down the command history. Remember!! You are in vi mode now.

Q. Why does my C++ comment style "//" doesn't work?

If during the project building process you defaulted to build ANSI compliant code, this will happen. If you wish to use C++ style comments, do the following.

1) In your workspace window, click the 'builds' tab.
2) Expand the tree if its not already expanded and under your project click on default.
3) A small window will open with a number of tabs. Click on tab that says C/C++ compiler
4) In the window for this tab, remove the '-ansi' flag.

Build again and it shouldn't bark at you. I personally like to stay ANSI compliant to keep the code cross compiler

Q. When I type moduleShow, there are other modules that show up in the list that I didn't write or download. Where are they coming from?

Most likely someone is or was using the target. Ask around in the lab if someone is using the target, if no one is using it beside you, just reboot it, so you start fresh.

Q. When I download my code to the target, and run it, all the printfs go to the monitor attached. How can I capture the output for my report?

If you are typing your main function (main here is the name of the function you call at the host shell prompt to run your program, e.g. test_tasks1 in lab0) using the keyboard attached to the target; stop, there is a better way. Right click on the connected target in the "Target Manager" tab (usually bottom left of the screen) and click on "Target Tools" and then click "i Host Shell". As long as the target is connected, this should pop up a shell, just like you had one for simulator. Run your main function from this Host Shell.

Now, running it from Host Shell does not garenttee the output will stay in the shell and not go to the monitor attached. To avoid that, download the file, setout.c from here, and save it in your project directory. In your main function, when you initilize everything (e.g. set the sysClkRate, create and initialize semaphores), call setout(). This will force, all the output to the Host Shell, and the monitor will get nothing.

If you are a responsible individual, you will call the restore() funtion to restore everything back to normal, when your tasks are done. If not, the next student coming in might waste time trying to figure out where his output is going. If you happen to be that student (i.e. the student using the target before you was irresponsible), just reboot the target, it will come up with default settings.

This page is last updated on September 16, 2008

<< Back