完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
在导入了一些库文件时,他们正在进行更改。代码中有很多预处理器指令,并且不时地(但不是总是),MPLAB突然决定像它们是注释一样开始将它们变灰。语法似乎很好,但任意地。MPLAB对大量代码进行了筛选。例如,有很多这样的片段:在其中的一些中,最后一个“γ-Endif,}”和它后面的大部分代码都是灰色的。PS我想上传一个JPEG截图显示错误,但让人害怕:你没有权限访问“http://www. McCys.com /论坛/上载.ASPX?”在这个服务器上。参考文献18.B4357A5C.14955.222.2D6E61AD。
以上来自于百度翻译 以下为原文 Having imported a number of library files am going through them making changes. There are quite a lot of preprocessor directives in the code and, from time to time (but not always), MPLAB suddenly decides to start greying them out as if they were comments. The syntax seems to be fine but arbitrarily MPLAB greys out chunks of code. For example there are a number of segments like this: in SOME of them the final "#endif, }" and much of the code that follows it is greyed out. static sint8 p_nm_read_block(uint32 u32Addr, uint8 *puBuf, uint16 u16Sz) { #ifdef CONF_WINC_USE_UART return nm_uart_read_block(u32Addr,puBuf,u16Sz); #elif defined (CONF_WINC_USE_SPI) return nm_spi_read_block(u32Addr,puBuf,u16Sz); #elif defined (CONF_WINC_USE_I2C) return nm_i2c_read_block(u32Addr,puBuf,u16Sz); #else #error "Plesae define bus usage" #endif } How do I go about sorting this out? ps I wanted to upload a JPEG screenshot showing the errors but get the dreaded: You don't have permission to access "http://www.microchip.com/forums/upload.aspx?" on this server. Reference #18.b4357a5c.1495557222.2d6e61ad |
|
相关推荐
9个回答
|
|
什么版本的MPLABX?重新启动MPLABXFAIL吗?
以上来自于百度翻译 以下为原文 What Version of MplabX? does restarting MplabX help? |
|
|
|
产品版本:MPLAB X IDE V3.61Java:1.8 0121;Java热点(TM)64位服务器VM 25.121-B13RunTime:Java(TM)SE运行时环境1.80Y121-B13Stase:Mac OS X版本1012.5运行在X8664上;UTF-8;EnEnEN(MPLAB)
以上来自于百度翻译 以下为原文 Restarting doesn't do it. Product Version: MPLAB X IDE v3.61 Java: 1.8.0_121; Java HotSpot(TM) 64-Bit Server VM 25.121-b13 Runtime: Java(TM) SE Runtime Environment 1.8.0_121-b13 System: Mac OS X version 10.12.5 running on x86_64; UTF-8; en_EN (mplab) |
|
|
|
不知道你在看什么,但是你知道它是一个不活动的部分(如果……)的特征。是“灰色”(像评论)?这影响了C源代码,但也嵌套了γIFS…在这种情况下,它是一个特性,而不是bug。在打开项目时,分析器可能需要一些时间才能显示编辑器中当前活动文件的更新。您可以尝试发布PNG而不是JPG。这应该更小。
以上来自于百度翻译 以下为原文 Not sure what you are seeing, but you are aware that it is a feature that inactive parts (per #if ... ) are 'grayed out' (like comments) ? This affects C-source code, but also nested #ifs ... In this case it is a feature, not a bug. When opening a project the parser may need some time before the display of a currently active file in the editor is updated. You could try to post a PNG instead of JPG. That should be smaller. |
|
|
|
|
|
|
|
这看起来像是一个bug(我以前从来没有见过)。如果我尝试过这个问题,那么我也会遇到和你一样的问题,即最后一个词根会被灰色化,而它应该是之前应该被灰色化的线。NB,语法分析器也强调了介于π介子前面的α错误线。看来你很容易。如果用Apple PrimaMasaGeId::lt代替记录:MPLABX 3.61、Windows 10、X64和GT,则删除奇数行为;
以上来自于百度翻译 以下为原文 That looks like a bug (which I never saw before). If I try the same // #define AA // #define BB #if (defined AA) && (defined BB) #error "only one type of interrupt" #endif #if !((defined AA) || (defined BB)) #error "no interrupt defined" #endif then I have the same problem as you, i.e. the last #endif will be grayed out, while it should be the line before which should be grayed out . Nb that the parser also underlines the #error line before the #endif. It seems you can easily remove the odd behaviour if you substitute #error with #pragma message edit: < for the records: MpLabX 3.61, Windows 10, x64> |
|
|
|
伟大的东西@ Roimss替换“错误”的消息“与”Apple PrimaGCC警告“消息”很巧妙。可能也会在3年前工作过!-我是否要用Microchip冲刷论坛的MPLABX漏洞,这将被拾起?
以上来自于百度翻译 以下为原文 Great stuff @rodims replacing #error "message" with #pragma GCC warning "message" does the trick nicely. Probably would have worked 3hrs ago too! ;-) Do I take it Microchip scour the forum for MPLABX bugs and this will be picked up? |
|
|
|
嗨,MPLAB X将尝试读取和使用那些知道它在哪里找到的包含文件,并解释它所熟知的预处理器条件,并尝试向你展示它所理解的。注意,MPLAB不使用与真正编译器相同的预处理器搜索列表。文件在MPLAB中被引入头文件,它通常会变得更好。在编译完成后,编辑器扫描似乎被更新,并且可能会变得更好。在MPLAB的各种版本中,PrimCAN中出现了许多奇怪的效果,似乎逐渐变得更好。
以上来自于百度翻译 以下为原文 Hi, MPLAB X will try to read and use those #include files that it know where to find, and interpret preprocessor conditionals as best it know, and try to show you what it understand. Note, that MPLAB do not use preprocessor search lists quite the same way as the real compiler. If the relevant #include files are introduced as header files in MPLAB, it usually get better. After a compilation have been completed, the editor scan seem to be updated, and may get better. There have been many strange effects in the prescan in various versions of MPLAB, it seem to get better gradually. |
|
|
|
我认为MPLABX的可能性很高,它会被Microchip所注意到,但是你有时只能知道它是否被开发出来。如果它对你有浓厚的兴趣,你可以提出一个支持票。
以上来自于百度翻译 以下为原文 I think for MpLabX the probability is high that it will get noticed by Microchip, but you only sometimes get to know whether it is forwared to development. If it is of strong interest for you, you could raise a support ticket. |
|
|
|
此外,如果这只是IDE中的一个红色的虚线,那么它也是一个“错误”,它出现在IDE语法分析器中。我确信(但不确定)微芯片知道这个“bug”,但仍然没有任何东西被修复。如果编译器有问题,那么你就有一个问题——但是从你所说的到目前为止,只有编辑器(IDE)指出了什么是错误的。苏珊
以上来自于百度翻译 以下为原文 Also,if this is only a red squiggly line within the IDE, then it is also a "bug" that as been present in the IDE parser for eons. I'm sure (but not certain) that Microchip are aware of this "bug" but still nothing has been fixed. If the compiler has an issue then you have a problem - but from what you have said so far it is only the editor (in the IDE) that indicates something is wrong. Susan |
|
|
|
只有小组成员才能发言,加入小组>>
5242 浏览 9 评论
2031 浏览 8 评论
1955 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3207 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2256 浏览 5 评论
778浏览 1评论
669浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
597浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
679浏览 0评论
577浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-24 03:47 , Processed in 1.409614 second(s), Total 62, Slave 55 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号