打开PICKIT3时崩溃停止工作

什么崩溃？MPLabX？独立工具？什么版本？PIC18没有用户OSCCAL值。



      以下为原文

    What crashes? MPLabX?
The standalone tool?
What version?
That pic18 does not have a user osccal value.

PICTIT3独立工具。如果我在打开PACIT3程序员之前打开它，如果我插上它不检测它，那么我关闭程序打开后，程序员连接它不会打开，典型的Windows弹出“PACIT3停止工作”，如果我去细节问题的名称说“CLR20R3”。在崩溃的窗口弹出PICTIT3程序员改变它的LED的颜色，状态变红，然后窗口弹出说它已经停止工作，状态LED变蓝。正如我之前所说的，IPE就像一个魅力。它必须是独立的工具。我认为所有的图片在最后一个内存地址上都有一个OSCCAL值。我失去了许多芯片不知道工厂OSCCAL值。所以现在我确信不会再发生了。当我得到HPC好奇心板，它与PIC16F18875与MCC预先编程。所以我用我自己的C代码（眨眼）启用LVP PrimMA，它工作，在改变我的代码编译它没有问题，PKOB说它无效的ID（0x00）…



      以下为原文

    The PICKIT3 Standalone tool. If I open before plug in the PICKIT3 programmer it works, If I plug it doesn't detect it, then I close the program open after programmer is connected it wont open and the typical windows pop up "PICKIT3 has stopped working" if I go to details the name of the problem says "CLR20r3". Before the crashing windows pop up PICKIT3 programmer change colors of it's led, STATUS goes RED and then the windows pops up saying it has stopped working and STATUS led goes BLUE. As I said before IPE works like a charm. It must be the Standalone tool.
 
 
I thought all PICs have an OSCCAL value on the last memory address. I lost many chips for not knowing factory OSCCAL value. So now Im making sure that wont happen ever again. When I got the HPC Curiosity board, it came with a PIC16F18875 pre programmed with MCC. So I used my own C code (blink) enabling LVP pragma and it worked, after changing my code wich it compiled with no problems, the PKOB said it invalid ID (0x00)... 

最新版本的独立工具？在IPE上使用了PICTIT3固件之后，你强迫它更新它吗？不只是老照片有用户OSCCAL。你在18875的时候禁用了LVP还是Mclr？这些都是LVP所需要的。仅仅因为代码编译并不意味着它会起作用。



      以下为原文

    The lastest version of the standalone tool?
Did you force it to update the PICKit3 firmware after you used it on IPE?
No only old pics have a user osccal.
Did you disable lvp or Mclr on the 18875?
Those are needed for lvp.
Just becuse code compiles does not mean it will work.

Aptudio1.0.0设备文件版本.0.00 .00。这是关于它的所有说明。我没有强迫它。我禁用了LVP和MCLR是的，但是它没有工作，所以在我改变了两者之后。代码只是闪烁的RB0。使用TIS和PORTB。我把芯片扔在垃圾桶上。那天我真的丢了筹码。IM学习汇编和C与GoigUm培训板，现在它不会再发生，Exp10f和12F系列。真的很疯狂的照片兄弟哈哈，我还有另一个问题HPC好奇板。如果我的PIC可以容忍2.3V-5.5V操作，LVP是启用的，我在DEV板上把电源从3.3V切换到5V，它会破坏芯片吗？



      以下为原文

    Aplication Version 1.0.0.0
Device File Version 00.00.00
 
that's all it says on about.
 
I Did not force it. 
I disabled LVP and MCLR yes, but it didn't work so after I changed both back on.
 
the code was simply blinking RB0. using tris and portb. I threw the chip on the trash. I was really done that day with losing chips. Im learning assembler and C with the Gooligum training board and now It does not happen anymore, exept 10F and 12F series. Really mad PICs brother haha.
 
I also have another question for HPC Curiosity board. If my PIC is tolerable for 2.3V-5.5V operation and LVP is enable and I switch power from 3.3V to 5V on the DEV board will it destroy the chip?

你在板和芯片之间跳跃。弄乱你的问题。您必须使独立的应用程序更新CIPIT3固件，它将不能正常工作与IPE固件。我怀疑你扔掉的芯片损坏了。为什么你担心在3.3和5V使用2.3到5.5的芯片？LVP关于VPP而不是VCC。



      以下为原文

    You are jumping around between boards and chips. Muddying your questions.

You must make the standalone app update the PICKit3 firmware it will not work properly with the IPE firmware.

I doubt the chip you threw away was damaged.

Why are you concerned about using a chip rated at 2.3 to 5.5 at 3.3 and 5v?
Lvp is about Vpp not Vcc.

如果PK3插入时程序不能运行，我怎么办？只有当PK3与USB断开时才独立工作。IPE工作良好。



      以下为原文

   


 
How would I do that if the program won't run when pk3 is plugged in? Standalone only works when pk3 is disconnected from USB. IPE works fine.

嗨，如果“IPE工作得很好”，那你为什么把旧的独立应用程序弄得一团糟？你真正想要解决的问题是什么？旧的独立应用程序和MPLAB X IPE/IDE在PICIT 3硬件中使用不同的固件，并且在改变时很容易绊倒。除了将PIKIT 3放入“Bootloader模式”的过程之外，您可以：退出独立的应用程序或MPLAB，断开USB连接到拾取3，重新启动计算机，R。如需要，ESTART MPLAIPI/IDE或独立的应用程序，根据需要使用“工具”或“Project Projices…”以鼓励固件更新。不要尝试同时运行MPLAB XIP/IDE和独立的应用程序。好奇板中的电压转换器将它们自己适配到实际电压，均为SI。DES，无需外部设置。PKOB在好奇心板下面的PIC24中运行，总是由3.3 V供电。只要它在目标设备的规格范围内，将电压改变到目标设备应该没有问题。不可能用LVP CON将设备编程成死锁状态。在LVP模式下，使用一个程序员来清除图形位。如果你已经能够对具有LVP配置位禁用的设备编程，则需要一个真正的硬件拾取3来擦除芯片。然后，不要用LVP禁用程序再次编程。将擦除的芯片移到好奇心板上；RAM，在配置比特中选择LVP模式。问候，Mysil



      以下为原文

    Hi,
If "IPE works fine", then why do you mess with the old Standalone App?
 
What is the problem you are actually trying to solve?
 
The old Standalone App, and MPLAB X IPE / IDE,
use different Firmware in the PICkit 3 hardware and it is easy to stumble when changing.
 
In addition to the procedure to put PICkit 3 into 'Bootloader mode', you may:
Exit the Standalone App or MPLAB,
Disconnect USB connection to PICkit 3,
Reboot computer,
Restart MPLAB IPE /IDE or Standalone APP as wanted,
Use 'Tools' or 'Project Properties ...' as appropriate to encourage a firmware update, as needed.
 
Don't try to run MPLAB X IPE / IDE, and Standalone App at the same time.
 
Voltage translators in Curiosity Board adapt themself to actual voltage, both sides, without and outside setting needed. The PKOB which run in a PIC24 on the underside of Curiosity Board, is always powered by 3.3 V.
Changing the voltage to the Target device should be no problem, as long as it is within specifications for the target device.
 
It should Not be possible to program a device into a deadlock state with LVP configuration bit cleared, using a programmer in LVP mode.
If you somehow have been able to program a device with LVP configuration bit disabled,
a Real Hardware PICkit 3 is needed to Erase the chip.
Then, do Not program the device again with LVP disabled.
Move the Erased chip to Curiosity Board, and program there, with LVP mode selected in Configuration bits.
 
Regards,
   Mysil