Jlink Failures

Comments

11 comments

  • Avatar
    Michael Johnson

    Not something I've seen what hardware are you using?

    0
    Comment actions Permalink
  • Avatar
    Mjscott

    Not sure which Hardware you are speaking of so:

    JLink Hardware - Ver 10.10, Manufactured 47-16 (WW-YY), latest Firmware. DLL is V 6.14b

    JLink Target settings: Current Speed - Adaptive, Enable Adaptive Clocking - No, Reset Type - Default, Show Log - Yes, Speed - Best Possible, Supply Power - No, Trace Buffer Size - 65536, Use Built-in Flash Loader - Yes, Verify Read Operations - Yes.

    CrossStudio 3.5 Hardware - ASUS, Laptop, I7, Windows 10. 8 gig RAM.

    I had been using my CrossConnect with this exact system for about 5 years without problem, but went to the JLink for better debugging of FreeRTOS applications.

    With this issue, when the Jlink is first connected it will program and verify with what looks like the Jlink flasher (a separate windows pops up). From that point forward if the debugger is stopped, code changed, and reprogramming attempted, it will never again program successfully, never again does the separate window appear. Everything has be either disconnected and software has to be exited and started all over again.

    Whatever this is it seems to have degraded over time, when it first appeared about 2 months ago 1 out of 3 attempts would fail. The debugging software could be stopped within CrossStudio and then restarted. The programming window would appear and all was good. But as of 3 weeks ago, that no longer works. Now everything has to be disconnected and all software has to be closed and restarted.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    Which ARM device? Try switching off the "Use Built-in Flash Loader".

    0
    Comment actions Permalink
  • Avatar
    Mjscott

    STM32F205VCT6,

    I turned off 'Use Built-in Flash Loader' and it is MUCH slower to program and verify, but it does not seem to hang. More testing is needed though.

    If my memory is correct to use Tracealyzer for FreeRTOS, which is a separate program outside CrossStudio, the two programs have to connect at the same time to the JLink. That will be the next hurdle, if we have solved the debugging problem.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    Is the j-link device set

    0
    Comment actions Permalink
  • Avatar
    Mjscott

    I don't understand the question.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    Open the j-link control panel when you are debugging and see what value the Device is set to.

    0
    Comment actions Permalink
  • Avatar
    Mjscott

    JLink control panel Device = STM32F205VC, little endian, 3.28V {green indicator}

    CrossStudio target properties window the Device Type is set to STM32F205xx,STM32F207xx,STM32F215xx,STM32F217xx

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    Looks okay - you could try changing the Target Reset Script project property to be TargetInterface.resetAndStop(1000) - this will use the j-link reset rather than the one in the STM32_target.js.

    0
    Comment actions Permalink
  • Avatar
    Mjscott

    Same error

    0
    Comment actions Permalink
  • Avatar
    Mjscott

    I'm not sure if this will help you or not. I hooked the JLink up to another project board, STM32L052C8 which is communication via SWD, and with the JLink setting as before (for STM32F205), i.e. Use Built-in Flash Loader set to No. It will not program the board, immediately getting a verify error. However if I set it to Yes, all is fine. It is able to program/debug time and time again using the JLink flasher.

    Got to fix this! It can't be that I have to reset the JLink properties for each type of board.

    0
    Comment actions Permalink

Please sign in to leave a comment.