完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我读过有关这个问题的每一篇文章。我得到了错误:我已经阅读了关于这个问题的每一个帖子。我得到的错误是:(944)SrC.Cudith.HEX和DALI-双BooLoad .x.Enguto.HiXi在地址0h之间的数据冲突,这是由于App和BooLoad链接器脚本中的内存重叠。更新链接器脚本,使应用程序内存远离BooTL。(944)在SRC生产.HEX和DALI-双BooLoad .x.Engutto.xOxTeX的地址8h之间的数据冲突,这与XC-1.30和上编译器处理所需默认中断的方式有关。解决这个问题的办法是进入App的属性XC16LS,检查无中断向量表选项,强制默认中断只在引导加载程序中。(最后一篇文章http://www. McCys.com /论坛/ FindPost / 985768)。当这不起作用时,我完全没有主意了。谁能告诉我这里发生了什么事?我已经附上了由MLA提供的原始链接器脚本和我所做的链接器脚本。侧注释:HEX TEAM将两个HEX文件结合在一起,但是一旦合并的HEX文件被编程到设备中,它就什么也不做了。最初我的计划是对应用程序编程,然后使用项目设置预先。服务内存范围,这样我就可以编程引导加载程序,而不是擦除应用程序。这工作,但当引导加载程序加载我的应用程序USB和I2C中断,但我的DALI网络工作意味着我的中断工作。
原AuthBLL.Link .txt(89.04 KB)-下载42次UpDeDeDayAppLIKL.TXT(89.05 KB)-下载38次升级后的ByLLILKL.TXT(88.82 KB)-下载47次 以上来自于百度翻译 以下为原文 I have read just about every post on this particular issue. I am getting the error: I have read just about every post on this particular issue. I am getting the error: (944) data conflict at address 0h between src.production.hex and DALI-DUAL-Bootloader.X.production.hex I realize this this is due to memory overlap in the app and bootloaders linker scripts. Updating the linker scripts so that the apps memory is sufficiently away from the bootloaders I get the error: (944) data conflict at address 8h between src.production.hex and DALI-DUAL-Bootloader.X.production.hex According to other posts this has to do with the way the XC-1.30 and up compilers handle a required default interrupt. The solution to this is to go into the app's properites, xc16-ls and check the No Interrupt Vector Table option forcing the default interrupt to be in the bootloader only. (last post here http://www.microchip.com/forums/FindPost/985768 ). When this does not work I am completely out of ideas. Can anyone tell me what is happening here? I have attached the original linker scripts provided by MLA and the linker scripts that I made. Side notes: Hex mate combines the two hex files fine, but once that combined hex file is programmed to the device, it does nothing. Originally my plan was to program the app, then using project settings preserve memory ranges so that I could program the bootloader and not erase the app. This works but when the bootloader loads my app USB and I2C breaks, but my DALI network works meaning my interrupts work. Attachment(s) original_app_linker.txt (89.04 KB) - downloaded 48 times original_bl_linker.txt (89.04 KB) - downloaded 42 times updated_app_linker.txt (89.05 KB) - downloaded 38 times updated_bl_linker.txt (88.82 KB) - downloaded 47 times |
|
相关推荐
2个回答
|
|
由于某种原因,我不能编辑原始帖子来说明这个问题已经解决了。我找到了一个解决方案,通过使用WiMeXo找到应用程序的MAP文件和Bootloader映射文件之间的差异。结果表明,仅仅因为在Bootloader链接器中移除IVT和IVT源,它们就消失了。我不得不删除Avit和IVT条目。
以上来自于百度翻译 以下为原文 For some reason I can not edit the original post to state that this has been solved. I figured out a solution by using winmerge to find the differences between the app's map file and the bootloaders map file. It turns out that just because you remove the IVT and IVT origins in the bootloader linker that they will be gone. I had to delete the aivt and ivt entries in the SECTIONS field as well. |
|
|
|
这是因为你的帖子包含了一个真实的URL。
以上来自于百度翻译 以下为原文 It is because your post contains a live URL. See: How to avoid errors when editing posts |
|
|
|
只有小组成员才能发言,加入小组>>
5282 浏览 9 评论
2054 浏览 8 评论
1967 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3228 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2275 浏览 5 评论
819浏览 1评论
708浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
651浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
708浏览 0评论
605浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2025-1-11 06:39 , Processed in 1.142686 second(s), Total 77, Slave 61 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号