Friday, November 24th 2017, 9:24pm UTC+1

You are not logged in.

  • Login
  • Register

AnCan

Beginner

Date of registration: Sep 26th 2017

Posts: 7

1

Thursday, September 28th 2017, 10:17am

J-Link + MKV58F1M0VLQ24 = Cpu did not halt.

I have problems to programming the MKV58F1M0VLQ24 (Cortex-M7) microcontroller with J-Link.
I did the various tests by selecting the device: MKV58F1M0xxx24 or MKV58F1M0xxx24 (allow security) but the result is always the same.

If I use J-Flash Lite, press ERASE button, after a few seconds I get the following:


If I use J-Link Commander, I can connect to the MKV58 without errors:


But if I try to reset the microcontroller, I get an error:

I have also tried to select other reset modes (RSetType) but the result is always the same.

The HALT and GO commands work fine, in fact, the CPU stops and then restarts without errors:


The ERASE command (from J-Link Commander), work fine and after the memory is erased:


If I send my file ".bin" to the CPU with the "loadfile" command I get this warning:

but in fact nothing has been loaded inside the CPU, in fact my program does not work.

Perhaps this problem can be caused by the protection to flash writing / reading?
So I use the "unLock Kinetis" command to unlock my cpu, and everything is done correctly:


If I send my file ".bin" to the CPU with the "loadfile" now the messages are:

Obviously the program has not been loaded into CPU memory, in fact it does not work.

I tried to program my CPU with other Debug Probe and everything worked fine so I do not think the problem is in my card.
If anyone has had experience of using J-Link with this kind of microprocessor and can give me some advice I'm grateful to.

Best regards
Andrea

AnCan

Beginner

Date of registration: Sep 26th 2017

Posts: 7

2

Friday, September 29th 2017, 3:28pm

Updated J-link software 6.20c

Today I downloaded and installed the new 6.20c software. I also updated the J-Link firmware.
I did the same tests but the result is always the same, so the 6.20c does not solve my problem.

Question:
Since in the release note of 6.20c it is written:
"Firmware: RISC-V: Under special circumstances, flash programming could
fail when checking IsHalted() state of CPU, before starting flash
programming. Fixed.
"
could it be a problem like this? Could it be a J-link firmware bug?

Regards
Andrea

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

3

Friday, September 29th 2017, 3:44pm

Hi Andrea,

No, this is most likely not a firmware issue.
RISC-V is a completely new architecture supported by J-Link.

I will give it try here and come back with the results.

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

AnCan

Beginner

Date of registration: Sep 26th 2017

Posts: 7

4

Monday, October 2nd 2017, 6:14pm

I'm waiting for your feedback

I will give it try here and come back with the results.
I did other attempts, but I can not communicate J-Link with this card.
please let me know news, otherwise I have no way to use J-Link.

Regards
Andrea.

AnCan

Beginner

Date of registration: Sep 26th 2017

Posts: 7

5

Wednesday, October 4th 2017, 8:43am

I will give it try here and come back with the results.
Please can you test so I can start learning how to use J-Link on my card?

Thanks
Andrea.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

6

Thursday, October 5th 2017, 12:30pm

Hi Andrea,


Sorry for the delay in response.
I could reproduce the issue with a Kinetis V58 device in a erased state.
This will be fixed in the next version of the J-Link software.

Do you want me to provide you with a preliminary version in the mean time?


Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

AnCan

Beginner

Date of registration: Sep 26th 2017

Posts: 7

7

Friday, October 6th 2017, 2:14pm

Do you want me to provide you with a preliminary version in the mean time?
Yes, I would be very happy to try the new version and see if it solves the defect.

Thanks
Andrea.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

8

Friday, October 6th 2017, 5:23pm

Hi Andrea,

J-Link Version 6.20e is available for Download:
https://www.segger.com/downloads/jlink/

Does it work for you?

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

AnCan

Beginner

Date of registration: Sep 26th 2017

Posts: 7

9

Monday, October 9th 2017, 9:45am

Test J-Link 6.20e

Does it work for you?
It works almost completely. I'll explain....

I tried the following tools:
  • J-Mem:works well with both SWD and JTAG.
  • J-Link SWO Viewer: works well with both SWD and JTAG.
  • J-Link GDB Server:works well with both SWD and JTAG.
  • J-Link Commander:works well with both SWD and JTAG.
  • J-Flash: with SWD interface works well. With JTAG interface, the TARGET -> TEST -> TEST SPEED
    it can read the ram and pass the test. Instead, if I run TARGET -> Manual programming -> Read Back Entire chip, I get this error:


  • J-Flash Lite: with SWD interface works well. With JTAG interface,the button ERASE CHIP generates these errors messages:


So I think there is still some small problem with J-Flash (normal and lite) using the JTAG interface.


Regards
Andrea.

This post has been edited 1 times, last edit by "AnCan" (Oct 9th 2017, 9:46am)


AnCan

Beginner

Date of registration: Sep 26th 2017

Posts: 7

10

Thursday, October 12th 2017, 9:16am

Does it work for you?
Hi Niklas,
Did you find the reason for the defect occurring on J-Flash in JTAG connection?

Regards
Andrea