实时调试器/hiwave.exe：运行多个实例？
我有几个 Freescale 68HCS08 MCU 连接在 I2C 网络中，运行不同的程序。当我单击“调试”时，Codewarrior 会检查 hiwave.exe 的运行实例来加载和调试程序。我想同时调试两者，这意味着运行两个实例。
最好的方法是什么？我需要两台电脑吗？尝试使用“构建”命令而不是在 Codewarrior 中进行“调试”来手动重新加载 MCU 是否更好？
I have a couple Freescale 68HCS08 MCUs connected in an I2C network, running different programs. When I click "debug," Codewarrior checks for a running instance of hiwave.exe to load and debug the program. I'd like to debug both simultaneously, which means having two instances running.
What is the best way to do this? Do I need two PC's? Is it better to try and manually reload the MCU's, using the Build command instead of Debug in Codewarrior?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我可以手动运行两个 hiwave.exe 实例，然后使用“文件”->“加载应用程序”菜单项选择 .abs 文件。尽管我目前使用的是全芯片模拟而不是硬件调试器，但似乎两个实例都运行良好，包括代码显示和断点。我猜这就是最有趣的地方，确保每个实例都使用正确的调试器，特别是如果您使用两个相同的 USB 设备。
“这太简单了”，我能听到你说。好吧，采用选项 2：
我在“Windows XP 模式”（在 Windows 7 下运行的虚拟 PC）中执行所有 CodeWarrior / Hiwave 操作，主要是因为 CodeWarrior 的安装程序不能在 64 位架构上运行（或者它没有运行在 64 位架构上）几个月前，我为此在他们的论坛上对他们大喊大叫）。
我不完全确定许可技术细节（如果您有 Windows 7 专业版，您应该至少获得一个免费许可证来使用 Windows XP 模式），但也许您可以做类似的事情 - 例如，使用一个运行虚拟 PC 环境的调试器传递到虚拟系统（Windows Virtual PC 和其他虚拟化环境允许您传递 USB 设备），并使其他调试器仍然连接到“主机”系统。然后，您可以在虚拟系统和主机系统上安装 CodeWarrior/Hiwave，其中一个控制系统 A，另一个控制系统 B。USB 乐趣仍然适用，因为您必须确保“正确”的 USB 调试器是传递到虚拟系统。
I can run two instances of hiwave.exe manually, and then use the "File"->"Load Application" menu item to select the .abs file. It seems to run both instances fine, including code display and breakpoints, although I'm using full-chip simulation rather than a hardware debugger at the moment. I would guess that's where most of the fun is, in making sure that each instance uses the correct debugger, especially if you're using two of the same USB devices.
"That's too easy", I can hear you saying. Fine, take option 2:
I do all my CodeWarrior / Hiwave stuff in "Windows XP Mode", a Virtual PC running under Windows 7, mostly because CodeWarrior's installer doesn't run on 64-bit architectures (or it didn't a few months ago, for which I yelled at them in their forums).
I'm not entirely sure of the licensing technicalities (if you have Windows 7 pro, you should get at least one free license to use the Windows XP mode), but perhaps you could do something similar - e.g. run a Virtual PC environment with one of your debuggers passed through to the virtual system (Windows Virtual PC and other virtualization environments let you pass USB devices through), and have your other debugger still attached to the 'host' system. You could then have CodeWarrior/Hiwave installed on both the virtual and host systems, with one controlling system A and the other controlling system B. USB fun-time still applies, as you'd have to make sure the 'correct' USB debugger was passed through to the virtual system.
调试器 HIWAVE.EXE 无法在 Windows XP 模式、VMWARE WORKSTATION 等虚拟机或 Linux 中可用的任何虚拟机中工作。这与 USB MULTILINK 驱动程序的架构方式有关。
通过修补安装程序，使 Codewarrior v6.x 在 Windows 7 中运行很容易。
我们无法让调试 Pod 来调试实时硬件，因为 USB 驱动程序是使用 Jungo Windriver 实现的，并且根据其他文章，两个虚拟机都无法将其推送到虚拟环境中。
我花了几个月的时间试图解决这个问题，最后我们恢复了旧的 XP 许可证并安装了 XP。但可以肯定地说，这一点，再加上飞思卡尔缺乏允许人们运行 Linux 进行芯片开发的远见，迫使我决定不再使用他们的产品。
但是，可以运行调试器的多个实例。最大好像是20左右
The debugger, HIWAVE.EXE will not work in either Windows XP mode, nor VMs such as VMWARE WORKSTATION, nor any of the VMs available in Linux. This is to do with the way the driver for the USB MULTILINK has been architecured.
Making Codewarrior v6.x work in Windows 7 is easy, by patching the installer.
We were not able to get the debugging pod to work to debug live hardware, because of the fact that the USB driver is implemented with Jungo Windriver, and, as per other articles, neither of the virtual machines can push that across into the virtual environment.
I have wasted months trying to solve this, in the end we resurrected old XP licenses and installed XP. However safe to say that, this, combined with Freescale's lack of vision to allow people running Linux to develop for the silicon, forced me into a decision that I will no longer use their products.
However, running multiple instances of the debugger is possible. The maximum seems to be around 20