ICD 4在循环供电后无法对零件进行编程

ICD 4不能在循环功率之后编程部件。ICD 4硬件：AsYY/N:10-10079 Rev 4-没有外部电源应用到ICD4电源插座，USB电源只。通过定制电缆连接到定制板与PIC32 MZ或PIC18部分。在ICD3和PICtiT3程序员下，对电缆和板进行编程和调试。板是自供电的。软件版本：产品版本：MPLAB X IDE V4.15Java:1.8 0144；Java热点（TM）64位服务器VM 25.144-B01RunTime:Java（TM）SE运行时环境1.80Y144-B01Stase:Linux版本4.130至37在AMD64上运行；UTF-8；EnUMUS（MPLAB）：以下错误发生时尝试通过USB电缆断开/连接来编程PIC32 MZ2048和PIC18部件，并尝试编程或甚至刷新部件状态。02.16Bug版本…01.00 .FPGA版本….01.00 .00脚本版本….0.02.2.23脚本构建号….45 A591CBC0应用程序构建号…012345 67 89.目标电压检测硬件错误已由内置自测试RAMA A检测到。你可以把程序的速度设置成正常的。电路板上的电路可能要求您减慢速度。请将工具属性中的设置更改为“低”，然后再次尝试操作。获取设备ID失败。请确认目标设备已被附加并再次尝试操作。连接失败。= =使其再次工作的工作方式＝＝如果ICD 4通过USB电缆与Vin重新供电。连接器插销短路（强制启动加载模式程序），然后在仪表板中刷新刷新后发生以下消息：&在用VIN启动时，在电源上短路，连接到MPLAB ICD 4…当前加载的版本：博城现在为目标设备下载新固件：PIC32 MZ2048 ECM100更新固件应用程序…连接到MPLAB ICD 4…当前加载的版本：应用程序版本…01.02.16BooD版本…01.00 .00 FPGA版本…01…….00 .02.00脚本版本…….4A591CBC0应用程序构建号…012345 67 89-目标电压检测目标设备PIC32 MZ2048 ECM100。设备ID修订＝0xA5序列号：NUM0= 120 A64 FDNUM1= B29 5801 FF编程和调试工作精细如长其他的注释：回环测试仪工作良好，甚至W/O做强制启动加载模式。它也有相同的问题，试图编程PIC18F8J94部分，除非使用强制启动加载模式。我已经在Linux Ubuntu 16.04 64位和Windows Vista 32位测试了该设备。结果是一样的。我还尝试了XC32 2.07（Free）编译器，结果相同。我已经尝试了所有三种编程速度。唯一的差异似乎是关于ASRAM测试的错误信息是0x55 0xAA，当使用低速编程模式时，出现的问题是存储的固件，因为问题只发生在功率循环之后。当MPLABX被迫下载新固件时，程序员工作得很好。我也有MPLABX强制固件到当前*.JAM文件中的4.15。程序员最初有一个在应用程序中更高的版本。版本4.15，但它有与当前版本相同的问题，在一个案件提交给技术支持，但没有更新的情况下，在17天。



      以下为原文

    ICD 4 not able to program parts after cycling power.

ICD 4  Hardware:
ASSY/N: 10-10079 Rev 4
No external power applied to ICD4 power jack, USB power only.
Connecteed via a custom cable to custom boards with PIC32MZ or PIC18 parts.  Cable and boards program and debug fine under ICD3 and PicKit3 programmers.  Boards are self-powered.

software version:
Product Version: MPLAB X IDE v4.15
Java: 1.8.0_144; Java HotSpot(TM) 64-Bit Server VM 25.144-b01
Runtime: Java(TM) SE Runtime Environment 1.8.0_144-b01
System: Linux version 4.13.0-37-generic running on amd64; UTF-8; en_US (mplab)

The following error occurs when trying to program PIC32MZ2048 and PIC18 parts after power cycling via USB cable disconnect/connect and trying to program or even just refresh the part status.

*****************************************************
Connecting to MPLAB ICD 4...

Currently loaded versions:
Application version............01.02.16
Boot version...................01.00.00
FPGA version...................01.00.00
Script version.................00.02.23
Script build number............45a591cbc0
Application build number.......0123456789

Target voltage detected
null
A hardware error has been detected by the built-in self test
SRAMA Address Test - Walking ones
You have set the program speed to Normal. The circuit on your board may require you to slow the speed down. Please change the setting in the tool properties to low and try the operation again.

Failed to get Device ID. Please make sure the target device is attached and try the operation again.
Connection Failed.


== Workaround to get it working again ==
If the ICD 4 is repowered via the USB cable with the Vin connector pins shorted (forced boot load mode procedure) then the following message occurs after hitting refresh in the Dashboard panel:


*****************************************************
Connecting to MPLAB ICD 4...

Currently loaded versions:
Boot version...................01.00.00

Now Downloading new Firmware for target device: PIC32MZ2048ECM100
Updating firmware application...
Connecting to MPLAB ICD 4...

Currently loaded versions:
Application version............01.02.16
Boot version...................01.00.00
FPGA version...................01.00.00
Script version.................00.02.23
Script build number............45a591cbc0
Application build number.......0123456789

Target voltage detected
Target device PIC32MZ2048ECM100 found.
Device Id Revision = 0xA5
Serial Number:
Num0 = 120a64fd
Num1 = b295801f

Programming and debug works fine as long as the ICD4 stays powered.

Other notes:

The loop back tester works fine, even w/o doing the forced boot load mode.

It also has the same problem trying to program a PIC18F87J94 part unless forced boot load mode is used.

I've tested the device under Linux Ubuntu 16.04 64 bit and Windows Vista 32 bit . Results are the same. I've also tried the XC32 2.07 (free) compiler with the same results.

I've tried all three programming speeds. The only difference seemed to be the error message regarding the ASRAM test was 0x55 0xAA when using low speed programming mode.

It appears there is a problem with the stored firmware as the problem only occurs after power cycling. When mplabx is forced to download new firmware the programmer works fine.

I also had mplabx force the firmware to the current *.jam file in 4.15. The programmer initially had a version that was higher in the App. version #, but it had the same problem as the current version in 4.15.

A case was filed with tech. support, but no updates to the case in 17 days.

0