MSP430F5659: MSP430F5659 with USB BSL for installation on a fresh install of Windows 10

Hi,

I do not think we have different driver for windows 10/11. 

What debugger you are using? Are you testing on a Launchpad? Could you use the CCS to download project to your MCU in Windows 10?

Best regards,

Cash Hao 

(Mass erased) device with TI factory USB BSL should be enumerated as HID, without any drivers on any Windows, Linux, Mac OS, whatever. If device USB related hardware is OK.

Hello Experts,

Good day.

The system that did not work never had IAR, Eclipse, CCS, Elprotronics, or anything like that installed.

This process is to be used by production staff, not developers, so no compiler, IDE or debugger of any kind is being used and there is not any sort of "project" being used for this process.

We are not using a launchpad in this situation - this is happening with a production board equipped with a MSP430F5659, a micro-USB connector, a reset button and a "SW Load" button.  However, this process should be identical if using a MSP-TS430PZ100USB board with a 5659 in the socket.

The goal is to program an application hex file into a MSP430F5659 target board via the USB BSL alone.  The JTAG fuse has been blown for security reasons (a non-zero non-FF pattern has been written in the Fuse Location in BSL).

Here is the procedure we followed on the Windows 10 PC that did not work properly:

1. Obtain MSP430Ware from www.ti.com/.../3.80.14.01
2. Unzip and install on machine.
3. Browse to InstallDirectory\ti\msp\MSP430Ware_3_80_14_01\usblib430\Host_USB_Software\Python_Firmware_Upgrader
4. Connect the device end of a microUSB cable into the USB port on the target board.
5. Connect the other end of the USB cable to the Windows PC.
6. While holding the SW Load button down, press and release RESET on the MCB and then release the other button.  The PC should detect the USB device.
7. Open the app, Python_Firmware_UpgraderGUI.exe from within the Python_Firmware_Upgrader directory.  The app's output window should display "Ready".
8. From the File menu, select Open User Firmware, browse to the desired hexfile.txt and click Open.
9. The image should be programmed successfully and the program will start.
10. Observe the Serial Output - new program output should be displayed.

The problem was that the "Ready" prompt did not appear in the Python Firmware Upgrader application window and Device Manager was showing the device as not recognized.

We then discovered that we had an older set of Windows drivers on our file server.  When we installed them on the problem machine, everything started to work correctly.

However, when I first made this inquiry, I couldn't find the original source of the drivers on the TI site.  The person who originally downloaded the files to our server could not remember where they came from as they were downloaded nearly 3 years ago.  I tried doing several searches at the time to find out where these came from so I could properly document the souce of the files but I was unsuccessful.

Now, I was always able do this on my own machine (Windows 11 with full-licensed IAR EW430 installed), another Windows 11 machine here in the office - no IAR - and everything works.  I did not need to install any additional driver.  It also worked fine on my previous Windows 10 machine (also had IAR on it).

However, I just did another google search and, lo and behold, I got lucky and found them here:

software-dl.ti.com/.../index_FDS.html

So, the real question still unanswered is this:  why was it necessary to install these drivers on the machine in question?

Since the original question has been answered (where to find the drivers), maybe you can answer the why question.

Hi,

Good to know you have solve the issue. 

Well, I am not sure why you need to install these drivers. My guess is the origin driver is broken somehow and need to reinstall it. 

Best regards,

Cash Hao