如何将PIC32 USB入门工具包II（DM320003-2）连接到MPLAB X IDE V4.01

是的，你把USB电缆从你的PC连接到板上的迷你B连接器。它显示在硬件工具窗口下的传统启动工具包& & SDK PIC32。我已经附加了一个屏幕截图从我的Linux系统。它在我的Windows 7 PC上工作，但外观略有不同。在Windows系统上，它显示（在“设备和打印机”下）为“定制微芯片USB设备”在Linux上，LSUB报告“ID04D8:00 E0 Microchip技术公司PIC32启动板”，我还没有与任何其他PC开放测试。评级系统，但这些都符合预期：没有外部程序员需要。底线：一旦附加它的行为就像一个皮卡3。编程是完美的，但我不使用（即没有使用）调试功能。另一件事：我会说，对于一些版本的MPLABX，我注意到某些PKOB设备没有被识别，除非它们在启动MPLABX之前连接到PC。无论是在MPLABX版本4.01和4.05之前或之后插入它，似乎都没什么区别，但我想我会提到它。有时事情有点不一致。或者至少这是我不时听到的声音。戴夫，



      以下为原文

   
Yes, you connect a USB cable from your PC to the Mini-B connector on the top of the board.  It shows up in the Hardware Tool window under Legacy Starter Kits->SDKE PIC32.
 
I have attached a screen shot from my Linux system.  It works the same on my Windows 7 PC, but the appearance is slightly different.
 
On the Windows system it shows up (under "Devices and Printers") as "Custom Microchip USB Device"
On Linux, lsu*** reports "ID 04d8:00e0 Microchip Technology, Inc. PIC32 Starter Board"
 
I haven't tested with any other PC operating systems, but with these it works as expected: No external programmer needed. 
 
Bottom line: Once attached it acts like a PICkit 3.  Programming has been perfect, but I don't use (i.e. haven't used) the debug functionality.
 
One other thing:
I will say that for some versions of MPLABX I noticed that certain PKOB devices aren't recognized unless they are connected to the PC before starting MPLABX.  It seems not to make a difference whether you plug it in before or after starting MPLABX version 4.01 and 4.05, but I thought I would mention it.  Sometimes things are a little inconsistent.  Or at least that's what I hear from time to time.
 
 
Regards,

Dave
 
   Attached Image(s)

你好，戴夫，谢谢你的回复。正如你所建议的，我在打开MPLAB X IDE（V4.01）之前连接了USB启动器套件。IDE被检测到板，我可以编程。[MMKAPEX LCDUbjStruthKiTyth-DimoOx项目BuffrVIDES 编程。PNG[/Image ]，但我的问题是在编程板之后，在MPLAB X IDE中，它显示为运行目标。（请检查附加图像）。但实际上它并没有运行我下载的程序，所有三个LED都被关闭了。请告诉我，我们如何确认编程的应用程序是否在电路板上运行。



      以下为原文

    Hi Dave,
 
Thank you for your reply.
 
as you suggested, i have connected the USB starter kit before opening MPLAB X IDE(v4.01). IDE is detected the Board, i'm able to program it. 
[image]D:MMKApex LCDUSB_STR_KIT__DEMO_PROJECTSObeservationsprogramming.png[/image]
but my question is after programming the board, in MPLAB X IDE it is showing as running target.(please check the attached image). but actually it is not running the program which i have downloaded and all the three leds went to off state.
 
please tell me, how we can confirm whether the programmed application is running or not on the board.
 
   Attached Image(s)

谢谢你，戴夫，我终于可以为初学者准备节目了。



      以下为原文

    Thank you DAVE finally i'm able to program the Starter kit.
 
 
Regards
Krishna

程序员验证字节，即上传到设备是成功的。我建议你从一个裸露的金属（即非和谐）应用开始，只是闪烁一个LED。我总是从底层做起，努力工作。（但那只是我，我很滑稽。）有一件事在我脑海中浮现：我不记得哪种版本的MPLABX，或者哪个程序板程序员在编程后没有自动重置目标有问题。在MPLABX窗口顶部有一个图标，用于重置和释放重置目标。你可以试试，只是为了踢球。如果它可以重置和释放，那么你必须假设它正在运行。也许代码中有些东西不起作用。（这很难让我承认，但有时我的程序确实有漏洞。总之，无论如何，在任何应用程序中：然后回到主程序的开头，然后介绍一些可视的（比如闪烁的LED）来显示一些进展。你不必一路回到协调器来用这样的东西来检测你的代码。写代码就行了！那么现在一切都好吗？还是运行代码有问题？问候，戴夫



      以下为原文

   


The programmer verifies, byte by byte that the upload to the device was successful.
I suggest you start with a bare-metal (i.e. non-Harmony) app that just blinks an LED.  I always start at the bottom and work my way up.  (But that's just me; I'm funny that way.)
 
One thing crosses my mind:
I can't remember which version of MPLABX or which on-board programmer had a problem with not automatically resetting the target after programming.  There is an ICON at the top of the MPLABX window to Reset and Release From Reset the target.  You might try that, just for kicks.  If it can Reset and Release, then you have to assume it's running.  Maybe something in the code is not working.  (It's hard for me to admit, but it happens from time to time that my programs actually have bugs.  Really.)
 
Anyhow, with any application:
Then back up to the beginning of main() and introduce something visual (like a blinking LED) that shows some progress.  You don't have to go all the way back to the Harmony configurator to instrument your code with stuff like this.  Just write the code!
 

 
So: Is everything OK now?  Or are there still problems running code?
 
 
Regards,

Dave
 

是的，戴夫，工作很好。没有问题的LED。我已经开始工作的SPI使用PIC32 USB启动器套件II。我只是使用了现有的SPI（SPI循环回）代码（这是在安装后的MPLAB和谐实例）来测试SPI通道。它正在失败。据我所知，环回工作是因为SDO连接到SPI的SDI线。你能建议一些例子代码来测试SPI吗？为什么SPI环回失败？



      以下为原文

    yes dave, it is working fine. no problem with LEDS.
 
i have started working on SPI using PIC32 USB starter kit II. i just used the existing SPI (SPI Loop back) code (which comes in MPLAB harmony examples after installation) to test SPI channels. SPI it is getting failed. as per my knowledge, the loop back is working as SDO is connected to SDI line of SPI. can you please suggest with some example codes to test SPI. and also why SPI loop back is getting failed?
 

我假设您已经阅读了和声示例文档，并且您看到了LeD2被点亮，表示失败。嗯，我在文档中没有明确指出的事情是，为了进行回环测试，您必须将SDO1与SDI1连接到外部。也许他们认为很明显，一个回环项目需要你把东西循环回去。我认为它应该是三步序列中的第0步（因此它是一个四步序列）。这个问题的底线是：当我连接SDO1（RD0）到SDI1（RC4）时，LeD3被点亮，表示成功。删除外部连接，单击MPLABX工具栏图标“保持复位”，然后“从复位释放”，并点亮LED 2。重新连接外部跳线，重置和释放，并且LeD3被点亮。现在，如果你不使用起动器工具包I/O扩展板（或者你的UKII插入的其他东西），我不知道你将如何做出外部连接，但是如果你是，你可以查找连接。在USK2示意图和扩展板示意图上看到J10和/或J11上的引脚对应于RD0和RC4。我使用PICTHE原型板插入到扩展板中，对于这些信号，标记的名称用于此。（注意：对于一些信号和一些初学者工具包模块，标记在PICTHOST PROTION板上的名称已经被稍微加扰，所以总是检查图表。）我不是一个和谐的家伙。我说这并不意味着贬低和谐，但我的意思是我根本没有足够的经验去帮助别人。有一个和谐的子开云(中国)官方。也许你可以在那里问一些和谐的问题。如果你只想测试SPI，你可以写一个裸露的金属（非和谐）项目来初始化SPI模块并锻炼它。最后，一个或两个意见（参见脚注）：（/开始意见）我讨厌USSKII板没有重置按钮。在开发过程中，即使最终产品没有重置功能，也总是需要重置按钮。我（几乎）总是布置PCB来容纳一个复位开关，或者至少有一个垫板，我可以将电线连接到一个外部复位按钮。我（几乎）总是把这样的测试放在一个循环中，这样我就可以连接和断开外部跳线，看到LED图案的变化。可以观察一个范围内的位模式，看看到底发生了什么。[ DaveFootnote ]：这里表达的意见不一定是我自己的。这是我脑子里的声音。



      以下为原文

   
I am assuming you have read the Harmony Examples documentation and you see that LED2 is lit, indicating failure.
 
Well, the thing that I don't remember seeing explicitly stated in the documentation is that in order to do the loopback test you have to connect SDO1 to SDI1 externally.  Maybe they thought it was obvious that a loopback project requires you to loop something back.  I think it should have been Step 0 in the three-step sequence (thus making it a four-step sequence).
 
Bottom line for this part of your question:  When I connect SDO1 (RD0) to SDI1 (RC4), LED3 is lit, indicating success.  Remove the external connection, click the MPLABX toolbar icon for "Hold in Reset" then "Release from Reset" and LED2 is lit.  Reconnect the external jumper, Reset and Release, and LED3 is lit.
 
Now, if you aren't working with a Starter Kit I/O Expansion Board (or something else that your USKII is plugged into), I don't know how the heck you would make the external connection, but if you are, you can look up the connections on the USK2 schematic and the Expansion Board schematic to see what pins on J10 and/or J11 correspond to RD0 and RC4.
I use a PICTail prototype board plugged into the Expansion Board and, for these signals, the marked names work for this.  (Beware: For some few Signals and some few Starter Kit modules, the names marked on the PICtail protype board have been scrambled slightly, so always check the schematics.)
 

I'm not a Harmony guy. I say this not meaning to disparage Harmony, but I mean that I simply don't have enough experience to try to help others.  There is a Harmony subforum.  Maybe you can ask Harmony-specific questions there.
 
If you just want to test SPI, you can write a bare-metal (non-Harmony) project that initializes a SPI module and exercises it.
 
Finally, an opinion or two (see Footnote):
[/Begin Opinion]

• I hate it that the USKII board doesn't have a reset button.  I always need a reset button during development, even if the final product doesn't have a reset function.  I (almost) always lay out the PCB to accommodate a Reset switch, or at least with pads to which I can connect wires to an external reset button.
  

• I hate one-and-done tests like this.  I (almost) always put tests like this in a loop so that I can connect and disconnect the external jumper and see the LED pattern change. Can observe bit patterns on a 'scope to see what the heck is going on.
  

[/End Opinion]
 
Regards,

Dave
 
Footnote:
   The opinions expressed here are not necessarily my own.
   It's these dang voices in my head.