无法选择Curiosity board作为编程工具

嗨，工具是红色的。它可能意味着你选择了一个不受好奇心HPC板支持的图片。你选择了哪一个PIC？当做



      以下为原文

    Hi,
the tool is red. It probably means you selected a PIC which is not supported by the Curiosity HPC board.
Which PIC have you selected?
Regards

PIC18F26K42



      以下为原文

    PIC18F26K42

嗨，我已经成功地使用了PIC18F47 K40，但是K42家族可能太近了。希望它将来会得到支持。我用好奇心板来进行快速原型制作，也因为它很容易添加点击板。



      以下为原文

    Hi,
I have used PIC18F47K40 successfully but probably the K42 family is too recent...
Hopefully it will be supported in the future. 
I use curiosity boards for quick prototyping and also because it is easy to add click boards.
Regards
 

嗨，我试了好奇心HPC上的PIC18F25K42，它工作得很好。我很惊讶PIC18F26K42不支持iPIC18F25K42支持：MPLAB X V4.05MCC插件V3.36XC8V1.44



      以下为原文

    Hi,
 
I just tried PIC18F25K42 on Curiosity HPC and it works fine.
I would be surprised that PIC18F26K42 is not supported if PIC18F25K42 is supported
I use :
MPLAB X v4.05
MCC plugin v3.36
XC8 v1.44
 
Regards

嗯，我可以如实地说，我（几乎）从未对这样的事情感到惊讶，虽然我并不经常感到震惊。例如，使用MPLABX 4.05和XC8版本1.44，我已经完成了PIC18F25K42项目的初步软件（尽管PKOB中有黄色PIP，但是工作得很好）。他硬件选择工具，但PIC18F26K42显示红色，并不会让我选择PKOB无论我多么努力。另一方面，我看到一个黄色PIP上的PIC18LF26K42（但我没有一个测试）。另一方面（第三只手）像Zaphod Beeblebrox？）我已经用PIC18F26K22（绿色PIP）完成了工作，但是最终计划使用的PIC18LF26K22有一个红色PIP。算了吧。（至少我可以用支持的软件来完成这个软件）哦，嗯……底线：我发现好奇心板非常有用，当我发现它们支持我感兴趣的芯片时，我总是很高兴。我没有抱怨，如果我发现有差距的报道。我对微芯片不断涌现的无数芯片的支持印象深刻。戴夫，



      以下为原文

   
 
Well, I can truthfully say that I am (almost) never surprised by stuff like this, although I am not infrequently shocked.
 
For example, using MPLABX 4.05 and XC8 version 1.44, I have completed preliminary software for a PIC18F25K42 project (seems to work just fine, in spite of Yellow pip by PKOB in the hardware selection tool), but the PIC18F26K42 shows Red, and won't let me select PKOB no matter how hard I try.
 
On the other hand I see a Yellow pip on the PIC18LF26K42 (but I don't have one to test with).  Go figure.
 
On the other hand (The third hand?  Like Zaphod Beeblebrox?), I have done work with a PIC18F26K22 (Green pip), but thePIC18LF26K22, which I plan to use eventually, has a Red pip. Go figure.  (At least I can complete the software with the one that is supported.)
 
Oh, well...
 
Bottom line: I am finding the Curiosity boards to be very useful, and am always delighted when I find they support chips that I am interested in evaluating.  I'm not complaining if I find that there are gaps in the coverage.  I am impressed by the support of the gazillions of chips that Microchip keeps churning out.
 
 
 
Regards,

Dave
 
 

我还安装了一个WL10系统的MPLABX V4.05，它看起来是“好奇”HPC DEV板，但是它不允许在好奇心板上安装一个带有PIC18F26K63的板。我会尝试安装原来的MCU，但是考虑到上面的注释，我想知道XX26KXX MCU上的额外的RAM/ROM是否是问题的一部分。迪安



      以下为原文

    I've also got MPLABX v4.05 installed on a Win10 system, and it appears to 'see' the Curiosity HPC dev board, but it won't allow selection of the board with a PIC18F26K83 installed in the Curiosity board. I'll try it with the original MCU installed, but given the comment above, I wonder if the extra RAM/ROM on the xx26Kxx MCU is part of the problem. 
Dean 

从我以前的帖子…我回到好奇心板，在不删除PIC18F26K83的情况下，我将初始的项目配置MCU改变为具有较低RAM /ROM（PIC18F25K83）的家庭成员。结果是不变的，板在MPLAX4.05中是可见的，但不是可选择的。然后我重新安装了好奇板用PIC16F18875装运的MCU，系统就好了，好奇心DEV板是可选择的，等等。我要重新安装PIC18F26，但我会看看是否可以。用我的皮卡3调试器和迪安对话



      以下为原文

    Following on from my earlier post... I went back to the Curiosity board and, without removing the PIC18F26K83, I changed the initial project configuration MCU to the family member with lower RAM/ROM (the PIC18F25K83). The result was unchanged, the board was visible in MPLABX4.05 but was not selectable. 
 
Then I re-installed the MCU that the Curiosity board shipped with -- PIC16F18875 and the system came up fine, the Curiosity dev board was selectable, etc.
 
I'm going to reinstall the PIC18F26, but will see if I can 'speak to' the board with my PICkit 3 debugger. 
 
Dean
 

嗯，我可以如实地说，我（几乎）从未对这样的事情感到惊讶，虽然我并不经常感到震惊。例如，使用MPLABX 4.05和XC8版本1.44，我已经完成了PIC18F25K42项目的初步软件（尽管PKOB中有黄色PIP，但是工作得很好）。他硬件选择工具，但PIC18F26K42显示红色，并不会让我选择PKOB无论我多么努力。另一方面，我看到一个黄色PIP上的PIC18LF26K42（但我没有一个测试）。另一方面（第三只手）像Zaphod Beeblebrox？）我已经用PIC18F26K22（绿色PIP）完成了工作，但是最终计划使用的PIC18LF26K22有一个红色PIP。算了吧。（至少我可以用支持的软件来完成这个软件）哦，嗯……底线：我发现好奇心板非常有用，当我发现它们支持我感兴趣的芯片时，我总是很高兴。我没有抱怨，如果我发现有差距的报道。我对微芯片不断涌现的无数芯片的支持印象深刻。关于DaveHavaveKW7Xi获得了好奇心HPC，我正努力与PIC18F26K22一起工作。我看到你在用它。问题是我想在Microchip网站上运行一个演示代码，不能让它工作。我先尝试了MPLAB X IDE V4.15，然后我读到这个版本对这个微计算机有漏洞。然后我用V3.65得到这个错误信息：目标电压侦测目标设备ID（0x0）是一个无效的设备ID。请检查您的连接到目标设备。设备擦除…编程…下面的内存区域将被编程：程序存储器：开始地址＝0x0，结束地址＝0x5。FFCOM内存程序地址：0预期值：54接收值：编程失败，有什么想法？当做



      以下为原文

   
 
Well, I can truthfully say that I am (almost) never surprised by stuff like this, although I am not infrequently shocked.
 
For example, using MPLABX 4.05 and XC8 version 1.44, I have completed preliminary software for a PIC18F25K42 project (seems to work just fine, in spite of Yellow pip by PKOB in the hardware selection tool), but the PIC18F26K42 shows Red, and won't let me select PKOB no matter how hard I try.
 
On the other hand I see a Yellow pip on the PIC18LF26K42 (but I don't have one to test with).  Go figure.
 
On the other hand (The third hand?  Like Zaphod Beeblebrox?), I have done work with a PIC18F26K22 (Green pip), but thePIC18LF26K22, which I plan to use eventually, has a Red pip. Go figure.  (At least I can complete the software with the one that is supported.)
 
Oh, well...
 
Bottom line: I am finding the Curiosity boards to be very useful, and am always delighted when I find they support chips that I am interested in evaluating.  I'm not complaining if I find that there are gaps in the coverage.  I am impressed by the support of the gazillions of chips that Microchip keeps churning out.
 
 
 
Regards,

Dave
 
 




Hi davekw7x

I got the Curiosity HPC and I'm trying to work with the PIC18F26K22. I read you were using it. The thing is I'm trying to run a demo code that is in Microchip website and can't get it working.
 
I first tried with MPLAB X IDE v4.15 and then I read that this version has bugs for this micro. Then I used v3.65 and got this error message:
 
Target voltage detected
Target Device ID (0x0) is an Invalid Device ID. Please check your connections to the Target Device.
Device Erased...
Programming...
The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0x5ff
configuration memory
program memory
Address: 0 Expected Value: 54 Received Value: 0
Failed to program device
 
Any idea what's going on?
 
Regards

您好，不要使用MPLAB X的旧版与好奇心板，因为您将不是表选择一些图片…我使用MPLAB X V4.15，它像每一个版本，一些bug，但它的工作总体罚款。如果一个工具/ PIC显示黄色，不在乎它只是意味着它还没有生产发布。需要几个月的时间才能移动绿色，但实际上黄色和绿色相似。不支持的是Red。我个人已经开发了好奇心HPC和PIC18F27 K42，所以我知道它工作得很好；=）有时可能不是所有来自PIC的记忆变体都得到支持。选择一个与你的WAN相同的引脚，它可能比你在最终系统中使用的内存要多。在某个阶段，你可能会切换到你自己的板上；



      以下为原文

    Hi,
 
Do not use old version of MPLAB X with curiosity boards because you will not be table to select some PICs...
I use MPLAB X v4.15 which has, like every version, some bugs but it works overall fine.
If a tool/PIC is shown yellow, don't care it just means it is not yet production released. It takes some months before to move green but actually yellow is similar to green. What is not supported is red.
I have personally already developed with Curiosity HPC AND PIC18F27K42 so I know it works well ;=)
sometimes it could be that not all memory variants from a PIC are supported. Select one which has the same pinout with possibly more memory than the one you wan to use in your final system.
At some stage you'll probably anyway switch to your own board ;=)
 
Regards

因为获得新的好奇心板的主题出现了很多，我将分享我的经验…首先，我发现如果我在打开MPLABX之前插入好奇心板就没那么麻烦了。我假设你已经这样做了。根据我的经验，有三个步骤可以让任何新的好奇心板工作：如果MPLABX版本不同于用于编程好奇心的程序，PKOB基本操作固件通常必须更新。已更新（或先前在MPLABX的当前版本下更新，并且当前项目的芯片不同于最近使用该好奇板的芯片），该芯片的特定数据必须上载到好奇心PKOB。最后，MPLABX发送H。将当前项目归档到PKOB。如果执行步骤1，后续步骤总是失败，并且您必须再试一次。至少对我来说，他们总是，总是，在第一步的失败总是在步骤1。我再次点击“制作和程序”重试。第1步是我唯一真正的头部抓痕器，这可能是一个绊脚石。在一些情况下，在第一次重试时，不是告诉我固件是“增强的中程”（或一些适当的家族）很多次它说“未知类型”或一些这样的事情。在这一点上，有时如果我在项目中选择另一个“硬件工具”-gt；属性框（PICTIT3），它会起作用。模拟器，或任何东西，然后点击“应用”，然后，它让我选择好奇心板，并准备好下一步。有时候，我不得不拔掉插头，插入好奇板，让它工作。曾经有一些时候，我必须退出MPLABX，拔出并插入好奇心板并在MPLABX中重新打开这个项目。然后，假设它通过一个好的“固件”消息通过第1步……在步骤2：如果它到达你想要选择你的芯片的那一部分，请注意以下内容：如果有一个R爱德华.皮普：Fuggedaboudit。您将无法选择PKOB与您的芯片。也许你的芯片PKOB将在下一个版本的MPLABX。如果有一个绿色PIP旁边的PKOB，它可以让你选择好奇心板，你应该很好去。（只需确定插入到好奇板中的芯片与这个项目配置的芯片相同。）如果有黄色PIP，你可以选择好奇心。也许它会计划，也许不会。（请参阅脚注）现在，假设您已经选择好奇心板，它将尝试对设备进行编程。在我的经验中，用一个新的芯片，它总是失败的第一次尝试程序。我只需点击“制作和程序”图标，它就会尝试。如果你得到一个消息，比如“目标设备ID（0x0）是一个无效的设备ID”，你可以中止并重试，但是绝对有点试图通过警告。这种尝试将失败。时期。如果你有一个绿色PIP，仍然不能通过这一点，作为最后的手段，首先做我建议的所有事情：从MPLABX出来，拔出和插入好奇心板然后再试一次。例如，PIC18F27 K42在MPLABX版本4.10下出现了黄色PIP，但是不能被编程。在MPLABX版本4.15下，它仍然有黄色PIP（实际上XC8版本1.45也有黄色PIP），但是我为这个芯片测试的一切工作都很好。



      以下为原文

   
Since the subject of getting new Curiosity boards working comes up a lot, I'll share my experiences...
 
First of all, I have found it less problematic if I plug in the Curiosity board before opening MPLABX.  I'll assume you have done this.
 
Now...
In my experience there are three steps to getting any new Curiosity board working:

• If the version of MPLABX is different from the one that was used to program the Curiosity, the PKOB basic operational firmware usually has to be updated.
  
• If the basic firmware has just been updated (or was previously updated under the current version of MPLABX, and the chip for the current project is different from the chip that was most recently used with this Curiosity board), the specific data for this chip must be uploaded to the Curiosity PKOB.
  
• Finally, MPLABX sends the hex file for the current project to the PKOB.
  

 
If step 1 is performed, subsequent steps always fail, and you have to try again.  At least for me, they always, always, always fail at the first attempt at step 1.  I click "Make and Program" again to retry.
 
Step 1 is the only real head-scratcher for me, and this can be a stumbling block.  In some cases, at the first retry, instead of telling me that the firmware is for "Enhanced Midrange" (or some appropriate family) many times it says "Unknown type" or some such thing.
 
At this point, sometimes it works if I select another "Hardware Tool" in the Project->Properties box (PICKit3 or Simulator, or whatever) and click "Apply."  Then, it lets me select the Curiosity board, and it's ready for the next step.  Sometimes I have had to unplug and plug in the Curiosity board to get it to work.  There have been times when I had to get out of MPLABX, unplug and plug in the Curiosity board and reopen the project in MPLABX.
 
Then, assuming it gets past Step 1 with a good "Firmware" message...
 
At Step 2: If it gets to the part where you want to select your chip, note the following:

• If there is a Red Pip beside the PKOB: Fuggedaboudit.  You will not be able to select the PKOB with your chip.  Maybe PKOB with your chip will be in the next version of MPLABX.
  
• If there is a Green Pip beside the PKOB, and it lets you select the Curiosity board, you should be Good To Go.  (Just make sure the chip that is plugged into the Curiosity board is the same as the chip specified for this project configuration.)
  
• If there is a Yellow Pip, you can select the Curiosity.  Maybe it will program, maybe not.  (See Footnote)
  

 
Now, assuming you have selected your Curiosity board, it will try to program the device.  In my experience, with a new chip, it always fails the first attempt to program.  I just click the "Make and Program" icon again and it tries.
If you get a message like "Target Device ID (0x0) is an Invalid Device ID," you can  abort and try again, but there is absolutely point in trying to click through the warning.  This attempt will fail.  Period.  Full stop.
 
If you got a green pip and still can't get past this point, as a very last resort, do all of the things I suggested at first: Get out of MPLABX, unplug and plug the Curiosity board and try again.
 
Regards,
 
Dave
Footnote:
Sometimes devices with a Yellow Pip can work; sometimes not.  For example the PIC18F27K42 showed up with a Yellow Pip under MPLABX version 4.10, but couldn't be programmed.  (Got the Invalid Device ID message.)  But under MPLABX version 4.15, it still has the Yellow Pip (in fact XC8 version 1.45 has a Yellow Pip also), but everything that I have tested for this chip works just fine.
 
   Attached Image(s)

嗨，PICkit在船上主要使用皮卡3软件和表，所以许多设备可以与皮卡3一起使用。可以与PKOB一起使用，条件是它们可以在不使用PGM PIN的情况下用LVP编程。另外一个表列出了预期的与PKOB板一起工作的设备类型，它存储在.jar文件中，在我的计算机上，它在：C:程序文件（x86） Microchip  MPLABXv4.15。MPLAbID\MicroCIP-MPLAB-MPBCORE PKOBSKDE.JARIN的文件是：COM Microchip MbAcMbCyPKOBSKDe.jar Microchip  MPLAB MBOCKPKOBSKDEDPKOBSKDE.PULTALMODATORK.XML，在MPLAB X V4.15中，它看起来像K42设备：“beta”表示黄色PIP，“Yes”意思是绿色。PIP将出现。在K22设备的列表中，PIC18F26K22存在，PIC18LF26K22确实丢失了！我有一些PIC32毫米器件在28引脚PDIP封装，MICROSTICK II板与PKOB。默认情况下，PKOB不喜欢这种组合，而36引脚设备的支持。通过编辑这样的文件，它被接受：每个新版本必须进行相同的编辑。编辑在.jar文件中的文件是棘手的。在尝试更改之前复制文件是有意义的。我使用WiZip打开容器，然后用记事本+ +打开WiZip中的文件进行编辑。当保存更新的文件时，WiZip将要求替换.jar文件。在编辑时，必须关闭MPLAX X，然后缓存目录必须被清除以进行更改以产生效果，用户目录应该保持不变。



      以下为原文

    Hi,
PICkit On Board mostly use PICkit 3 software and tables,
so many devices that can be used with PICkit 3. may be used with PKOB, on condition that they are able to be programmed with LVP without use of PGM pin.

There is an additional table listing which device types that are expected work with PKOB boards,
It is stored in a .jar file, on my computer, it is in:
C:Program Files (x86)MicrochipMPLABXv4.15mplab_idemdbcoremodulescom-microchip-mplab-mdbcore-pkobskde.jar
Inside the file there is:
commicrochipmplabmdbcorepkobskde.jar
commicrochipmplabmdbcorepkobskdepkobskde.platformTool.xml

In MPLAB X v4.15 , it look like this for K42 devices:
            
            
            
            

            
            
            
            
            
            
            

            
            
            
            
            
            
            

            
            
             
"beta" means yellow pip is shown,
"yes" means green pip will show up.

In the list of K22 devices, PIC18F26K22 is present, and PIC18LF26K22 is indeed missing!

I have some PIC32MM devices in 28-pin PDIP package, and Microstick II board with PKOB.
As default, PKOB do not like this combination, while 36 pin device is supported.
By editing the file like this, it is accepted:
            
            
            
The same edit have to be done for each new version.

Editing files residing in a .jar file is tricky. It make sense to make a copy of the file before trying to make changes.
I have used WinZip to open the container, then Notepad++ to open the file for editing inside Winzip.
When updated file have been saved, WinZip will ask to replace the file in .jar.

MPLAB X must be closed down while editing,
and then Cache directory must be cleared for change to have effect, User directory should be left untouched.
 
Regards,
    Mysil

嗨，Mysil，谢谢这个极好的解释，它打开了在没有官方支持的情况下向PKOB添加一些设备的能力；



      以下为原文

    Hi Mysil,
 
Thanks for this excellent explanation which opens up the ability to add some devices to PKOB when not officially supported ;=)
 
Regards