Ez430-rf2500 vista

It also didn't help that Microsoft constantly changes their driver models, so things that used a workaround here to implement things that weren't thought of when designing the OS, suddenly stop working. I'm pretty sure with a PC like the ones used in teh TI hardware labs you'll never encoutner a problem.

But with all the othe rindividual components and drivers Even the most popular and sure working medicines may stop functioning when used together with an unrelated other one. Software including drivers isn't different. You may try to download the latest drivers uninstall the old ones first. Or using a different PC. Or check which other, often poorly designed 3rd party software conflicts with the EZ driver installation e.

If it were a general issue, there would be way more complaints in this forum than a thread that was sleeping for 2 years and then 2 years again. How much does TI pay you to write these blame-someone-else apologies? You seem to like writing them; just like a reply gasp! Lack of complaints does not mean lack of a problem; it means that most of us just put up with the lack of help from TI, and move on.

I, for one, have largely abandoned TI as a vendor. I have written here as a response; I no longer waste my time asking TI for help with their bugware. I have not needed to download a new FTDI driver in years. Sadly, the same cannot be said of TI's driver arrangement, and I am not the only one to observe it. If this is somehow not a "general issue" it is perhaps because a lot of people do not know how to use a serial port at all.

Steve Kranish said: How much does TI pay you to write these blame-someone-else apologies? However, this functionality won't by far be enough for doing the things the application UART driver has to do.

Just like I don't say that you can't have problems with the TI driver because it works flawlessly for me. Steve Kranish said: If this is somehow not a "general issue" it is perhaps because a lot of people do not know how to use a serial port at all. Especially if the problems cannot be reproduced in the lab without having the PC of these users for investigation of the problem. The third is rather unlikely.

I've seen what happens in a support forum when a faulty product is released. The second is unlikely too, because then the product had vanished form the shop long ago.

This has happened before. The PC was called 'Macintosh' and the system was for use in the prinmting pland and graphical desing business. However, the prices had several digits more before the decimal point, compared to the EZRF I doubt such an "MSP development station" would sell, but it would definitely work as expected. So I believe that I have the latest available software. If there is something more current that should be used, I would, of course, be interested.

I believe that the problems exist in the firmware in the USB dongle. I am also not aware of any public source-code for the firmware from TI. I am also interested in any updates or fixes available for this part. I am going to copy the last paragraph from my previous post, since I still think it summarizes what I am asking for:. Jon Peterson said: I am also not aware of any public source-code for the firmware from TI.

Jon Peterson said: I am also interested in any updates or fixes available for this part. So instead of ranting about TI's in ability to provide a driver that runs stable on your system on mine, it does , what about starting to provide information that could track the issue down?

Sometimes the video driver interferes with USB data transfers because of incompatibilities in the interrupt chain, sometimes a different USB port or a different loading order of the USB drivers makes a significant difference etc. As I stated before, to fix a problem that affects only a few of many customers, one would need his PC to track the issue down.

I understand your frustration. It's not fun having a problem and no solution. However, in near future, your current PC will be obsolete anyway as it will always be, if it isn't already, due to planned obsolescence and with the new one, maybe it works like a charm from the first moment. I have 5 count 'em, FIVE computers on my desk right now.

All are at least slightly different. They have been used in tens of millions of products, and most users are probably unaware of their presence. If the functionality of the serial channel on the RF board was too complex for TI to do it correctly, they should have had someone else do it. This is not rocket science. Again, lack of complaints does NOT mean a lack of problems, only a lack of complaints.

There seem to be plenty on this thread. It went silent for a long time because we all accepted the same thing: TI is incapable of fixing the problem. Why should they? This are cheap kits, and many wind up in the hands of students who barely understand them - and are highly unlikely to do something as complex as use the much ballyhooed 'backchannel UART' for anything. Jens-Michael Gross said: So instead of ranting about TI's in ability to provide a driver that runs stable on your system on mine, it does , what about starting to provide information that could track the issue down?

I have not been, nor do I "rant". Your personal attacks are not helpful, professional nor wanted. So far you have written more than anyone else without providing any useful information.

I would personally request that you think twice about posting until and unless you have useful information to provide. I will be happy to provide, to Texas Instruments, any and all such information that would prove helpful in finding the cause of the problems we have been seeing. I don't go on fishing expeditions however. I have been on too many of them: tell me this, tell me that, try this, try that Jon Peterson said: I have not been, nor do I "rant". Jon Peterson said: I would personally request that you think twice about posting until and unless you have useful information to provide.

Since there is apparently no 'well, we know your problem and you only have to press this button and all will be fine' type of solution, providing an approach to find the cause of failure in your specific situation that cannot be easily reproduced by anyone else could be considered useful - if you're willing to use it for own work.

Of course you always have the option to ignore it and wait for an out-of-the-box solution that also apparently didn't come for years. Your choice. I can't give you what I and apparently nobody else have. Jon Peterson said: I don't go on fishing expeditions however. For example: in the very common case of CSS not being able to find the FET, it turned out that in one case it was the Razor mouse driver, in another case it was a smartphone synchronizing app that was grabbing the connection as soon as it appeared in the device manager.

Nothing TI could have done would have prevented this. And since nobody at TI was using a gamers mouse of this brand or this smartphone on one of the development machines, no effort in the labs could have led to a solution. However, the not useful, in your eyes information of possibly conflicting software allowed the two people to detect what's going on on theit specific system and solve the problem permanently.

Steve Kranish said: If the functionality of the serial channel on the RF board was too complex for TI to do it correctly. Steve Kranish said: This is not rocket science. Steve Kranish said: Again, lack of complaints does NOT mean a lack of problems, only a lack of complaints.

Steve Kranish said: TI is incapable of fixing the problem. Steve Kranish said: This are cheap kits, and many wind up in the hands of students who barely understand them - and are highly unlikely to do something as complex as use the much ballyhooed 'backchannel UART' for anything.

Site Search User. Mentions Tags More Cancel. Ask a related question What is a related question? A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question. Ask a new question Ask a new question Cancel. Tags More Cancel. Share More Cancel. Similar topics. This thread has been locked. Intellectual points.

Depending on the phase of the moon, one or more of the following steps seem to necessary to clear the problem: Unplugging and replugging the dongle. Cycling power on the laptop. Has anyone else experienced this? My thanks for any insight anyone can provide on this problem. At least for you it works most of the time :- I think I'll give up and use an older computer which still has CCE v2 on it and it works fine.

Up 0 Down Cancel. When I try Debug I get: Error initializing emulator: Could not initialize device interface I tried disconnecting the board to make sure at least CCE sees it when connected and in this case the error is below, different than one connected. Thanks for taking a look at my issue. Prodigy 50 points. Did you ever get this problem resolved? What's up with that??

Thanks guys, Sean. Mmm, looks like I'll go your way on this. Thanks for you help though, appreciate the response! Again, thanks for your help!

Prodigy 20 points. TIA for any insight. Brandon, I have seen this problem in Vista - Windows does not correctly typify the device during install in Vista and the "Could not initialize device interface" occurs when launching any debug. Regards, Jerry Campbell. CCE build 3. Any ideas would be well appreciated. Prodigy points. Regards, Clark. Am I missing anything? Yours Simon M. The fix is not to disable other devices my touchpad fer instance.

I find it depressing! I wonder if the Bluetooth driver is messing with the com ports? Silicon Labs now has a Ver 5. Stay Tuned! I am still not able to reliably connect my EZRF device. By using our site, you acknowledge that you have read and understand our Cookie Policy , Privacy Policy , and our Terms of Service. Introduction to Microcontrollers Mike Silva. Arduino Robotics Lonnie Honeycutt. Forums More Forums msp How does that work?

It would be nice to have a serial port available which didn't require a debugging session. Dies und viel mehr bietet das neue Yahoo! Mail - www. You may need to go to Connect under Menu to get the demo to run. If something isn't shown right away, try toggling the jumper again or swapping USB ports. I found it to be somewhat finicky. Remember to flip the jumper on the battery-powered sensor when you are done. If you don't do this, the batteries will die! Project Ideas 3.

Home Security Motes We will use the motes to put around a door presumably an entrance to an important room. Each mote will have some sensor s attached to it to help detect when the door opens. Accelerometer for mote on door. Passive infrared sensor for motion detection. When a user opens the door, 1 or more sensors should be triggered. If a designated sensor is within range the user presumably has it in his pocket, for example , the system will detect the presence of another wifi signal, and entrance is OK.

If no designated sensor is within range, the system will expect the password to be entered within X number of seconds. If the password is not entered correctly within X seconds given Y number of tries, the user will be deemed an intruder. The sensors will inform the USB-powered sensor, and the computer will take appropriate actions. Sound an alarm through the speakers. Send an e-mail to an address specified to alert that there is an intruder. Ambitious Project This one may be difficult.

Some people claim to have done this, with limited success. Pieces of the process have been done, including a cross compiler under Linux msp gcc with the eZ's processor correctly targeted and the basic port and pin mapping found for TinyOS. Also, using a somewhat different platform, the CC or similar radio has been shown to work in TinyOS. As the semester proceeds, we will look at TinyOS and see if there is interest in getting it to work on this platform.

Sensors There are some places to wire sensors or other communication on the sides of the circuit boards. These are documented in datasheets for the eZRF For ideas about sensors, see notes on the Sentilla Group.