• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 78 subscribers
  • Views 2439 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430FR2433: "Unknown Device" message shown when trying to program in MSP-TS430RGE24A

Ali Anwar
Prodigy 160 points
Part Number: MSP430FR2433
Other Parts Discussed in Thread: MSP-TS430RGE24A, , UNIFLASH, MSP-FET

Using the MSP-TS430RGE24A to program the MSP430FR2433 and getting an "Unknown Device" status. See error log below. Tried to program with Code Composer, Uniflash, and MSP430Flasher and still the same result. Tried both JTAG and SBW. How can we address this?

Fri May 26 04:44:57 2017:       * -----/|-------------------------------------------------------------------- *

Fri May 26 04:44:57 2017:       *     / |__                                                                   *

Fri May 26 04:44:57 2017:       *    /_   /   MSP Flasher v1.3.14                                             *

Fri May 26 04:44:57 2017:       *      | /                                                                    *

Fri May 26 04:44:57 2017:       * -----|/-------------------------------------------------------------------- *

Fri May 26 04:44:57 2017:       *

Fri May 26 04:44:57 2017:       * Evaluating triggers...done

Fri May 26 04:44:57 2017:       * Executing FET detection sweep:

Fri May 26 04:44:57 2017:        - 1: MSP-FET430UIF @ COM5

Fri May 26 04:44:58 2017:        - Select FET number: Fri May 26 04:45:00 2017: 1

Fri May 26 04:45:00 2017:       * Initializing interface @ COM5...done

Fri May 26 04:45:00 2017:       * Checking firmware compatibility:

Fri May 26 04:45:00 2017:       * FET firmware is up to date.

Fri May 26 04:45:00 2017:       * Reading FW version...done

Fri May 26 04:45:00 2017:       * Setting VCC to 3000 mV...done

Fri May 26 04:45:01 2017:       * Accessing device...

Fri May 26 04:45:06 2017:       # Exit: 16

Fri May 26 04:45:06 2017:       # ERROR: Unknown device

Fri May 26 04:45:06 2017:       * Powering down...done

Fri May 26 04:45:06 2017:       * Disconnecting from device...done

Fri May 26 04:45:06 2017:       *

Fri May 26 04:45:07 2017:       * ----------------------------------------------------------------------------

Fri May 26 04:45:07 2017:       * Driver      : closed (Internal error)

Fri May 26 04:45:07 2017:       * ----------------------------------------------------------------------------

Fri May 26 04:45:07 2017:       */

  • 0
    TI__Guru 68116 points
    Hi Ali,

    Since you are seeing the same issue with all those different programs I will guess this may be something hardware-related like an incorrect jumper setting. Here is a checklist of things you may want to check:

    1. Check that the device is oriented correctly in the socket. The dot on the corner of the device indicates pin 1 and you want to make sure this is in the same corner of the socket as pin 1 on the board. Also make sure the device is well-seated within the socket so it is making good contact. I have seen this happen many times before and I've done it myself as well.
    2. Is the part supposed to be powered from the MSP-FET (you aren't using an external power supply or battery)? If so, make sure that the jumper setting for J1 is set to INT position.
    2a. Also ensure that you do not have any other external power supply/voltage connected to any pins on the device that could come up before Vcc (e.g. this can happen if you have other boards connected that have their own batteries etc).
    3. Make sure that JP1 DVCC is populated
    4. Are you using the provided ribbon cable to connect between the FET tool and the target board, or are you using single wires? If you use the provided ribbon cable with the soket on the board this helps assure that you have correct connections.
    5. Has this particular unit had any code loaded into it previously? Sometimes bad code or a failed load can make it difficult to access the device because it is resetting quickly or crashing.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    TI__Guru 68116 points
    Hi Ali,

    Any update on these details?

    Regards,
    Katie
  • 0 in reply to Katie Pier
    TI__Prodigy 160 points
    Hi Katie,

    It turns out the device was not oriented properly in the socket. Thank you for your support!

**Attention** This is a public forum