完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我想在我的项目中添加AppIO。它失败了。AppIO系统根本不起作用。它甚至不允许SysSoSoeleSimult.c编译。下面的函数更改会修复编译问题。BUF的演员做得不正确。之后,Appo仍然不起作用。这是关于和谐2Y02Y100B和MPLABX 3.51和XC32 1.42i开始与USB鼠标演示。并遵循了“简单”调试指令中的热点!解决:在MPLAB X IDISSIZEZT SysSconSoeleRead(const SysMuleEndex index index,int fd,Vult*Buf,SiZeStt计数){sisixt NUMLUTB=0;dBGET((char *)BUF,128);同时(*(char *)(BUF)+NUBEnter);= LynPiFor){NuthByth++;}返回计数;}
以上来自于百度翻译 以下为原文 I'm trying to add APPIO to my project. It fails. The APPIO system doesn't work at all. It does not even allow the sys_console_static.c to compile. The function change below fixes the compile problem. the cast of buf was done incorrectly. After that APPIO still doesn't work. This is on hARMony 2_02_00b and MPLABX 3.51 and XC32 1.42 I started with the USB mouse demo. and followed the "simple" debug instructions in the Hot!Solved: The ABSOLUTE simplest way to set up a AppIO Console Debug Session in MPLAB X IDE ssize_t SYS_CONSOLE_Read(const SYS_MODULE_INDEX index, int fd, void *buf, size_t count ) { size_t numBytes = 0; DBGETS ((char*)buf, 128); while ( *((char *)(buf) + numBytes) != LINE_FEED ) { numBytes++; } return count; } |
|
相关推荐
13个回答
|
|
哦,修复这个问题后,AppIO菜单项就变灰了。
以上来自于百度翻译 以下为原文 OH, the issue after fixing this is that the APPIO menu item is greyed out. |
|
|
|
为什么这个函数返回它的一个参数?当然,返回NUMBULL会更有用。
以上来自于百度翻译 以下为原文 Why on earth is that function returning one of its parameters? Surely it would be more useful to return numBytes. |
|
|
|
这一个怎么样:我猜他们一段时间重写了部分内容,没有测试其余的构建选项。只是在样例应用程序中使用的那些选项。
以上来自于百度翻译 以下为原文 How about this one: ssize_t SYS_CONSOLE_Read(const SYS_MODULE_INDEX index, int fd, void *buf, size_t count ) { return numBytes; } I guess they rewrote part of it a while back and did not test the rest of the build options. Just the ones used in the Sample Applications. |
|
|
|
我假设“计数”是指所提供的缓冲区的大小,在这种情况下,这条线应该是
以上来自于百度翻译 以下为原文 I'm assuming "count" is meant to be the size of the supplied buffer, in which case, this line DBGETS ((char*)buf, 128); should have been DBGETS ((char*)buf, count); |
|
|
|
我不知道它是怎么做的…我现在知道的是,调试工作是一个问题,它会影响调试器的目的……你知道,它不应该这么难。应该有一个盒子,你点击打开Prtf到你选择的UART。这些东西有足够的,你可以运行足够快,它应该是足够的。
以上来自于百度翻译 以下为原文 I have no idea what it even does... all i know right now is that getting debugging working is a problem, which kind of defeats the purpose of the debugger.... You know, it shouldn't be this hard. there should just be a box that you click to turn on printf to the UART of your choice. These things have enough of them and you can run them fast enough that it really should be sufficient. |
|
|
|
对于许多PIC Appo不支持:(快速和DryPrimTf到您的选择UART(或其他端口)=提供您自己的One MunthPutc())ValueMun-Putc(char cByb)/重定向STDUT到UART {//REF:http://MychIpDePosich/COX/XC32:重定向STDUT(DRVIUASARTI TimeBuffReSISLULL(UartHandle)){/*Walth*/}//等到空间(阻塞)DrviUsARTHARDIGETELL字节(UARthHANDLE,CBOLL);/ /直接输出数据到EUDIAG}建议写入到一个环缓冲器,然后将RUN缓冲器转储到UART空间可用,否则阻塞输出会阻塞系统。铃声缓冲区大小取决于你打印多少。保罗
以上来自于百度翻译 以下为原文 For many PIC APPIO isn't supported :( Quick and dirty printf to UART (or other port) of your choice == supply your own _mon_putc() void _mon_putc(char cByte)//Redirect STDOUT to UART { // Ref: http://microchipdeveloper.com/xc32:redirect-stdout while(DRV_USART_TransmitBufferIsFull(UartHandle)){/*wait*/} //Wait Till Space (Blocking) DRV_USART_WriteByte(UartHandle, cByte); //Direct Output Data to EuDiag } Recommend writing to a ringbuffer, then dump ringbuffer to uart as space available, otherwise blocking output can block up system. ringbuffer size depends on just how much you printf. Paul |
|
|
|
我确认,在2H03B函数中,SysSoSoeleRead函数错误地返回了其中一个参数而不是“NUMB”。它在更新之后中断了我的代码。不得不花上几个小时试图弄清出了什么问题。
以上来自于百度翻译 以下为原文 I confirm that in Harmony 2_03b function SYS_CONSOLE_Read incorrectly returns one of its arguments instead of 'numBytes'. It broke my code after the update. Had to spend few hours trying to figure out what was wrong. |
|
|
|
感谢寻找和张贴-我已经进入了一个错误报告反对这一点。
以上来自于百度翻译 以下为原文 Thanks for finding and posting - I have entered a bug report against this. |
|
|
|
一年前我报道过。在这里,通过一张支持票。
以上来自于百度翻译 以下为原文 I reported it a year ago. On here and via a support ticket. |
|
|
|
一年前我报道过。在这里,通过一张支持票。我的心和你们这些人一样,他们做了大量的努力来帮助Microchip改善和谐。不幸的是,支持看起来像是一个完全没有任何其他东西的黑洞。
以上来自于百度翻译 以下为原文 I reported it a year ago. On here and via a support ticket. My heart goes out to people like you who have made a substantial and extended effort to help Microchip improve Harmony. Unfortunately support seems to be like a black hole totally unconnected from anything else. |
|
|
|
在这一点上,我很想投入时间来报告一个和谐的错误。巴甫洛夫灭绝试验相当成功。
以上来自于百度翻译 以下为原文 At this Point I am leery about investing the time to report a Harmony Bug. The Pavlovian Extinction trials have been quite successful. |
|
|
|
你能试试和声V2.03B吗?我猜想在V2.03B中报告的编译问题不存在。
以上来自于百度翻译 以下为原文 Can you try harmony v2.03b i guess the compilation issue reported is not there in v2.03b |
|
|
|
我编写了自己的调试库。它不需要包括任何额外的和声库。只需要USAT。我可以在运行时为每一个任务设置调试级别,恰好达到我想要的级别。如果有需要,调试通过以太网到可配置服务器。所以我可以在现场的设备上进行远程调试。用简单的定义,一切都消失了。Nick
以上来自于百度翻译 以下为原文 I wrote my own debugging library. It doesn't have to include any extra Harmony libraries. Only needs USART. I can set the debug level for each and every task during runtime exactly to the level I want. And if there is need, debugging goes over ethernet to a configurable server. So I can do remote debugging on a device out in the field. And with a simple #define, all is gone. Nick |
|
|
|
只有小组成员才能发言,加入小组>>
5244 浏览 9 评论
2035 浏览 8 评论
1955 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3214 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2261 浏览 5 评论
779浏览 1评论
673浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
599浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
683浏览 0评论
580浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-25 20:06 , Processed in 1.822373 second(s), Total 105, Slave 88 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号