MLA Library错误

哪些错误？



      以下为原文

    which errors?

没有找到任何与USB相关的头文件的文件目录。复制和粘贴后，文件目录THA错误固定，但之后出现了对象文件错误。



      以下为原文

    no found such file directory for whatever u*** related header file. after copy and paste that file directory tha error fixed but after that object file error occured.

你的描述有点草率。目前还不清楚，你使用的是基于GB110的项目。如果编译器输出存在问题，最好添加一些输出（使用代码标签！）您仍然使用相当老的MPLABX，MLA V2015Y08Y10也有点老了。MLA V2016Y08Y08示例CDC基本构建没有错误（框外）。例如，对于Exp16PIC24FJ256GB110，您也可以尝试PIC24FXSTARTYLKITKET.X，它使用PIC24FJ256GB106。介绍了USB框架中包含路径的一些问题，例如U.B。HMICROCHIPS改变了样本的布局，并不断地重复，很可能样本在该版本中被破坏了。如果你正在试用GB612系列，你应该更新MPLABX和MLA。你甚至应该CHH。确定你的XC16版本。



      以下为原文

    Your description is a bit sloppy. Still it is not clear, which GB110 based project you have used.
If you have problems with compiler output, better add some of the output (using code tags !)
 
You are still using quite old MpLabX and also MLA v2015_08_10 is a bit old. 

The MLA v2016_08_08  sample cdc-basic builds without errors (out of the box) e.g. for exp16_pic24fj256gb110.
You can also try pic24f_starter_kit.x, which uses pic24fj256gb106.
 
The current MLA v2016_11_07 again seems to have introduced some problems with include paths for u*** framework, e.g. u***.h
Microchip changed the layout of the samples and includes again and again, likely the sample is broken in that version.
 
If you are experimenting with the GB612 family, you should updated MpLabX and MLA anyway.
And you even should check your XC16 version.

制作[ 1 ]：进入目录'C/:MPEBAXHEX/MPLABXPROST/UBVV.x'-FB-NBjtudio/Maun-Fiel-Deult.MK-Dist/Deult/UsBVv.x.Puth.xOutStudio（2）：从C:/Script文件（x86）/Microchip /MPLAB C30/bin /bin中加入目录：C//VIGNESHE/MPLABXPROST/UBVV.X.In文件…//…/Suffelal24F/Pic24FyPLIb.h：44，从UBMeN.C：/程序文件（x86）/Microchip /MPLAB C30/bin /….. /支持/外围设备24F/DMA。H：953:2：警告：“在这个目标上不建立”文件中包含从C//程序文件（X86）/ Microchip /MPLAB C30/bin / bin /…/支持/ PyPHEraly24F/Pic24FyPLIB。h：45，来自UBMeN.C：/程序文件（X86）/Microchip /MPLAB／BIN／BI/..…/Suffelal240F/DPSLP。H:137:2：警告：“C”/程序文件（X86）/Microchip /MPLAB C30/BIN／BI/…/Suffelal24F/PIC24FYPL中包含的文件“不建立在这个目标上”。iB.H：46，从UBMeN.C：/程序文件（x86）/Microchip /MPLAB／BIN／BI/..…/Suffelal24F/ECRC。H:399：2：警告：“不在这个目标上建立”文件中包含的来自C/:程序文件（X86）/Microchip /MPLAB C30/BIN／BI..…/Suffelal24F/PIC24FYPLIB。H：47，来自于UBMA。在C中：8：C/MPLA/MPLAB／30BI/BI/B/..…/Suffelal24F/EMP. H：1201:2：警告：“不建立在这个目标上”的文件包含在从UbMeN. C：15：…//..…/Microchip /ML/V2012-04-03/Microchip /包含/USB /UBSHOST。h：111:6：错误：应用程序必须出错。定义UBSImPrimalVBuSUBLASH为OTG的主机100或8mA。在文件中包含从UbMeN. C：15：…//..…/Microchip / MLA/V2012-04-03/Microchip /包含/USB /UBSHOST。h：329：“UBBEAGEL”…///…/Microchip /MLA/V2012-04-03/Microchip /包含/USB /UBSHOST之前的语法错误。H：1423：ERRo:在VBestEvest.UbMeun.C中的语法错误：在函数“主”中：警告：控件到达非虚函数的结尾。主体：C：24：错误：“UBSUpApple EngestEnEnter and EnBulEngEng:C：24：语法错误：在AdvestsUbMeun.C：25：警告：RET之前的语法错误：RETURN类型默认为“UnbUpBestEngult:”函数：UbMeNealEvestHANDELL：：错误：“事件”未声明（在这个函数中首次使用）：UbMe.C：26：错误（每个未声明的标识符仅在OncUsBbMe.C：26：错误：对于它出现的每个函数）。VBuSRealEdvestPosie'未声明（第一次使用此函数）UbMe.c：30：错误：“EnvivVBuxRelaseE.POWER”未声明（在该函数中首次使用）：EbMeun.C：31：错误：“EnvithHubAtNo附着”未声明（在该函数中首次使用）：UbMeun.C：32：错误：“EnvithUnService Type”未声明（第一次使用在T中）他的函数“UbMeun.C：33：错误：“EnvivAnNoNoToNo.Read”未被声明（第一次使用此函数）：UbMn.c：34：错误：“EnvithCclipTyInTyOrror”未声明（在这个函数中首次使用）：UbMeun.C：35：错误：“EnvithOutux的“内存”未声明（在这个函数中首次使用）：UbMeun. C：36：错误：EndothUnSPECiFiEdError“未声明（第一次使用此函数）UbMeun.C：37：错误：“true”未声明（第一次使用此函数）UbMeun.C：41：错误：“EnvithCdcNo附着”未声明（在该函数中首次使用）：UbMeun. C：42：“EndojCCDCNONE”未声明（第一次使用此函数）UbMeun. C：43：错误：EVuntCdC.CuxRead做了“未声明（第一次使用此函数）UbMn.c：44：错误：‘EnvivCdCyCuMrWrdErgEndo'（第一次使用此函数）UbMeun.C：45：错误：‘EnvithCdCdDATA.Read’doRun'未声明（第一次使用此函数）UbMeun.C：46：错误：‘EnvithCdCdDaAdWrWeWr.Error’未声明”（在这个函数中的第一次使用）：UbMeun.C：47：“EnvivCdcCyRead”未声明（在这个函数中首次使用）：UbMn.c：48：错误：“EnvithCdcNaKiTimeOUT”未声明（在该函数中首次使用）：UbMeun.C：警告：隐式声明函数“AppHythCdBaseCeVeEnEdLeLeR'UbMeun.C：49：错误：A”dWrave'未声明（第一次使用此函数）UbMe.c：49：错误：“数据”在这个函数中（第一次使用此函数）：UbMe.C：49：错误：“大小”未声明（在这个函数中首次使用）：UbMeun.C：56：错误：“false”未声明（在这个函数中首次使用）：UbMeun.C：58：警告：控件到达非终结符-虚函数（2）：*[B:\程序文件（x86） Microchip MPLAB C30bin PIC30GCC .exe“-G-OMF = ELF-X-C-C-MCPU＝24FJ256GB106- FNO短双壁”-I.//..…./..…程序文件（X86）/Microchip /XC16/V1.26/ICOR/LEGA-C“-MMD -MF构建/默认/产品ON/UBMNE.O.D.Ong/Deult/Ung/UbMeN.O.BbMeN.C NbPosi/MaFaMeCurrime.MK：106：目标“Buff/Deule/Studio/UbMeNe.O.FrimeDeD[[ 1 ] ]：***[Buffic CONF]错误2的配方



      以下为原文

    make[1]: Entering directory 'C:/Users/vigneshed/MPLABXProjects/USBvv.X'
make -f nbproject/Makefile-default.mk dist/default/production/USBvv.X.production.hex
make[2]: Entering directory 'C:/Users/vigneshed/MPLABXProjects/USBvv.X'
In file included from c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/PIC24F_plib.h:44,
from u***main.c:8:
c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/dma.h:953:2: warning: #warning "Does not build on this target"
In file included from c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/PIC24F_plib.h:45,
from u***main.c:8:
c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/dpslp.h:137:2: warning: #warning "Does not build on this target"
In file included from c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/PIC24F_plib.h:46,
from u***main.c:8:
c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/ecrc.h:399:2: warning: #warning "Does not build on this target"
In file included from c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/PIC24F_plib.h:47,
from u***main.c:8:
c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/epmp.h:1201:2: warning: #warning "Does not build on this target"
In file included from u***main.c:15:
../../../../Microchip/mla/v2012-04-03/Microchip/Include/USB/u***_host.h:111:6: error: #error The application must define USB_INITIAL_VBUS_CURRENT as 100 mA for Host or 8-100 mA for OTG.
In file included from u***main.c:15:
../../../../Microchip/mla/v2012-04-03/Microchip/Include/USB/u***_host.h:329: error: syntax error before 'USB_EVENT'
../../../../Microchip/mla/v2012-04-03/Microchip/Include/USB/u***_host.h:1423: error: syntax error before 'vbusEvent'
u***main.c: In function 'main':
u***main.c:23: warning: control reaches end of non-void function
u***main.c: At top level:
u***main.c:24: error: syntax error before 'USB_ApplicationEventHandler'
u***main.c:24: error: syntax error before 'address'
u***main.c:25: warning: return type defaults to 'int'
u***main.c: In function 'USB_ApplicationEventHandler':
u***main.c:26: error: 'event' undeclared (first use in this function)
u***main.c:26: error: (Each undeclared identifier is reported only once
u***main.c:26: error: for each function it appears in.)
u***main.c:29: error: 'EVENT_VBUS_REQUEST_POWER' undeclared (first use in this function)
u***main.c:30: error: 'EVENT_VBUS_RELEASE_POWER' undeclared (first use in this function)
u***main.c:31: error: 'EVENT_HUB_ATTACH' undeclared (first use in this function)
u***main.c:32: error: 'EVENT_UNSUPPORTED_DEVICE' undeclared (first use in this function)
u***main.c:33: error: 'EVENT_CANNOT_ENUMERATE' undeclared (first use in this function)
u***main.c:34: error: 'EVENT_CLIENT_INIT_ERROR' undeclared (first use in this function)
u***main.c:35: error: 'EVENT_OUT_OF_MEMORY' undeclared (first use in this function)
u***main.c:36: error: 'EVENT_UNSPECIFIED_ERROR' undeclared (first use in this function)
u***main.c:37: error: 'true' undeclared (first use in this function)
u***main.c:41: error: 'EVENT_CDC_ATTACH' undeclared (first use in this function)
u***main.c:42: error: 'EVENT_CDC_NONE' undeclared (first use in this function)
u***main.c:43: error: 'EVENT_CDC_COMM_READ_DONE' undeclared (first use in this function)
u***main.c:44: error: 'EVENT_CDC_COMM_WRITE_DONE' undeclared (first use in this function)
u***main.c:45: error: 'EVENT_CDC_DATA_READ_DONE' undeclared (first use in this function)
u***main.c:46: error: 'EVENT_CDC_DATA_WRITE_DONE' undeclared (first use in this function)
u***main.c:47: error: 'EVENT_CDC_RESET' undeclared (first use in this function)
u***main.c:48: error: 'EVENT_CDC_NAK_TIMEOUT' undeclared (first use in this function)
u***main.c:49: warning: implicit declaration of function 'APP_HostCDCBasicEventHandler'
u***main.c:49: error: 'address' undeclared (first use in this function)
u***main.c:49: error: 'data' undeclared (first use in this function)
u***main.c:49: error: 'size' undeclared (first use in this function)
u***main.c:56: error: 'false' undeclared (first use in this function)
u***main.c:58: warning: control reaches end of non-void function
make[2]: *** [build/default/production/u***main.o] Error 1
"C:Program Files (x86)MicrochipMPLAB C30binpic30-gcc.exe" -g -omf=elf -x c -c -mcpu=24FJ256GB106 -fno-short-double -Wall "-I../../../../Program Files (x86)/Microchip/xc16/v1.26/include/lega-c" -MMD -MF build/default/production/u***main.o.d -o build/default/production/u***main.o u***main.c
nbproject/Makefile-default.mk:106: recipe for target 'build/default/production/u***main.o' failed
make[1]: *** [.build-conf] Error 2

请使用伊恩在这里描述的代码标签：HTTP://www. McCHIP.COM/FUMMS/FUNDSPE/77101



      以下为原文

    Please use code tags as Ian describes here http://www.microchip.com/forums/FindPost/777101

2周后，您只需在没有代码标签的情况下粘贴输出。你没有花时间评论上一篇文章。你希望我们做什么？您不使用演示项目或简单的副本，显然您使用的是您自己的项目，我们不知道。如果确实如此，这与粘贴的输出没有关系。您没有回答您使用过的CDC基础样本的哪个项目/平台。但这表明你走错了路。你的GB110或GB106都没有一个DMA外围设备，你也没有意识到你有一个完全错误的目标设备。我猜你甚至没有清晰地区分你自己的线程：HTTP://www. McCHIP.COM/FUMMS/M981201.ASPXI认为你搞乱了你的项目文件和配置，没有。用你愿意投资的信息和时间来支持这一点。更具体和冗长或不可能给予任何支持。



      以下为原文

   
 
After 2 weeks you just paste your output without any comment, without code tags. You did not take the time to comment on the previous post. What do you expect us to do ?
 

 
You are NOT using a demo project or a simple copy, you are obviously using a project of your own, which we don't know. If you do did, this has nothing to do with your pasted output.
 
You did not answer which project / platform for the cdc basic sample you have used. But this

from u***main.c:8:
c:/program files (x86)/microchip/mplab c30/bin/bin/../../support/peripheral_24F/dma.h:953:2: warning: #warning "Does not build on this target"

indicates that you are on the wrong way. Neither your GB110 or GB106 has a DMA peripheral, nor do you realize that you have a completely wrong target device.
My guess is you are not even cleanly distinguishing between your own threads:
http://www.microchip.com/forums/m981201.aspx
 
I think you messed up your project files and configuration, no way to support that with the information and time you are willing to invest.
 
Be more specific and verbose or it is not possible to give any support.
 
 
 
 
 

也许你想写PIC24FJ512GB606代替。



      以下为原文

   
May be you wanted to write pic24fj512gb606 instead.

对不起，所有的，& lt；/p & gt；& p & gt；任何一个程序都能为实现USB主机CDC（WHIC是我试图连接PC超终端）与PIC24F与C30和MLA V2012-04-03提供程序。我为PIC24FJ256GB106编辑了硬件和振荡器，并成功编译成功。但是，如果试图用USB插入USB，它甚至不响应任何错误。USB主机栈仍在运行。我只是把它的LED指示。它没有检测到我的PIC。我应该插入任何驱动代码在我的代码或与PC或编辑INF文件，如VID PID.但我只是使用默认的VID PID。



      以下为原文

    sorry all,

could any one give procedure for implementing u*** host cdc(whic is i trying to connect with pc hyper terminal) with pic24f with c30 and mla v2012-04-03. i edited hardware things and oscillator for my pic24fj256gb106 and compiled it successfully. but if try to plugin the u*** with pc.it doesn,t response even any error. u*** host stack still running. i just put an led indication with it.its not detect my pic u***.should i insert any driver code in my code or with pc or edit inf file for it.like vid pid.but i just use default vid pid.

是否可以在不使用MLA库的情况下在PIC24F中实现USB主机CDC？



      以下为原文

    is that possible to implement u*** host cdc in pic24f without using MLA library? 

当然，是的，但这需要相当长的时间，实际上这是不需要的。



      以下为原文

   


Well, of course yes, but it will take quite some time and actually it's not needed...

对于PIC24J256GB106的MPLAX IDE版本和MLA版本和编译器版本的匹配，我完全感到困惑。我的使用是MPLAB X IDE V3.10和MLA 2012-04-03和XC 16编译器。可以吗？或者我应该在这个列表中改变一些东西。真正的事情是，我需要实现这些结构，包括包含目录和INF文件编辑的文件。（读取线程很多）都是18F。



      以下为原文

    i m totally confused about matching of versions of mplab x ide and MLA version and compiler version for the pic24j256gb106.
my usage was mplab x ide v3.10 and MLA 2012-04-03 and xc 16 compiler for this pic. is that ok or should i change some thing in this list. real thing is that i need structure of implementing those thing like including files in include directories and inf file editing.(read lot of threads) all was about 18f.

为什么要使用一个5岁的MLA？“匹配”版本，例如，简单地使用当前版本的MPLABX（3.55），MLA（2017年3月）和XC16（1.31）；如果有的话，支持更有可能为当前版本。不清楚你想说什么。一些结构已经由MLA示例（例如，USB，主机CDC BASIC）给出，MPLAB允许您根据需要构造任何东西。到目前为止，我的印象是，您不应该尝试这样做。



      以下为原文

   
Why do you want to use a 5 year old MLA ? A "matching" version e.g. is simply using current versions of MpLabX (3.55), MLA (March 2017) and XC16 (1.31);  and if any, support is more likely for current versions.

Not clear what you want to say. Some structure is already given by MLA example (e.g USB, Host CDC Basic), and MpLab allows you to structure anything as you want.

My impression so far is that you defnitely should not try that.
 
 

主机CDC BASIC和设备CDC基本构建在EX1616PIC24FJ256GB110（XC16 1.31）的MLA V2017111107中没有错误



      以下为原文

   
 
Both host CDC-basic and device CDC basic build again without errors in MLA v2017_11_07 for exp16_pic24fj256gb110  (xc16 1.31)
 

谢谢罗迪姆。现在我把MLA版本改为2013。是的，应该升级。PC将其检测为未知设备。我的PIC作为设备。



      以下为原文

    thanks rodims. now i done it with changing my MLA version to 2013. yes it should be upgrade. pc detected it as unknown device. my pic act as device.

你应该决定你是否需要CDC作为主机或设备，这有区别。以前你说的是“主机”，现在你说“设备”。MLA V20170306 USB设备CDC的基本工作原理与Exp16PIC24FJ256GB110很好。



      以下为原文

   
 
You should decide whether you need CDC as Host or Device, this makes a difference. Previously you were talking about 'host', now you say 'device'.
The MLA v20170306 sample USB Device CDC Basic works fine with the exp16_pic24fj256gb110.

是的，我两个都说。我试图连接PIC与PC。首先，我把PIC作为主机，所以PC不承认。然后我尝试PIC作为设备。现在PC承认它作为未知设备。你能说如何修改USB设备CDC基础工程与Exp1616PIC24FJ256GB110到PIC24FJ256GB106？我知道如何在MPLAB中配置文件。我需要在没有.O对象文件错误的情况下创建它。制作（2）：*[Bug/PIC24FJ256GB106/生产/Ext/ 1682852123 /系统.O]错误255Nbjtudio/MaMeCop-PIC24FJ256GB106. MK：78：目标''.构建CONF '的配方.



      以下为原文

    yes i say that both. i tried to connect pic with pc.first i put pic as host so pc doesnt recognized.then i tried pic as device.now pc recognized it as unknown device.could you say how to modify that USB Device CDC Basic works fine with the exp16_pic24fj256gb110 to pic24fj256gb106? i know upto how to configure in mplab and including files. i need to create it without .o object file error.
 
make[2]: *** [build/PIC24FJ256GB106/production/_ext/1682852123/system.o] Error 255
nbproject/Makefile-PIC24FJ256GB106.mk:78: recipe for target '.build-conf' failed

注意，我们目前使用的是完全不同的MLA版本和MPLABX版本（我猜）。MLA V2013仍然是4年。将处理器从GB110改为GB106不超过3次点击。选择Project属性，在组合框中将“设备”改为PIC。该平台Exp16Pic24FJ256GB110意味着这是Microchip Explorer 16板，具有用于GB110的PIM。对于GB106，您将看到LababTITE、TrISabIt和TrISD13等的编译错误，但这只是一个症状，您需要将这些部分调整到平台（嵌入式板）上。您的任务是，您需要修改（或替代）LED和按钮的代码部分，使其在某种程度上对您的平台有意义。BTW。您所显示的错误消息没有多大帮助。您将隐藏在LIN之上的真实错误消息。正如已经说过的，您还可以从MLA的另一个示例开始，该示例已经是基于GB106的。你仍然需要用LED和按钮来调整零件。



      以下为原文

    Beware that we are currently using quite different MLA versions and MpLabX versions (I guess).  MLA v2013 is still 4 years old.
Changing the processor from GB110 to GB106 is no more than 3 clicks.
Choose project properties and in the combo box change the 'device' to your PIC.
 
The platform exp16_pic24fj256gb110 means that this is the Microchip Explorer 16 Board with a PIM for GB110 . 
If you compile that for a GB106 you will see compiler errors for LATAbits, TRISAbits and TRISD13 etc.  But this is only a symptom, you need to adjust these parts to your platform (embedded board) anyway. The task for you is that you need to modify (or substitute) the code portions for LED and Button so that it somehow makes sense for YOUR platform.
 
Btw. your shown error message is not much helpful. You are hiding the real error message(s) somewhere above that line.
 
edit: as already said, you can also start with another sample from the MLA, which is already GB106 based.  Still you need to adjust the parts with the LEDs and Buttons

感谢罗迪姆斯，现在了解如何改变目标设备。我还有一个查询，我不能在我的项目中添加一个源文件。它显示源文件夹是只读的。（我只是复制和编辑演示主机CDC项目）。这是我的设备端描述符。主机如何识别我的设备。从主机端检查设备地址。设备地址是什么？这是主机侧，



      以下为原文

    const USB_DEVICE_DESCRIPTOR device_dsc=
{
    0x12, // Size of this descriptor in bytes
    USB_DESCRIPTOR_DEVICE, // DEVICE descriptor type
    0x0200, // USB Spec Release Number in BCD format
    CDC_DEVICE, // Class Code
    0x00, // Subclass code
    0x00, // Protocol code
    USB_EP0_BUFF_SIZE, // Max packet size for EP0, see u***_config.h
    my vid, // Vendor ID
    my pid, // Product ID: CDC RS-232 Emulation Demo
    0x0100, // Device release number in BCD format
    0x01, // Manufacturer string index
    0x02, // Product string index
    0x00, // Device serial number string index
    0x01 // Number of possible configurations
};
thanks rodims, now understood how to change the target device. i have an another query that i couldnt add an source file in my project.it shows source folder is read only.(i just copy and editing the demo host cdc project). and this is my device side descriptor.how does the host will identify my device. from host side its checking the address of device.what is the address of device.
this is host side,
bool USBHostCDC_ApiDeviceDetect( void )
{
    USBHostTasks();
    USBHostCDCTasks();

    if ((USBHostCDCDeviceStatus(CDCdeviceAddress) == USB_CDC_NORMAL_RUNNING) &&
        (CDCdeviceAddress != 0))
    {
        return true;
    }

    return false;
}

使用代码标签是一个很好的开始。你切换了一次更多的项目，现在回到“主机”CDC BASIC？你需要决定你到底想做什么。我想，你从来没有提到过。你不应该改变USB相关的代码和描述符，直到CDC基本演示程序工作。现在还保持你的PID，VID的手指。你必须开始工作的东西，否则你会迷路。只读：然后使它可以写或复制到别处。在MLA安装过程中，你选择了“只读位置”吗？这不是个好主意。您不仅要更改源文件，还将使用编译器、链接器创建输出文件…



      以下为原文

    Using code tags is a good start.
 
You switched one time more your projects, now back to 'host' cdc basic ?
You need to decide what you actually want to do. You did never mention that, I think.
 
You should not change the USB relevant code and descriptors until the CDC basic demo works.
Also keep you fingers of the PID, VID for now.
You must start with something that works, otherwise you will get lost.
 
Read only:  then make it writeable or copy it elsewhere. Did you choose a 'read only location' during MLA Setup  ? Would not be a good idea. You do not only want to change source files, you also will create output files with the compiler, linker ...