them engage in 2-way communication based on what they send each other. Currently, I have one cypress
2018-10-29 11:31
亲爱的大家，我的问题是如何通过LVDS将ADC AFE 5804 12位http://www.ti.com/product/afe5804连接到Spartan 3E入门套件。首先，我想模拟知道ADC和FPGA之间的数据传输方式。有人可以帮帮我吗？非常感谢！以上来自于谷歌翻译以下为原文Dear all,My problem is how can i connecting ADC AFE 5804 12 bit http://www.ti.com/product/afe5804 to Spartan 3E starter kit by LVDS. First i want to simulate to know how data transfer between ADC and FPGA. anyone can help me?Many thanks!
2019-07-10 08:19
我最近购买了STM32F767ZIT6 Nucleo套件，以及X-Nucleo-IKS01A2 MEMS扩展板。我安装了Unicleo-GUI，并下载了X-CUBE-MEMS1软件。我无法弄清楚如何让固件在主板上运行。我将几个.bin文件放到了适当的位置（虽然Projects / Multi / Applications目录中的所有文件夹似乎只有STM32F401RE-Nucleo，STM32L152RE-Nucleo和STM32L476RG-Nucleo的文件夹......）。当我点击“Program”时，电路板上的LED会循环，但当程序进入“等待固件响应”部分时，它永远不会得到响应。 我不关心我甚至运行什么固件，我只是想看看Unicleo GUI与我的电路板对话。现在我所拥有的只是“固件描述：未知”。以上来自于谷歌翻译以下为原文I have recently purchased an STM32F767ZIT6 Nucleo kit, as well as an X-Nucleo-IKS01A2 MEMS expansion board. I installed Unicleo-GUI, and downloaded the X-CUBE-MEMS1 software. I can't figure out how to get firmware to run on the board though. I dropped a couple of .bin files into the appropriate location (although all of the folders in the Projects/Multi/Applications directory seem to only have folders for STM32F401RE-Nucleo, STM32L152RE-Nucleo, and STM32L476RG-Nucleo...). When I click on "Program", the LEDs on the board cycle, but when the program gets to the "Waiting for firmware response" section, it never gets a response. I don't care what firmware I even run, I'd just like to see the Unicleo GUI talk to my board. Right now all I have is "Firmware Description: Unknown".
2019-02-26 07:46
嗨，有人可以帮助编写以下框图的VHDL代码吗？我为信号处理设计了框图并测量了时间。在图中，我已经为每个块提供了我想要做的事情。谢谢！以上来自于谷歌翻译以下为原文Hi, Can someone help to write VHDL code for the following block diagram? I have designed the block diagram for my signal processing and to measure the time.In the diagram, I have given the cooments for each block what I want to do. Thank you!
2019-02-12 06:07
cant understand how to engage 2nd Capture using CCP2 Module.MCU Used -pic18F4520/* * File: main.c
2018-11-23 15:17
你好，AVS应用程序支持SDK 6吗？如果是，它位于哪里，以及如何测试它？谢谢 以上来自于百度翻译 以下为原文Hello,is the AVS application supported with SDK 6.0 ?if yes, where is it located, and how to test it ? thanks
2018-11-30 16:15
investigate and verify this, that would be greatly appreciated. Otherwise, I would need to engage
2018-11-09 09:59
您好，我想使用一对E1437A ADC进行高达8 MHz的频谱分析，并可选择显示交叉频谱。由于我有限的VEE经验，这看起来像是一项艰巨的任务，特别是因为我还不熟悉VXI乐器。我可以从哪些程序模块开始？即使是E1437A的波形采集也会非常有用。谢谢，阿德里安 以上来自于谷歌翻译 以下为原文Hello, i would like to use a pair of E1437A ADC's for spectrum analysis up to 8 MHz, with the option to display cross spectrum.Due to my limited VEE experience, that looks like a massive task, especially as I'm not yet familiar with VXI instruments. Are there any program modules available that I could start from? Even waveform acquisition for the E1437A would be very helpful. Thanks, Adrian
2018-10-10 17:12
我正在使用以下组件在客户处设置新的POC设置：•VMware ESXi 6.5•XenApp 7.14.1•Nvidia Tesla M10•Windows Server 2016 当从Igel Linux瘦客户端连接到已发布的桌面时，我们会体验到附件中的行为。会话运行正常，但我们没有看到整个屏幕。这有时会发生在Windows客户端，但几秒后似乎发生刷新，整个屏幕变得可见。 这种情况发生在较低（1280 * 1024）和更高分辨率的单显示器和多显示器设置上。解决方法/故障排除：如果我们重新启动XenApp服务器，则第一个会话成功。从第二次会议开始，我们遇到了这个问题。如果我们使用传统图形模式而不是默认的Thinwire模式，我们就不会遇到此问题。但是，这不是最佳的。如果我禁用Microsoft RDS GPO设置“为所有远程桌面服务会话使用硬件默认图形适配器”，则不会发生此问题。但是，加速浏览器需要此设置。堆栈信息：•硬件o Dell PowerEdge R730o Nvidia Tesla M10，M10-8A型材•虚拟机管理程序o GRID版本4.3：367.106o ESXi 6.5.0,5310538•VMo GRID版本4.3：370.12o GRID版本4.1：369.71也经过测试（因为类似的kb：http：//nvidia.custhelp.com/app/answers/detail/a_id/4273/~/nvidia-grid-vgpu-%E2%80%93-corruptions ％2Fblack屏％2Fincorrect- 小鼠行为常常）o Windows Server 2016操作系统，完全修补o XenApp 7.14.1•客户端o Igel UD5-LX-50co固件测试：5.11.200.01＆amp; 5.10.240o接收器测试：12.1.8,13.3.2,13.4.2以上来自于谷歌翻译以下为原文I’m setting up a new POC setup at a customer using the following components:•VMware ESXi 6.5•XenApp 7.14.1•Nvidia Tesla M10•Windows Server 2016 When connecting from an Igel Linux thinclient towards the Published Desktop we experience the behavior in the attachment. The session is running fine, but we don’t see the entire screen.This sometimes happens from a Windows client, but a refresh seems to happen after a few seconds and the entire screen becomes visible. This is happening on lower (1280*1024) and higher resolutions, single and multi-monitor setup.Workarounds/troubleshooting:If we reboot the XenApp server, the first session is successful. Starting from the second session, we experience the issue. If we use Legacy Graphics Mode instead of the default Thinwire mode, we don’t experience this issue. However, this is not optimal. If I disable the Microsoft RDS GPO setting "Use the hardware default graphics adapter for all Remote Desktop Services sessions", the issue does not occur. However, this setting is needed for accelerating browsers. Stack information:•HardwareoDell PowerEdge R730oNvidia Tesla M10, M10-8A profiles•HypervisoroGRID version 4.3: 367.106oESXi 6.5.0, 5310538•VMoGRID version 4.3: 370.12oGRID version 4.1: 369.71 also tested (because of similar kb: http://nvidia.custhelp.com/app/answers/detail/a_id/4273/~/nvidia-grid-vgpu-%E2%80%93-corruptions%2Fblack-screen%2Fincorrect-mouse-behaviour-often) oWindows Server 2016 OS, fully patchedoXenApp 7.14.1•ClientoIgel UD5-LX-50coFirmware tested: 5.11.200.01 & 5.10.240oReceivers tested: 12.1.8,13.3.2,13.4.2
2018-09-25 17:32
嗨，我正在寻找新的思路和方法来调试这个问题。我的问题是，当我擦除设备内存时，0x4000以上的显示为0x00。我使用的是引导加载程序：这是一个生存在0x000中的引导加载程序。0x07FF和接收命令通过USB / HID擦除/写入/读取闪存与加密。我已经使用了多年，它一直工作良好，但我的代码已经很小，所以它符合内存在0x0800…0x3FFrangang.现在我发现，我不能在0x4000…0x7FFF范围内编程内存，以调查擦除设备并读出整个闪存。0x4000以下的内存读取为0xFF，高于0x00。显然这暗示了一些代码保护功能正在插入。HooBootloader代码是这样的：引导表读取保护，并且我已经验证了.HEX文件在这方面看起来是正确的（为清晰而增加了空间）。我发现特别令人困惑的是，正如我们所看到的，所有的CpPN、WRTn、EBTRN位都是相同配置的，而YETI可以对0、1、但不是2、3块进行编程。我已经看过芯片，它是40引脚DIP PIC18F45 K50，所以它确实应该有32 K闪存，除非有假芯片周围；所以我失去了什么检查下一步或试图找出更多的事情正在进行。这可能是愚蠢的，我会觉得真正的白痴没有发现它，但他再也不去了…… 以上来自于百度翻译 以下为原文 Hi, I'm searching for fresh ideas and ways to debug this. My problem is that when I erase the device memory above 0x4000 appears as 0x00. I'm using the bootloader from here: This is a bootloader that lives in 0x0000 .. 0x07FF and receivescommands via USB/HID to erase/write/read Flash with encryption.I've been using this for years and it has been working fine, butmy code has been small so it has fit the memory in the 0x0800 ... 0x3FFFrange. Now I've discovered that I cannot program the memory in the range 0x4000..0x7FFF. To investigate I erase the device and read out the entire Flash.Memory below 0x4000 reads out as 0xFF and above as 0x00.Obviously this suggest that some of the code protection functionalityis kicking in. My config (in the bootloader code) is like this:CONFIG CP0 = OFF ; Code Protect CONFIG CP1 = ON CONFIG CP2 = ON CONFIG CP3 = ON CONFIG CPB = ON ; Boot Sect Code Protect CONFIG CPD = OFF ; EEPROM Data Protect CONFIG WRT0 = OFF ; Table Write Protect CONFIG WRT1 = OFF CONFIG WRT2 = OFF CONFIG WRT3 = OFF CONFIG WRTB = ON ; Boot Table Write Protest CONFIG WRTC = ON ; CONFIG Write Protect CONFIG WRTD = OFF ; EEPROM Write Protect CONFIG EBTR0 = OFF ; Ext Table Read Protect CONFIG EBTR1 = OFF CONFIG EBTR2 = OFF CONFIG EBTR3 = OFF CONFIG EBTRB = ON Boot Table Read Protectand I've verified that the .hex file looks correct in thatrespect (added space for clarity) :02 0000 04 0030 CA:01 0008 00 00 F7:01 0009 00 80 76:01 000A 00 0F E6:01 000B 00 80 74:01 000C 00 0F E4 What I find especially confusing is that as can be seen all theCPn,WRTn,EBTRn bit as configuredidentically and yetI can program blocks 0,1 but not 2,3.And I've looked at the chip and it is 40 pin DIP PIC18F45K50so it really should have 32k Flash, unless there are counterfeit chips around ;) So I'm at loss what to check next or try to find out morewhat is going on. This is probably something silly and I'll feel a real idiotfor not spotting it but here goes nothing... wbr Kusti
2019-03-22 07:54
