需要Explorer 16/32和MM7150 PICTail连接和示例代码

看来没有样本程序可用于PIC24FJ1024GB610从MM7150读取数据。所以，我试图转换代码“MM7150，Exp16.SAMPADYCODEV1.3.5”，这是为P24FJ128GA010。什么是正确的转换代码的步骤，我想如下：在MPLAB X IDE（编译器：XC16）中，在LinkerFiles内部，用P24FJ1024GB610GL删除P24FJ128GA010GLD。然后我需要以某种方式设置P24FJ1024GB610.H，但是在哪里做？然后，我还需要检查这两个PIC24的数据表比较。请给出建议，以便它能够更快。



      以下为原文

    It looks like there is no sample program available for PIC24FJ1024GB610 to read data from MM7150. So, I am trying to convert the code "MM7150_Exp16_Sample_Code_v1.3.5" which is for P24FJ128GA010. What shall be the correct steps to convert the code, I think like below:
In the MPLAB X IDE (Compiler:XC16), inside LinkerFiles, remove P24FJ128GA010.gld with P24FJ1024GB610.gld.
Then I need to somehow set the P24FJ1024GB610.h, but where to do that?
Then I will also need to check the Datasheet comparision of these two PIC24.
 
Kindly give suggestion so that it can be faster.

如果你能等待PIM P24FJ128GA010，这将使你的评估变得更简单。如果你想在任何情况下使用PicfjxGB6，你现在当然可以用转换开始了。警告：你可能也在Microchip站点上阅读了他们不推荐的MM7150。对于新的设计，从GA010到GB610的改变不像交换头文件和链接器文件那样容易。（无论如何，如果你的项目包括XC.H，那么GLD文件也不一定是必需的，GLD文件通常是自动选择的。我看到老项目还明确地有GLD的本地副本。另外，定义了XC16 1.21的GLD文件夹的路径。这是非常危险的，可能不是必要的）在外围设备和SFR中有很多其他的差异，当它们隐式地使用GB6.H和.GLD文件时，它们中的大多数也变得可见（编译器和链接器错误）。您必须非常仔细地阅读数据表，以注意所有的差异。更容易让编译器发现至少发现缺少SFR定义的差异变得明显。这是一个快速测试，通过简单地改变MpLabXOf中的目标设备，这也取决于相关差异的数量取决于项目，即外围设备的数量。最后，你发现的最新的MM7150样本也使用MCC。将现有的MCC代码从GA010变成GB610也可能比预期的困难。你必须自己修改，或者重新创建MCC代码，我猜。



      以下为原文

    If you can afford to wait for the PIM p24FJ128GA010, this will make your evaluation much more simpler.
If you want to use a PICFJxGB6 in any case, you can of course already start now with conversion.
Caveat: you probably also have read on the Microchip site for the MM7150 that they do not recommend it for new designs.
 
The change from GA010 to GB610 is not as easy as exchanging header and linker files.
(This should not be necessary anyway, if you / the project includes xc.h. Also the GLD file is usually selected automatically. I saw the older project also explicitly had a local copy of the GLD. And additionally a path defined to the GLD folder of XC16 1.21.  That's all dangerous and likely not necessary)
 
There are many other differences in peripherals and SFRs, most of them become also visible (compiler and linker errors) when implicitly using the GB6 .h and .gld files.
 
You would have to read the datasheet very closely to notice all the differences.
It's easier to let the compiler find at least find the differences becoming obvious by missing SFR definitions.
 
This is a quick test by simply changing the target device in MpLabX

make -f nbproject/Makefile-MM7150_SampleCode.mk SUBPROJECTS= .build-conf
make[1]: Entering directory 'D:/DevPrj/MM7150_Exp16_Sample_Code_v1.4.1'
make  -f nbproject/Makefile-MM7150_SampleCode.mk dist/MM7150_SampleCode/production/MM7150_Exp16_Sample_Code_v1.4.1.production.hex
make[2]: Entering directory 'D:/DevPrj/MM7150_Exp16_Sample_Code_v1.4.1'
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/traps.c  -o build/MM7150_SampleCode/production/mcc_generated_files/traps.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/traps.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/mcc.c  -o build/MM7150_SampleCode/production/mcc_generated_files/mcc.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/mcc.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/interrupt_manager.c  -o build/MM7150_SampleCode/production/mcc_generated_files/interrupt_manager.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/interrupt_manager.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/pin_manager.c  -o build/MM7150_SampleCode/production/mcc_generated_files/pin_manager.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/pin_manager.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/ext_int.c  -o build/MM7150_SampleCode/production/mcc_generated_files/ext_int.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/ext_int.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/i2c1.c  -o build/MM7150_SampleCode/production/mcc_generated_files/i2c1.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/i2c1.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
mcc_generated_files/mcc.c:50:9: error: unknown configuration setting: 'OSCIOFNC'
mcc_generated_files/mcc.c:60:9: error: unknown value for configuration setting 'ICS': 'PGx2'
mcc_generated_files/mcc.c:64:9: error: unknown configuration setting: 'BKBUG'
mcc_generated_files/mcc.c:66:9: error: unknown configuration setting: 'GCP'
mcc_generated_files/interrupt_manager.c: In function 'INTERRUPT_Initialize':
mcc_generated_files/interrupt_manager.c:67:17: error: 'IPC4BITS' has no member named 'CNIP'
make[2]: *** [build/MM7150_SampleCode/production/mcc_generated_files/interrupt_manager.o] Error 255
make[2]: *** Waiting for unfinished jobs....
nbproject/Makefile-MM7150_SampleCode.mk:246: recipe for target 'build/MM7150_SampleCode/production/mcc_generated_files/interrupt_manager.o' failed
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/uart2.c  -o build/MM7150_SampleCode/production/mcc_generated_files/uart2.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/uart2.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/tmr1.c  -o build/MM7150_SampleCode/production/mcc_generated_files/tmr1.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/tmr1.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
"C:Program Files (x86)Microchipxc16v1.33binxc16-gcc.exe"   mcc_generated_files/tmr2.c  -o build/MM7150_SampleCode/production/mcc_generated_files/tmr2.o  -c -mcpu=24FJ1024GB610  -MMD -MF "build/MM7150_SampleCode/production/mcc_generated_files/tmr2.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_MM7150_SampleCode=MM7150_SampleCode  -legacy-libc    -O0 -msmart-io=1 -Wall -msfr-warn=off  
nbproject/Makefile-MM7150_SampleCode.mk:239: recipe for target 'build/MM7150_SampleCode/production/mcc_generated_files/mcc.o' failed
make[2]: *** [build/MM7150_SampleCode/production/mcc_generated_files/mcc.o] Error 255
mcc_generated_files/pin_manager.c: In function 'PIN_MANAGER_Initialize':
mcc_generated_files/pin_manager.c:84:5: error: 'CNPU1' undeclared (first use in this function)
mcc_generated_files/pin_manager.c:84:5: note: each undeclared identifier is reported only once for each function it appears in
mcc_generated_files/pin_manager.c:85:5: error: 'CNPU2' undeclared (first use in this function)
mcc_generated_files/pin_manager.c:101:5: error: 'AD1PCFG' undeclared (first use in this function)
mcc_generated_files/pin_manager.c:107:2: error: 'CNEN1bits' undeclared (first use in this function)
mcc_generated_files/pin_manager.c:112:2: error: 'CNEN2bits' undeclared (first use in this function)
mcc_generated_files/pin_manager.c:115:13: error: 'IEC1BITS' has no member named 'CNIE'
mcc_generated_files/pin_manager.c: In function '_CNInterrupt':
mcc_generated_files/pin_manager.c:135:16: error: 'IFS1BITS' has no member named 'CNIF'
mcc_generated_files/i2c1.c: In function 'I2C1_Initialize':
mcc_generated_files/i2c1.c:212:5: error: 'I2C1CON' undeclared (first use in this function)
mcc_generated_files/i2c1.c:212:5: note: each undeclared identifier is reported only once for each function it appears in
mcc_generated_files/pin_manager.c:157:17: error: 'IFS1BITS' has no member named 'CNIF'
mcc_generated_files/i2c1.c: In function '_MI2C1Interrupt':
mcc_generated_files/i2c1.c:296:17: error: 'I2C1CONbits' undeclared (first use in this function)
mcc_generated_files/i2c1.c: In function 'I2C1_Stop':
mcc_generated_files/i2c1.c:598:5: error: 'I2C1CONbits' undeclared (first use in this function)
nbproject/Makefile-MM7150_SampleCode.mk:253: recipe for target 'build/MM7150_SampleCode/production/mcc_generated_files/pin_manager.o' failed
nbproject/Makefile-MM7150_SampleCode.mk:267: recipe for target 'build/MM7150_SampleCode/production/mcc_generated_files/i2c1.o' failed
make[2]: *** [build/MM7150_SampleCode/production/mcc_generated_files/pin_manager.o] Error 255
make[2]: *** [build/MM7150_SampleCode/production/mcc_generated_files/i2c1.o] Error 255
make[2]: Leaving directory 'D:/DevPrj/MM7150_Exp16_Sample_Code_v1.4.1'
nbproject/Makefile-MM7150_SampleCode.mk:90: recipe for target '.build-conf' failed
make[1]: Leaving directory 'D:/DevPrj/MM7150_Exp16_Sample_Code_v1.4.1'
nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
make[1]: *** [.build-conf] Error 2
make: *** [.build-impl] Error 2

BUILD FAILED (exit value 2, total time: 3s)

 
 
 
Of course this depends also on the number of relevant differences depends on the project, i.e. the number of peripherals which you use. 
 
Finally the latest MM7150 sample which you have found also uses MCC.
Changing the existing MCC code from GA010 to GB610 might also be more difficult than expected.
You would have to modify that yourself, or recreate the MCC code, I guess.
 
 

谢谢你的回复。我已经购买了16/32和MM7150。Mouser.jp似乎HavePIM P24FJ128GA010（100PIN）从下面的链接明显：HTTPS://www. MouSer.jp/OpWorkDeLy/MyCHIPC技术/MA2400？QS＝SGAEPIMZMTMLCK3P7ZBOVXI6UISISMVO。所以，将购买PIM。将拔出24FJ1024GB610从探索16/32板，并插入GA010PIM。那应该很好（这里没有兼容性问题吗？）更容易。BTW，在微芯片站点上警告“不推荐新设计”，它具体指的是“新设计”这个词。这是否意味着它不被推荐为PIC XXXGB6XX？想了解它，这样我就不会再买错误的东西了。是的，关于P24FJ1024GB610的样例代码转换是很费力的。首先尝试从MCC创建.gLD文件。但是MPLAX X在试图把它添加到“重要文件”中时被吊死。今天将联系Masor看我是否能很快地得到那个GA010 PIM。



      以下为原文

    Thank you for the reply. 
I already have bought Explore 16/32 and MM7150. Mouser.jp seems have PIM p24FJ128GA010 (100PIN) as evident from below link: https://www.mouser.jp/ProductDetail/Microchip-Technology/MA240011?qs=sGAEpiMZZMtLck3p7ZBovXI6USISRmvo. So, will buy that PIM. Will pull out p24FJ1024GB610 from Explore 16/32 board and plug in the GA010 PIM. That should be fine (no compatibility issue here right?) and easier. 
 
Btw, with the caveat "Not Recommended for new designs" on the Microchip site, what does it specifically mean by the words "new designs"? Does it mean that it is not recommended for PIC  xxxGB6xx onwards? Wanted to understand it so that I do not buy the wrong things in future. 
 
Yes, about converting the Sample code for p24FJ1024GB610 is struggle. First tried to create the .gld files from MCC. But MPLAB X is getting hanged when tried to add it into the "Important Files".
 
Today will contact mouser to see if I can get that old GA010 PIM quickly. 

嗨，我不知道你下载了哪一个样本代码，但是我直接用它编译的PIC24FJ128GA010没有任何错误。它甚至被设计使用MCCIT在这里可下载：HTTP://www. McCHIP.COM/SWLabyWeb/Studio.ASPX？产品= MM7150，HooStI.示例最新版本



      以下为原文

    Hi,
I don't know which sample code you downloaded but the one I used compiled directly for PIC24FJ128GA010 without any error. it is even designed using MCC
It is downloadable here : http://www.microchip.com/SWLibraryWeb/product.aspx?product=MM7150_Host_Example
Take the latest version
Regards
 

是的，样品是为GA010而设计的（但不为GB610编译）。页上的“不推荐用于新设计”的页面在HTTPS://www. MigCHIP.COM/WWWORDSTMS/En/MM7150上应该意味着，如果您刚刚开始新开发，则不鼓励您使用这个（旧的）MM7150设备。与你在设计中使用的MPU无关。可以是GB610或PIC32，甚至ARM。不确定在该页上提到的其他“相关”产品是否可以作为一种（新的）替代品。Masor从美国到欧洲的装运通常很快，例如4天（使用默认装运……）。



      以下为原文

    Yes, the samples are designed (only) for GA010 but do not compile for GB610.
 
The phrase "Not Recommended for new designs" on the page
https://www.microchip.com/wwwproducts/en/MM7150
should mean, that you are not encouraged to use this (old) MM7150 device, if you are just starting a new development. 
It has nothing to do with the MPU which you use in your design. Could be GB610 or PIC32 or even ARM.

Not sure whether the other "related" products mentioned on that page could be uses as a (newer) replacement.
Mouser shipment from US to Europe is usually quick, e.g. 4 days (using default shipment ... )

我不理解如何从MCC中创建.gLD文件。但是正如说不需要创建任何特殊的GLD文件，链接器应该自动地使用正常的GLD文件，用于在XC16编译器目录中自动找到的GB610文件。（有一个目录GLD，不需要将它本地复制到您的项目中）。



      以下为原文

   
I do not understand how you would create a .gld file out of MCC.
But as said there should be no need to create any special .gld file, the linker should automatically use the normal GLD file for the GB610 which he finds automatically in the XC16 compiler directory. (there is a directory GLD, no need to copy that locally to your project). 

在19月2日，我从MaseER订购并在19-2月收到，然后尝试样例代码，并按预期运行并获取数据。谢谢您。



      以下为原文

    On 19-Feb, I ordered from Mouser and received on 19-Feb. Then tried the sample code and it is running as expected and getting the data. Thank you.