PSoC Creator 2.0有什么问题？

我的用户名不包含任何非ASCII字符…我使用的是Windows XP 2002 SP3。我不认为这会引起问题，对吧？
另外，这个问题发生在所有PSoC创建者2项目中。所有的项目文件夹都分配在C:\…那么，我也不认为这是个问题…我不知道还能做什么…
当做



以下为原文
My user name does not contain any non ASCII character... I am using Windows XP 2002 SP3. I don't think that this may cause the problem, right?
Plus, that issue happens with all the PSoC Creator 2.0 Projects. All the Project folders are allocated in C:\.... Then, I don't think that's the problem either... I don't know what else can I do...
Regards

什么是名称的用户路径的系统使用的是你吗？
C：用户名称…？
检查一下！我有点不确定。
鲍勃



以下为原文
What is the name of the user-path the system is using for YOU?
C:UsersName..... ?
Check that! there IS something unusual I'm quite sure

Bob

具体的名称是“C:DEUTEST”。这些名称是我的项目名称。我在C中创建了一个新的项目，没有什么。与PSoC Creator 1没有问题…
谢谢。



以下为原文
The specific name is "C:Deugtest". These name is my Project name. I've created a new project with these name in C: and nothing. With PSoC Creator 1.0 no problems...
Thanks.

这个问题与项目所在的地方（路径）无关。当错误发生时，我们还没有发现哪个文件被访问，但我怀疑它只是一个临时文件，它总是位于C:用户…等等。
那么，Windows为您使用哪条路径？请检查一下。
鲍勃



以下为原文
The issue has NOTHING to do with the place (path) where the project is. We did not yet find out which file is accessed when the error occurs, but I suspect that it is only a temporare file which always is located under c:users... and so on.
So again, which path is windows using for you? check that please.
Bob

嗨，鲍伯，
路径是“c:文档和设置管理者”。我不太确定这是不是你的意思…
当做



以下为原文
Hi Bob,
The path is "C:Documents and SettingsAdministrador". I'm not quite sure if that's what you mean...
Regards

嘘！我想我可以帮你摆脱困境！我建议你用这些信息创建一个案例。我也为我的问题，我花了一个星期和几个冗长的电话来自印度，他们努力帮助我。
最后的尝试：你在XP的管理员（你显然）创建一个新用户（“TestUser”是一个合适的名字），尝试从帐户运行的创造者2。对我来说有帮助。
鲍勃



以下为原文
Sh**! I thought I could help you out of this! I suggest that you create a case with those informations. I did it for my issue, it took a week and a couple of lenthy phone-calls from India and they tried hard to help me out.
Last try for you: Under xp as Administrator (that you obviously are) create a new user ("TestUser" is a proper name) and try to run Creator 2 from that account. For me it helped.
Bob

嗨，你好！
我刚刚创建了一个名为“test”的新用户。我会通知技术支持这一点。不管怎样，谢谢你的帮助和建议。
当做。



以下为原文
Hi again,
I've just create a new user with the name "Test" and nothing. I will inform the technical support about this. Anyway thank's for your help and advices.
Regards.

向技术人员致以节日问候！
鲍勃



以下为原文
Seasons greetings to the technical stuff!
Bob

嗨，我有几个客户在西班牙有这个问题。至少在这里，问题是因为Windows是西班牙语，有几个文件夹以西班牙语（系统文件夹）的名称，所以，你有“配置ACNN本地”（注意重音），而不是“本地配置”。其中一个客户解决了安装虚拟机和安装W7（以及Win XP在其他版本）中的问题。但是这个解决方案是“Pauluz”（BoTCH？）奇怪的是，在所有版本的创建者1（BETAS和发行版）中，这个问题没有出现。



以下为原文
Hi,
I've several customers with this problem in Spain. At least here, the problem comes because windows is in spanish and there are several folders with name in spanish (system folders), so, you have "configuración local" (pay attention in the accent) instead of "local configuration".
One of the customer resolved the problem mounting a virtual machine and installing W7 (and Win XP in other) with the english version. But this solution is a "chapuza" (botch ?).
Curiously, with all version of Creator 1 (betas and release) this problem didn't appear

我很抱歉，我从来没有看到这个帖子去年看起来你们没有工作的调试器（在2.0）一会儿。我讨厌这样！
我们没有看到系统的问题调试的PSoC 5创造2的共同点似乎是你在Windows非英语设置运行。我们明确地检查这些配置工作作为你的释放过程的一部分，所以这是我担心的。我会在内部跟进此事。
一个有趣的现象是，这个问题不需要重音字符将在工程路径。我们需要看看所有的调试器使用的文件，而不只是那些在你的项目中。
对不起，我没有一颗银弹…
--马克。



以下为原文
I am sorry that I never saw this thread last year - it looks like you guys have not had a working debugger (on 2.0) for a while. I hate that!

We do not see systemic problems with debugging on PSoC 5 in Creator 2.0 and the common denominator appears to be that you are running on non-English setups of Windows. We explicitly check that those configurations work as part of your release process and so that is a worry for me. I'll follow up internally on that.

One interesting observation is that the issue does not require the accented characters to be in the project path. We need to look at all the files that the debugger uses, not just those in your project.

Sorry I do not have a silver bullet...
-- Mark.

忘了提另外一件事了，鲍伯…
沙一，不再支持PSoC 3沙一段，这是一个非常早期的硅片上，只有一个很小的客户所看到的。
PSOC 5 ES1仍然被支持。当然，如果你新买的包或芯片，我们会向您发送生产零件。
--马克。



以下为原文
Forgot to mention one other thing, Bob...
The ES1 that is no longer support is PSoC 3ES1, which was a very early piece of silicon that only a very small set of customers ever saw.
PSoC 5ES1 is still supported. Of course, if you buy new kits or chips we'll send you production parts.
-- Mark.

谢谢你的ESX提示！我真的希望ToaVeMy处理器模块在Creator的下一个版本发布之前交换。尽管如此，“特殊字符bug”并不容易规避一些“异形”Windows安装，并有一个单独的PC与美国。Windows会有帮助，但看起来有点过火了。
鲍勃



以下为原文
Thank you for the ESx hint! I really hope to have my processor module(s) exchanged before the next release of Creator comes out. Nonetheless, the "Special character bug" is not easy to circumvent for some "alien" windows installations and to have a separate PC with a US. Windows would help, but looks a bit overdone.

Bob

我也有一些问题，使用新的创造者进行调试。但是没有时间去检查。需要先和老创造者一起完成一些事情。



以下为原文
I have some problem using the new creator for debugging as well. But didn't have time to check it. Need to finish a few things with the old creator first.

在造物主2我项目安装是由于更新替换模块最新毁了。
一个新的项目无法编译，因为bootldr有错版。听起来像是一个四夜之夜…
鲍勃



以下为原文
After de-installation of Creator 2.0 my Project was ruined due to the updater which replaced the modules with the newest.
A new project couldn't compile, because the bootldr had a wrong version. Sounds like a fourtnight holydays...

Bob

鲍勃，
你能张贴你的设计吗？我来看看。
谢谢，
宋帕克



以下为原文
Bob,
Can you post your design? I'll take a look at it.
Thanks,
Sung Pak

你没有完全理解我：这是任何设计，甚至没有一个模块。调试器退出上述错误消息。
我有一个截止日期在星期一上午（9:00小时UTC + 1）
想，我会立案的
快乐的压力
鲍勃



以下为原文
You did not understand me quite right: It is ANY design, even without a module. Debugger exits with the above errormessage.
I have a deadline on monday morning (9:00h utc+1)
Think, I'll gonna file a case...
Happy stressing
Bob

鲍勃，
psoccreator应该自动创建“*在“备份”文件夹备份您的项目。cydsn”。所以，你不应该重做任何你以前的工作环境。
我不确定调试问题。Sung Pak是那个对的人，看来他正在调查已经。
CKF



以下为原文
Bob,

PSoC Creator should have automatically created a backup of your project in the "backup" folder in "*.cydsn". So, you should not have to redo anything in your previous working environment.

I am not sure about the debugging issue. Sung Pak is the right person for that, and it appears he is investigating already.

-CKF

我切换到C造作1（SP2），这是大量的DE和重新安装，现在我可以再次访问项目。唷！！！！
可能我的KoSo1处理器的PSoC5模块太旧了。可以吗？
鲍勃



以下为原文
I switched, back to Creator 1 (SP2) which was a lot of de- and re-installing and now I can access the projects again. Phew!!!
Probably my PSoC5 processor module for the kit001 is too old. Can that be?

Bob

我不认为这是硅问题。我假设你使用的是CY8C5688 AXI-60。这同样适用于创建者V2Y0。项目成立于creator_v2_0不会工作在1_0。使它工作，你需要把备份的1_0项目和开放。



以下为原文
I don't think its an issue with silicon. I assume you are using CY8C5588AXI-60. The same should work for creator v2_0. Also project which was opened in Creator_v2_0 will not work in 1_0. To make it work, you need take up the backed-up project and open in 1_0.