完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我已经使用“最小”设置存档了PSoC创建者4.1项目,以便创建我需要的最小数量的文件来创建Git存储库。然后打开归档的ZIP文件,并将顶级目录及其整个内容复制到单独的目录中。在那个新目录中,我删除了包含“输出HEX文件”的路径“.CORTEXM0ARMGGCGY54”版本。我还删除了路径“.EngigabySoalsPSoC4”,其中包含了所有生成的源代码。然后我打开了这个新的项目,清理并建立了代码。然后我把原来的英特尔HEX文件与新的HEX文件进行比较,发现这2个文件有很大的不同。
因此,我再次启动存档文件,并将整个内容复制到另一个新目录。在这个新目录中,我再次删除了包含“输出HEX文件”的路径“.CORTEXM0ARMGGCGY54”版本。但是现在,我所做的是删除路径“.Eng衍abySoalsPSoC4”中的所有文件,这些文件包含了所有生成的源代码,但我没有删除路径(空目录)。GealDePySoalsPSoC4“仍然存在”。然后我打开了这个新的项目,清理并建立了代码。然后我把原来的英特尔HEX文件与新的HEX文件进行比较,发现这2个文件是相同的。 有人能解释一下吗?由于我们的项目最终将成为FDA的医疗设备,我们需要能够复制英特尔HEX文件。 注意:我没有触摸任何默认的项目设置。 以上来自于百度翻译 以下为原文 I have archived a PSOC Creator 4.1 project using the "Minimal" setting in order to create the minimal amount of files that I need to create a GIT repository. I then opened the archived zip file and copied the top level directory and its entire contents to a separate directory. In that new directory, I deleted the path ".CortexM0ARM_GCC_541Release" which contains the output hex file. I also deleted the path ".Generated_SourcePSoC4" which contains all of the generated source code. I then opened up this new project and clean and built the code. I then compared the original Intel hex file to the new hex file and discovered that the 2 files are significantly different. So I started again with the archive file and copied the entire contents to another new directory. In this new directory, I again deleted the path ".CortexM0ARM_GCC_541Release" which contains the output hex file. But now, what I did was delete all of the files in the path ".Generated_SourcePSoC4" which contains all of the generated source code but i did NOT delete the path (an empty directory ".Generated_SourcePSoC4" still exists). I then opened up this new project and clean and built the code. I then compared the original Intel hex file to the new hex file and discovered that the 2 files are IDENTICAL. Can someone explain. Since our project will eventually become an FDA medical device, we need to be able to identically reproduce the Intel Hex file NOTE: I did not touch any of the default project settings. |
|
相关推荐
6个回答
|
|
你能比较生成的文件(在存档和生成的文件之间)吗?另外,您是否正在调试模式下构建?如果是这样,则调试信息可以具有对项目路径或时间戳的引用。
以上来自于百度翻译 以下为原文 Can you compare the generated files (between your archive and what generated)? Also, are you building in debug mode? If so, the debug information could have references to the project paths, or time-stamps) |
|
|
|
lxhzx 发表于 2018-12-19 20:26 我已经为发布配置和调试配置建立了代码,结果也一样。如果HEX文件(即任何链接库或对象文件)中都有日期/时间戳或项目路径信息,我会感到震惊,但谁知道呢。 鉴于上面的测试条件在我的第一篇文章中,我已经做了一些进一步的调查,看起来只要删除了“生成的源”路径并重新构建,CyPRJ文件就发生了巨大的变化。 以上来自于百度翻译 以下为原文 I've built the code for the Release Configuration and the Debug Configuration with the same results. I would be shocked if the hex files (i.e. any linked library or object files) would have date/time stamps or project path info in them, but who knows. Given the above the test condition in my first post, I've done some further investigation and it seems as soon as one deletes the "generated source" path and rebuilds, the .cyprj file changes dramatically. |
|
|
|
你好,
根据亨德里克的建议,请对对应于两个不同的HEX文件的派生源目录进行不同的处理。这可能有助于调试这个问题。 谢谢 Jobin燃气轮机 以上来自于百度翻译 以下为原文 Hi, As per Hendrik's suggestion, please do a diff of the Generated_Source directories corresponding to the two different hex files. That might help in debugging the issue. Thanks Jobin GT |
|
|
|
只是比较了生成的源目录(用WiMeCyt),所有文件都是相同的。看起来,对象文件的链接顺序正在发生变化,从而改变了HEX文件内容。我猜测链接顺序可能会受到正在发生的.CyPRJ的更改的影响。BTW:要么在目标硬件上编程的HEX文件工作正常,但如前所述,我必须为FDA重建相同的HEX文件。 以上来自于百度翻译 以下为原文 Just did a comparison of the Generated Sources directory (with WinMerge) and all files are identical. It looks like the link order of the object files is changing and thus changing the hex file contents. I'm guessing the link order may be affected by changes to the .cyprj that is occurring. BTW: either hex file that is programmed on the target hardware works properly, but as noted previously, it is imperative that I can rebuild identical hex files for the FDA. |
|
|
|
wkg_liusha 发表于 2018-12-19 21:11 实际上,我从头开始创建了一个新项目,执行了上述测试案例,无法重现失败。英特尔HEX文件是相同的。不确定这是否与这个问题有关,但是这个项目在几个月前从4升级到4.1。 以上来自于百度翻译 以下为原文 I actually created a new project from scratch and performed the above test case and could NOT reproduce the failure. The Intel hex files were identical. Not sure if this has anything to do with the issue, but the project in question was upgraded several months ago from 4.0 to 4.1 |
|
|
|
wkg_liusha 发表于 2018-12-19 21:29 地狱戴维, 看来这个问题是项目特定的。我在一个示例项目中尝试了相同的步骤,并获得了同样的HEX文件。 我们可能需要查看迁移的项目进行调试。您可以在这里共享或创建TigSuff案和共享,如果它是机密的。 谢谢 Jobin燃气轮机 以上来自于百度翻译 以下为原文 Hell David, It seems the issue is project specific. I tried the same steps in an example project and getting the HEX file same. We might need to have a look into the migrated project to debug. You can share here or create techsupport case and share, if it is confidential. Thanks Jobin GT |
|
|
|
只有小组成员才能发言,加入小组>>
757个成员聚集在这个小组
加入小组2134 浏览 1 评论
1874 浏览 1 评论
3697 浏览 1 评论
请问可以直接使用来自FX2LP固件的端点向主机FIFO写入数据吗?
1811 浏览 6 评论
1557 浏览 1 评论
CY8C4025LQI在程序中调用函数,通过示波器观察SCL引脚波形,无法将pin0.4(SCL)下拉是什么原因导致?
755浏览 2评论
CYUSB3065焊接到USB3.0 TYPE-B口的焊接触点就无法使用是什么原因导致的?
508浏览 2评论
CX3连接Camera修改分辨率之后,播放器无法播出camera的画面怎么解决?
469浏览 2评论
421浏览 2评论
使用stm32+cyw43438 wifi驱动whd,WHD驱动固件加载失败的原因?
1112浏览 2评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2025-2-2 01:55 , Processed in 0.737700 second(s), Total 54, Slave 49 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号