完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
电子发烧友论坛|
我已经拥有了PIC32 MZEF开发板，并且正在尝试使用MPLAB X V4.05连接它。我已经跳板使用内部调试器（PKOB），并有一个USB电缆插入到板的USB调试连接器（J3）和我的PC。运行MPLAB X我试图从项目属性中的“硬件工具：”菜单中选择板上调试。“启动工具包（PKOB）-gt；PIC32 MZ EF系列”是红色的，并将鼠标光标悬停在上面，上面写着“不支持”。由于板上调试应该模仿一个PICtiT3，所以我尝试了这个选项，但是MPLAX X不承认该板是一个PICTIT3。该怎么办？我已经使用了最新版本的MPLAB X（V4.05）。这个董事会还不支持吗？
以上来自于百度翻译 以下为原文 I've got the Curiosity PIC32MZEF Development Board and am trying to connect to it using MPLAB X v4.05. I've got the board jumpered to use the internal debugger (PKOB) and have a USB cable plugged into the board's USB debug connector (J3) and my PC. Running MPLAB X I try to select the on-board debug from the "Hardware Tool:" menu in the project properties. The "Starter Kits (PKOB)->PIC32MZ EF Family" is red and hovering the mouse cursor over it it says "Not Supported". Since the on-board debug is supposed to emulate a PICkit3, I tried that option, but MPLAB X doesn't recognize the board as a PICkit3. What to do? I'm already using the latest version of MPLAB X (v4.05). Is this board just not supported yet? 
0
|
|
相关推荐
9个回答
|
|
|
在我的PC Windows 10上，我必须首先连接到USB 2端口进行更新。
以上来自于百度翻译 以下为原文 On my PC Windows 10 I had to first connect to a USB 2 port for it to update. |
|
|
|
|
|
现在USB 3端口看起来像这样
以上来自于百度翻译 以下为原文 Now on USB 3 port it looks like this Attached Image(s) |
|
|
|
|
|
当我最初把板插入到我的电脑上的USB端口时，我看到了一条标准消息，说它正在搜索和安装一个驱动程序。我没有看到任何东西说它正在更新任何东西。它列举了设备管理器中的“人机界面设备”类别中的“USB输入设备”，所以PC正在看它，但是出于某些原因，MPLAB X不是。有什么额外的建议吗？
以上来自于百度翻译 以下为原文 When I initially plugged the board into a USB port on my PC I saw the standard message saying it was searching for and installing a driver. I didn't see anything saying it was updating anything. It enumerates as a "USB Input Device" in the "Human Interface Devices" category in Device Manager, so the PC is seeing it, but for some reason MPLAB X is not. Any additional suggestions? |
|
|
|
|
|
我只是好奇而已：[代码]
以上来自于百度翻译 以下为原文 I just tried my Curiosity: Currently loaded firmware on Starter Kit on Board Firmware Suite Version.....01.51.06 Firmware type..............PIC32MZTarget voltage detected Target device PIC32MZ2048EFM100 found. Device ID Revision = A1 DEVSN0 = ec4b5682 DEVSN1 = d61d5410Device Erased...Programming...The following memory area(s) will be programmed: program memory: start address = 0x1d000000, end address = 0x1d071fff boot config memory configuration memory Programming/Verify complete [/code] |
|
|
|
|
|
这里还有另一个数据点：有一个小印刷开始入门指南，在箱中与董事会。它说，为了确保J8上的引脚3和4被短路（它们是），USB电缆连接到J3（一个是），并且如果连接正确，LeD1、LeD2和ReD3将闪烁在下面的图案中：LeD1: on，LeD2:On，LeD3:OffDele1:OFF，LeD2:OFF，LeD3 Oon on Mead，LED闪烁模式不同。ENT:LeD1: On，LeD2:Off:LeD3:OnDele1:Off:LeD2:On，LeD3 Fun幸运，指南没有说明这种模式意味着什么。我找不到董事会的演示应用程序的源代码来查找这个眨眼模式意味着什么。
以上来自于百度翻译 以下为原文 Here's another data point: There's a small printed getting started guide that came in the box with the board. It says to ensure that pins 3 and 4 on J8 are shorted (they are), a USB cable is connected to J3 (one is), and that if connected correctly, LED1, LED2, and LED3 will blink in the following pattern: LED1: ON, LED2: ON, LED3: OFF LED1: OFF, LED2: OFF, LED3 ON On my board, the LED blink pattern is different: LED1: ON, LED2: OFF, LED3: ON LED1: OFF, LED2: ON, LED3 OFF Unfortunately, the guide doesn't say what this pattern means. I couldn't find the source code for the board's demo app to look up what this blink pattern means. |
|
|
|
|
|
更多的数据：我在IC卡上焊接了一个ICSP头，并尝试用我的ICD3编程它，而且效果很好。我可以下载代码并运行它。然后我尝试了内部PKOB调试器，现在MPLAB X识别它，但是当编程板时，要么挂起，要么抱怨某个内存地址上的数据不匹配。
以上来自于百度翻译 以下为原文 More data: I soldered an ICSP header onto the board and tried to program it with my ICD3, and that worked just fine. I could download code and run it. I then tried the internal PKOB debugger and now MPLAB X recognizes it, but either hangs when programming the board or complains about a data mismatch at a certain memory address. |
|
|
|
|
|
电路板也用ICD4工作得很好。我尝试了一台不同的机器，并与内置调试器（PKOB）有相同的问题——MPLAB X没有看到它。USB连接工作，因为Windows在插入时看到了电路板。我假设PKOB不需要安装一个特殊的驱动程序？好奇快入门指南和用户手册不提任何关于司机…
以上来自于百度翻译 以下为原文 The board works fine with an ICD4 as well. I tried a different machine and have the same issue with the built-in debugger (PKOB)--MPLAB X doesn't see it. The USB connection is working, because Windows sees the board when I plug it in. I'm assuming that PKOB doesn't require a special driver to be installed? The Curiosity quick start guide and user manual don't mention anything about drivers... |
|
|
|
|
|
你好，Sal Ammoniac，有一些相同的演示代码，你可以从子目录中找到和谐的标准项目：Microchip Hyror V2Y05AppWeb侧演示代码是独立的项目，你可以参考文件“迁移独立和谐项目到标准和谐项目”PDF。
以上来自于百度翻译 以下为原文 Hi Sal Ammoniac, Some same demo code, you can find the standard project from Harmony in subdirect C:microchipharmonyv2_05apps The web side demo code is Standalone project, you can reference the file "Migrating Standalone Harmony Project to Standard Harmony Project.pdf" |
|
|
|
|
|
我猜它是特定于Windows的东西。我使用的是同一个板，但使用的是MACOS，它使用内置的调试器工作得很好。我最近决定使用一个PICTIT3，因为我认为它允许更多的调试选项。我只能猜测，可能有某种类型的Windows。在项目的属性下是否出现在MPLAB中？
以上来自于百度翻译 以下为原文 I'm guessing it's something specific to Windows. I'm using the same board but with MacOS and it worked fine with the built-in debugger. I recently decided to use a PicKit3 because I think it allows more debugging options. I can only guess, perhaps there's some type of Windows. Does it show up in MPLAB under the project's properties? |
|
|
|
|
只有小组成员才能发言，加入小组>>
5313 浏览 9 评论
2071 浏览 8 评论
1977 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比？
3246 浏览 3 评论
请问电源和晶体值之间有什么关系吗？PIC在正常条件下运行4MHz需要多少电压？
2285 浏览 5 评论
829浏览 1评论
722浏览 1评论
有偿咨询，关于MPLAB X IPE烧录PIC32MX所遇到的问题
669浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
722浏览 0评论
618浏览 0评论
/6 
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
2237
评论
淘帖
2902
