ST意法半导体
直播中

盛文凤

7年用户 171经验值
私信 关注
[问答]

Windows 7下的STVD工作非常慢

嗨,


我是一名项目工程师。我在项目中使用ST7,STM8作为微控制器。我使用COSMIC作为编译器。我使用STVD和STVP。

我没有任何问题吗?在Win XP下使用这些程序。但是?有很多与STVD和STVP相关的问题(My O.S:Win7 Professional和Home Prem。)

1.当我打开工作时或从正常模式转到调试模式时,我丢失了菜单栏。其他sembols失败了。而且?失去了我的工作......以及类似的问题。

2. STVD工作非常非常慢....特别是,从正常模式到调试模式的时间过程...

3.在调试模式下,?不能把断点放在有效线上!我收到一条失败的消息!

4.在调试模式下;程序计数器流口水。因此我无法关注我的源代码。调试器可以使用一些有效的行。

请帮帮我......我需要你的意见并解决......

我的项目停止了这个问题

金枪鱼

#stvd #cosmic #stvp#win-7#menu-bar #crash

以上来自于谷歌翻译


以下为原文




Hi,


I am a project engineer. I use ST7,STM8 as microcontroller in my projects. And i use COSMIC as a complier. And i use STVD and STVP.

I had not any problem while ? was using these programs under Win XP. But ? have a lot of problem related STVD and STVP( My O.S : Win7 Professional and Home Prem.)

1.    I loss menu bar when i open worksapce or when pass from normal mode to debug mode. And other sembols fail. And ? loss my worksapce...And similar problems.

2.    STVD is working  ver very very slowwww....Especially, at time pass from normal mode to debug mode...

3.    In debug mode, ? can not put breakpoint on valid line !!! I take a fail message!

4.    In debug mode; program counter drool.Therefore i can not follow my source code. Some valid lines are skiped by debugger.  

Please help me... I need your comments and solves...

My projects stoped related this problem

TUNA
  
#stvd #cosmic #stvp #win-7 #menu-bar #crash

回帖(7)

黄锐

2018-9-19 17:47:35
我们也看到了Win7-Pro的问题。我们的解决方案是安装XP-Virtual机器,我相信它可以免费从微软获得。在XP-Virtual机器中安装STVD,STVP和COSMIC。适合我们(到目前为止)。
 
 
 JDF

以上来自于谷歌翻译


以下为原文





We've seen issues with Win7-Pro too.  Our solution is to install the XP-Virtual machine which is available fro microsoft at no charge I believe.  Install STVD, STVP and COSMIC in the XP-Virtual machine.  Works well for us (So far).


jdf
举报

朱燕媚

2018-9-19 17:53:20
我在使用Windows 7 Enterprise时遇到了完全相同的问题。在虚拟WinXP机器上安装STVD对我不起作用,因为COSMIC编译器不允许在虚拟机中运行Dongle许可证。
 
 
 重新安装不能解决问题。有人有解决方案吗?是不是有更多的人有这个问题?

以上来自于谷歌翻译


以下为原文





I have exactly the same problems using Windows 7 Enterprise. Installing STVD on a virtual WinXP Machine doesn't work for me as the COSMIC compiler doesn't allow the Dongle license running in a virtual machine.


Reinstall doesn't fix the problem. Does anybody have a solution yet? Isn't there more people with this problem??
举报

任斌

2018-9-19 18:01:35
我的ST7(DVP3)仿真器在Windows 7上根本无法工作,我在Win 7上遇到过与STM8 dev类似的问题。
 
 
你将永远等待ST的修复。
 
 我最终把事情掌握在自己手中并使我的新PC双启动WIN 7 / Win XP - 问题解决了。

以上来自于谷歌翻译


以下为原文





My ST7 (DVP3) emulator won't work at all on Windows 7 and I have seen similar problems with STM8 dev on Win 7.


You will wait forever for a fix from ST.

I eventually took matters into my own hands and made my new PC dual boot WIN 7 / Win XP - problem solved.
举报

朱燕媚

2018-9-19 18:16:51
我终于得到了一个答案来支持STVD的奇怪行为(缺少菜单,缺少工作空间等......)
 
 
 
这个问题与我们在STVD中使用的图形库有关,有时也是如此
 
 
 
 
 无法重新定位用户可配置的项目(工具栏,窗口,菜单...),何时
 
 切换工作区(或从编辑模式切换到调试模式,反之亦然)。
 
 
 
 它已经存在于旧版本的STVD中;不幸的是更新了库
 
 没有解决问题。我只有退出这种糟糕状态的解决方法,还有一些
 
 有关降低再次进入风险的建议:
 
 
 
 1.问题发生后,退出STVD并删除* .wdb和* .wed文件。应该有一个
 
 项目名称为root的文件对,以及带有“默认”根的一对文件。
 
 [有关信息,wed文件包含编辑模式下的用户设置:已打开文件列表,
 
 工具栏和窗户的位置,......; wdb文件包含完全相同的信息但在
 
 调试模式]。它们将由STVD再次创建。
 
 
 
 2.之后,第一次打开现有工作区时,请转到:
 
 ''工具 - 选项 - 工具栏''并点击''全部重置''。开始后重复该操作
 
 debug(第一次会影响wed文件,第二次会影响wdb文件)。
 
 如果使用不同的工作区,尽可能保留相同的工具栏列表
 
 他们(不要忘记''默认''一个,这是没有加载工作空间时使用的那个)
 
 =>我们的想法是尽可能使工具栏重新定位
 
 
 
 3.一旦在所有编辑/调试模式下所有使用的工作空间都达到稳定状态,
 
 问题不应该发生。但不幸的是,只要打开1个损坏的工作区,
 
 它可能会在同一STVD会话中打开的所有工作区上传输问题...

以上来自于谷歌翻译


以下为原文





I finally received an Answer from support for the strange behaviour of STVD (missing menu, missing workspace, etc...)



this issue is linked with the graphical library we are using in STVD, which sometimes





fails in re-positioning user-configurable items (toolbars, windows, menus …), when

switching workspaces (or switching from edit mode to debug mode and conversely).



It was already present in old versions of STVD; unfortunately updating the library did

not solve the issue. I only have a workaround for exiting this bad state, and some

recommendations for reducing the risk entering it again:



1. after the issue, quit STVD and remove *.wdb and *.wed files. There should be one

pair of files with the project name root, and one pair of files with the ''default'' root.

[for information, wed file contains the user settings in edition mode: list of opened files,

position of toolbars and windows, …; wdb file contains quite same information but in

debug mode]. They will be created again by STVD.



2. afterwards, when opening an existing workspace for the first time, go to:

''Tools-Options-Toolbars'' and click ''Reset All''. Repeat the operation after having started

debug (the first time will affect the wed file, the second one the wdb file).

As much as possible, if using different workspaces, keep the same toolbar list in all of

them (don't forget the ''default'' one, which is the one used when no workspace is loaded)

=> the idea is to make the easiest as possible the toolbar re-positioning



3. once a stable state has been reached on all used workspaces in all edit/debug modes, the

problem should not occur. But unfortunately as long as 1 corrupted workspace is opened,

it may transmit the issue on all workspaces opened in the same STVD session …
举报

更多回帖

发帖
×
20
完善资料,
赚取积分