从PICTIT3拔出USB电缆设备随机运行错误

如果拾取器3从电路中移除会发生什么？当拾取器3不供电时，我看到MCLR线下垂从3.3V到2.5V左右。有可能使其低，特别是低于VDD，将导致该部件出现问题。



      以下为原文

    What happens if the PICkit 3 is removed from the circuit?
 
When the PICkit 3 is unpowered, I see the MCLR line sag from 3.3V to around 2.5V. It's possible that having it that low, especially below VDD, will cause a problem for the part.

这个装置的行为是错误的/意外地工作。我无法理解正在发生的事情。测试：1）没有PICTIT3的编程设备：错误的行为2：仅用PICTIT3编程的设备：错误行为3）具有带USB电缆的PICTIT3的编程设备：正常行为



      以下为原文

   
 
The device behaves wrong / works unexpectedly. 
 

I'm unable to understand what is happening.
Tests:
1) Programmed device without PICkit3: wrong behavior
2) Programmed device with PICkit3 only: wrong behavior
3) Programmed device with PICkit3 having USB-Cable: normal behavior

PICTIT3还将把下拉电阻连接到PGD和PGC引脚。如果你自己把这些信号拉低，会不会有什么不同？



      以下为原文

    The PICkit3 will also be connecting pulldown resistors to the PGD and PGC pins.
Does it make a difference if you pull those signals low yourself?
 
 

我正在努力理解这一点。如果你不使用PICTIT3，你是如何编程的？你正在通过车载引导程序吗？



      以下为原文

   
I'm trying to understand this. How are you programming it if you're not using the PICkit3? Are you going through the on-board bootloader?

我认为它们是用PK3编程的，然后在PK3被移除之后。



      以下为原文

    I think they mean programmed with the PK3, then after the PK3 is removed.
 

我正在尝试使用这个设备学习ARDUNO工具。我在ARDINO下配置SPI有问题（但这不是我目前的问题）。在我尝试改变/配置ARDUINO库之前，我决定先用SPI运行一个PIC32项目。我当前的“工作”配置为一个编程设备是：“& lt & & gt”是一个物理连接。该设备工作不正确，没有USB电缆连接到皮卡3（！）！！）请注意，PICTIT3没有连接到PC。



      以下为原文

   
I’m trying to learn the arduino tools using this device. I have got problems configuring the SPI under arduino (but this is not the issue I'm having currently). I decided first to get a PIC32 project with SPI running before I try to change / configure the Arduino libraries.
 
My current "working" configuration for a programmed device is:
TCHIP011 <-> PICkit 3 <-> USB cable

where "<->" is a physical connection.

The device works incorrectly without the USB cable connected to the PICkit 3 (!!). Please note that the PICkit3 is not connected to the PC.

我尝试了你的建议，在PGEC（RB1）和PGD（RB0）上使用弱下拉，但是我得到了同样的故障。如果我插入了皮卡3（具有USB电缆连接的PICTIT3），设备就如预期的那样正常工作。其他配置：



      以下为原文

   


I tried your recommendation with weak pull-down on the PGEC (RB1) & PGED (RB0) using
CNPDB = 0x0383;
but I'm getting the same malfunction. If I plug-in the PICkit 3 (PICkit3 having the USB cable connected) the device inmediatly works as expected.
 
Other configurations:
#pragma config FWDTEN = OFF    // Watchdog Timer Enable->WDT Disabled (SWDTEN Bit Controls)
#pragma config DEBUG = OFF // Background Debugger Enable->Debugger is Disabled
#pragma config JTAGEN = OFF // JTAG Enable->JTAG Disabled
#pragma config ICESEL = ICS_PGx1 // ICE/ICD Comm Channel Select->Communicate on PGEC1/PGED1

 

我只是临时拆掉PGD和PGC，每一个都有10K欧姆，看起来很有效。但是，我为什么要这么做呢？我把PIC配置错了吗？我误解或误解了什么？



      以下为原文

   
 
I just temporarily pull down the PGD & PGC each with a 10K Ohm and it seems to work.

But, why should I do this?
Did I configure the PIC wrong? What did I misread or misunderstand?
 

我只是临时把PGD和PGC用10K欧姆拉了下来，似乎是有效的。但是，为什么我要这么做？我把PIC配置错了吗？我误解或误解了什么？我猜你把这些插脚设置为输入，所以当程序员没有连接时，它们是浮动的，并且在这些引脚上被激活或改变的其他设置有一些中断。试着将它们更改为输出低电平。这将在编程模式中被过度使用，这样就不会损坏程序员。



      以下为原文

   
 
I just temporarily pull down the PGD & PGC each with a 10K Ohm and it seems to work.

But, why should I do this?
Did I configure the PIC wrong? What did I misread or misunderstand?

My guess is you have those pins set as inputs, so they are floating when the programmer is not connected,
and there's some interrupt on change or other setting getting activated by those pins.
Try changing them to outputs driven low. That will be over-ridden in programming mode, so you won't damage the programmer.
 

我仍然在试图找出PIN的错误。我把PIN定义为输出（所有其他未使用的引脚），我也“评论”ICSEL：我只定义了一个定时器上的一个中断，我做了一个同样的结果禁用它。我在PICS上是新的，我真的想要。了解正在发生的事情。有些东西似乎是错误的配置考虑Fubarino作为ARDUNO能够工作编程没有下拉。还有什么可能是错的？顺便问一下，当WPD定义为PGxs时，为什么内部WPD不工作？



      以下为原文

   
 
I’m still trying to figure out what is going wrong with the pins.
I defined the pins as output (all other unused pins too) and I also "commented" the ICESEL:
TRISB = 0x0385;
//#pragma config ICESEL = ICS_PGx1

I only have defined one interrupt on a timer and I make a test disabling it with the same results.
I’m new on the PICs and I really want to understand what is happening. Something seems to be wrong configured considering that Fubarino acting as Arduino is able to work programmed without pull downs.
What else could be wrong?
By the way, why the internal WPDs don’t work on those pins when they are defined as PGxs?

嗨，PGC和PGD^引脚不应该被拉上或下降，如果他们被使用的ICSP。尝试电源FuBARINO板从皮卡3 VDD = 3.45 Voices



      以下为原文

    Hi,
PGC and PGD ^pins should never be pulled up or down if they are used by the ICSP.
Try to power the fubarino board from Pickit3 vith Vdd = 3.45V
Regards
 

HISRC，在PICTIT3用户指南（2.5.5电路，这将阻止调试器的功能）下，没有关于PGXS引脚下拉的限制。但是我想按原样对设备进行编程，而不需要下拉。它应该是可能的，因为Fubarino引导加载程序没有正确地执行拖拽操作。我下载并查看了Bootloader（http://Github.com／ChIPKI…32 AvrdUD引导加载程序），配置“BoADufFuBaNiNiMuiSubBy48 MHz”），在C代码下，我没有发现任何不同的F。我的配置可以澄清这个问题。在Bootloader项目中也有汇编代码，但我不能理解。我使用MPLAB-X“程序目标项目”对设备进行编程，我也尝试使用PROD HEX和MPLAB IPE。在没有插入USB电缆的PICTIT3的情况下，我总是无法运行这个设备。我试图在这个设备中运行的程序使用SPI，用一个定时器扫描一个矩阵按钮。我猜想这个问题存在于我的项目的配置中。——我的配置中可能有什么问题。设备是否需要连接好的皮卡3才能正常运行？



      以下为原文

   
Hi RISC,
 
Under the PICkit3 User’s Guide (2.5.5 Circuits That Will Prevent the Debugger From Functioning) there is no restrictions about pull downs on the PGxs pins.

But I would like to program the device as it is, without the pull downs. It should be possible because the Fubarino bootloader works without pull downs correctly.
I downloaded and took a look under the bootloader (https://github.com/chipKI...32-avrdude-bootloader, configuration “BOARD_FUBARINO_MINI_USB_48MHZ”) and under the C code I didn’t find anything different from my configuration that could clarify the problem. There’re assembly codes too in the bootloader project, but I’m unable to understand it.
 
I programmed the device using the mplab-X “Program Target Project” and also I tried using the prod hex and mplab IPE. I’m always unable to run the device without the PICkit3 connected having the USB cable plugged in.
 
The program I'm trying to run in the device uses SPI and scans a matrix button using a timer.
 
I suppose that the problem resides under my project's configuration.
 
-> What could be wrong in my configurations that the programmed device needs the connected PICkit3 for running correctly?

嗨，看PICTIT3海报说明。没有PIC文档指定应该使用下拉式。如果电路是正确的，既不拉也不拉下来。你试着增加皮卡3 VDD到3.45 V？当做



      以下为原文

    Hi,
Look at the Pickit3 poster notes.
No PIC document specifies that pull down should be used. If circuitry is correct neither pull nor pull down are needed.
Did you try to increase Pickit3 Vdd to 3.45V ?
Regards
 

嗨，RISC，你是对的，我们也有相同的看法：不应该有理由使用下拉。我可以确认拉下可以消除当前的故障，但我想了解原因。我使用的是Microchip部件No.CHCHIP011。用PICTIT3作为PIC32（或ARDUINO）调试或运行设备，我没有任何问题。我在编程设备（PROD）时遇到了麻烦，也就是说，设备应该在没有PICTIT3（！）的情况下运行。TCHIP011能够运行（用引导加载程序）作为ARDUINO。也就是说，TCHIP011运行ARDUINO的代码，没有PGXS上的拖拽，我问自己为什么我不能像PIC32那样正确地编程设备。



      以下为原文

   
 
Hi Risc,
You’re right and we’re the same opinion: there should be no reasons to use pull downs. I’m able to confirm that pull downs remove the current malfunction but I want to understand the reasons of this.
 
I’m using the microchip Part Number TCHIP011. I don’t have any problem debugging or running the device with the PICkit3 acting as PIC32 (or Arduino). I’m having troubles when I program the device (prod), that is, the device should run without the PICkit3 (!).
 
TCHIP011 is able to run (with a boot loader) as Arduino. That is, the TCHIP011 runs Arduino’s code without pull downs on PGxs and I’m asking myself why I’m unable to program the device correctly as PIC32.
 
 
 

嗨，你不能比较编程与Bootloader（RTSP）和使用ICSP编程。编程算法是完全不同的。我个人不使用PICTIT3我喜欢ICD3有几个原因之一是，它的程序快得多……PIC32。不知道为什么……我在论坛上注意到大多数用户都有PICTIT3的问题，更不用说ICD3的问题了，这对我的观点更为可靠。



      以下为原文

    Hi,
You cannot compare programming with bootloader (RTSP) and programming using ICSP.
the programming algorithms are totally different.
I personally don't use Pickit3 I prefer ICD3 for several reasons one of them being the fact that it programs much faster...Pickit3 seem to have mostly issues with detecting PIC32. Not sure why...I noticed in the forum that most users have issues with Pickit3 and much more rarely with ICD3 which is to my opinion much more robust.
Regards
 

我知道，RISC的配置不同吗？我的意思是，“ARDUINO”模式应该使用PIC32并配置RB0＆AMBR1，使其能够在不拖动的情况下工作。PIN 7和8分别是RB0和Rb1，并分配给通用IOs，我想：HTTP://WW1.MICCHIP.COM/DeLoSt/En/DeVICECD/FuBuimoMnIIIV15Sy.PDFHTPX://WW1.MICCHIP.COM/下载/ En/DeDeCo O/FuBuimoMnimuleServReal.PDF



      以下为原文

    Hi RISC,
 
I understand, but are the configurations different?
 
I mean, the “Arduino”-mode should use the PIC32 and configure the RB0 & RB1 in a way being able to work without pull downs.
 
Pins 7 & 8 are the RB0 & RB1 respectively and allocated for general IOs, I suppose:
http://ww1.microchip.com/downloads/en/devicedoc/fubarinomini_v15_sch.pdf
http://ww1.microchip.com/downloads/en/devicedoc/fubarinominiuserrefmanual.pdf
 
 
 

我认为可能存在某种地面问题。我的理论是，任何USB电缆（要么为您的F**ION，要么为PICTIT3）提供接地并解决问题。



      以下为原文

    I think there might be some sort of ground problem. My theory is that any USB cable (either for your F**ino or for PICkit3) provides ground and solves the problem.

您好，FuBARINO板是一个来自Mikroelektronika的转售产品。它的主要目的不是使用ICSP编程，而是使用内置的引导加载程序。我个人试着用ICD3编程，但是我知道你没有这个工具。如果Bootloader模式没有用，为什么不设计自己的板呢？当做



      以下为原文

    Hi,
The fubarino board is a resale product from Mikroelektronika. It is primarily not aimed to be programmed using ICSP but with the built-in bootloader. I would personally try to program it with an ICD3 but I understand you don't have this tool. Why not design your own board if the bootloader mode is useless ?
Regards

他说PK3的电缆不需要插入任何东西。这只是PGC和PGD上的PuldLoad停止了这个问题。这就是为什么我认为这两个引脚上的噪声会导致浮动时出现问题。可能问题是它是一个调试图像，而不是一个正在发布的图像。程序化的。



      以下为原文

    He said the PK3's cable doesn't need to be plugged into anything.
It's just the pulldowns on PGC and PGD stopping the problem.
That's why I think it's noise on those two pins causing a problem when they are floating.
Maybe the problem is simply that it's a debug image, not a release one that is being programmed.