矩阵键盘和数码管实现简易计算器，但是在烧录后只能显示第一次按下的数字，后边就没反应了不知道是哪里写作了求大神帮忙看看#include#include#define uchar unsigned char#define uint unsigned int***it duan=P2^6;***it wei=P2^7;uchar temp;uchar codetable[]={0x3f,0x06,0x5b,0x4f,0x66,0x6d,0x7d,0x07,0x7f,0x6f};uchar code weima[]={0xff,0xfe,0xfd,0xfb,0xf7,0xef,0xdf}; voiddisplay(unsigned long a);uchar keyscan(); void delay(uint xms);void main() {unsigned long num1=0,num2=0,dispbuf=0;unsignedchar key,flag=1,fuhao;while(1){if(flag==1){key=keyscan(); if(key
2016-12-23 12:32
HALO，我在应用程序中使用GRC将位图转换成bin。这很好。现在我想把字体转换成bin。没有机会。每次从Java模块中获取长错误消息。我使用Java 8更新66。我发现GRC应用程序相当旧，不能用于Java版本高于6的信息。现在我的问题是：有没有任何一个字体与GRC应用程序的命令行转换？哪个Java版本？谢谢你
2019-09-26 06:06
我在Linux下使用MPLAB X 4.05，并尝试创建一个“用户MaFIX文件”项目进行一些测试。然而，MPLAB似乎完全忽略了我在Makefile属性中输入的构建命令，而只是默认为“make”或“make.”。启动调试生成也似乎只运行“使”，没有进一步的参数，不管我输入什么作为构建命令。旧版本的MPLAB也做同样的事情。从命令行手动运行与同一个Mag文件一样运行，这是怎么回事？我假设能够以这种方式指定我喜欢的任何构建命令。这个项目类型完全崩溃了还是我遗漏了什么？这是非常不可用的，因为调试构建是不可能的。
2020-03-13 10:47
所有的，在过去的4个月里，我一直在努力使PIC32 MZEFX版本与DAC芯片接口，并使音频工作正常。使用MaqAddioOHiHiRes示例，我们中的几个人试图找出为什么在I2S DMA ISR中称为SycCrrCh的过程。这个过程被称为2000次关闭，然后迫使SPI模块关闭，然后迫使SS线（LRCK，Word时钟，无论你想调用它）到0或1取决于采样率。首先，ISR与I2S馈送不同步，因此在ISR SE中随机地强制该状态。疯狂，真的不需要。其次，评论似乎表明，有一个启动问题的SS线和正确的极性关于正确引用左或右通道。评论说，更好的是，但2000似乎疯狂。此外，无论是PIC32 MX270和PIC32 MX470产品，我开发，从来没有任何问题的字时钟线，我们有超过100K的产品在该领域。同样，对于所有寄存器的比特指定是相同的，因此我只能猜测在PIC32 MZ中这个模块的IP是相同的。当然，我们都知道，SPI模块之外的一些东西会影响到这一点，因此会引起一个误报。沮丧的是，我采用了蓝牙开发板和PIC32 MZ2048 EF专用PIM，并进行了一些测试。真的，如果你把采样率设置为选中的，然后连续流，McAyAddiooHiSiRes工作得很好。问题是，除了iTunes以外的任何应用程序都不会改变采样率，而是将歌曲的速率重新调整到音频MIDI中所选的速率，问题真正开始了。使用比特完美、Audirva、AAMRA、Roon、J河甚至一些DoW SOF。TWALE改变采样率以匹配轨道的采样率，下面的问题将发生：嗡嗡无音频，嗡嗡启动，然后同步到帧，然后音频，根本没有音频，最后应用程序崩溃和重新启动。在飞行中的变化，并设置和保持这种方式。任何一个做过任何类型的音频的人都知道这不是真的。所以我正试图挽救这个产品，并且很快就要把PIC32 MZ（奴隶）从DAC（Master）中赶走，但是我认为从选择和帧同步控制（参见SPI/I2S模块框图中的图1）被打破和R。同样的问题也会反过来发生。但我稍后再给你答复。我的另一个问题是…在31位-gt；24中有框架细节，并强迫这些可能的帮助修正这个尚未被发现的勘误表吗？谢谢，戈登 以上来自于百度翻译 以下为原文 All,For the last 4 months I have been trying to get the PIC32MZ EFx versions to interface to a DAC chip and get audio to work correctly. Using the mac_audio_hi_res example there were several of us trying to figure out why there was this procedure in the I2S DMA ISR called syncLRClock. This procedure called 2000 times then turned off was forcing the SPI module off then forcing the SS line (LRCLK, word clock what ever you want to call it) to either a 0 or a 1 depending on sample rate. First the ISR is not synchronous with the I2S feed so forcing this state randomly during an ISR seemed crazy and really not required. Secondly the comments seemed to indicate that there was a startup problem with the SS line and correct polarity with regard to correctly referencing the Left or Right channel. The comments said more is better, but 2000 seems crazy. Furthermore with both the PIC32MX270 and PIC32MX470 products that I developed, never was there any problem with the word clock line and we have over 100K products in the field. Also the bit designations for all the registers are identical and therefore I can only guess that the IP for this module in the PIC32MZ is the same. Of course we all know that something outside of the SPI module can be effecting this and therefore an errata can be caused. Frustrated I took the Bluetooth development board and the PIC32MZ2048EF specialized PIM and did some testing. Really if you set the sample rate to anything selected and then stream continuously the mac_audio_hi_res worked pretty well. The problem is using any application other than iTunes which does not change the sample rate on the fly, but which resamples the rate of the song to the selected rate in Audio Midi, the problems really started to mount. Using Bit Perfect, Audirvana, Amarra, Roon, J River and even some of the DAW software which changes sample rates to match the sample rate of the track the following problems would happen: Buzz-no audio, Buzz start then sync to frames then audio, no audio at all and finally the application crashes and restarts. Asking corporate about this they assumed that the sample rate never changes on the fly and is set and stays that way. Well anyone who has done audio of any kind knows that is not true. So I am trying to salvage this product and will be trying to drive the PIC32MZ (SLAVE) from the DAC (MASTER) soon, but I think the Slave Select and Frame Sync Control (see Figure 1 in the SPI/I2S module block diagram) is broken and really the same problem is going to happen in reverse. But I will get back to you later. My other question is this... There is framing details in bits 31->24 and would forcing these possible help fix this errata that has not been discovered yet? Thanks,Gordon
2018-09-12 14:45
