J-Link + MKV58F1M0VLQ24 = Cpu did not halt.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • 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:
    [img]https://i.imgur.com/dVvCefV.png[/img]

    If I use J-Link Commander, I can connect to the MKV58 without errors:
    [img]https://i.imgur.com/IYVGUg0.png[/img]

    But if I try to reset the microcontroller, I get an error:
    [img]https://i.imgur.com/BiwkutI.png[/img]
    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:
    [img]https://i.imgur.com/5jD8J94.png[/img]

    The ERASE command (from J-Link Commander), work fine and after the memory is erased:
    [img]https://i.imgur.com/cNVolXy.png[/img]

    If I send my file ".bin" to the CPU with the "loadfile" command I get this warning:
    [img]https://i.imgur.com/3Rnct9c.png[/img]
    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:
    [img]https://i.imgur.com/eYsIHU2.png[/img]

    If I send my file ".bin" to the CPU with the "loadfile" now the messages are:
    [img]https://i.imgur.com/YBkvKl2.png[/img]
    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

  • 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

  • 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
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • 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
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Andrea,

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

    Does it work for you?

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Test J-Link 6.20e

    SEGGER - Niklas wrote:

    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:
    [img]https://i.imgur.com/Fx05QyJ.png[/img]

    • J-Flash Lite: with SWD interface works well. With JTAG interface,the button ERASE CHIP generates these errors messages:
    [img]https://i.imgur.com/ZvqpKK8.png[/img]

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

    Regards
    Andrea.

    The post was edited 1 time, last by AnCan ().