From jwbruce at ece.msstate.edu Tue Oct 2 18:06:27 2007 From: jwbruce at ece.msstate.edu (J. W. Bruce) Date: Tue Oct 2 18:06:32 2007 Subject: [ece4723] Re: Esos timers In-Reply-To: <46D977EF.5010701@msstate.edu> Message-ID: <26159544.94631191366387130.JavaMail.root@zimbra.ece.msstate.edu> ESOS uses TMR0 for the system tick. So, you shouldn't touch it at all. It should say that somewhere in the lab spec. I vaguely recall typing it. So, timers 1-3 are yours. Just be sure to use ESOS functions if you use any timer IRQs. jwb ------------------ J.W. Bruce, Ph.D., Associate Professor Department of Electrical and Computer Engineering Mississippi State University 216 Simrall, Hardy Road Mississippi State, MS 39762-9571 Office: (662) 325-1530 FAX: (662) 325-2298 ----- Original Message ----- From: "Daniel Cranford" To: "J. W. Bruce" , "Lee Hathcock" Sent: Saturday, September 1, 2007 9:32:15 AM (GMT-0600) America/Chicago Subject: Esos timers Does esos use any of the timers or are they all free for our use? --Daniel --The earth is the Lord's and everything in it. Psalm 24:1 From lah1 at ece.msstate.edu Thu Oct 4 10:57:07 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Thu Oct 4 11:13:20 2007 Subject: [ece4723] Procedure for reporting ESOS problems Message-ID: Everyone, If you are having trouble with ESOS, send me a test case that shows the bad behavior ONLY. I want the simplest test case possible. It's not cool to get tons of code around it. :P Also, make sure to tell me exactly what's going on. I've had a few times working on this where I swore up and down that it was the ESOS code, and it turned out to be a problem with yours truly. Shocking, no? Still, I want to know about any problems, so let me know. Also, grades are forthcoming. Tasks 1-3 are already graded, but I haven't applied the peer evals yet. Lee From jwbruce at ece.msstate.edu Thu Oct 4 21:44:53 2007 From: jwbruce at ece.msstate.edu (J. W. Bruce) Date: Thu Oct 4 21:44:59 2007 Subject: [ece4723] Re: Task 5 question In-Reply-To: Message-ID: <29652115.99031191552293212.JavaMail.root@zimbra.ece.msstate.edu> Sorry about that. I thought I had included that in the lab spec. Wind direction varies from 0-360 degrees (compass heading) as the voltage varies from 0-2.5V. It's that simple. jwb ------------------ J.W. Bruce, Ph.D., Associate Professor Department of Electrical and Computer Engineering Mississippi State University 216 Simrall, Hardy Road Mississippi State, MS 39762-9571 Office: (662) 325-1530 FAX: (662) 325-2298 ----- Original Message ----- From: "James Sakalaukus" To: "J. W. Bruce" Sent: Thursday, October 4, 2007 7:19:47 PM (GMT-0600) America/Chicago Subject: Task 5 question The excel spreadsheet does not have values for the wind direction sensor. Will you please post those on the website. Thank you, -- James Sakalaukus jrs229 From lah1 at ece.msstate.edu Fri Oct 5 10:41:51 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Fri Oct 5 10:42:14 2007 Subject: [ece4723] Barometric pressure In-Reply-To: <27409311.91941191271594503.JavaMail.root@zimbra.ece.msstate.edu> References: <27409311.91941191271594503.JavaMail.root@zimbra.ece.msstate.edu> Message-ID: From a random student... What are we supposed to do about the Barometric pressure? The lab manual is sketchy. From Dr. Bruce... I haven't been able to ID a barometric pressure sensor that is (i) affordable, (ii) not some bizarre surface mount, and (iii) doesn't require some crazy low-noise analog design. SO..... we will continue to retrieve barometric pressure from NOAA/NWS. jwb From lah1 at ece.msstate.edu Fri Oct 5 16:21:06 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Fri Oct 5 16:22:09 2007 Subject: [ece4723] Missing prototypes In-Reply-To: <24304660.98741191530666651.JavaMail.root@zimbra.ece.msstate.edu> References: <24304660.98741191530666651.JavaMail.root@zimbra.ece.msstate.edu> Message-ID: About the missing prototypes for the following functions: Do you know where the prototypes to esos_EnableUserInterrupt => _esos_hw_EnableUserInterrupt esos_MarkUserInterruptServiced => _esos_hw_ClearUserInterruptFlag are? I took a look in esos_p18_irq.h and found some macros that perform that function. Should I use those instead? Dr. Bruce's response... Yes... They were functions initially, but changed to macros to (i) get around some strange MCC18 behavior, and (ii) improve performance (stack accesses) since they are used in ISRs. The macros just make them look like functions in case we change them back (and the PC port of ESOS uses a function call). jwb From lah1 at ece.msstate.edu Thu Oct 11 11:51:09 2007 From: lah1 at ece.msstate.edu (Lee A. Hathcock) Date: Thu Oct 11 11:51:14 2007 Subject: [ece4723] Task 5 and sensor readings Message-ID: <2099181.107101192121469214.JavaMail.root@zimbra.ece.msstate.edu> Everyone, I believe almost everyone has checked off their task 5. However, you need to do some heavy stress testing to make sure that you do not get incorrect data measurements due to control signal switching. For example, the ADC values should be almost rock solid, all the time. You may need to give a little time on the control signal switch if you are seeing, for example, the 2.5v reference every once in a while. Something similar may also happen on humidity / wind speed. Note that this is NOT what median-filtering is supposed to resolve. Instead, this is to filter out noise on readings received from the roof, as the cable in 331 has been snaked down through the elevator shaft and wherever the cable could go to get it here. So there's a goodly amount of noise. Some of these issues will become very apparent when we start logging weather data, so these issues will need to be resolved. However, it will not affect the checkoffs I have received, at least for THIS task. Lee From lah1 at ece.msstate.edu Thu Oct 11 14:43:23 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Thu Oct 11 14:43:50 2007 Subject: [ece4723] Tagged releases, and lack thereof Message-ID: Everyone, Please, make sure that you have tagged releases for each task. When I start grading, they should be there, ESPECIALLY considering how far behind I've been. Future infractions may incur... penalties. Of which we will not speak. So check your tags. Thanks. Lee From jwbruce at ece.msstate.edu Fri Oct 12 05:36:40 2007 From: jwbruce at ece.msstate.edu (J. W. Bruce) Date: Fri Oct 12 05:36:45 2007 Subject: [ece4723] Re: Tagged releases, and lack thereof In-Reply-To: Message-ID: <21828904.108121192185400190.JavaMail.root@zimbra.ece.msstate.edu> Here, here. The point of SVN is to allow you (or anyone else) to roll back the code tree to a particular point. I would assume that your "trunk" files are evolving on a daily basis as each new task requires you to modify and/or extend your code from the previous tasks. If so, I ask you: How do I get a valid copy of your task3 code tree, for example? I would checkout your "task3" tag tree which contains a snapshot of your trunk taken at the point when task3 was issue du jour. You should be able to "create" a task3 (or any other task) tag at this point by identifying the proper revision # in the history. Check that tree out. (I'd verify that it works by building & testing it just like you would have done back then. Your procrastination means that you must redo work.) Then commit the code back under the tag folder. Yes, you could do this at any point. So why create "tags"? So, you don't have to go back through the history to ID the correct revision. And what happens when you leave the company? Who is left to "remember" how the development progressed. jwb PS: Several companies I talk to remind me time and again that one of the biggest failings of Mississippi State students is that they "do not follow corporate directives". PPS: In some companies, failure to properly revision control and document code is grounds for immediate firing. Get into the habit NOW!!!! ------------------ J.W. Bruce, Ph.D., Associate Professor Department of Electrical and Computer Engineering Mississippi State University 216 Simrall, Hardy Road Mississippi State, MS 39762-9571 Office: (662) 325-1530 FAX: (662) 325-2298 ----- Original Message ----- From: "Lee Hathcock" To: ece4723@ece.msstate.edu Cc: jwbruce@ece.msstate.edu Sent: Thursday, October 11, 2007 2:43:23 PM (GMT-0600) America/Chicago Subject: Tagged releases, and lack thereof Everyone, Please, make sure that you have tagged releases for each task. When I start grading, they should be there, ESPECIALLY considering how far behind I've been. Future infractions may incur... penalties. Of which we will not speak. So check your tags. Thanks. Lee From jwbruce at ece.msstate.edu Fri Oct 12 10:18:32 2007 From: jwbruce at ece.msstate.edu (J. W. Bruce) Date: Fri Oct 12 10:18:37 2007 Subject: [ece4723] Fwd: The Embedded Muse 150 In-Reply-To: <37edc07866eac3c56028af5d72c097f8@jackganssle.com> Message-ID: <29167566.108751192202312790.JavaMail.root@zimbra.ece.msstate.edu> Here's the latest from Jack. Enjoy! ----- Forwarded Message ----- From: jack@ganssle.com To: jwbruce@ece.msstate.edu Sent: Friday, October 12, 2007 8:17:55 AM (GMT-0600) America/Chicago Subject: The Embedded Muse 150 --------------------------------------------------------------- Embedded Muse 150 Copyright 2007 TGG October 11, 2007 ---------------------------------------------------------------- You may redistribute this newsletter for noncommercial purposes. For commercial use contact info@ganssle.com. EDITOR: Jack Ganssle, jack@ganssle.com CONTENTS: - Editor's Notes - Book Review - Tools and Tips - Open Spaces - Jobs! - Joke for the Week - About The Embedded Muse Editor's Notes -------------- Did you know it IS possible to create accurate schedules? Or that most projects consume 50% of the development time in debug and test, and that it's not hard to slash that number drastically? Or that we know how to manage the quantitative relationship between complexity and bugs? Learn this and far more at my Better Firmware Faster class, presented at your facility. See http://www.ganssle.com/classes.htm . Are you in the Seattle or Minneapolis area? For the first time I'll present a public version of the Better Firmware Faster class in Minneapolis and Seattle, on December 5th and 7th. Registration and other info here: http://www.ganssle.com/classes.htm . You'll earn 0.7 Continuing Education Units, learn a lot, and have more than a little fun. My colleague Bill Gatliff has just announced some new dates for his highly-regarded Embedded Linux Jumpstart class. Bill is a professional Linux developer and tenured instructor at the Embedded Systems Conference, where his classes consistently rank in the top 5%. He's arguably the most sought-after embedded Linux instructor around. See his website at http://billgatliff.com for more information. Book Review ----------- Only rarely do I review a non-technical book, but many of us are managers working hard to find ways to make our teams more effective. Management is an odd sort of job; most technical leaders are folks who have been promoted from the ranks of the engineers, usually with no real managerial experience and even less training. It's important that we get the skills needed, at the very least by reading broadly. I found "First, Break All The Rules" by Marcus Buckingham and Curt Coffman to be a fascinating, important and easy-to-read book that every manager should study. The Gallup organization interviewed 80,000 managers and something like a million workers to find the essential qualities of leadership. This work distills the wisdom found in that study. They found the best employees can positively answer twelve essential questions. The most important half-dozen are: 1) Do I know what is expected from me at work? 2) Do I have the materials and equipment I need to do my work right? 3) Do I have the opportunity to do what I do best every day? 4) In the last seven days, have I received recognition or praise for good work? 5) Does my supervisor, or someone at work, seem to care about me as a person? 6) Is there someone at work who encourages my development? The most important four roles of the manager are: 1) Select people 2) Set expectations 3) Motivate the people 4) Develop the people None of this is surprising or rocket science, but few managers make a concerted effort to practice these roles, and to ensure employees can answer all twelve questions affirmatively. The strength of this book is it isn't infused with slogans; it's all based on real research which the authors translate into useful strategies for working managers. Don't look for cookbook recipes because there are none; every person is different. Do expect general approaches that we *must* practice to build world-class teams. The book is a bit repetitious, and would be better if it were only two-thirds of its 271 pages. But it's a very fast and interesting read. Highly recommended. If you're not a manager, but suffering under someone who has poor leadership skills, slip a copy of the book under your boss's door. Tools and Tips -------------- Jim Donelson recommends the following sites for code for the Blowfish block cipher. He says they look like very promising methods for embedded projects: - http://www.schneier.com/blowfish.html - http://www.schneier.com/blowfish-download.html Open Spaces ----------- Jim Scandale has some experiences to relate about open spaces: "I work in an open lab at a university. We have anywhere from none to six people working simultaneously at any one time. These are almost all senior-level graduate students in Computer Science and Industrial Engineering. I have always been an advocate of the silent workspace since I am easily distracted but this experience (going on six years now) has been a real eye-opener. I have gotten some very complicated work done and except for the occasional lapse into "social hour", we have all been able to work. "The key I believe is to keep the room silent. This is not an enforced rule and in fact is not a rule at all. But the students and workers here are all focused on what they are doing instead of a paycheck and that makes the difference. For a while this lab was also a meeting and conference room and that made things, literally impossible. But since we moved the conference room next door, the lab is an ideal workspace. I don't know how this would work in a corporate office or even an engineering one but I believe that the key to making it work is the quiet." Sharon Foster wrote: "Sometimes partitions only give the illusion of privacy and productivity. The noisiest, most disruptive environment I ever worked in had 6 foot high partitions. Since no one could see them, people felt free to talk in a normal tone or louder, whether they were on the phone or talking to a visitor. Some people used their speaker-phone feature to play back messages. Others carried on conversations with people three cubicles away. I hated it, and it was one of many reasons that I left engineering. In one of the software engineering books that I sold away,--possibly one of the Steve McConnell books?--there are statistics that show that interruptions take a lot more time than responding to the actual question or input. There's also the time it takes to context switch from what you were doing to what the person who interrupted you wants to talk about. And there is the time it takes to context switch back to what you were doing. That can take as much as 20 minutes. Longer if, as in your example, you were working out a complex piece of code in your head and hadn't written anything down yet." A reader who wishes to remain anonymous wrote: "In the latest issue of the Muse, you asked about people who have experience in working in an open office. Well, I have about 5.5 years worth of this "experience" in an open office while working for a large Japanese automotive OEM in North America. The original concept, of course, is to improve open communication. In Japan, this seems to work reasonably well. However, over there, children are taught from a very early age to get consensus on everything!!! For those of us who have not been trained like this, this takes some getting used to. Just to clarify, when I say I work in an open office, I mean it's completely open. There are no cubicles of any sort, no 1/2 wall dividers... nothing. Just a large open area filled with desks. When it does come time to get a group of people together to get consensus on something quickly, it makes it very easy to stand up at your desk, take one sweeping view of the office and decide if everyone that you need for the meeting is present. So, it does create communication, but to the opposite extreme where there is way to much communication that you don't need or want to know about...you know...they guy across from you arguing with his wife, the guys beside you discussing the latest changes and testing that needs to get done, the engineers behind from you discussing how the schedule just won't work, and of course, the endless interruptions from project managers who decide that every little schedule change needs to be personally broadcast as soon as it happens. Believe me, there are no doors to hide behind, no cubicle entrances to cover up, ...oh and headphones are not allowed since they prevent open-communication. For someone who appreciates a quiet environment when concentration is needed, it can be quite a challenge. As far as data on this issue goes, it appears that most people have realized that if you want to get a lot done, relative to normal productivity, come in early or stay late or work on the weekends. Based on conversations I have had with co-workers, we've unscientifically determined that we can double productivity if we work during hours that no-one else is around!!!" Steve deRosier offered this: "Joel Spolsky has a lot to say about productivity and private offices. Here's how he designed his office: http://www.joelonsoftware.com/articles/BionicOffice.html "On interruptions: http://www.joelonsoftware.com/articles/fog0000000068.html "And on productivity of different programmers: http://www.joelonsoftware.com/articles/HighNotes.html "Oh and on getting things done (#5 applies to interruptions): http://www.joelonsoftware.com/printerfriendly/articles/fog0000000332.html and http://www.joelonsoftware.com/articles/fog0000000073.html (older version, but the important item is at the top in this one "Smart and Gets Things Done.")" Rob wrote: "My manager is a good coder, and prefers to bounce his ideas off of me and my co-worker. While this is productive for him, it's absolutely destroying my ability to code. The biggest stretch I ever get is maybe 10 uninterrupted minutes, unless he's not in the office. *Walls* aren't the issue, it's distractions of any kind (interruptions, meetings, chit-chat). "That said, there are definitely times where interaction is required: at the DESIGN phase. "I should also clarify: I'm not talking about multiple people working on the same piece of code (extreme programming or agile), I'm talking about 2 or more people, each supposed to be working on different pieces (even if it's of the same system). The cards do collapse when you're interrupted. When I consulted from my home, my wife never 'got' that concept, and she interrupted me frequently throughout the day, then got upset when I had to work long hours just to get anything done. "People who don't write code don't understand." Jobs! ----- Let me know if you're hiring firmware or embedded designers. No recruiters please, and I reserve the right to edit ads to fit the format and intents of this newsletter. My company, ILX Lightwave, has several open engineering positions in Bozeman, MT. Email resumes to Adam Lamb (alamb@ilxlightwave.com). These jobs include: Analog Design Engineer - This person will work on a dynamic R&D team in defining, designing and developing our next generation of test and measurement instruments. Responsibilities include the design and development of analog and mixed-signal control loops that utilize lasers, photo detectors, A/D and D/A converters, and thermoelectric coolers. BS in Electrical Engineering is required, MSEE preferred. Experience working with laser diodes and other electro-optical devices is a plus. A high energy, self-starter with excellent teamwork and interpersonal skills is desired. Strong oral and written communication skills are essential. Engineering Group Manager - For this position we are looking for an exceptional individual to lead a small team of highly motivated professionals to meet schedule, performance, and cost objectives in the development of test and measurement instruments. In addition to project leadership responsibility, this position will also be a primary resource for senior level analog, digital, or firmware design on the project team. This position requires at least 5 years of senior level design and at least 3 years of project management experience. A BS or MS in Electrical Engineering or related field is required. The successful candidate for this position will be a high energy self-starter with excellent technical and people management skills. Firmware Engineer - This person will work on a dynamic R&D team in defining, designing and developing our next generation of test and measurement instruments. Responsibilities include the design and development of embedded firmware designed to interface digital control loops with analog and mixed-signal control circuitry. The designs are for the development of our benchtop test instruments that utilize lasers, photo detectors, A/D and D/A converters, and thermoelectric coolers. Manufacturing Engineer - This individual will work with our production team to design high performance automated test systems, troubleshoot electronic instruments, and collaborate with development teams in the design and introduction of new instrumentation products. BSEE or BSCE required, advanced degree preferred. Joke for the Week ----------------- "The process is called estimation, not exactimation." - Philip Armour About The Embedded Muse ----------------------- The Embedded Muse is a biweekly newsletter sent via email by Jack Ganssle. Send complaints, comments, and contributions to me at jack@ganssle.com. The Embedded Muse is supported by The Ganssle Group, whose mission is to help embedded folks get better products to market faster. We offer seminars at your site offering hard-hitting ideas - and action - you can take now to improve firmware quality and decrease development time. Contact us at info@ganssle.com for more information. -- If you do not want to receive any more newsletters, http://www.jackganssle.com/lists/?p=unsubscribe&uid=e054cf7788a17a7ea25d9054032f2c06 To update your preferences and to unsubscribe visit http://www.jackganssle.com/lists/?p=preferences&uid=e054cf7788a17a7ea25d9054032f2c06 Forward a Message to Someone http://www.jackganssle.com/lists/?p=forward&uid=e054cf7788a17a7ea25d9054032f2c06&mid=16 -- Powered by PHPlist, www.phplist.com -- From lah1 at ece.msstate.edu Mon Oct 15 16:27:41 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Mon Oct 15 16:28:13 2007 Subject: [ece4723] wxSensorInterface.py Message-ID: Everyone, Here is the file I needed to supply for task 7. Apologies for not having it ready. The lab spec has also been updated, but I don't have access to the proper folder, so it is where all the handouts are for now. It basically restates the information in this template file. Lee -------------- next part -------------- A non-text attachment was scrubbed... Name: wxSensorInterface.py Type: application/octet-stream Size: 2680 bytes Desc: not available Url : http://www.ece.msstate.edu/pipermail/ece4723/attachments/20071015/dc31ef96/wxSensorInterface.obj From lah1 at ece.msstate.edu Wed Oct 17 14:48:24 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Wed Oct 17 14:48:48 2007 Subject: [ece4723] Calculators on test Message-ID: Everyone, Dr. Bruce says simple function calculators are allowed for the exam next week. Lee From lah1 at ece.msstate.edu Fri Oct 19 16:43:29 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Fri Oct 19 16:43:54 2007 Subject: [ece4723] Missing Task 4 and 5 evals Message-ID: Everyone, I seem to be missing several evals from many of you. I do not see them in my email, and my searching through all my paperwork, while admittedly messy, has not produced them, which leads me to believe they were not turned in at all. :P Please, get them in ASAP. People I have not received evals from for tasks 4 and 5: Daniel Cranford Joshua Lunn Tyler Poschel Bryan Reese Andrew Bracey Khanh Bui Larita Copprue James Sakalaukus Joey Ward Michael Weir Scott Wilson Ravi Alapati That's a lot of names, so I'm pretty sure I didn't misplace THAT many. Please send your ratings to me via email, since that will be the easiest and fastest way. Also, to teams Nubium and Tranquillitatis, be sure to note that task 4 is before the addition of another team member, so you will only have three people to rate. My apologies if you did get the ratings to me or told me, which I have promptly forgotten. I seem to remember some of you just saying all excellents for everyone, but I can't remember them all, so having them in electronic form will be very helpful. Thanks. Lee From lah1 at ece.msstate.edu Mon Oct 22 13:51:25 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Mon Oct 22 13:51:55 2007 Subject: [ece4723] Lab attendance this week Message-ID: Everyone, If you are not through with task 7, then Dr. Bruce says you must attend your normal lab section. If you are, you're free to come in, checkoff, and leave. Lee From lah1 at ece.msstate.edu Mon Oct 22 13:54:15 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Mon Oct 22 13:54:46 2007 Subject: [ece4723] Missing evals + task 6 evals Message-ID: Everyone, Right now, I'm missing evals from the following people: Brandon Leatherwood: Task 5 Daniel Cranford: Task 4 and 5 Larita Copprue: Task 4 Bryan Reese: Task 4 and 5 Also, task 6 is completed, so _everyone_ needs to get me their task 6 evals. Lee From lah1 at ece.msstate.edu Tue Oct 23 15:34:23 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Tue Oct 23 15:34:51 2007 Subject: [ece4723] USB Lecture woes Message-ID: No wonder you didn't respond on the last one, nothing changed on the one I sent you. And to make matters worse, apparently I was editing from the temp file from my email browser, which promptly deleted all my hard work. That really ticks me off. I had some good stuff in there, and now I've got to do it all over again... I've got some stuff to use, obviously, but I lost all my good stuff on HID, CDC, and mass storage. Lee From lah1 at ece.msstate.edu Tue Oct 23 15:54:02 2007 From: lah1 at ece.msstate.edu (Lee Hathcock) Date: Tue Oct 23 15:54:30 2007 Subject: [ece4723] Tagged releases, AGAIN Message-ID: Folks, make sure you've got tagged releases in your repository. Everyone should be up to task 6. As far behind as I am, next time I start grading and it's not there, points are coming off. Lee From jwbruce at ece.msstate.edu Wed Oct 24 02:45:26 2007 From: jwbruce at ece.msstate.edu (J. W. Bruce) Date: Wed Oct 24 02:45:32 2007 Subject: [ece4723] PE#2 Thursday Message-ID: <10971529.126581193211926106.JavaMail.root@zimbra.ece.msstate.edu> PE#2 will be held on Thursday during normal lecture hours. Topics on the exam will include all lecture, lab, external readings, and submitted homework up to and including last Tuesday's lecture on timers. The exam is closed book and notes. Laptops, PDAs, cell phones, MP3 players, etc. are prohibited. You will be allowed the use of a simple 5 function calculator, so bring one if you desire. Happy studying and good luck. JWB PS: I would assume that you are nearly finished with your dissections. ------------------ J.W. Bruce, Ph.D., Associate Professor Department of Electrical and Computer Engineering Mississippi State University 216 Simrall, Hardy Road Mississippi State, MS 39762-9571 Office: (662) 325-1530 FAX: (662) 325-2298