⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
8个帖子/ 0新
Last post
mkelwood
Offline
Last seen:6 days 15 hours ago
加入:2017-05-19 18:27
J-Link Hot Plug

We have noticed that our DA14585-based device will occasionally stop advertising. We have tried running the application on the debugger but it has not shown the issue with this configuration, so we are trying to hot plug the debug adapter after the device has stopped advertising. I have the CFG_DEVELOPMENT_DEBUG defined in da1458x_config_basic.h and I have followed the instructions located here:

http://www.keil.com/support/docs/3697.htm

However, the device still ends up at the reset vector after attach, and still appears to be reloading the image at attach. How do we execute a hot plug of the adapter without resetting the device?

设备:
PM_Dialog
Offline
Last seen:1小时35分钟前
Staff
加入:2018-02-08 11:03
Hi mkelwood,

Hi mkelwood,

Could you please clarify how you hot attach the debugger? From Keil or from JLink Commander? If you hot attach the debugger from Keil, the sysram_case23.ini script will be executed, the device will reset and the image will be loaded again.

Thanks, PM_Dialog

mkelwood
Offline
Last seen:6 days 15 hours ago
加入:2017-05-19 18:27
Thank you PM_Dialog. I

Thank you PM_Dialog. I am using the Keil uVision IDE for debugger attachment. I substituted an empty .ini as the initialization file and was able to hot attach the debugger. This appears to allow assembly-level debug only; there is no source-level debug function. But I can still set breakpoints in the disassembly window, view memory, examine state, etc so this is still quite useful.

Interestingly, it does not appear to matter whether the CFG_DEVELOPMENT_DEBUG is defined or not; the hot attach function appears to work the same in both cases.

Thank you for your help!

PM_Dialog
Offline
Last seen:1小时35分钟前
Staff
加入:2018-02-08 11:03
Hi mkelwood,

Hi mkelwood,

Could you please clarify what do you mean with the empty .ini file? You are not using the sysram_case23.ini script? If the CFG_DEVELOPMENT_DEBUG is undefined should not be able to attach the debugger. This definition either enables or disable the debugger. Are you able to hot attach the debugger without resetting the board?

Thanks, PM_Dialog

mkelwood
Offline
Last seen:6 days 15 hours ago
加入:2017-05-19 18:27
Hi PM_Dialog,

Hi PM_Dialog,

我基本上使用了sysram_case23.ini与注释的所有命令 - 见附件。使用此作为初始化文件(并清除在原始帖子中包含的链接I中所注明的设置)我能够热将调试器到运行系统,无论cfg_development_debug是否定义。系统不会重置,但我只能做汇编级调试(看起来没有符号信息,这是奇怪的)。

With CFG_DEVELOPMENT_DEBUG undefined, I hot attach and I can see from the Program Counter and the map file that I am executing inside of main (not at the reset vector). The contents of SYS_STAT_REG are 0xE5, indicating that PD_DEBUG is functional. From here I can single-step the assembly, set breakpoints in the assembly etc.

最诚挚的问候,
MKE

Attachment:
PM_Dialog
Offline
Last seen:1小时35分钟前
Staff
加入:2018-02-08 11:03
Hi mkelwood,

Hi mkelwood,

With the procedure that you have followed, you will not able to attach the source code, so it is expectable that you are able only to do assembly-level debugging. Please try to do the following procedure. I tried it into theble_app_bareboneexample of the SDK. In the SDK directory of you project, please make 2 copies of your project. So, you should have yourinitial project, onecopy and oneSIMULcopy of your project. Please check thesdk_folder.屏幕截图进入附件。原始项目将被使用,以便将固件下载到DA14580中,而不在调试选项卡中进行任何修改,只需下载二进制图像。这copy, will be used to attach the debugger without resetting you board, so please check thedebug_attach_1 / 2.screenshots from the attachments in order to do the same modifications. You should remove thesysram_case23.ini.在连接后,文件和解除重置选项。这SIMUL复制将用于模拟,并且您将能够找到源代码在不进行重置的情况下停止的位置。请检查一下debug_SIMUL图像,以便在该项目中执行正确的配置。在配置我所描述的配置之后,您应该以调试模式运行附加和SIMUL。请检查以下示例。在里面图像,你会看到代码停止进入0x07FC088Aaddress, so if you copy-paste this address intoSIMUL项目的PC, you will see the source code that the firmware stops. Please try to do this procedure, and let me know if is working. Be aware that I tested in my side and it is working. There are not any configurations needed in the sysram_case23.ini file, so use it as it is. Please let me know if you have any follow up questions or issues.

Thanks, PM_Dialog

Attachment:
mkelwood
Offline
Last seen:6 days 15 hours ago
加入:2017-05-19 18:27
你好pm_dialog,

你好pm_dialog,

这个方法使用项目仅仅是一起ly as an aid in translating the assembly-level view from the ATTACH project into a source-level view? That is, breakpoints/steps/data view will still need to be done at the assembly level in ATTACH, but the SIMUL workspace assists in relating the code addresses, data addresses etc. to the source code?

Of course this can also be done with a MAP file and the LST file, but I can see the utility of using SIMUL to facilitate this process.

我会尝试一下,让你知道。

MKE

PM_Dialog
Offline
Last seen:1小时35分钟前
Staff
加入:2018-02-08 11:03
Hi mkelwood,

minor-latin;mso-bidi-theme-font:minor-latin;background:white;mso-ansi-language:
EN-US">Himkelwood,

minor-latin;mso-bidi-theme-font:minor-latin;border:none windowtext 1.0pt;
mso-border-alt:none windowtext 0cm;padding:0cm;background:white;mso-ansi-language:
EN-US">Yes, exactly, the SIMUL project merely as an aid in translating the assembly-level view from the ATTACH project into a source-level view. Please try it and let me know.

minor-latin;mso-bidi-theme-font:minor-latin;border:none windowtext 1.0pt;
mso-border-alt:none windowtext 0cm;padding:0cm;background:white;mso-ansi-language:
EN-US">Thanks, PM_Dialog
mso-ascii-theme-font:minor-latin;mso-hansi-theme-font:minor-latin;mso-bidi-theme-font:
minor-latin;background:white;mso-ansi-language:EN-US">