cancel
Showing results for 
Search instead for 
Did you mean: 

Connection refused UDE STK on SPC574K-DISP

belangjd1
Associate

I am trying to connect to the SPC574K-DISP board through PLS UDE Starter kit to program but am getting a "Can't determine the default communication device! Current selection is ambiguous!" Pop up error message.

I followed the Part 7 - AutoDevKit™ detailed tutorial: Debug and release of firmware created with AutoDevKit™ tutorial step-by-step (though I'm using a different board, and I used the RLA IRQ Test Application). To get to this step.

I am using a new SPC574K-DISP board for this, it has not been used/programmed since it came out of the box this week, so I can't verify that it's not a board issue. Though, when powered, the board runs it's Blink LED test application.

Device Manager shows two instances of "SPC574K-DISP Discovery+" under "Other devices", before I install the PlsUsbJtagDrivers, and still the same after, see attached "SPC574K-DISP Investigation_Device Manager.png". If I install the UDESTK drivers from SPC5Studio's OpenOCD, then the Device changes to a COM Port called "UDESTK USB Serial Port (COM7)". Regardless of driver installation, the same error appears in the UDE Debugger.

The board has jumpers to allow selecting the VDD_JTAG voltage level as well as the VDD_CPU source. Both have 3.3V and 5V options. The board is shipped in 5V position for both, I have tested all of the permutations of jumper positions.

According to the video, external power is not required. Never-the-less, I've tried all of the above permutations with only USB connection, and USB connection and external power. I'm also only using the USB cable, not a UDESTK device.

In UDE STK (currently using UDE STK 5.02.04) I get the above noted error when I open my configuration file. Configuration file can be found in the zipped up workspace attached below under ...\UDE\debug.wsx.

I tried a couple of options on the "PowerPC JTAG Target Interface Setup" dialog box that I get after I close the error window. Under "Access Device", I tried both "Any suitable communication device", and "Any FTDI device, attached to USB port." Both resulted in the same error. All of the other settings are default from fresh install. I've attached the connection failed report, it's in the workspace download too. 

Firmware is set to load into Flash, though I doubt that matters.

 

Please help, I'm quite at a loss for other things I can test. I've seen a few people post with similar issues, and all of them state that they bought a new board and that was the solution... Is that really my only option here?

(Virus scan in progress ...)
(Virus scan in progress ...)
(Virus scan in progress ...)
0 REPLIES 0