Problems configuring J-Link with the peripheral_examples project

15 posts / 0 new
Last post
jteng7
Offline
Last seen:6 years 11 months ago
加入:2014-05-09 19:33
Problems configuring J-Link with the peripheral_examples project

Hi there,

我am having problems configuring the J-Link options in the peripheral_examples project.

After opening the peripheral_examples project via the "DA14580_peripheral_setup.uvproj" file, I tried to do the following:
1. Click on options for target...
2. Click on the Debug tab
3.在右边,我选择“使用J-LINK /J-TRACE Cortex"
4. When I click on "Settings", no window appears.

我tried this with both Keil v4 and Keil v5 but both result in the same issue.

我am using JLink version 4.84f.

Do you have any idea what could be wrong here?

Thanks for your help,
Jeff

AK_Dialog
Offline
Last seen:2 months 3 weeks ago
工作人员
加入:2013-12-16 15:49
Hi Jeff,

Hi Jeff,

Due to some differences between Keil IDE version 4 and version 5 there is a possibility that starting the debugger in Keil IDE V5 will crash when using a project file.
A couple of guidelines have been added in the following document : UM-B-014_DA14580_Development_Kit.pdf (see chapter 4.2)
This document (version 1.1) can be downloaded from this website :http://support.dialog-semiconductor.com/system/files/UM-B-014_DA14580_De....

Dialog Support Team.

hull39
Offline
Last seen:6 years 2 months ago
加入:2014-07-08 16:28
the document (v. 1.1) is

the document (v. 1.1) is missing

jteng7
Offline
Last seen:6 years 11 months ago
加入:2014-05-09 19:33
Hi there,

Hi there,

Thanks, but the updated steps in the documentation still does not fix the problem I am having.

AK_Dialog
Offline
Last seen:2 months 3 weeks ago
工作人员
加入:2013-12-16 15:49
Hi Jeff,

Hi Jeff,

我f the guidelines do not resolve your problem than there maybe an issue with the Keil/Segger tools itself. Since we are not in control of these tools you may try to search the Keil and/or Segger forums.

Dialog Support Team.

sentieri
Offline
Last seen:6 years 10 months ago
加入:2014-05-06 19:47
Any news about this issue? I

Any news about this issue? I followed a similar path before finding this post. I tried with keil 5.10 and 4.74. I tried with Segger 4.54d, 4.84f, 4.85e, and a few others. Could you please inform the exact version that are being used internally by DIalog?

pswitch
Offline
Last seen:6 years 10 months ago
加入:2014-05-20 08:20
Hi, I would like to provide

Hi, I would like to provide my solution to this issue..

Problem:
我had a similar issue trying to load up the Proximity example, where when I went to debug, and J-LINK / J-Trace Cortex was already selected, clicking Settings would make Keil uVision crash...
Solution:
As the Peripheral example/documentation states.. Click the Options for Target.. and then click the Device Tab, select ARM->ARM Cortex M00>ARMCM0 ... it is now fixed ... click back to Debug tab, you should notice JTAG is no longer select.. so select it again and Settings should work.. continue with the normal Port change to SW, etc etc..

我f this works for you:
You're Welcome

我f this did not work for you:
我am sorry.... Please explore similar fixes and request more assistance from Dialog..

>Chris

hull39
Offline
Last seen:6 years 2 months ago
加入:2014-07-08 16:28
我followed these steps

我followed these steps exactly and the IDE crashes when I select "J-Link/J-Trace Cortex" and press Settings in the Debug dialog.

我'm running uVision 5.11.1.0. The Device tab shows that the Software Pack is ARM.CMSIS.4.1.1

The UM-B-014 Development Kit document shows the software pack should be Keil.ARMCortex_DFP.0.0.1 but that's been deprecated in favor of ARM.CMSIS.4.1.1

Any ideas what might be going on?

Thanks,
Jon

JE_Dialog
Offline
Last seen:1 month 1 week ago
工作人员
加入:2013-12-05 14:02
Hi Jon, when you open up the

Hi Jon, when you open up the options tab, can you check to see if Keil has picked the right M0 ? It needs to be as below - but what you may find is that by default, it picks up an M0 under M4 ... not sure why... seems there is some confusion on part database .

我have this exact problem and this worked for me... as soon as i pushed it back to the ARMCM0 below and tried JLINK settings again, worked fine.

BR JE_Dialog.

hull39
Offline
Last seen:6 years 2 months ago
加入:2014-07-08 16:28
Thanks. on the suggestion of

Thanks. on the suggestion of one of my colleagues, I installed the "ARM Cortex-M Profile Device Support Template" fromhttp://www.keil.com/dd2/Pack/and that included Keil.ARMCortex_DFP.0.0.1 that fixed the problem.

Best regards,
Jon

DesignExt
Offline
Last seen:3 years 8 months ago
加入:2014-08-01 12:17
你好,

你好,
我had these Problem too and with that It has been solved. But I have other Problem now. I configured the right device, JTAG Settings,.. without problem but when I try Debug the project, it appears a message: "Error: Flash Download failed - Cortex-M0". I think that the problem is with the Flash Download program in the Settings but I can't found the right device in the list. What is the right configuration of Flash Download for DA14580?

Thank you very much,
Jvp

JE_Dialog
Offline
Last seen:1 month 1 week ago
工作人员
加入:2013-12-05 14:02
Hello Jvp, can you confirm

Hello Jvp, can you confirm that you have the use external tool for flash programming selected ?

BR JE_DIalog

DesignExt
Offline
Last seen:3 years 8 months ago
加入:2014-08-01 12:17
Hello,

Hello,

no I haven't selected this option.Because in the Documentation it doesn't say anything of that. Then I muss selected the "Use External Tool for Flash Programming" option and Should I add something in Programmig Algorithm (in Flash Download Tab)? Thanks

Jvp

MHv_Dialog
Offline
Last seen:2 months 6 days ago
工作人员
加入:2013-12-06 15:10
Hi DesignExt,

Hi DesignExt,

Please look at Appendix A in the UM-B-014 user guide. There is a description on how to change the projects file. This will solve your problem.

Marc
Offline
Last seen:5 years 5 months ago
加入:2014-11-14 09:17
Hi

Hi

我had the same issue with uVision 4.74 using smart tag reference design 3.20.6. The description in Appendix A of UM-B-14 (v 1.5, p. 34) solved my problem. It is important to add the lines directly before the line: < / TargetOption >. Right underneath the key < TargetOption > won't work..

Marc