If there are significant differences this could very well be the source of your problem. See this article for more information and a workaround. See the Custom Board Comparison topic above. Hardware considerations can be ruled out by using a TI target board, available for order at www. The blinking pattern only applies on FET firmware v2.
|Date Added:||1 September 2006|
|File Size:||17.4 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
This indicates that the device is receiving power.
Technical support Request assistance here. Sometimes updating the firmware will fix this problem, but if not the hardware could be damaged. To downgrade the FET firmware to v2 anyway, use: Updating to the latest version fixes bugs in previous releases and provides support for the latest MSP devices.
FET firmware and IAR Embedded Workbench for MSP
The message seen is:. The message seen is: Solution 2 Downgrade to the v2 version of msp This has been corrected in later releases of the v3 DLL. If so were able to successfully program and debug with this tool at any time in the past? Newsroom Press releases, subscriptions, and more. Could dcc find device or device not supported Note for version 5. Using the latest version will eliminate software variables as a cause of your issue.
The blinking pattern only applies on FET firmware v2.
Hardware considerations can be ruled out by feh430uif a TI target board, available for order at www. The flash memory can be erased and programmed in seconds with only a few keystrokes, and since the MSP flash is ultra-low power, no external power supply is required.
After the above fet430if have been performed please do the following: When your device is plugged in do the LEDs blink? Debugging and trace probes.
FET firmware and IAR Embedded Workbench for MSP430 5.40
FET-firmware upgrade and downgrade. Embedded Trust Integrate security into your workflow. This should rule out software considerations. If there are significant fer430uif this could very well be the source of your problem.
If the tool used to work but no longer responds it could be damaged, or the drivers could have a conflict with newly installed 3rd party software.
Both types of drivers create a virtual COM port. Downgrade to the v2 version of msp Note for version 5. Was the tool in question ever recognized by any PC? All product names are trademarks or registered trademarks of their respective owners.